yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] krneki10:
Could you please examine my battery life, I don't think it's really good. I didn't know which screenshots are the most important, so I've uploaded all of them:

I've also attached all logs from betterbatterystats.

Thanks!:)
[Samsung Galaxy Nexus] vfmmeo:
Try disabling force fast charge if it's enabled.
[Samsung Galaxy Nexus] wisefreakz:
[MENTION=2838735]aosp[/MENTION] maybe Vanir ROM do miss this commit as well...
[Samsung Galaxy Nexus] jhonnyx:
[MENTION=4286189]krneki10[/MENTION]

Same battery life here. I Think that's the best battery life for stock battery for Kitkat.
[Samsung Galaxy Nexus] imjustafq:
reboot your baby :)

via my neighbour's forehead
[Samsung Galaxy Nexus] bsmitty83:
Anybody besides [MENTION=4278473]Hetalk[/MENTION] try this so I can continue building ? , I need to know if anyone is having deep sleep issues before I move forward .
[Samsung Galaxy Nexus] jhonnyx:
dl'ing & testing
[Samsung Galaxy Nexus] BestBrd:
You have built a dirtyv version with those commits?Could you please upload it??
[Samsung Galaxy Nexus] osm0sis:
Probably not useful unless Smitty adds the extra fuse for GPU so that it has more than 2 steps. Right now it's 153-Max, where max is either 307, 384 or 512.

I know Franco made 512 stable for everyone by hardcoding some voltages in CORE, then added it as an extra step, so his can actually go 153-384-512. If Smitty went that route then faux's governor could be really interesting to try. :)

Smitty's got it committed, he'd just need to copy over the updated /sbin and /res files from the full ramdisk directory. If you really need one I can make it later today. Just let me know.

Ahh they added multi-sim back. Let the "CM breaks sh*t" games begin again. ;)

Hell yeah. I need to get around to opening a thread for it. So lazy though.. :p

Bro.. You need to be taking that to the BetterBatteryStats thread. This is a kernel development thread. :)
[Samsung Galaxy Nexus] ASHURiCAN:
Kernel doesn't work with last CM nightly ...

"Envoyé depuis mon Galaxy Nexus avec Tapatalk"
[Samsung Galaxy Nexus] David 617:
See here - http://xdaforums.com/showthread.php?p=50810390
[Samsung Galaxy Nexus] aaron13:
Yes deep sleep issue in dirtyv R 03_02_14

And a root issue (see log)
[Samsung Galaxy Nexus] jhonnyx:
I'm testing Antutu, Quadrant, 3DMark, anything else?
[Samsung Galaxy Nexus] osm0sis:
Y'all be trippin'. There is no deep sleep issue in DirtyV-RSR.3.2.14. My device slept 9h last night. 20min awake.

[MENTION=2088054]jhonnyx[/MENTION] Smitty just needs it verified that the deep sleep issue is still present in Test1 so he can keep looking for the source of the problem.

My phone's dead and charging or I'd do it myself. Working on the updated ramdisk since CM broke sh*t (per usual) now. :)
[Samsung Galaxy Nexus] bsmitty83:
Can you try that 3.3 any kernel test zip I put up . since you know for sure you were getting sleep on 3.2 . I reverted some things to test and I need someone to confirm since my phone isn't on me
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4544860]osm0sis[/MENTION]

Is your version of DirtyV-03.02 working on the newest CM? I don't know if it has Ramdisk or this is AnyKernel version :)
[Samsung Galaxy Nexus] jhonnyx:
I can confirm there is no deep sleep on the phone after flashing the test zip after letting the phone rest for about 20 minutes without usage.
[Samsung Galaxy Nexus] SoftWord:
All version of this kernel, is very laggy for me

Fancy it's ok, franco 396 optimized give me 12036 of score leaving all defaults, 1228mhz of oc.

Why on my phone is so laggy ?

