yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] drawde40599:
I get 3.75 -4 hours screen on time with this kernel (AOKP ROM)with screen 90% bright, 300+ texts a day data on 24/7, internet, sync everything on, and over 100 useless apps probably some running in background, that's with 700/1200 gov, ondemand and 512 gpu kernel no UV, nothing checked in his app, .trying the interactive gov now, with hot plug checked in app . I like this interactive better its faster, hoping the hot plug setting keeps battery at my 4hour mark ( just guessing interactive will suck lil more juice??? Don't no tho ) . From what I've seen most r getting 3-4 hours except one guy getting 7 hours ( funny) guess I could have said u kinda have to test your self o_O but those my results from last I'd say 12 kernel updates .... ( now that I think about it this don't answer ur question at all o_O ): ) do much drink getting off phone now
[Samsung Galaxy Nexus] samizad:
Having read the explanations of the different governors I have learned that performance and battery drain really depend on how you use your phone. There's no way you can compare with someone else. Pick On Demand if it's working better for your daily usage.
[Samsung Galaxy Nexus] franciscofranco:
#3.9.2

* Added menu option "Upload crash log" to email me last_kmsg logs directly if you had a system crash caused by my kernel

* Re-arranged CPU modes panel - now you have a ListPreference where you can choose either Single-core or Dual-core mode. This setting doesn't stay on boot and it's intended

* Smartreflex option re-arranged for better understanding of what it does

* Reduce voltages thread refresh rate to make it jump less

* Small fixes across the board
[Samsung Galaxy Nexus] drewlim:
Nice i thought its only me seeing those voltages jump often when monitoring them through your app.
[Samsung Galaxy Nexus] zammbi:
I gave it a test(didn't send the actual email), but it really lagged my phone. I think it was too much text for gmail to handle it seems. Are you able to pass gmail a text attachment instead?

I also find that in 3.9.2 you can no longer scroll in the nightlies change log.
[Samsung Galaxy Nexus] drawde40599:
Scrolling threw change log not working here either ..
[Samsung Galaxy Nexus] franciscofranco:
It lags because of the big amount of text, but after it's sent/discarded it doesn't lag anymore.

**** happens. Will fix later.
[Samsung Galaxy Nexus] drawde40599:
Just putting it out there brother......
[Samsung Galaxy Nexus] dwang:
Getting the best battery life I've ever had with r130 512gpu and interactive governor.

5:30 screen time and 13 hours of uptime with the 2000mah extended battery using cm9.
[Samsung Galaxy Nexus] samizad:
The scrolling issue is a good observation. I think Francisco's response was more in the spirit of humour.
[Samsung Galaxy Nexus] kashix:
For interactive governor, what speed are you guys running at? 729/1228?
[Samsung Galaxy Nexus] samizad:
Even with the extended battery, that's very impressive. What screen brightness?
[Samsung Galaxy Nexus] dwang:
25%
[Samsung Galaxy Nexus] schizophrenia:
is it only me?

on r130

i tried "interactive" as you guys suggested but it keeps running on "Single Core". Same for "on-demand" i just tried

i thought it was the kernel problem so I switched back to "Hotplug" and it runs "Duel Core" again....

I used Quick System Info Pro to check
[Samsung Galaxy Nexus] drawde40599:
temple run

Just noticed temple run is real laggy on build 130, 512 gpu . I no its cause of the gpu speed ( flashed the 384 version and was fine ). There's no fix for this is there? I mean besides keeping the 384 version?

---------- Post added at 11:03 PM ---------- Previous post was at 10:59 PM ----------

Cool little app for looking at that ... both my chips running on interactive and on demand , I'm guessing ur looking at the pull down menu?? So ya its ur phone not kernel
[Samsung Galaxy Nexus] zephiK:
your phone cant handle 512
[Samsung Galaxy Nexus] alvespt:
Two questions os hot plug function. Can it ruin my cpu? Can this affect my signal strength? Or app sync like mail?
[Samsung Galaxy Nexus] drawde40599:
No not really tru, I have a lot different games and apps and been running 512 gpu speeds since Franco interduced months ago, temple run 1st time I have seen any lag . Guess I just won't play temple run: )

---------- Post added at 11:31 PM ---------- Previous post was at 11:24 PM ----------

Thanks for actually admitting u have a extended battery: ) u no ur signal sucks!! U could probably get even more out that battery with different radio . Witch one???? Try them all search xda for links
[Samsung Galaxy Nexus] ragnarokx:
Mobile signal strength is moot - he was on WiFi almost the entire time.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
Till now on r130 (384).

Works really fine for me. Last night I lost only 1% for about 6,5 hours when idle. It's amazing!

And still don't understand why I have problem with battery drain when using 512 GPU build. There no other issues were found - just abnormal battery drain.
[Samsung Galaxy Nexus] drawde40599:
I seen that, and I'm on wifi 80% of the time and my signal is green all day long not choppy like his
[Samsung Galaxy Nexus] kashix:
What governor and speed are you guys running to get good battery and performance?
[Samsung Galaxy Nexus] raubkatze:
ondemand governor

max cpu 1228

min cpu 729

no uv

cm9

brightness 25%
[Samsung Galaxy Nexus] alvespt:
With or without hot plug?
[Samsung Galaxy Nexus] raubkatze:
Now without Generic Hotplug.

It's interesting to see the difference for battery between using with or without Generic Hotplug. I didn't see a substantial difference on r130 so far.
[Samsung Galaxy Nexus] DontJoinTheDarkSide:
Seems I spoke too soon. Seems like installing this kernel gives me a SOD I'm not sure if I'm doing anything wrong but I posted a logcat I hope Its the right one. (Never posted one before)

Any help at all is very much appreciated.
[Samsung Galaxy Nexus] Remoteconcern:
You're going to hate this Franco, because I didn't get a log...but basically this morning, I clicked on better battery stats and the phone immediately rebooted to the Google with unlocked icon screen, and then wouldn't get past the boot animation (the AOKP unicorn). It was completely stuck, and I was out of the house so I had no choice but to restore a backup as the phone was mission critical!

I have no idea if this was kernel or AOKP 30 related, as that ROM is just getting buggier by the day.

Specifics are r130, 384/1228 interactive, 512mHz GPU, no other mods or voltage changes. Hopefully this wasn't kernel related but I'm sorry I couldn't get a log.
[Samsung Galaxy Nexus] jnr21:
Try 384mhz gpu version.
[Samsung Galaxy Nexus] DaLoona:
Flashed r.130, so far no issues. Batterylife improved even more, for me no SoD and no signal loss as long as cpu minimum is 729MHz, no wakelocks either, great work.

Bought your updater to support your work, great app.
[Samsung Galaxy Nexus] raubkatze:
On my experience b30 has a lot of bugs. After day using I restored b29. It works with franco's kernel completely fine without any issues.

---------- Post added at 02:22 PM ---------- Previous post was at 01:56 PM ----------

So now I have results for 4,5 hours usage after first charging on r130 (384). It's ordinary usage for me - some calls, social networks, mail and browsing. Looks fine on my mind.

CM9

brightness 25%

Max CPU 1228

Min CPU 729

ondemand governor

no UV

Generic Hotplug is off
[Samsung Galaxy Nexus] AdamZA:
Thanks - I hadn't realised my app was out of date! Don't check Google Play that much :P
[Samsung Galaxy Nexus] wollyka:
I am using r130 with 512 Mhz GPU with the following settings:

BlackIce

brightness 25%

Max CPU 1228

Min CPU 384

ondemand governor

no UV

Generic Hotplug is on

I noticed that when the screen is off, i am not getting any notifications (i tested using Gtalk and Whatsapp). If i wake the phone (screen ON), i receive all the notifications at once!

i disabled hotplug and increased the min frequency to 729 but it didn't helped.

I flashed back rXXX (r123) and the problem went away even with hotplug mod and min 384 frequency

Maybe it has to do with some settings (voltage) that affect on-screen that were introduced in r130?
[Samsung Galaxy Nexus] raubkatze:
I have not this issue. But if you're using Light Flow try to delete superuser permissons for this app then open Light Flow and allow superuser request.
[Samsung Galaxy Nexus] wollyka:
The problem is not with LED notifications, it seems that the "messages" are not received until i unlock and wake the screen. However, Wifi icon is still shown as blue and connected!
[Samsung Galaxy Nexus] raubkatze:
Ok. What rom do you use?

On CM9 and AOKP b29 everything works fine. With r130 (512) I had only one issue - abnormal battery drain. With r130 (384) I have no issues so far.
[Samsung Galaxy Nexus] RensoreK:
Why wouldn't it happen? Doesn't the faster the network or there amount of usage have effect on battery? Doesn't poor signal cause the battery to drop like crazy?

---------- Post added at 08:32 AM ---------- Previous post was at 08:22 AM ----------

regardless of wifi , signal does affect battery because the phone must put or more power searching for a signal or more power trying to keep a poor signal. Its not only and internet device, its a phone..
[Samsung Galaxy Nexus] wollyka:
Blackice (basically latest AOKP with black theme)
[Samsung Galaxy Nexus] raubkatze:
About latest AOKP I wrote above - http://xdaforums.com/showpost.php?p=24624954&postcount=11695
[Samsung Galaxy Nexus] stellaryt:
..never mind

I tried agian,could got notification when screen off.

Sorry...
[Samsung Galaxy Nexus] tossero:
Is you are using JuiceDefender try to disable it ! It worked for me ...

Cheers~
[Samsung Galaxy Nexus] wollyka:
No juice defender here :)
[Samsung Galaxy Nexus] SupWiz17:
I loaded this new kernel yesterday with the newest cm9 and I have noticed that when using the UV settings that I have been using with no problems for a month the phone was locking up and rebooting all day. It didn't matter what governor I used or if hotplug was on or not the phone was just not running right. It happened the most when I would open up a text. The messaging app was locking up and rebooting the phone. I overclock the phone to 1344 and keep the minimum frequency at 384. Once I stopped applying the undervolt settings I normally use and let the phone sit and charge for the night it hasn't happened since and battery life is great! I really like the interactive governor too.
[Samsung Galaxy Nexus] kashix:
Battery dropping fast. No idea why. Regardless of the governor used
[Samsung Galaxy Nexus] KLUVJ:
idle battery over night, more like 8 hours

