yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pkgnex:
I suggest you try keeping the stock settings, except change ONLY the last number (empty_apps) to 160.

Having secondary_server and hidden_app levels so high, and content_provider lower than those (???) is contrary to every LMK strategy Google has ever released on Android. I know a lot of people have been jumping on this bandwagon in the last week, but in reality the jury is still out on whether it actually improves anything over just raising the empty_app level marginally.

Raising just the last number provides a little more overhead for launching big, or memory-intensive, apps more quickly without maliciously killing stuff in the background you may actually want (like the launcher, your keyboard, notifications, etc.). Keeping the numbers in-line with the stock strategy of linearly increasing numbers as you get further from the foreground app probably still makes sense, too. I think Google did it for a reason.
[Samsung Galaxy Nexus] Hetalk:
This is what I love about this thread, and loved about the old AK thread. More people coming in and giving technical views on how stuff works.

Awesome stuff. :good:

I'm back to learning. :)
[Samsung Galaxy Nexus] Culex316:
Goes to show how much (safely) undervolting regulatory voltages can really help out with battery life. I once set VUSIM below 1000 and my phone's screen just turned off and blank and I had to do a battery pull. Luckily, there was no data corruption.
[Samsung Galaxy Nexus] pkgnex:
Agreed - we're all still learning!

I've heard reports that some people have seen antutu scores increase by 500 points with the settings satjy had problems with, which seems like a lot, but only equates to about 4%. This is not much more than the benchmark "noise" you will find if you run it 10 times over a few days without rebooting.

Just my opinion... but if a change causes users' launchers to lag and re-draw, who cares about 500 antutu points?

I suppose different people have different priorities, and the fact that Android can meet so many of them with Dev customization is one of the things that makes it great! Trial and error also benefits us all.

That said, I really believe there really is no one best LMK setting that will make everyone happy. It is a continuum between free ram and the ability to hold stuff open in the background at various levels. It's chocolate vs vanilla. Every person should research how the low-memory killer in android works, consider their own personal usage patterns, and adjust the levels as (or even if) they see fit.

I can recommend completely different settings for 1). A multi-tasking, uber-powerful 3 GB tablet power-user vs. 2). An ocd, task-killing, recent apps and cache clearing, one-app-at-a-time personal phone jockey with 512 MB RAM that would make each of them a little happier than they might be with the stock LMK settings, but that would absolutely infuriate the other person!
[Samsung Galaxy Nexus] metalspring:
actually it is possible and has been done lol

https://github.com/bsmitty83/DirtyV_tuna/commit/619b6b35471c5f25aee941c8f0b266300d22dc8f
[Samsung Galaxy Nexus] audit2:
Hey Neph,

Where can I find these setting using trister?

I/O Scheduler Tunables

async_scale: 6

read_scale: 2

sync_scale: 3

write_scale: 2

I can locate I/O Scheduler Tunables but those settings are not displayed. Could they be worded differently?
[Samsung Galaxy Nexus] memaro_maro:
this setting only on donation version...
[Samsung Galaxy Nexus] Kaemo:
I don't know if this is a common issue, but if I don't touch the device within 10 seconds after a reboot, it will reboot again, for absolutely no reason.
[Samsung Galaxy Nexus] pattyboi:):
no bro,not to sound ignorant,but thats something on your end,mine if perfectly fine,just rebooted and let it sit without touch and its been fine. rom? kernel in use? last dmesg? ;D
[Samsung Galaxy Nexus] audit2:
Got it!! Thanks
[Samsung Galaxy Nexus] Nephilim:
Hey guys, due to a reference Hetalk brought up to me, if you are using my custom settings please switch the values of above_hispeed_delay and timer_rate so they are reversed.

Thanks. :)
[Samsung Galaxy Nexus] Kaemo:
Both Vanir and OMNI. It doesn't happen every time I reboot, though. I'd say 1/3.