I'v used CM11 and slimkat.
[Samsung Galaxy Nexus] osm0sis:
Once it's up to 20% I'll give it a go. :good:
[Samsung Galaxy Nexus] Tubra:
dirtyv R 03_03_14 produces deep sleep issue, takes a while to wake up. No undervolting at all anywhere. This version seems to be laggy/buggy
[Samsung Galaxy Nexus] dbt816:
I'm having the same issue today. No change in voltage from stock values either.
[Samsung Galaxy Nexus] gohamstergo:
this got buried quick. maybe it got missed. ping [MENTION=4608636]bsmitty83[/MENTION] [MENTION=2538253]bponury[/MENTION].
[Samsung Galaxy Nexus] bsmitty83:
I know that the released 3.3 is causing issues, but I need to know if what I reverted fixed the issues or not .

I could care less about adding things or any other issue until deep sleep is resolved . so flash 3.3 test zip and let me now if it reaches sleep or not :thumbup:
[Samsung Galaxy Nexus] gohamstergo:
roger, will help test deep sleep. :)
[Samsung Galaxy Nexus] aaron13:
[MENTION=346208]smitty[/MENTION] have you seen this root issue?
[Samsung Galaxy Nexus] osm0sis:
As far as I can see, there is no issue in that log. Be more specific?

---------- Post added at 03:03 PM ---------- Previous post was at 02:59 PM ----------

Pac is back? Dayumm time to dig out all the old 4.3 ramdisk fixes. :p
[Samsung Galaxy Nexus] aaron13:
I meant the line : "returning to read only" in the log.

Today I had to reboot and restore the root privileges in cwm.
[Samsung Galaxy Nexus] osm0sis:
All not root issues. KK moved some things around in Settings, that log message is evidence of that and shouldn't be anything to worry about.

Then, that CWM message is because root doesn't work the same way in KK as it did in JB; su permissions don't matter anymore, only the daemon running on boot. Please read the Notes/Issues in the OP of my CWM thread for more on that.

Thanks for hunting around in the logs though! That's what we need more of around here. :)
[Samsung Galaxy Nexus] aaron13:
Thank you to Osmo, catlog works very fine :thumbup:
[Samsung Galaxy Nexus] aosp:
If you can bro please so I can link it in the VanirAOSP thread ;)
[Samsung Galaxy Nexus] osm0sis:
Did Vanir break some sh*t too?

I'm already running comparisons on the latest CM and PAC-Man.. Guess I'll throw Vanir in too. :rolleyes: ;)
[Samsung Galaxy Nexus] aosp:
Nope its just missing the voodoo
[Samsung Galaxy Nexus] osm0sis:
Ah okay.. you too much of an AnyKernel purist to use the bundled ramdisk versions? :p

Once I'm done with my comparisons I'll whip up a zip for you.
[Samsung Galaxy Nexus] aosp:
You think ?
[Samsung Galaxy Nexus] pattyboi:):
its not a dirtyv kernel,its my version of askp
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] I was surprised that only flashing the nomem zImage on VanirAOSP made the device get so funky I thought VanirAOSP already included all the voodoo one could voodoo with but you proved me wrong hopefully I can share the secrets with the team so no magic canada is required in the future ;)
[Samsung Galaxy Nexus] TheMan0790:
Grrr...I want to stay on the build from March 3 because it works so well, but the clock not working well (or at all sometimes) convinced me to go back to the March 2 build. And yes, I did reboot my phone, which was posted as a fix some pages ago...

Break me off a piece of that KitKat ROM!
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] The wasted ram zImages work fine oddly enough with no voodoo needed ?
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=2838735]aosp[/MENTION], [MENTION=4544860]osm0sis[/MENTION] ,ANYONE

try this out , its anykernel so flash over dirtyv ramdisk if need be

if you get sleep with this one , i got it down to 3 possible reasons

see attached
[Samsung Galaxy Nexus] poo706:
[MENTION=4671369]paarthdesai[/MENTION], this is for you too... Pretty sure the last kernel that still worked with touch control is DirtyV-R-2.25.14. That's what I'm using and TC works.

[poo]
[Samsung Galaxy Nexus] namtombout:
It sleeps. I'm on linaro pa
[Samsung Galaxy Nexus] bsmitty83:
Thank you bro , I'll have another out shortly to narrow it down further .

