yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sarkar1990:
The Vanir has settings built in. Why not just set up those? In settings, Brightness and then adjust.

Does Lux have any more advantages over this method?
[Samsung Galaxy Nexus] szucsgf:
Lux (and Velis, another similar app mentioned earlier) automatically adjusts your screen brightness depending on your surroundings. It will brighten your screen if you're outdoors and dim it when you go inside, for example. It's similar to the Autobrightness feature built into android (in the location you mention) I find Autobrightness in general keeps the screen too dim and flickers too much. With lux I have a brighter automatically adjusted screen and a useful persistent notification to tweak it on the fly if needed.

Velis is free, lux's free version is full featured (that's what I use).

Maguro | Vanir 4.002 03/04 nightly | AK Cylon 728
[Samsung Galaxy Nexus] infinit22:
Used op settings and got this yesterday. All on 4g
[Samsung Galaxy Nexus] androo45:
Your explanation doesn't cover rush-to-idle. It can do the same workload faster on 1.2Ghz and thus be faster back to idle (350MHz)than on 1036/920MHz. So technically it doens't save 56% of power but a bit less. But still, great explanation!

I don't run at 1036MHz max because the performance hit is too noticable (only so much a dual Cortex A9 can handle :( )

I run max 1.4GHz interactive with hispeed_freq and the touch input boost to 729MHz, and the go to hispeed at 90. This way the processor will use mostly 729 and 1036MHz when doing light stuff, but will ramp up to 1.4GHz when it needs to. At the end of the day it has only spent a couple minutes in 1.4GHz but much longer (30+ min) in 729 and 1036.
[Samsung Galaxy Nexus] szucsgf:
Great point! Another user made a similar comment and I might have misunderstood that time. If so I apologize.

Luckily frequency is just the inverse of period, which is the amount of time it takes to complete one operation. So I'm pretty sure I can quantify the effect of taking longer to get to idle. If I can I'll update. Thank you for helping.

Maguro | Vanir 4.002 03/04 nightly | AK Cylon 728
[Samsung Galaxy Nexus] Charmacas:
AW: Efficient Underclocking

I tried your settings nearly the whole week now. But I have to say that it's not nearly that smooth like the following setting. It I don't think that it makes such a big difference in battery draining. I will test this now.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] szucsgf:
Thanks so much for the feedback! Between keeping min CPU at 230 and overclocking to 1350 in not surprised its smoother than my settings.

How's battery life with your faster settings?

Maguro | Vanir 4.002 03/04 nightly | AK Cylon 728
[Samsung Galaxy Nexus] Charmacas:
AW: Efficient Underclocking

As I said I am going to test this. ;)

I read somewhere that keeping it at 230 does prevent the wakeup lag. And so I always kept it there and it works. ;)

Also I read that 1,4 GHz is the normal speed for the CPU. Google keeps it always at 1,2 GHz for some reasons. But they use another kernel with another configuration. So for us it might be better to use the normal speed of the CPU.

It would be cool if someone else could also test these settings. I am using AK Pirate 704 for this because it's the most stable for me.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] szucsgf:
Manufacturers often do that. A processor is more stable at lower frequencies. Our processor is probably officially rated at e.g. 1400 but Samsung probably underclocked it by default for greater stability. Apple does this with the iPhone too.

Maguro | Vanir 4.002 03/04 nightly | AK Cylon 728
[Samsung Galaxy Nexus] SPyxOff:
Efficient Underclocking test

So I tried it,

Your settings was pretty smooth, I did not noticed any kind of lag or whatsoever.

Atom v8 + AK Cylon 728

I mean I did a lot of photoshop, whatsapp, a little bit of browsing and social networking and

it got me through the whole day. (my regular day)

Woke up in 7am. Going to bed now at 11:00pm.

But I thought, I would get at least 4+ hours on screen time. Never achieve this with AK kernel though.

Only 2 kernels made for me 4hours+ OST possible.

STOCK KERNEL and LEANKERNEL from imoseyon.

Maybe to try these settings with those kernel will make significant improvements.

We'll see.

PM: These settings gave me 30 minutes+ of on screen time usage! :)
[Samsung Galaxy Nexus] szucsgf:
Thanks for the feedback! 30 more minutes of on screen time is just about the same improvement I had. My average ost over 4 battery cycles was 3h45m.

I wanted to test lean kernel but for some reason 6.1 gave me a bootloop, even after factory reset. Haven't had a chance to figure out why yet, but I want to see if there's a difference. Will try when a new lean comes out.