But it's not a big deal at all. :) Probably my Trickster settings messing things up.
[Samsung Galaxy Nexus] pkgnex:
This happens on many kernels if you have content adaptive brightness set to "off". Referred to as the CAB Bug. Not sure if this is your issue, but it sounds like it. There are multiple work-arounds, but no fix.
[Samsung Galaxy Nexus] evilSuRGe:
Content Adaptive Brightness use to cause that before on other kernels. Mine is on and doesn't reboot.
[Samsung Galaxy Nexus] Nephilim:
I had that on a few roms back in the day, it comes from not allowing trickster to activate your set on boot settings before the screen goes off. It's quite random, some roms it happens on and some it doesn't. I've not had this problem on LiquidSmooth.

---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------

CAB never made a difference on that issue for me, honestly, even though alot of people claim CAB is no good. I have researched quite a bit on it and it's very good for battery life improvement.
[Samsung Galaxy Nexus] osm0sis:
I noticed AOKP works around the CAB bug by not allowing the screen to turn off for longer than usual on first boot.
[Samsung Galaxy Nexus] Nephilim:
OT, damn osm0sis, gettin' pretty close to that 10,000 thanks count. ;) :good:
[Samsung Galaxy Nexus] osm0sis:
Haha yeah it's pretty crazy! You're not too far behind buddy! ;)

Sort of annoying thing is most of my real high thanks count posts got overshadowed by the counts of some threads I inherited, so that 237 for the radios thread didn't actually contribute to my count at all. This was all pretty hard earned by helping people. :)
[Samsung Galaxy Nexus] memaro_maro:
learn a lot of thing from you. tq
[Samsung Galaxy Nexus] metalspring:
Damn that's a lot lol, I was just happy when my thanks passed my post count, but 10,000 is amazing, congrats
[Samsung Galaxy Nexus] metalspring:
hmm, I did my own build of SmittyV version with all kinds of config changes to remove all kinds of logging and surprise, surprise, it actually booted lmao

havent tested performance yet, but one thing that would definitely need added back for even basic debugging is logcat (yes, somehow i removed logcat completely lol)

maybe [MENTION=4222651]bsmitty23[/MENTION] could look through the config file to see if theres anything there he could also change in his config to hopefully improve performance some? Also if anyone would want to test it, and bsmitty allows it then you could message me for the test version
[Samsung Galaxy Nexus] ahmadairfan:
Dang you all lol XD will try your settings asap! :good:

Thats on 1750 mAh battery right are you kidding me :laugh::laugh:
[Samsung Galaxy Nexus] metalspring:
These didnt work on omni at all lol

Screen would freeze in less than a second, couldnt really get past the lockscreen and logcat filled up with errors and surfaceflinger warnings, good idea though, but either omni doesnt have all the commits needed or those settings wont work for some reason

Maybe [MENTION=3500210]tiny4579[/MENTION] could try them in one of his cm 11 builds?
[Samsung Galaxy Nexus] ahmadairfan:
Hey smith I did a search in the thread but nobody mention this.

https://www.dropbox.com/s/4na9r9qajcs61z3/DirtyV4.1-Linaro.zip the RAM is 741 MB, thought it was SR in the OP (?)

I dunno whether it is regular DirtyV or maybe you forgot the commit again just like in early days lol :D

Thanks! Been running it great :good:
[Samsung Galaxy Nexus] pianistaPL:
Uhh... I'm just installing 4.1 version on new AOKP Nightly... :P

Why didn't you tell this 5 minutes earlier? :D
[Samsung Galaxy Nexus] Vekhez:
Here goes nothing..