not the best i've seen, anyone else can compare theirs？

b130 with aokp b31.

700/1300, hotplug, generic off, wifi boost, sound boost, undervolted. 384mhz version

EDIT: cant seem to post screenshots, dont know why, saying not permitted. but it was like 10 percent drain from 95 to 85 with perfect signal and wifi 100percent on. phone was in deep sleep for 90 percent of the time. rest was at 700mhz
[Samsung Galaxy Nexus] franciscofranco:
No need to undervolt, smartreflex does that for you.
[Samsung Galaxy Nexus] homer2320776:
r121 has been my favorite of the bunch, r130 has increased my overnight battery drain significantly. During my work hours I can see almost 5-8% per hour drop with the phone just sitting at my desk.

With r121 the battery was pretty much flatlined until I used it and even then the percentage didn't bother to move. Almost 3 hours, stock battery, screen on time with r121. 55 minutes screen on, 10:20 AM, 40% battery left, better find my charger. :)
[Samsung Galaxy Nexus] brb123:
Same here for me..
[Samsung Galaxy Nexus] Fredriksen:
Same her. R121 has better battery life and works better in games for me. GTA was almost unplayable on r130.
[Samsung Galaxy Nexus] Neejay:
I also went back to R121, purely for battery life. I haven't done any CPU intensive things to notice a difference.