Maguro | Vanir 4.002 03/04 nightly | AK Cylon 728
[Samsung Galaxy Nexus] SPyxOff:
Cool

Yes. 6.1 is just a bad kernel. Go try 6.0 that runs just fine. Try 6.0 and I am going to try the stock with the vanir.

Next day I will post another battery stats
[Samsung Galaxy Nexus] tiny4579:
Instead of just sayinf its a bad kernel you should they to get a last_kmsg for the kernel dev or the issue may still exist for your device in future builds.
[Samsung Galaxy Nexus] albsat:
I am using your settings in Vanir and trinity kernel. The settings are close to yours and till now I am having good battery life. I will post later on at the end of the day how it goes.
[Samsung Galaxy Nexus] albsat:
Back again. Not a good result but I had to do a reboot and change a theme.

I will give a go to trinity kernel another day.

My settings are:

Min 307

Max 1036 mhz

Interactive

High speed freq 691 mhz

Max screen off 691 mhz

Cubic,

Deadline

2048 buffer

Wi-Fi performance on

Sync on

Velis app
[Samsung Galaxy Nexus] fieldside:
Underclocking franco kernel...worth it!

Underclocking from the default 1288 to 1036 in franco 366 kernel will cost about 8% decrease in speed (as measured by Antutu) but will increase battery life by over 12%. Worth it, for the speed decrease is not felt in non-game use and the system still feels very smooth.
[Samsung Galaxy Nexus] mrm43:
Great. Thanks for the detailed explanation. Will try this one for sure. Thanks
[Samsung Galaxy Nexus] bluewhite79:
I am running CM10.1 M2 and I just flashed AK Cylon 728. So far so good. I've used all of szucsgf settings except I put min at 230. I just decided to go away from LK 6.1 because it just wasn't doing anything at all for battery life with SOT. I still had to charge once a day regardless of the settings.

So far, AK has been smooth even at the settings above.
[Samsung Galaxy Nexus] szucsgf:
So I've learned: AK Kernel is so good you can underclock and not even notice.

Maguro | Vanir 4.002 03/04 nightly | AK Cylon 728
[Samsung Galaxy Nexus] str8killinya:
AK has never let me down either. Always runs great even when clocked at 920 like I have been for days with 0 problems

DEVICE: Maguro

ROM: Cataclysm 3-6-13

KERNEL: Purity v30

LAUNCHER: Nova Launcher Prime
[Samsung Galaxy Nexus] mrm43:
Just wanted to know, with your settings, when opening/closing apps are they as fast as when min/max cpu were set at default values. Or has there a slight decrease in overall smoothness in place of longer battery. Thanks
[Samsung Galaxy Nexus] ufrat:
I use Intellidemand with minimum freq set to 180. (To set it lower then 525 on intellidemand you need the kernel compiled with CONFIG_CPUFREQ_ID_PERFLOCK=n) and the max to 1060.

I Think it is smooth but smoothness is real not something you can really measure. so just try without thinking about
[Samsung Galaxy Nexus] szucsgf:
I haven't noticed any slowdown. However Charmacas has. I'm sure it depends a lot on the other aspects of your setup, particularly which ROM you're using.

Maguro | Vanir 4.002 0305 | AK Cylon 728
[Samsung Galaxy Nexus] bluewhite79:
Mobile network won't connect to matter what I try. I've got bars and icons, but it won't connect Data.
[Samsung Galaxy Nexus] szucsgf:
Last time this happened to me simply restarting the phone worked. Have you already done that?

Maguro | Vanir 4.002 0305 | AK Cylon 728
[Samsung Galaxy Nexus] bluewhite79:
ok, nevermind. Verizon is down big time. no 4G or 3G. my family with a bunch of iphones are having the same issue.
[Samsung Galaxy Nexus] bluewhite79:
Well the first day is very bad.:confused:

10 hours on battery. NOPE, you did not read that wrong.

Items of note:

3-4 hours of LTE (but not using the phone at all during this time)

about 20-30 minutes of no Data (VZW network was down) - this drained the battery a good bit.

Screen on time: 63 minutes.

trying to figure out how to post screens without spending money on tapatalk.

---------- Post added at 07:29 PM ---------- Previous post was at 07:16 PM ----------

Ok, here is an issue. Every time I open TricksterMOD, all of my settings are gone. I'm hitting the check mark after making changes and I've checked "set on boot"

do i need to check frequency lock?
[Samsung Galaxy Nexus] bluewhite79:
Ok, I can confirm that it is not Deep sleeping at all. under "info" in trickster it states that "deep sleep" is not being used at all since the last phone reset.