how does one add the new Wi-Fi Drivers [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Piti8576:
ROM: 4.4.2 TREX 30.01.2014

Kernel: DirtyV-SR Linaro v4.1 (with Nephilim's Settings)

Recovery: TWRP 2.6.3.2

Akku: Samsung Original 2000 mAh

WiFI always on, Data only 2G, GPS always on and in the car bluetooth on.

I use Nephilim's Settings but set CPU to 1200 max and GPU to 384 (with 512 freeze my phone).
[Samsung Galaxy Nexus] oubeichen:
I think it is dirtyV v4（ASRAM） with dynamic fsync option.

he might edit the wrong link by mistake
[Samsung Galaxy Nexus] redj12:
Nice stat buddy but you have a tractor battery :D

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
You tried it on the stock kernel or super ram version?

Link me those surfaceflinger logs
[Samsung Galaxy Nexus] büscher:
My phone also restarts itself if I don't use it after a boot.

I have CAB disabled through trickster (or is this the problem?)

also after such a dirty reboot my volume rocker does not work anymore I have to reboot again and if I miss it to use the phone it reboots once again and the rocker is messed up again :eek:

but no biggie ;)
[Samsung Galaxy Nexus] akash3656:
For some people they can't boot up properly with CAB disabled on boot. Maybe you're one of them?
[Samsung Galaxy Nexus] aosp:
Android Developers Blog: Process Stats: Understanding How Your App Uses RAM - http://goo.gl/WCzo3G
[Samsung Galaxy Nexus] Nephilim:
OT, who has a Toro+ and is serious about alpha/beta testing a rom thoroughly?? I need someone ASAP! Btw, no I am not building my own rom but this is important and strongly benificial to Toro+!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Haha yea I screwed up the links . dirtyV4.1 is bigmem . I added dfsync , and made it off at boot . sorry bout that confusion .

And the links are correct now
[Samsung Galaxy Nexus] fracama87:
Absolutely great! Finally something to see how apps (and which ones) stay in memory in background :) thanks

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pattyboi:):
gotta love when your testing something amazing and your battery decides to $h*T on you.. [MENTION=4608636]bsmitty83[/MENTION] ,that tester was going good. didnt have any issues at all man. you could defiantly feel the change. ;) but i may be gone a couple day since i dont have a dang battery :(
[Samsung Galaxy Nexus] b4u2:
Toro+ here. I will test.
[Samsung Galaxy Nexus] Ashtrix:
It's actually not CAB. It's coz of the screen settings I've asked bigeyes0x0 on the offical page, he replied that it's like that on trickster for now and maybe it i'll be like that only for our nexus. Luckily the SlimKat has proper screen off timing and keeping the settings in trickster to 15sec gives no restart :good: !!
[Samsung Galaxy Nexus] Nephilim:
Cool, I got your message on Hangouts so we'll go from there. :)
[Samsung Galaxy Nexus] bsmitty83:
Gonna have a couple new builds up for dirtyV and "-SR in a little bit . SR version should be at 765 but I won't know till its finished compiling . i added the ram oc from the commits [MENTION=2838735]aosp[/MENTION] linked . I havent noticed a huge gain in ramspeed , but ATM the effects don't seem negative so for now there in

Along with updated clean cache frontswap and zcache

I added a new governor too . adaptive .

Should have the links up in a little while
[Samsung Galaxy Nexus] aosp:
Using the SmittyV from the 29th no stack traces in my dmesgs so far ;)
[Samsung Galaxy Nexus] aosp:
Looking at all the memory reclaiming commits taking ram from the framebuffer and the tiler etc you should try my suggestions on the stock omni kernel with no bigmem or super ram action going on ;)
[Samsung Galaxy Nexus] Nephilim:
I'm not finding any info on Adaptive governor, any links?
[Samsung Galaxy Nexus] pattyboi:):
maybe its a smitty exclusive :eek:
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] you and [MENTION=4443334]Grarak[/MENTION] gotta collaborate on at least one build ;)
[Samsung Galaxy Nexus] Grarak:
No need for that

He can pick my commits I can pick his ones

That's the benefit of Open Source.
[Samsung Galaxy Nexus] aosp:
Well it would be awesome to say I flashed one that was built by [MENTION=4443334]Grarak[/MENTION] and [MENTION=4608636]bsmitty83[/MENTION] add [MENTION=3685904]ak[/MENTION] and I'll pay to flash this special limited edition :beer:
[Samsung Galaxy Nexus] bsmitty83:
From the kconfig

Adaptive

