yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
Test build is running absolutely perfect. It now has slimrecents, only thing I don't like about them is that when you open recents while in an app it doesn't show the app you are in, which sucks because I am one of those anal people that likes to clear all apps right when I am done with them unless I actually need to multitask.

Either way, I feel you guys should be expecting a 3/5 build sometime today when rkpeterson gets to it. :)
[Samsung Galaxy Nexus] rchristy:
+1, always lost Wifi password after flash. Always use TB to restore the wifi password. It happens in recent DirtyVs. Was fine before.

Sometime, the UICC read issue makes APN lost. When trying create new APN but the MCC/MNC was not in the setup. Have to reboot to get APN setup back and cellular data working.
[Samsung Galaxy Nexus] marcocsh:
Try the Gravity app maybe?
[Samsung Galaxy Nexus] pmbabu:
It is already ready.. go go go folks!

http://www.drdevs.com/devs/teamliquid/Nightly/Galaxy Nexus gsm/LS-KK-v3.0-2014-03-05-maguro.zip
[Samsung Galaxy Nexus] Nephilim:
Same here, Wifi hand off is perfect. Never had a problem on any build with it though.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Godra:
[MENTION=4608636]bsmitty83[/MENTION] What about UKSM? [MENTION=2838735]aosp[/MENTION] said its only draining battery and not actually improving performances but as I can see it's still on by default. I'm on latest DirtyV version
[Samsung Galaxy Nexus] pvkiniyan95:
Guys try adaptive governor...its smooth...at least for me
[Samsung Galaxy Nexus] vfmmeo:
You mean this?

Maybe. But it's too much sensor-stuff related. I mean, if i swipe (or double-tap), the screen turns on. No more, no less. Using sensors could be less accurate.
[Samsung Galaxy Nexus] Nephilim:
I tested Adaptive when Smitty first added it and found that it was had inferior performance compared to Interactive, I'm glad it works well for you though. :D
[Samsung Galaxy Nexus] Charmacas:
I am back to "cwm-DirtyV-RSR-3.2.14-Synapsed.zip".

I don't know what is causing the new kernel from the 4th to be slower but it's definitely there. Now where I am back to the old version I am feeling it. :)

[MENTION=4608636]bsmitty83[/MENTION] if we should test builds... I am ready! ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Really? the new 3/4 SmittyV is killing it for me, performance and battery are great and benchmarks are between 12800 and 13100. After bumping max screen-off to 525mhz and letting the device settle for the night wake lag is barely noticeable as well.
[Samsung Galaxy Nexus] Charmacas:
Try the mentioned version with the same settings and you will also feel the difference I think. It's especially in daily tasks as opening, closing and switching apps.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] shag_on_e:
Wow! bsmitty88 you really freaking nailed it this time on the 3-4 Dirty SR. The last batch 3-3 all three were causing strange behavior closing apps automatically and such, but this is dreamy. I'm oozing with RAM, battery is wonderful, touch response is instant, and multitasking is great. This has finally taken over from Fancy 44 test2 ext.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] sdzbwxp:
I too hoping touch control support will come back soon. I flashed osmosis fix 3.4.it's running great and battery life is very impressive. Early suspend may played role.
[Samsung Galaxy Nexus] osm0sis:
It's both. CM added MSIM support back in and it requires changes to the ramdisk. My fixed version is the only one here that works:
[Samsung Galaxy Nexus] aosp:
I'm telling you guys I got hundreds of apps installed no joke but I flashed the latest VanirAOSP maguro nightly

http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/maguro/vanir_maguro_4.4.2.030514.zip

Then flashed the latest NoMeM zImage only

https://www.dropbox.com/s/lm9154zz6lj19s8/SmittyV-zImage-NoMeM-3.4.14.zip

Then deleted the below files from VanirAOSP

rm -f /system/etc/init.d/00firsties

rm -f /system/etc/init.d/01ksm

rm -f /system/etc/init.d/06ENTROPY

rm -f /system/etc/init.d/09cron

rm -f /system/etc/init.d/98SONIC_SHOCK

rm -f /system/etc/init.d/99vanir

rm -f /system/etc/init.d/ZZafterboot