Your this kernels savior :beer:
[Samsung Galaxy Nexus] aosp:
I flashed it but forgot that stock vanir and nomem don't mix like a fool so now I wait on [MENTION=4544860]osm0sis[/MENTION] to let me know what ingredients vanir is missing ?
[Samsung Galaxy Nexus] buhohitr:
Confirmed, deep sleep is working, My opinion this rom is slightly quicker than the previous version.
[Samsung Galaxy Nexus] jhonnyx:
+1 @PA 4.1
[Samsung Galaxy Nexus] osm0sis:
Vanir's ramdisk isn't very different from CM's. Not sure what the problem would be... Couple tunable differences (which actually originate with boype I think) and shouldn't pose a problem:

write /proc/sys/kernel/sched_latency_ns 4000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 1600000

write /dev/cpuctl/apps/bg_non_interactive/cpu.shares 91
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_runtime_us 400000
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_period_us 1000000

[MENTION=4608636]bsmitty83[/MENTION] do we want to try them too? I have no idea how that sched sh*t works, so it'd be blind testing other people's tweaks. ;)

Also some (unnecessary extra) perms settings for CAB and scheduler, their "oh sh*t" button, and minor unimportant things. They had UKSM stuff, which I did add to ours for the hell of it even though it shouldn't be necessary.

Edit: Hmm there's this:

restorecon /sys/class/rfkill/rfkill0/state

restorecon /sys/class/rfkill/rfkill0/type

Perhaps the issue? Seems to be more Bluetooth related though..
[Samsung Galaxy Nexus] aosp:
So maybe nomem requires osmods to run now?
[Samsung Galaxy Nexus] osm0sis:
Nopers. Also makes no sense, unless you didn't revert your media_profiles.xml, that'd f*ck some sh*t up for Camera, since that happens in the ramdisk scripts.

Hey can you point me to a nice pure AOSP ROM recent nightly I can pull the latest charger binary from? I might as well update all the things.
[Samsung Galaxy Nexus] qu4nd:
Sleeping on SlimKat...
[Samsung Galaxy Nexus] Nephilim:
Smitty, I just gotta chime in real quick, I'm still having major issues with 2/28 SmittyV reaching deep sleep perfectly and having the best battery life out of all the DirtyV kernels I've used so far, it's really a big issue. Another problem I have been encountering is extra amazing performance and speed. Also, SmittyV 2/28 sucks at not being the smoothest kernel I've used in forever.

Please, do something about these issues.
[Samsung Galaxy Nexus] pianistaPL:
Sorry bro, it seems this is utopia :(
[Samsung Galaxy Nexus] bsmitty83:
ok heres one more

let me know if it sleeps , especially if you flashed test2 so you know if what to expect
[Samsung Galaxy Nexus] jhonnyx:
TestV3 Sleeps on PA 4.1 Beta
[Samsung Galaxy Nexus] p34rp34r:
Wow, are you sure about min screen on 1200? I think you might be better off using Neph's settings and tweaking some of the values like target_load and go_high_speed to get the gov to ramp up CPU faster if you want that extra performance.

You have over 3 hours wakelock from your email...something is going on there. I'm sure that if that wasn't keeping your phone awake, it'd be a lot better.
[Samsung Galaxy Nexus] GilGameshn1:
Will check gladly ... Sorry that I can't help sooner.

Sent From My GNex
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4544860]osm0sis[/MENTION] I figured it out all I had to do for NoMeM to play nice with stock VanirAOSP was edit and use one script in /system/etc/init.d

https://www.dropbox.com/s/yztzqhxvrdgasmr/00dvbootscript

#!/system/xbin/busybox sh

# portions from franciscofranco, ak, boype & osm0sis + Franco's Dev Team

# lmk tweaks for fewer empty background processes

minfree=6144,8192,12288,16384,24576,40960;

lmk=/sys/module/lowmemorykiller/parameters/minfree;

minboot=`cat $lmk`;

while sleep 1; do

if [ `cat $lmk` != $minboot ]; then

[ `cat $lmk` != $minfree ] && echo $minfree > $lmk || exit;

fi;

done&

# wait for systemui and increase its priority

while sleep 1; do

if [ `pidof com.android.systemui` ]; then

systemui=`pidof com.android.systemui`;

renice -18 $systemui;