'adaptive' - This driver adds a dynamic cpufreq policy governor

designed for latency-sensitive workloads and also for demanding

performance.

This governor attempts to reduce the latency of clock increases so that the system is more responsive to interactive workloads in loweset steady-state but to reduce power consumption in middle operation level level up will be done in step by step to prohibit system from going to max operation level.

......allows you to get a full dynamic cpu frequency capable system by simply loading your cpufreq low-level hardware driver, using the 'adaptive' governor for latency-sensitive workloads and demanding performance.

Best I can do ,

Its not mine , I used it before on some of my other kernels . can't remember the origin .
[Samsung Galaxy Nexus] Sik-1:
No its been around for awhile now, its more built for Qualcomm devices based on its hotpluggin nature
[Samsung Galaxy Nexus] pattyboi:):
lol sarcasm broski :P
[Samsung Galaxy Nexus] sd3993:
How long till the builds are up? I only ask coz i gotta wake up early tomorrow and it's late here...i can be up fr another half hour max :)
[Samsung Galaxy Nexus] Nephilim:
I only ask because I want to flash a new goddamn kernel by smitty. :p
[Samsung Galaxy Nexus] sd3993:
Well that too :p
[Samsung Galaxy Nexus] bsmitty83:
Maybe an hour ,
[Samsung Galaxy Nexus] sd3993:
Okay. Gonna wait :)

Maybe throw in atleast one version? Please? :p
[Samsung Galaxy Nexus] redj12:
Ahah ! You are a junkie and you need your dose buddy ?
[Samsung Galaxy Nexus] sd3993:
You have no idea how difficult it is to sleep when you have a mindset to flash a kernel but it's not released yet :P
[Samsung Galaxy Nexus] aamadorj:
I think there are many junkies around... :D
[Samsung Galaxy Nexus] Nephilim:
WTF? If it's going to take that long this new version better have 2gb of available ram at 120% ramspeed increase!
[Samsung Galaxy Nexus] michierusama:
And when I just installed 4.1 lol. Ill be waiting ?
[Samsung Galaxy Nexus] oli20021978:
At least 20 hours screen on time

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
the two DirtyV kernels are up , links in the op

also the old versions are on devhost , for some reason my laptop wouldnt let me get my devhost untill i rebooted ,
[Samsung Galaxy Nexus] michierusama:
Thank you so mucho. ?
[Samsung Galaxy Nexus] TheMan0790:
I really wanted to make an Animal House "Ramming Speed!" joke here....

http://www.youtube.com/watch?v=odA_EVwVycU <- This is what I'm referring to....

---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------

Just as I finish downloading SR V5, the CM nightly for the GNex shows up....DAT TIMING!
[Samsung Galaxy Nexus] sd3993:
DFsync mussing again in non-sr version lol :p
[Samsung Galaxy Nexus] pianistaPL:
:crying:
[Samsung Galaxy Nexus] bsmitty83:
sorry bout that fixed it

DirtyV5.zip - 3.33 MB

link in the op is good too again :good:
[Samsung Galaxy Nexus] Nephilim:
Hmmm, only 766mb available ram, you are still missing 1034mb.....
[Samsung Galaxy Nexus] bsmitty83:
Lmao
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION]

https://github.com/Grarak/grakernel-tuna/compare/4bc1f97d24...cb15c89f65
[Samsung Galaxy Nexus] rtfpessoa:
Grarak just reverted those commits.
[Samsung Galaxy Nexus] midnightdevil66:
I'm loving this kernel with metal's omnirom on toro. Thanks for your work. Question on the touch wake option in trickster. How do I set it up so that a double tap wakes? I have the delay off and it seems that a single tap wakes it. What does the delay do?
[Samsung Galaxy Nexus] aosp:
For this ;)

omap2: lpddr2 ram overclock · cb15c89 · Grarak/grakernel-tuna · GitHub - http://goo.gl/B6jxsN
[Samsung Galaxy Nexus] rtfpessoa:
In fact i think there is nothing there about RAM OC, he reverted all commits till 5 hours ago.