rm -f /system/etc/sysctl.conf

rm -f /system/etc/vanir.cfg

rm -f /system/lib/hw/power.tuna.so

rm -f /system/xbin/CB_RunHaveged

rm -f /system/xbin/haveged

rm -f /system/xbin/vanir

rm -f /system/xbin/vanircheckcpu

rm -f /system/xbin/vanirentropy

rm -f /system/xbin/vanirflash

rm -f /system/xbin/vanirinteractivegovernorgovernor

rm -f /system/xbin/vanirnice

rm -f /system/xbin/vanirtweakapply

rm -f /storage/emulated/0/vanir.cfg

Wiped /cache/dalvik-cache /data/dalvik-cache before booting let it settle for at least ten minutes rebooted again and have had no issues at all to report just silky smooth all stock [MENTION=4608636]bsmitty83[/MENTION] ridiculous dude ;)
[Samsung Galaxy Nexus] aaron13:
I couldn't get gps working in smitttys nomemory 4-3.

Also an mtu error and floatservice problem (see logs(

Can someone explain what's wrong?
[Samsung Galaxy Nexus] cmoG530:
Your kernel is working great with the latest Vanir and even on stock settings, the smoothness and speed is pretty freaking sweet. I think I'll keep it stock for a while. Thanks! :)
[Samsung Galaxy Nexus] aosp:
Pastebin the contents from the audit.log please /data/misc/audit/audit.log
[Samsung Galaxy Nexus] Nephilim:
I've gotten almost the same thing twice since I woke up this morning. I'm at work so I jumped back to 2/28 so I'm glad you were able to post a log. :D

I only noticed the second time because of Trickstermods set on boot notification.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Unzitron:
Where are ksmg messages located?
[Samsung Galaxy Nexus] osm0sis:
Nada.

u0_a108@maguro:/ $ su
root@maguro:/ # cat /data/misc/audit/audit.log
sh: cat: /data/misc/audit/audit.log: No such file or directory
1|root@maguro:/ #

Directory's empty, even.
[Samsung Galaxy Nexus] poo706:
If anyone's interested, I made a flashable zip for the 2/25 zImage, i.e. no ramdisk. That way you can have the latest nightly of your favorite ROM, DirtyV (albeit a slightly older version), and touch control support. Working great for me on Vanir 3/5.

[poo]

---------- Post added at 03:18 PM ---------- Previous post was at 03:05 PM ----------

What's the purpose of removing all these Vanir files? Should I be doing this on Vanir 3/5 with DirtyV 2/25 zImage?

[poo]
[Samsung Galaxy Nexus] osm0sis:
It's just to make sure Vanir doesn't interfere with the kernel defaults. Basically to ensure you're getting the experience Smitty intended.
[Samsung Galaxy Nexus] poo706:
So nothing I need to worry about if I'm using Trickster to apply neph's settings?

[poo]
[Samsung Galaxy Nexus] Spoderman:
Hello guys, im here to give a little feedback.

I'm using ShinyRom, stock 4.4.2, flash'ed it, flashed root, booted up, everything was nice and dandy.

Decided to install this kernel, the latest one with SR, and everything is good, smooth as crystal water.

But (oh noes),

but, i've noticed that everytime my wifi is on, (not downloading, just connect to my internet), the slide animations for the notification bar drop to like 15fps, as soon as i disable wifi, boom, back to 60, turn it back on, boom, back to being slugish.

Maybe it's just a 4.4.2 thing? But it didn't happen on the stock kernel for this rom.

Anyway, because i don't use wifi as much as 3G and it only happens on the notification bar, i don't really care.

Just a heads up.
[Samsung Galaxy Nexus] büscher:
had some more time to test smittyV 3/4 and I find alot of these in my dmesg (don't know what they mean but I didn't see these on previous builds, at least not the second one)

<6>[ 912.130523] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND
<4>[ 912.130767] link down if wlan0 may call cfg80211_disconnected. event : 6, reason=7 from XX:XX:XX:XX:XX:XX
<6>[ 912.132293] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK
<6>[ 912.135833] cfg80211: Calling CRDA to update world regulatory domain
<4>[ 912.594390] wl_bss_connect_done succeeded with XX:XX:XX:XX:XX:XX
<6>[ 912.630126] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[ 912.638793] wl_bss_connect_done succeeded with XX:XX:XX:XX:XX:XX
<3>[ 912.714996] init: untracked pid 4269 exited
<4>[ 912.755615] net_ratelimit: 5 callbacks suppressed
<4>[ 912.755706] dhd_pno_get_for_batch : wifi location service is not supported
<4>[ 912.755889] failed to getting batching results
<4>[ 912.757446] dhd_pno_stop_for_batch : wifi

<7>[ 958.952453] PM: Entering mem sleep
<3>[ 958.965270] pm_op(): platform_pm_suspend+0x0/0x5c returns -16
<3>[ 958.965637] PM: Device alarm failed to suspend: error -16
<3>[ 958.965972] PM: Some devices failed to suspend
<6>[ 958.968353] PM: resume of devices complete after 1.800 msecs
<7>[ 958.970642] PM: Finishing wakeup.
<4>[ 958.971221] Restarting tasks ... done.
<6>[ 959.008026] PM: suspend exit 2014-03-05 20:32:27.550573671 UTC

Failed to suspend leads me to battery drain....?

and the one above may another clue to my wifi issue? (didn't use my phone alot, wanted to test idle battery life)

lulz edit: http://xdaforums.com/galaxy-nexus/development/kernel-ak-t1883298/page2535

[MENTION=3685904]ak[/MENTION] : do you remember something here? did you ever find any solution for this?
[Samsung Galaxy Nexus] GilGameshn1:
Had something like that in dmsg here and there and I have a drain feeling also . matter of inner feelings . :D

Sent From My GNex
[Samsung Galaxy Nexus] bsmitty83:
Selinux is pretty far behind so I'm working on it ,

[ 339.393981] SysRq : Emergency Remount R/O

[ 339.407897] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)

[ 339.460357] EXT4-fs (mmcblk0p12): re-mounted. Opts: (null)

[ 339.469512] Emergency Remount complete

[ 339.495452] DSSCOMP: dsscomp_early_suspend

[ 339.515075] DSSCOMP: blanked screen

[ 339.517425] [MODEM_IF] xmm6260_off()

[ 339.773223] Disabling non-boot CPUs ...

[ 339.775451] CPU1: shutdown

[ 339.783416] Restarting system with command

First I'm seeing of this , thanks for the log .
[Samsung Galaxy Nexus] pvkiniyan95:
G+ app has lot of lags with this kernel or is that only me
[Samsung Galaxy Nexus] gohamstergo:
very unlikely the kernel is the cause of one app's issue. try clearing app data, rebooting, etc.
[Samsung Galaxy Nexus] TheMan0790:
Oh man, Dirty V RSR with Liquid Smooth is unreal! Did not think my phone could get any faster...on a side note, this is the first custom ROM other than CM that I have ever been on for my phone.
[Samsung Galaxy Nexus] cmoG530:
Not here. Actually, it's pretty darn slick and buttery as is with everything on Vanir 3-5 and the latest DirtyV Osmosis.
[Samsung Galaxy Nexus] cujo6801:
Same here.

Sent from the "DOG" pound
[Samsung Galaxy Nexus] wisefreakz:
+1 ... Vanir 3-05 + Latest DirtyV

Damn buttery...
[Samsung Galaxy Nexus] aosp:
What they said ↑ ?
[Samsung Galaxy Nexus] aosp:
Hey do any of you know if this kernel runs awesome on VanirAOSP? ?
[Samsung Galaxy Nexus] cujo6801:
Link and I'll find out... :what:

Sent from the "DOG" pound
[Samsung Galaxy Nexus] wisefreakz:
Oh yeah.... :beer: lmfKo
[Samsung Galaxy Nexus] 47th_Ronin:
I heard that this kernel is being tested by NASA on behalf of an ancient alien civilization who seem to be tired of recurring issues on their personal communication devices and want something that's always evolving and cutting edge...

But you didn't here that from me ok?

Warning!

This statement is not officially endorsed by NASA or any of it's affiliates, any similarities with past or future official statements are purely coincidental and will be refuted openly and publicly.

And dammit we mean it.

Sent from my Galaxy Nexus using "borrowed" alien technology and stuff
[Samsung Galaxy Nexus] Royal King:
Sorry for off topic, but is Vanir more towards stock or similar like liquid? (customization and all) :confused:
[Samsung Galaxy Nexus] wisefreakz:
I would say yes! Vanir has also lots of customizations tough.
[Samsung Galaxy Nexus] cmoG530:
I was going to basically compare and contrast between the two, but God knows it would've started a war. So, just try Vanir out for yourself and see. You won't be dissapointed. :)
[Samsung Galaxy Nexus] bsmitty83:
OP updated SmittyV-R-NoMeM

updated ramdisk , more on my github , mostly stealth commits :silly:

[MENTION=4544860]osm0sis[/MENTION]

SElinux dmsg is just a log as the kernel is set to boot permissive , so dont think it was that , but i reverted a commit that might have caused a failure to reset error in your log ,

[MENTION=2853378]Nephilim[/MENTION]

I think the "wakelag" is from early suspend having to actually do a cycle because the only time it delays is when i rapidly screen off then back on
[Samsung Galaxy Nexus] wisefreakz:
Flashing....

Edit: Booted superb on 3-05 Vanir.... No lags... Buttery as a BUTTER!!!

Let's see battery....
[Samsung Galaxy Nexus] Nephilim:
After ramping max screen-off to 525mhz and giving 3/4 time to settle I barely noticed the lag, I only went back to 2/28 because I was at work and kept getting reboots. I'll test 3/5 right now. :)

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 10:59 PM ---------- Previous post was at 10:41 PM ----------

*UPDATE 3/5 is running great, no noticeable wake lag at all!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Noticing a bit of wake lag here. Going to play with some settings to see if I can get around it.
[Samsung Galaxy Nexus] Nephilim:
3/4 gave me slight wake lag with my settings but 3/5 has none for me. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
Testing it. I will report back more later.

So far after the flash it feels faster again. Loading and switching applications seem to be fast again.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Yea, 3/5 SmittyV has the smoothest performance yet.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] winamp26:
why i cant turn on smart reflex control on smitty 5/3?
[Samsung Galaxy Nexus] osm0sis:
Yeah I'm talking 3.5.14.. :(
[Samsung Galaxy Nexus] cujo6801:
Because he has them off in his personal build...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] garyngkt:
CM11 4/3 & 5/3 does not work well with DirtyV, keep on getting phone process error. So the last good build was 3/3. Maybe time to change ROM? :laugh:
[Samsung Galaxy Nexus] Nephilim:
CM11 is a piece of crap.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gohamstergo:
id definitely recommend ROMs other than plain CM11. Search around, there's tons of ROMs that run as good, or better and with more features.