echo -17 > /proc/$systemui/oom_adj;

chmod 100 /proc/$systemui/oom_adj;

exit;

fi;

done&

# lmk whitelist for common launchers and increase launcher priority

list="com.android.launcher com.google.android.googlequicksearchbox org.adw.launcher org.adwfreak.launcher net.alamoapps.launcher com.anddoes.launcher com.android.lmt com.chrislacy.actionlauncher.pro com.cyanogenmod.trebuchet com.gau.go.launcherex com.gtp.nextlauncher com.miui.mihome2 com.mobint.hololauncher com.mobint.hololauncher.hd com.qihoo360.launcher com.teslacoilsw.launcher com.tsf.shell org.zeam";

while sleep 60; do

for class in $list; do

if [ `pgrep $class | head -n 1` ]; then

launcher=`pgrep $class`;

echo -17 > /proc/$launcher/oom_adj;

chmod 100 /proc/$launcher/oom_adj;

renice -18 $launcher;

fi;

done;

exit;

done&

Now bring on the AnyKernel's with those dirty zImage's ;)
[Samsung Galaxy Nexus] buhohitr:
deep sleep stills working, but when I boot up I have full screen mode without any back/home/recent buttons available, I'm running Liquid smooth.
[Samsung Galaxy Nexus] aosp:
Sleeping as in a coma? Then Yes!
[Samsung Galaxy Nexus] GilGameshn1:
V2 +1 V3 +1 on OmniMetal

Sent From My GNex
[Samsung Galaxy Nexus] buhohitr:
what rom are you using? I'm running Liquidsmooth and when boot up I have full screen without any of the back/home/recent buttons available??wtf?
[Samsung Galaxy Nexus] GilGameshn1:
Did you reboot after that .

Sent From My GNex
[Samsung Galaxy Nexus] osm0sis:
Haha yeah, if you want to "add the magic back" then sure, but NoMem shouldn't not "play nice" without it, so I'm still not sure what you mean.

Also, most busybox binaries don't include the sh extension. Stericson's definitely doesn't. :good:
[Samsung Galaxy Nexus] buhohitr:
Yes 3 times still same issue!

edit: let me wipe cache/davil and reflash see if that help..
[Samsung Galaxy Nexus] GilGameshn1:
As you know I am on omnimetal ... But I use this route to check the test :

Flash [MENTION=4544860]osm0sis[/MENTION] anykernel/synapsed 2.0 / 3.2 --> flash testv2 --> flash testv3 ... I am OK .

Sent From My GNex
[Samsung Galaxy Nexus] buhohitr:
I already have synapsed installed ->flash testv2 -OK, flash testv3 -> **** hit the fan -> wipe cache/davik cache -reflash testv3 -> back to normal. Thanks
[Samsung Galaxy Nexus] milojoseph:
SYNAPSE AND TRICKSTER DO NOT PLAY WELL TOGETHER...... Do not i repeat do not make trickster & synapse reboot with your kernel profile. Disable one (which i did with trickster), Unistall synapse, reboot your device..... install synapse and than click the check mark AFTER you insert your values, Reboot again. the heat thing should not appear. Visa verse when you disable synapse and keep trickster.
[Samsung Galaxy Nexus] osm0sis:
Using more than one tweaking app WILL cause your device to burst into flames.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] to make your life a little easier, I've got a pull request incoming for all the ramdisk fixes. :good: :)
[Samsung Galaxy Nexus] aosp:
Think you meant AnyKernel?
[Samsung Galaxy Nexus] bsmitty83:
Sweet I changed the bootclass path but I'll revert that if it conflicts .
[Samsung Galaxy Nexus] osm0sis:
Also AnyKernel2 updates adding the latest Synapse fixes. :highfive::good:

"ramdisk + AnyKernel2: latest updates/fixes"

Should be fine, mine will just probably reorder it or something since I put them in the order CM and PAC had them. :cool:

Edit: Request sent. :)
[Samsung Galaxy Nexus] malybru:
Mod Edit

Thread cleaned.

Please stay on topic in this Development Thread

Thank you

malybru

Forum Moderator
[Samsung Galaxy Nexus] aosp:
You should start a thread called osModMyRamdisk ;)