EDIT: Just added it again.
[Samsung Galaxy Nexus] idkidk:
Hi [MENTION=4608636]bsmitty83[/MENTION],

Thank for you work! SRV5 kernel is awesome! But for my actual configuration touch wake make my phone unresponsive after unlock. Whithout touch wake phone unlock work correctly. Do you think to add bponury's PGM in future?

Thanks

Idk
[Samsung Galaxy Nexus] redj12:
You can't set double tap. You can just set touch to wake. That's all.

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] midnightdevil66:
Great, thanks.
[Samsung Galaxy Nexus] fracama87:
Double tap is another thing :) touchwake works with a single tap ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] midnightdevil66:
What does the delay do?

Via Toro Tapatalk
[Samsung Galaxy Nexus] pattyboi:):
delay is how long the digitizer will stay o after the screen is turned off. basically how long you have to wake the phone with touch wake,its used to save battery. basically setting a fixed interval of time that touchwake is allowed
[Samsung Galaxy Nexus] metalspring:
still waiting on this to get added to bsmitty's versions lol ;)

https://github.com/metalspring/DirtyV_tuna/commit/867c6e2dfdd3b3d5095d42bd5c4be39cae1d422d
[Samsung Galaxy Nexus] midnightdevil66:
Thanks for the explanation.

Via Toro Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
For me the delay breaks touchwake . I don't use it . whenever I set it I always set it and use the button anyways lol
[Samsung Galaxy Nexus] scarcry:
just flashed smitty's V5 SR and reapplied Neph's and [MENTION=3777325]wavedashdoc[/MENTION]'s Minfree settings. let's give this some time to see how stable and fast this still is (couldn't really see it getting any better but one can always hope :) )

Tapatalked from my maguro running Vanir nightlies + Dirty V SR Linaro kernel
[Samsung Galaxy Nexus] ashclepdia:
Just catching up on this thread, sorry if this was stated already, but before I also used to have the "hot reboot on boot complete" issue if I didn't unlock the device after it booted. This was caused by trickster itself. Trickster updated and fixed the issue. But it seems to have started again recently after a certain app update or around 4.4 release. I'm NOT certain if this is the cause NOW also, but it could be. I just always made sure to unlock after boot before screen timeout and it would be fine.
[Samsung Galaxy Nexus] Nephilim:
Tried out Adaptive, seems a little laggy even when I messed with the tunables. I'm now doing some more tweaks to Interactive governor tunables, hoping to increase performance a bit without killing any battery efficiency.
[Samsung Galaxy Nexus] sagara.sandaru:
Asked Touch Control developer for Dirty_V kernel support.. This is what he said
[Samsung Galaxy Nexus] michierusama:
Ill be waiting for those lol
[Samsung Galaxy Nexus] Nephilim:
I would stop using his app, rude developers do not deserve a userbase.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] sajty:
Thanks for your suggestions. Tried and no problems so far.

Sent from my GN
[Samsung Galaxy Nexus] cmoG530:
I didn't really find that to be rude at all. Remember, interpretations are different when text is involved instead of voices and faces and thus, people may sound different ways unintentionally to different folk. If he's focusing his time on changing his app for the better, then what he said was understandable. I say to the OP, give him a bit to finish his work and check back later. We don't know how much he has to do, xda wise and life wise. Just don't be so quick to jump the gun.
[Samsung Galaxy Nexus] adoboyo:
Just thought I'd share my battery stats from last night and this morning! Running 1/30 build of Commotio (Vanir) with ART and V4. This was on WiFi doing the usual texting, Chrome, Instagram, Facebook, some games, etc.. I'd like to think it isn't bad :silly:

Running westwood, 896 rab, sioplus, 180 min, 1200 max, 350 max screen off, 180 min screen on and ondemandplus. Didn't mess with voltages or anything else. I'm still messing around with the minfree settings. Also this is a toro with an aftermarket battery (EC TECHNOLOGY 2300mAH).