such a diplomatic answer :P
[Samsung Galaxy Nexus] garyngkt:
Thanks guys. Leave the crap soon I shall :silly:
[Samsung Galaxy Nexus] osm0sis:
It'll work with my fixed 3.4.14 ones and today's SmittyV 3.5.14, as has been discussed a few times. They just needed a ramdisk fix for MSIM. And it's not just CM, guys; even your beloved Vanir has MSIM and the same problems with the 3.4.14 builds in the OP. :p ;)

Go here: http://v.ht/osmod

[MENTION=4608636]bsmitty83[/MENTION] what version of BFQ are you using?

http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php

v7r2 is out as of mid-February?! I seem to recall v6 being much smoother than v5 but at the trade off of some stability. This makes me pretty hopeful for v7. :)

Edit: I checked and see we're still on v5 - gogogo! :D
[Samsung Galaxy Nexus] qu4nd:
I've just had a strange graphic glitch at first boot after flashing 3-05 SmittyV build. It was like the google logo got blurred. A few seconds later the phone rebooted again and everything seems to work...
[Samsung Galaxy Nexus] gummie:
I suggest to keep the bad mouthing to your selves. CM Team has gone this far porting Android to Android even on legacy devices. I'm no fan boy, its just that I thought that you of all people know better not to judge developers works. Anyway CM got its own ramdisk opts so pulling a couple of commits from I think [MENTION=4544860]osm0sis[/MENTION] introduced that fix.