"Android OS" is wakelocking the device? how do I fix?
[Samsung Galaxy Nexus] szucsgf:
I answered this question in a PM as well. I recommend this app:

https://play.google.com/store/apps/...SwiY29tLnJvb3R1bmluc3RhbGxlci5iYXRyc2F2ZXIiXQ..

It forces your CPU into deep sleep when your screen is off. Set it up, turn off your screen for 5-10 minutes, then check in Trickster to see if you phone was in deep sleep. If it works (it's worked for everyone I recommended it to), it's likely worth it to buy the paid version. Good luck!
[Samsung Galaxy Nexus] bluewhite79:
Thanks for the tip. The only downside is that PUSH gmail won't really work anymore since it totally turns off data. The pro version you can set to 5 minutes which isn't terrible per se.

I sent a PM for other questions.
[Samsung Galaxy Nexus] snuffykl:
yo bro applied your settings and will observed the battery life.noticed the performance does not impact which is running smooth..thank you for ur hard work..see how can it push the battery life on mugen 4000mah :)
[Samsung Galaxy Nexus] szucsgf:
Wow how long OST do you get with that battery normally?
[Samsung Galaxy Nexus] snuffykl:
estimate screen on with Edge sometimes if needed 3G around 7 hour +.. usually if come back from work will be using wifi at home..
[Samsung Galaxy Nexus] ufrat:
get better battery stats and look for what exactly is holding it awake. under the "Android OS" flag in battery is actually a hole bunch of things.
[Samsung Galaxy Nexus] szucsgf:
Added adjustment for longer race-to-idle in the OP.
[Samsung Galaxy Nexus] crea78:
Do you use Ascending or Dynamic for the auto brightness?
[Samsung Galaxy Nexus] szucsgf:
Dynamic. That way brightness will be adjusted in both directions, higher and lower, based on changes in your surroundings. Ascending will increase brightness when your surroundings get brighter but won't decrease, even if your surroundings get darker, until you turn off your screen. I can't imagine that's very good for battery life.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] kevdliu:
Searched the thread and found nothing so sorry if this has been asked before, but if everything below 525mhz use the same voltage, wouldn't it be more efficient to set min freq at 525?
[Samsung Galaxy Nexus] szucsgf:
Thanks for searching first. You're right, that hasn't been asked before.

The reason is because power is determined not just by voltage but also by frequency. Remember the measure of power we're using is P* = (voltage^2)(frequency). So even though the phone is at the same voltage at 180 and 525, it's s still using a lot more power at 525.

I hope that helps.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] timothyung:
Since I can safely over clock to 1420 (which uses the same voltage as 1200 due to my settings), the performance loss by under clocking to 1060 is about 25%, versus 21% power saving. I guess it can be considered worthy.

By the way, if my understanding is correct, over clocking will actually improve battery life provided that the voltage is unchanged. Although screen on time will likely decrease by a bit, loading time should also decrease while spending the same amount of energy , thus saving some juice used by the radio and screen etc.
[Samsung Galaxy Nexus] albsat:
I am trying your settings with rasjellybean rom and purity v30. I am using velis. Hope I get a satisfying result.
[Samsung Galaxy Nexus] szucsgf:
:) I had a very similar thought. I believe most of the battery savings I achieved came from lowering hispeed_freq because of the effect you mention: at a higher frequency the cpu can compete tasks and go back to idle faster. I'm testing at 1350 right now.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] chevlar:
I love the perspective that you're taking on this. I'm not sure if you're familiar with the nexus s research done by Bedalus (& Haarb), but if not, take a look. It's all quite interesting, and I believe his general conclusion that using the lowest frequency for the longest time will result in longest battery life. Note that the thread, experimentation, and much of the discussion, revolves around experimental testing of kernel developer Ezekeel's Deep Idle mod. While much of the results are widely generalize-able, it's important to keep in mind. At some point in that thread there was some experimentation on race to idle, but I think the results did not indicate that the difference was discernible. I do remember something from that work about certain processor states being more efficient than others. On the NS, which ran 100, 200, 400, 800, and 1000 MHz stock, 200-800 MHz were the most efficient. I wonder what the case is for the GNex? Either way, I hope these old threads find some value here.
[Samsung Galaxy Nexus] szucsgf:
That Nexus S thread is awesome. I've only read the first 2 posts so far and I've learned a lot. It's encouraging that the second post calculates power exactly the same way I do. Thank you for showing me this.
[Samsung Galaxy Nexus] D-KAKES:
Fancy Kernel + ondemandplus