Question though: If this kernel has custom voltage control, we should disable SmartReflex, right?
[Samsung Galaxy Nexus] rookie8155:
Is R121 compatible with ICS 4.0.4? I will appreciate your reply.
[Samsung Galaxy Nexus] mikeandjaimie:
Read OP
[Samsung Galaxy Nexus] kashix:
of course it is, most of us here are flashing addicts, there's no way we are not on 4.0.4 the moment it's out, so yeah. you should understand we were previously using R121 with 4.0.4

---------- Post added 10th April 2012 at 12:01 AM ---------- Previous post was 9th April 2012 at 11:59 PM ----------

unless you're planning to do manual UV, I suggest keeping SmartReflex.
[Samsung Galaxy Nexus] rookie8155:
Thanks, I will try R121 then. How it works? Flash kernal first, then ROM?
[Samsung Galaxy Nexus] drawde40599:
121

I also went back to 121 found it to be best out of the bunch, battery drain is high with screen off on 130 . I think I'm sticking 121 . I see no reason to change: ). Thanks Franco
[Samsung Galaxy Nexus] spovat:
As is always the case with people claiming better performance with an older revision... anyone got a link to 121?
[Samsung Galaxy Nexus] aleve1983:
it' s true and phone is hotm when i use it
[Samsung Galaxy Nexus] rafael-as:
I also went back to R121, battery life is better !!
[Samsung Galaxy Nexus] raubkatze:
Here - http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/