Edit: Oh the man himself beat me to it.
[Samsung Galaxy Nexus] gohamstergo:
I know you didn't quote me, but I'll defend myself anyway ;) All I meant by my recommendation is that, while CM is great work, I wouldn't run the plain ROM just because 1. It doesn't have the features that all the cherry pick ROMs have and 2. It doesn't have the little device-specific fixes that Gnex devs tend to add in (if we're talking about the automated CM Nightlies). It's a good base though. See my sig :P
[Samsung Galaxy Nexus] gohamstergo:
We better be careful. We're gonna get another mod edit for being OT :|
[Samsung Galaxy Nexus] mangusZen:
Without CM, you would be resident in some crappy apple forum. And XDA probably would't exist.
[Samsung Galaxy Nexus] Grarak:
CM wouldn't exist without XDA*
[Samsung Galaxy Nexus] cmoG530:
The issue comes from the fact that, just because some of you don't like specific things, it does not mean that others won't. CM is still arguably one of, if not THE most used ROM to date. Add that, with the fact that CM is so heavily relied on by many devs. Instead of saying something sucks, it'd be more productive to ask what the said user was asking for in a ROM and then direct him from there, because believe it or not, some people actually love stock based ROMs. No, I'm no fan boy and I myself do not use CM, but I am still very grateful for their work. Without them, my Nexus would suck.