I've been "lurking," conducting similar testing since your original post. I'm not much of a contributer (in fact, this may be my first post...) but wanted to thank you for your efforts, while bringing ondemandplus (governor) into the convo.

Courtesy of boype:

"Knowledge base: ondemandplus guide"

http://xdaforums.com/showpost.php?p=38456009&postcount=390

I've been rocking boype's Fancy Kernel v9 for 4 or 5 days, over a variety of popular ROM choices of today (atom, xylon, xylon/carbon, vanir to be specific). I, too, have been riding the developmental AK build bandwagon but I highly recommend giving Fancy Kernel a test run.

Of course, I'm assuming you haven't to this point -- but I'm really just curious as to your opinion and insight re: ondemandplus.

"Fancy Kernel (r9)"

http://xdaforums.com/showpost.php?p=38456009
[Samsung Galaxy Nexus] Citizen_Snips:
So I applied your settings with roughly ~65% battery. Xylon 2.2 On AK kernel v731. Literally have never seen my battery drain so slow with my screen on. It's been hovering at 7% now for a good 5-7 minutes at least. 2.5hr SOT since so far, from only 60%....wow. Going to run this dry and plug it in. I'll report back later. Thanks
[Samsung Galaxy Nexus] szucsgf:
You know, I'm actually trying Fancy kernel today for the first time. And it's largely because I found Ondemandplus interesting! It's going well so far, but I'm going to ignore the results of this first battery cycle and really observe the second.

I found Ondemandplus interesting because of the inter_lofreq and inter_hifreq controls. I see those two together as two-step hispeed_freq. This might mean the processor will be encouraged to spend even less time at Max CPU, except when really necessary. I plan to run at:

Min CPU 192

Inter_lofreq 537.6

Inter_hifreq 729.6

Max CPU 1036.8

and see if I get better battery results than AK Cylon with Interactive and the rest of the settings in the OP.

I must say though, I don't know if anything will run as smooth on my phone as AK. Fancy seems to be quite responsive but I do see the occasional stuttering. Maybe that's just the new kernel settling?

Incidentally, I have seen a few AK fans giving Fancy a try in recent days.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] CHU WANT:
I agree that it may not live up to AK in terms of smoothness. But "apples to apples" (with settings geared toward smoothness, I mean) this kernel feels remarkably smooth. It's also got some toys not presently built into cylon that I'm interested in messing around with -- thought you may, too.

Interactive/ondemandplus are two entirely different beasts, but the extended rev 9 has a great balanced feel to it right out the box with the recommended default settings. I'm not saying these devices can push screen-on time numbers combined w/ the smoothness that your settings are putting out, but I really just wanted to share so we could all better get our geek on
[Samsung Galaxy Nexus] szucsgf:
And I appreciate it! Found any other toys you can share? I'm on Fancy for a few days at least and I'd certainly like try experiment.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] CHU WANT:
I feel there's a better screen on min value, higher than 192 but for its purpose more conservative than 384 MHz. Still got a lot to play around with
[Samsung Galaxy Nexus] D-KAKES:
The login name XXXXXXXXXXXXXX is me. LastPass auto-login setting yay
[Samsung Galaxy Nexus] szucsgf:
OK. I tried Fancy Kernel. I was interested in Ondemandplus governor. Ignored the first battery cycle to let the kernel "settle". These are the settings I used on the second cycle:

Cubic

512

sio

Ondemandplus

Min 192

Max 1036

Max Screen off 537

Min Screen on 192

inter_lofreq 537

inter_hifreq 729

All else my usual: wifi high performance ON, Multicore power saving 2, GPU 384, Smartreflex all ON, anarkia colors. These are my results. Overall, approximately 15 minutes more OST than AK kernel with the settings in the OP. However it was also noticeably slower/laggier than AK. Not terrible, but not the same seamless butteryness. But that's just how my phone reacted to it. It seems Fancy is a bit more battery friendly, and other people report that it feels buttery smooth on their phones. Definitely worth trying. Myself, I think I'd prefer AK.

Next I'm going to test a kernel that reportedly is very smooth and has better battery life than anything: the stock 4.2.2 kernel!
[Samsung Galaxy Nexus] murso74:
you're the second person that showed volume boost in their numbers. any reason for that? i'm assuming it doesn't have anythign to do with battery life?

also, curious on why you don't use hotplug
[Samsung Galaxy Nexus] szucsgf:
My hearing isn't great, so I like that the volume can be a little higher than stock if needed. Since the phone spends very little of its time making sounds I can't imagine this takes much battery. Also I understand that producing sounds takes very little battery. For example when listening to music using headphones with screen off the battery drains very slowly. I'm no expert on this though.