---------- Post added at 09:11 PM ---------- Previous post was at 09:04 PM ----------

Guys, who went back to 121, what built r130 you tried? With 512 or 384 GPU?

For me r130 with 384 GPU works great but with 512 I had abnormal battery drain as wrote above.
[Samsung Galaxy Nexus] kashix:
rom 1st then kernel as the rom carries a kernel with it when you flashed it.

the link to 121 is in the op thread.

---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------

all along using 512 regardless of the nightly, worked well until R130.
[Samsung Galaxy Nexus] bendirkss:
Idk how you people manage 4+h of screen time with this
[Samsung Galaxy Nexus] raubkatze:
For me 512's builds worked fine until r123 (XXX).

But question was: What built r130 you tried? With 512 or 384 GPU?
[Samsung Galaxy Nexus] hawkye:
r130 on 3G/4G has been spectacular with battery life. I turned on my wifi at work and it seems to be killing my battery. I turned it off to see if the phone will sleep now.

EDIT:

Yep it is draining due to Wifi being on. I turned off Wifi and now my phone is going to sleep. With Wifi on it barely slept at all. (Keep Wi-Fi on during sleep is set to Only when plugged in).
[Samsung Galaxy Nexus] rafael-as:
I tried 384
[Samsung Galaxy Nexus] drawde40599:
Build 121, 512 gpu data on, wifi, on sync on, brightness 80% ,300+ texts a day I get lil over 5 hours with extended 2000 battery 3.5 -4 stock battery

---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------

512, I want the speed of 512, 384 to slow for me after trying 512 ,I tried the interactive and on demand governors
[Samsung Galaxy Nexus] raubkatze:
I had a problem with battery drain on r123 (it has 512 GPU OC) and on r130 (512). So I thought that it might be interconnected.
[Samsung Galaxy Nexus] Stretlow:
For me 121 has been the best out of any of the kernels.

3.5 hours screen on time where my personal best was 3 ish
[Samsung Galaxy Nexus] nikulogical:
If you're getting bad battery life on r130 try interactive rather than on demand.
[Samsung Galaxy Nexus] raubkatze:
I can't tell for everyone but I've tested all governors on r130 (512) - the same results.
[Samsung Galaxy Nexus] kashix:
no offense but it's the interactive governor which is draining the battery.
[Samsung Galaxy Nexus] drawde40599:
Didn't help, I fully tested before I started whining: ) lost 20% in less then hour from full charge 2x ( I test it a lot more than that that's just an example) build 121, 512gpu going on 2h now off charger same amount of use I'm only lost 8% and I'm OC 1300 ...BTW!! I'm not complaining, just trying help!!
[Samsung Galaxy Nexus] zephiK:
i dont have any battery drains on Interactive O.o
[Samsung Galaxy Nexus] homer2320776:
Yeah, no complaining here. Flashing kernels / ROMS / firmwares is my nerdy version of crack.