End of OT
[Samsung Galaxy Nexus] Charmacas:
Report: Today's SmittyV does run smooth. Tested it a few hours now and can say: Great work [MENTION=4608636]bsmitty83[/MENTION]!

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] pianistaPL:
Many ROMs are based on this crap or have a lot of commits ;)
[Samsung Galaxy Nexus] TheMan0790:
Gentlemen, you can't fight in here. This is the war room!

XOOM XOOM!
[Samsung Galaxy Nexus] bsmitty83:
I'm using your ramdisk from your devhost , so the multi sim fix is present in 3.5 .

I'm still using bfqv5. But I don't ever use bfq or cfq anyways , they are more for spinning disks
[Samsung Galaxy Nexus] büscher:
bfq is not even present in your smittyV builds, zen is great btw!

also your latest 3/5 runs good so far! no issues detected while using it since 8 hours now.

One thing I noticed is a launcher or systemUI restart, I think because of oom, not sure tough. Didn't have this on SR Builds
[Samsung Galaxy Nexus] Punkiderma:
Here all fine with latest smittyV.

Sometimes I have microlags, but nothing serious.

With your latest nomem releases I'm really starting to understand what "is better to manage less memory well, than have a lot of memory with bad managing" means: As of now, NEVER had a launcher redraw, gravity screen and lux always remains in memory, what app, messenger etc. Sync well.

This, with the standard amount of ram.

Thanks, great work!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] poo706:
So I'm not sure if I missed this at some point in the thousands of posts to this thread, but [MENTION=4608636]bsmitty83[/MENTION], what is the situation with touch control? Please don't get me wrong, I'm not asking for an ETA. Just wondering if we knew what it was that broke touch control after 2/25, or if investigation is required, or if we needed an update of the module from the touch control dev. Thanks.

[poo]
[Samsung Galaxy Nexus] GilGameshn1:
Thank you ... Smoothest ... Can't resist to use it as daily driver -----> SmittyV

Sent From My GNex
[Samsung Galaxy Nexus] DevVorteX:
I thought this was because it's using smart reflex version v3 or something. Metalspring mentioned it here: http://xdaforums.com/showpost.php?p=50314433&postcount=3212

I don't know if this is still relevant for the smittyV builds, but I assumed it was.
[Samsung Galaxy Nexus] Shambola:
By now latest release runs fine for me too!!!
[Samsung Galaxy Nexus] wisefreakz:
[MENTION=4608636]bsmitty83[/MENTION] got a wake delay with latest 3-05

This was in dmesg:

<4>[ 1905.481323] Disabling non-boot CPUs ...