I tried hotplug, but it would cause my phone to free once every few hours. This feature doesn't work very well with the GNex's CPU. Since a reboot takes about 1% battery, the freezing easily negated any battery savings that hotplugging would have.

The benefit of the hotplug governor is that it shuts off one CPU core when it's not needed. This is unnecessary with AK kernel using Interactive, since Anarkia has implementing this feature in the Interactive governor. Also, in newer versions of TricksterMod there is a feature under the Specific tab called "Multicore Power Saving". This can be set at "0", "1", or "2". Enabling this will cause one CPU core to shut off when not needed, I assume on any governor. So, since Interactive is much more stable on my phone than hotplug, and since hotplug's main feature is available on other governors, there is no reason to use hotplug.
[Samsung Galaxy Nexus] murso74:
thanks for the explanation. i'm mirroring your settings now.
[Samsung Galaxy Nexus] ufrat:
Hotplug is not the most beloved govenor og the gnex. you could try intellidemand. the newest version of ak kernel is configured to allow smaller min freq then 525mhz on intelli and it runs rock solid for me on 180mhz.

on the last thing you're just wrong... the multicore power saving won't disable any core. it just group the processes in an other fashion which have some good effects on the powerconsumtion because an idling core at some frequency uses less power then one which is not idling.

This can have some nice effects with govenors which set one cpu core offline too...

HTC have something like the thing which enables and disables a core according to the load on every govenor. This is called mpdesicion and is in its normal form as userspace software a big load of sh**. Someone put it in kernelspace then and it was something but not that nice ... this was when i get it right one reason why faux developed something like intellidemand to get rid of that software
[Samsung Galaxy Nexus] szucsgf:
Thanks for correcting me regarding Multicore power saving! And thanks for pointing out intellidemand. I'll give it a try.
[Samsung Galaxy Nexus] szucsgf:
Well, I tried intellidemand. My phone froze twice, requiring reboot, after just a few minutes of active use. Didn't tweak anything. I would love some insight on this. For now I'm back to interactive. Thanks.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] FC1032:
Hello! I was going to give you settings a try, but ended up choosing hotplug over interactive (but same min Max clock and voltage settings.)

Do you think that's going to make a further difference or should i stick to your settings to the dot?
[Samsung Galaxy Nexus] szucsgf:
Please experiment! The settings I wrote the OP about were just an example. It's fully generalizable to different governors or different kernels. The key idea is just to understand the relationship between voltage, frequency, and power. My settings may not be the best possible settings.

I'm always trying different things too. For example I've been testing the OP settings except increasing Max CPU to 1350. The sacrifice in battery life isn't huge. I had about 15 minutes less on screen time. I believe the majority of my batter savings came from underclocking hispeed_freq.

I would like to point out that I believe anarkia built hotplugging (turning off one CPU core) into his Interactive governor, and hotplug is less stable on our phone than interactive, so if you're using AK kernel there may be little advantage to using hotplug.
[Samsung Galaxy Nexus] FC1032:
GENIUS! right before I commented, my phone locked up and I had to pull battery. I think I'll stick with yours and work from there.

Thanks!
[Samsung Galaxy Nexus] kevdliu:
Honestly I didn't notice much or any battery savings from intellidemand. Maybe its just me anyone else have experience with it?

update: annnndddd my phone just froze. No overlclocking or undervolting. I think im done with hotplugging governors taking off the case is a pain is the butthole
[Samsung Galaxy Nexus] murso74:
how about interactive x?
[Samsung Galaxy Nexus] szucsgf:
Intellidemand freezes for me too. Stability is very important when your goal is increased battery life; one freeze can negate whatever benefit the unstable governor might have had with the power used in rebooting.

Interactive is the quickest stable balanced governor I've used (maybe that's the reason it's so popular). I'm giving Wheatley a try now though.

Maguro | Vanir 4.002 0305 | AK Cylon 731
[Samsung Galaxy Nexus] szucsgf:
My understanding is that interactivex is the same as interactive when screen is on but turns off one cpu core when screen is off. But anarkia built this into his interactive governor anyway, so no there's no difference.

Maguro | Vanir 4.002 0305 | AK Cylon 801
[Samsung Galaxy Nexus] Wh1t3Rose:
Exactly. dead on

Toro | Atom v9 | AK Cylon 734
[Samsung Galaxy Nexus] Charmacas:
I posted this question on the ak thread! :)