[MENTION=4608636]bsmitty83[/MENTION] Who called the cops?
[Samsung Galaxy Nexus] metalspring:
What was cleaned? I thought everything lately was on topic for the most part?
[Samsung Galaxy Nexus] osm0sis:
Just an amusing tangent about what happens when you use more than one tweaking app. :p
[Samsung Galaxy Nexus] DR3W5K1:
Is there a section I'm missing to toggle eco mode in Synapse? Could just be the build I'm on doesn't support it (Osmosis 3.2)? If not no big deal can configure it with script.

---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------

Btw it's not on just wanted to try it out.
[Samsung Galaxy Nexus] osm0sis:
Intelliplug was never added to mainline DirtyV, it was just in metalspring's test builds. :)

And until we can decipher AndreiLux's cryptic clues, we can't add conditional controls...

;):p
[Samsung Galaxy Nexus] DR3W5K1:
A script to make more scripts sounds confusing
[Samsung Galaxy Nexus] Kaemo:
we need to go deeper
[Samsung Galaxy Nexus] metalspring:
Intelliplug doesn't work well on the gnex yet (even though faux ported it over), it causes bug messages in dmesg and definitely does not play well at all with early suspend governors so it's not a good idea to add it anyway...

If [MENTION=4608636]bsmitty83[/MENTION] decides against early suspend interactive may I at least suggest adding intelliactive governor or imoseyons interactivex governor?

(I haven't tried interactivex yet but it should work fine and intelliactive does need a little tweaking to work well, which grarak and the vanir kernel have in source)
[Samsung Galaxy Nexus] osm0sis:
Bahahahah! In-script-tion! :laugh:

Made me laugh with my own voice. Amazing sir. Well played! :p

---------- Post added at 09:56 PM ---------- Previous post was at 09:47 PM ----------

I gotta say... I'm pretty damn excited for tonight's Dirty builds, guys. Sounds like Smitty has killed the deep sleep problem with burning fiery fire! :D
[Samsung Galaxy Nexus] bsmitty83:
OP UPDATED 3/4

DIRTYV -- AMBIEN EDITION

fixed deepsleep issue - thx testers and testes

Updated ramdisk by [MENTION=4544860]osm0sis[/MENTION]

Early suspend is included for now , I've been playing around with my phone and it unlocks a hair slower but for now its included .

Thanks for all the feed back testing the latest kernels as always its very necessary for improvements
[Samsung Galaxy Nexus] Nephilim:
Good to hear, lemme know when you decide to do one without early suspend or when interactive doesn't have wake lag with it. I prefer to keep my settings so I'll keep enjoying SmittyV 2/28 for the time being. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] oman0123:
Maybe in crazy but I'm not seeing it yet. My thumb hurts from pushing the refresh button

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Kaemo:
What DirtyV, specifically? SR? SRS?
[Samsung Galaxy Nexus] milojoseph:
ironic cause im using your settings in the early suspend.......................... lml weird... really weird and it works well.
[Samsung Galaxy Nexus] bsmitty83:
Im working on a fix atm broski , you know theres a reason i kept it ;)

Lol try now . I forgot to save the edit

All 3 kernels in the op
[Samsung Galaxy Nexus] Nephilim:
So your telling me with my exact settings you have instant wake when hitting the power button? I mean literally nothing changed at all, 230mhz max screen-off?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Kaemo:
I'm sorry, I thought you meant you only updated one of them. ;)
[Samsung Galaxy Nexus] bsmitty83:
I

Its noticeable to me but not as bad as my old interactive lol , I might have fixed it already
[Samsung Galaxy Nexus] Nephilim:
I'll give it a try. Worst case scenario I jump back to 2/28. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Gotta love peer pressure lol , itll still be slow on 3/4 but I'm working on it .
[Samsung Galaxy Nexus] milojoseph:
yes actually my settings is 180mhz screen off 230 was too much for me screenshot are on the way.
[Samsung Galaxy Nexus] wisefreakz:
I'm a bit slow in some aspects guys so help me out here.

Latest 3/4 still no honey with VanirROM.