<6>[ 1905.481811] tf_device_suspend

<6>[ 1905.481994] tf_power_management(1)

<6>[ 1905.482147] tf_power_management(c099916c): succeeded (not started)

<6>[ 1905.482482] Resume caused by IRQ 163, gpio_keys

<6>[ 1905.482482] Resume caused by IRQ 177, nfc_irq

<3>[ 1905.482482] Successfully put all powerdomains to target state

<6>[ 1905.482574] Suspended for 8.277 seconds

<6>[ 1905.482910] tf_power_management(3)

<6>[ 1905.483215] tf_power_management(c099916c): succeeded (not started)

<6>[ 1905.485137] PM: early resume of devices complete after 1.617 msecs

<6>[ 1905.620483] PM: resume of devices complete after 134.307 msecs

<7>[ 1905.621551] PM: Finishing wakeup.

<4>[ 1905.621856] Restarting tasks ...

<3>[ 1905.622863] hub 1-0:1.0: activate --> -22

<4>[ 1905.645874] done.

<6>[ 1905.646728] PM: suspend exit 2014-03-06 14:20:53.104394685 UTC

<4>[ 1906.106781] dhd_set_suspend: Remove extra suspend setting

<6>[ 1906.477752] DSSCOMP: dsscomp_late_resume

<3>[ 1906.477996] omapdss DISPC error: SYNC_LOST, disabling LCD

<3>[ 1906.478118] omapdss DISPC error: First SYNC_LOST.. ignoring

<4>[ 1907.563201] CPU1: Booted secondary processor

<6>[ 1907.563598] Switched to NOHz mode on CPU #1

<4>[ 1907.564514] Interactive - Screen ON Hot-plug!

Its all as expected?
[Samsung Galaxy Nexus] aosp:
staging: android: lowmemorykiller: Management of not killable processes · 004b561 · bsmitty83/DirtyV_tuna · GitHub - http://goo.gl/2JKCEd

staging: android: lowmemorykiller: Management of not killable processes

This feature allows the user to define processes and system processes

white-lists filled with the preferred process names and to not be killed

by lowmemorykiller, unless it is absolutely necessary.

This feature exposes four new lowmemorykiller parameters:

- donotkill_proc, is the flag to enable / disable this feature for the

processes chosen by the user

- donotkill_sysproc, is the flag to enable / disable this feature for the

system processes chosen by the user

- donotkill_proc_names, is the list of process names (comma separated)

chosen by the user to be preserved from killing

- donotkill_sysproc_names, is the list of user system process names (comma separated)

chosen by the user to be preserved from killing

When a the lowmemorykiller needs to free ram, it will first kill the processes

not included inside the two process name lists chosen by the user.

If there are no more standard killable processes, then it will be necessary to

kill one of the processes included inside one of the two white-lists, to

prevent system hangs, slowdowns, etc.

chown system.system /sys/module/lowmemorykiller/parameters/*

chmod 0666 /sys/module/lowmemorykiller/parameters/*

[APP][ROOT][4.0+] Performance Control - Open Source

http://xdaforums.com/showthread.php?t=2444376

[MENTION=4544860]osm0sis[/MENTION] ;)
[Samsung Galaxy Nexus] gohamstergo:
The forbidden topic! D: haha

Back on page 557:
[Samsung Galaxy Nexus] Nephilim:
No overnight reboots on 3/5 and wake has a split second at most of wake lag on occasion. Best SmittyV yet.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
Deep sleep has been solved, hasn't it?

[poo]
[Samsung Galaxy Nexus] dbt816:
I'll second that! :good:
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=2838735]aosp[/MENTION] that not killable process is already present in most of the ROMs, omnimetal has it too...I've been using it for phone and launcher

[MENTION=346208]smitty[/MENTION] its been a long time since I used nomem versions and 5/3 is really gr8 but takes some more time to settle after boot
[Samsung Galaxy Nexus] gohamstergo:
As far as I can tell.
[Samsung Galaxy Nexus] aosp:
No apps locked in memory for me with hundreds of apps installed LMK gives me no issues and VanirAOSP boots and settles very quickly on NoMeM but different strokes for different folk ;)