I was running r130 / 384 when I was having my issues , never tried a 512 kernel on this device.
[Samsung Galaxy Nexus] mrfrag1337:
r130, 384/1228, OnDemand, Hotplug enabled.

Screen 3h 30m, with 25%, and 100% brightness very high usage today outside.

3g 4-5h, wifi 7h.

Im very happy with this rom and its battery duration! :D
[Samsung Galaxy Nexus] nikulogical:
Weird.. ondemand gave me lower screen on time battery but with interactive its on par with r121.
[Samsung Galaxy Nexus] heo_con184:
Rolling back to r121 - 512mhz GPU for now. R130 seems doesn't like my battery.
[Samsung Galaxy Nexus] aleve1983:
sorry my battery drain on screen off was gtalk, i logout and now is ok
[Samsung Galaxy Nexus] audibalso:
Battery Life: r121 was great, r130 slightly better. Not getting the decrease in battery life others have reported between r121 and r130.

I'm using/used 384 gpu, on-demand, no generic hotplug, 729min 1228 max. On CM9 toro 4/7 build. I always data wipe when updating roms. I never get the 4+ screen time people report. But yesterday I did about 35 hours with a 2+ hours screen time. I do have 4 gmail accounts syncing and 2 yahoo account sync every 30 mins. I'm thinking this maybe the reason why I don't get as high as other.
[Samsung Galaxy Nexus] raubkatze:
13h 26m after full charge.

Looks fine but I don't like periodically chart's jumps 1-2% up.
[Samsung Galaxy Nexus] franciscofranco:
People reporting worse battery life what roms are you using? All my regular testers and myself report awesome battery life so unless I get harder evidence I call it a bad rom and not the kernel.
[Samsung Galaxy Nexus] Neejay:
Slim ICS 3.2

729/1036 cpu + generic hotplug mod
[Samsung Galaxy Nexus] franciscofranco:
Disable generic hotplug and report back if it helped.
[Samsung Galaxy Nexus] kashix:
aokp b29.

Generic hotplug

729/1228.
[Samsung Galaxy Nexus] raubkatze:
Skankwich CM9.

Max CPU 1228

Min CPU 729

ondemand governor

no UV

Generic Hotplug is off

But I have problem only with 512's builds and only since r123.
[Samsung Galaxy Nexus] rafael-as:
Liquid ICS + hotpluged + 700/1200 + 384 gpu

Now i flashed AOKP b31 and trying r130 again. Results later.
[Samsung Galaxy Nexus] franciscofranco:
Interesting as generic hotplug seems to be the common item. All of you try to disable.it.
[Samsung Galaxy Nexus] raubkatze:
I disabled Generic Hotplug only to test the battery life without it. As a rule I use it. There is no problem on r130 (384) without or with Generic Hotplug.
[Samsung Galaxy Nexus] supercluver:
I'm down 5% 6 hours after flashing r130. I'm on Paul O'Brien's awesome modaco Ir13 4.0.4 ROM. I'm using the 384 MHz GPU version, 384-1228 MHz via interactive governor (switched from ondemand on r121), no UV, generic hotplug on, logging turned off. Auto brightness. Nothing else done. I've been on wifi the whole time. So to me definitely no worse than r121, and it seems to be even a little better though time will tell that definitively.

This weekend I had awesome results with r121 while out and about in San Antonio. Used the phone quite a bit taking pics and stuff like that, some GPS navigation, listening to music. Went well into the night Friday night (15 hrs off charger and still 40% left, about 1.5 hrs screen on) and then Saturday off all day again and still over 45% when I got home to Houston at 10 pm (13 hrs off charger, about 1.5 hrs screen time again). The weekend was all AT&T 3G HSPA+ data too, never any wifi.