Do we still need [MENTION=4544860]osm0sis[/MENTION] voodoo?
[Samsung Galaxy Nexus] Nephilim:
Yea, wake lag still blows ass but it's not quite as bad as 3/3 so I'll bear with it for the time being. I'm curious to see if battery life improves enough with early suspend to even warrant keeping it. I only say this because 2/28 has such great idle drain. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
I believe early suspend is slightly configurable right in the code (I think this was specifically to help any wake up lag)

cpufreq_gov_lcd_status_interactive = 0;

/*

* During passive use-cases, i.e. when display is OFF,

* value of timer, which is used for frequency increasing,

* may be increased. This will significantly reduce the amount

* of OPP switching during passive use-cases.

*/

stored_timer_rate = timer_rate;

timer_rate = DEFAULT_TIMER_RATE * 10;

I'm not entirely sure how that could be tuned to be more responsive so I never messed with it lol, maybe someone who knows more can chime in?
[Samsung Galaxy Nexus] milojoseph:
Yesssssssssssssss suspend works.... do you need me to record..... to prove to you its everything.
[Samsung Galaxy Nexus] bsmitty83:
Yea push it (timer rate)to thirty its what I did a little while ago , seems to help I'll add it next build
[Samsung Galaxy Nexus] midnightdevil66:
Smittyv 3/4 running and sleeping like a champ.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] milojoseph:
I hope im proving myself that early suspend is the gateway to other battery saving mods...... and slight minor performance. lml i really made a video but i think i had to fun doing it :(
[Samsung Galaxy Nexus] osm0sis:
It takes a real man to thank his testes. :laugh:

Just remember, "The Ambien Walrus told me to do it!" WILL hold up in court. :silly:

230 MHz is too low for max screen off. For race-to-idle you're better off having it at 525 MHz so it can complete the waking tasks more quickly and get back to nappytime as soon as possible. :)

3/3 never went to sleep so it didn't technically have wake lag. ;)
[Samsung Galaxy Nexus] gummie:
So they finally managed to convince you on adding that precious "early suspend" of theirs. LoL. Trying this out "for now" too.
[Samsung Galaxy Nexus] Nephilim:
Even with max screen-off at 700mhz it still lags terribly. I never has a single issue with wake lag on 230mhz max screen-off for any smitty/dirty kernels besides the two smitty made and the one metalspring made that had early suspend.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] YoungDaddy:
how can you get to this
[Samsung Galaxy Nexus] metalspring:
I usually have mine set to min of 180, with a max screen off of 700 (this seems to help with playing music while screen off so it isn't choppy or lagging). Also, low CPU speeds aren't everything, if a task finishes quicker at a higher CPU speed then your phone can enter deep sleep sooner, but if a low CPU speed makes a task take longer to finish then you'll end up using more battery since it's less deep sleep time
[Samsung Galaxy Nexus] milojoseph:
I just proved that 180 mhz is perfect for me

I feel bad we need to get this guy back his kernel that works.

Thank you maybe i should show off again
[Samsung Galaxy Nexus] bsmitty83:
Its hardcoded into the kernel , I changed it , compiled , flashed . tested ,repeated , lol
[Samsung Galaxy Nexus] bsmitty83:
I do see the lag so hopefully I can correct it because its one thing I always liked about the kernel was how damn fast everything was , wakeup included
[Samsung Galaxy Nexus] wisefreakz:
Really guys... I wanna try 3/4... VanirROM does not like it... What should I do?
[Samsung Galaxy Nexus] bsmitty83:
Not sure what the deal is , its osm0sis' updated ramdisk , supposed to cure all the bootclasspath issues
[Samsung Galaxy Nexus] osm0sis:
You need to explain what "does not like" means. I found nothing in Vanir's ramdisk today that should be a problem, in fact I added most of it to ours.
[Samsung Galaxy Nexus] dbt816:
I had all kinds of problems with Vanir and 3/4 today, mostly phone and acore crashing to the point where the error popup rendered the phone useless :)
[Samsung Galaxy Nexus] wisefreakz:
OK... Here it goes... After I flash 3/4 phone reboots normally... When it reaches to phone screen I FC to com.process.phone which turns the phone unusable.