Any suggestions on switching some settings besides voltages?
[Samsung Galaxy Nexus] Sik-1:
How comes there's no smittyV5?
[Samsung Galaxy Nexus] bsmitty83:
Just haven't had a sec to build it lol
[Samsung Galaxy Nexus] adoboyo:
I always get confused when I see that option in Trickster with how it's worded. Do I turn Adaptive Brightness off or on for better battery life? :p

sent from my gnex!
[Samsung Galaxy Nexus] Nephilim:
I was referring to adaptive governor. As for Content Adaptive Brightness, I've researched it and it is better for battery to keep it on.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
OK no problem, I'll wait for that and since your personal build would you mind throwing in intelli-demand for my testing purposes ?
[Samsung Galaxy Nexus] bsmitty83:
I've been trying to , but some code dosent like intellidemand , I haven't been able to get it to build yet .. If I do I'll include it tho
[Samsung Galaxy Nexus] redj12:
OT [MENTION=3234943]adoboyo[/MENTION] Dude can you share your theme please ?

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] Grarak:
you need two pages for intellidemand

https://github.com/Grarak/grakernel-tuna/commits/grakernel?page=10

https://github.com/Grarak/grakernel-tuna/commits/grakernel?page=8
[Samsung Galaxy Nexus] pattyboi:):
its DHO'S vanir build,or commotio as he calls it :)
[Samsung Galaxy Nexus] NeverSeparate:
Dude this thread moves so fast...Smitty the kernel has been solid for me. Still using v2. Great job. Just downloaded v5. Thanks for your efforts.
[Samsung Galaxy Nexus] adoboyo:
Oh haha :p well thank you very much for all your research and what you've done for the community!

Yup! Just flash the ROM, it's awesome and my personal favorite. I used his builds in JB and it was always the best running. Didn't know he was building KK until yesterday :p

To give an update, I put my phone to charge at 2% and got 4 hrs screen time and a time on battery 19hrs 14min. I missed with minfree settings a lot of that remaining time.

sent from my gnex!
[Samsung Galaxy Nexus] Sik-1:
Cool thanks for trying man
[Samsung Galaxy Nexus] michierusama:
Threads moves fast when there's a lot of communication with the devs /users and disposition too.
[Samsung Galaxy Nexus] pkgnex:
Glad to have helped.
[Samsung Galaxy Nexus] adoboyo:
It's great. It's keeping the gnex alive. Not sure if I really need to upgrade anymore.

Sorry if this would be the wrong thread for this but I've been using Yahoo! Weather and it's a little laggy. It's super pic intensive but awesome and "pretty". Would changing minfree values make it smoother or is that something that would require messing with the kernel settings? I understand it could just be the app because it is pic intensive but it seems like we can use that app as a benchmark :p

sent from my gnex!
[Samsung Galaxy Nexus] michierusama:
I won't upgrade anytime soon. Im ok with my Gnex.
[Samsung Galaxy Nexus] fracama87:
No changing minfrees doesn't solve lags. That's for ram ;) you could try different governor or scheduler or probably it's app ralated...

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] memaro_maro:
hope that in next build, i can have saberMod toolchain from dirty-v kernel. seem much more friendly wt my current setting and rom after compared wt linaro. ?
[Samsung Galaxy Nexus] Swede2008:
Would love to see a kernel of this quality on the original nexus 7 :D
[Samsung Galaxy Nexus] milojoseph:
Is this kernel compatible with 4.3.1 some 4.4 kernels work on some 4.3.1 phones. wondering did anyone try it on this.
[Samsung Galaxy Nexus] dereaper:
I've installed it on 4.2 so it should be, its in any kernel format for just try and see how it runs . if it doesn't work just install your old kernel back
[Samsung Galaxy Nexus] milojoseph:
cool cool. I herd this is a very good kernel.
[Samsung Galaxy Nexus] ashclepdia:
you KNOW a kernel dev is doing SOMETHING right when people start asking for similar on a DIFFERENT DEVICE hahahaha

:D