To me, Franco, it is just wonderful how I can leave in the morning and just not even think about my battery dying. Also, I have the 2000 mAh extended battery from Samsung.
[Samsung Galaxy Nexus] sago62:
I use cm9 and haven't problem with gpu 512,cpu 384-1228....ondemand+hotplug
[Samsung Galaxy Nexus] mrfrag1337:
I have better battery response with hotplug option enabled i think. CM9 here ;)
[Samsung Galaxy Nexus] nikosrs4:
yes, bad signal drains more battery, that's for sure. But if I understood right, we were talking about the band a network is using and not the signal its own. It's just the band, it shouldn't use more battery(but I'm not an engineer :p)
[Samsung Galaxy Nexus] SupWiz17:
Thanks I never really paid attention to the smartflex because my uv settings were very close to how smartflex lowers the voltage. I dunno if my phone just needed to reboot a few times or if I had a bad flash/download so I downloaded it again and flashed it a few more times but now it seems to be running very good. I'm gonna play around with the governors now that it's stable and see what looks smooth since I have always been able to make it all day like close to 20 hours with your kernel.
[Samsung Galaxy Nexus] drawde40599:
I'm on aokp build 31, same exact setup using 121 as 130 both testing done with full wipes, I dunno then? I basically use my phone exactly the same everyday and 130 was pretty bad on my battery, using interactive and on demand gov??? I'm not one to even care about battery I'm.more into speed, but it was pretty noticeable how fast 130 drained for me ..... if u want me try or test something lemme no .....
[Samsung Galaxy Nexus] franciscofranco:
Are you sure you dont have an app holding a wakelock or something similar? My device is running great :(
[Samsung Galaxy Nexus] drawde40599:
BB stats said everything working as it should, nothing was "awake" I'll try agn tonight and just flash over top of 121 tonight cause everything is perfect ATM . I dunno could be bad install or something.... 130 was running perfect very fast and smooth just killed my battery .... all good I'll try agn . Thanks
[Samsung Galaxy Nexus] CaspaTheGhost:
I found worse drain with hot plug enabled.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] heo_con184:
I'm trying to see what've waken my device up. So I did a reboot, connect to Wifi, check the running apps in Settings after 2-"idle"-hour. There are Facebook, WhatsApp, Mail, Google Services, Messenger.

Do you guys think one of these apps can cause these wakelocks ?

I'm running AOKP B31, r130 - 512mhz GPU. Wifi always ON, I tried also to set Refresh Interval for sync and other apps from 4-6h.

Thanks in advance.
[Samsung Galaxy Nexus] homer2320776:
Running AOKP milestone 4

On demand

Generic hot plug disabled

Only thing that changed between flashing of r121 and r130 was upgrading Volume+ from version 1.8 to 1.9.1 but it doesn't even register in the battery stats.
[Samsung Galaxy Nexus] jhericurls:
Getting weird google service problem with 130. When on wifi, my signal icons go grey. Fine when on 3G.
[Samsung Galaxy Nexus] franciscofranco:
Not related to the kernel I'm afraid.
[Samsung Galaxy Nexus] raubkatze:
Install BetterBatteryStats. You'll see all wakelocks.
[Samsung Galaxy Nexus] fjdifede:
Im on aokp m3 and got the best battery life 4ever!!!! Thanks Franco

Using hot plug every thing else is bad on quadrant!!!!!
[Samsung Galaxy Nexus] superbobup:
R130 is great! Only thing that's different is better battery life ;) 1.5 hours on 80% brightness and heavy browsing on 2g with 60% left

It also seems to be running a bit warmer but I think that's from the increased voltage to try and fix connection issues
[Samsung Galaxy Nexus] franciscofranco:
I think I fixed the IVA and CORE higher voltage usage by no reason since r130. Will give it a deep testing tomorrow during the day, but looks good.
[Samsung Galaxy Nexus] samizad:
I've had that a couple of times but a reboot has always fixed it.
[Samsung Galaxy Nexus] rookie8155:
Sorry, I am new to Android. I just installed R121 with AoKP B31 today. Do I need to do any settings for better battery life? I will appreciate your help.