yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nuwan32:
Great to see people on paranoid with amazing battery :D

I've tried to tell people this, but inverted apps REALLY help. These AMOLED screens are power hogs, specially compared to IPS. So color really makes a difference
[Samsung Galaxy Nexus] Luigi_2:
hi franco, i adjust conservative sampling rate and sampling rate min but it wont stick, otherwise everything is ok
[Samsung Galaxy Nexus] max4wdc:
r298-295 :i found one bug, when i check my apps in setting (settings/apps) app loading is slowly and laggy for 1 min and in the launcher one app move in the desktop and check system info still i waiting for 1 min until check my app size.but with stock kernel just i need only 2-5 sec .

sry for my en .
[Samsung Galaxy Nexus] Tarun95:
Settings works slow even for me on this kernel from day 1 but overall speed is better :)
[Samsung Galaxy Nexus] Shadow-Nexus:
I'm going to give these settings a try

I'll report back
[Samsung Galaxy Nexus] dominatore22:
One word: awesome.
[Samsung Galaxy Nexus] akash3656:
You need to two on the "Other" and select "Partial wavelock". And select since last unplugged and then we can help you as currently you aren't on the right screen.
[Samsung Galaxy Nexus] psycho2097:
dude.....dafuq happened 2 ur wifi? That aint good u knw....
[Samsung Galaxy Nexus] modgadgets:
Superb work Franco :thumbup:

Check out my battery stats with Franco + Rasbean and no mods at all :D
[Samsung Galaxy Nexus] 15israellai:
Oh god you guys just keep posting battery stats.

I can't even get much more than 2.5 hours screen on...

Transmitted from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Nah that looks sort of right when you have the policy for wifi off when sleeping. Though you can see that it got woken up an awful lot of times so I'd say he's got some rogue apps or settings to reign in still.
[Samsung Galaxy Nexus] The Gingerbread Man:
Bumped 192 voltage to 750 from 725 as had some sods and data drops today. Funny how its been fine for a couple of days and since last night I had freeze up, 2 sods, data drops when using 2g/3g but was fine before.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Wow so many happy users :)
[Samsung Galaxy Nexus] osm0sis:
Try it at 730 (or 735 if that doesn't work), I was thinking that might be where the safe range was when I was discussing it with yellowdie before.
[Samsung Galaxy Nexus] The Gingerbread Man:
Definately :) my last post wasnt meant to sound negative i was just giving some feed back. 298 is the best so far for sure :D

I'll try 735 first and try lowering in a few days checking for stability. Just odd how 2 days use was fine and and 2.5 - 3 days (last 15 hours) starting having issues :confused:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] whitedragonz83:
What do you and Yellowdie suggest for 384 and 537? I have been using 775mV and 800mV for them for a few days and it seems good, but wouldn't mind knowing your values.
[Samsung Galaxy Nexus] osm0sis:
Hmm yeah, really odd. Might be the 2g/3g switching like you mentioned. Try to recreate those conditions if you can. Someone else said that 537 also might be a notch too low voltage-wise, so you could try bumping that up a little if it ends up seeming like 192 isn't the problem.

384MHz@775mV has been rock solid for me (and 750mV gave me an occasional freeze). I don't undervolt 537MHz since Franco calibrated that bad boy himself, so I know it's pretty low, yet safe, to begin with. Besides we've got people saying it might already be too low for the average device, so 537MHz@900mV seems good unless more confirm it's too low, or those initial reports were mistaken.
[Samsung Galaxy Nexus] The Gingerbread Man:
Yes I saw that but I'll leave 537 as 900. I was wondering if I developed a hardware issue as when I rebooted before my 3g was working on boot I was finding WiFi turned on or WiFi icon showing connection but with WiFi turned off. Doing airplane mode on and off didnt fix it, reboot didnt fix it, su killall servicemanager didn't fix it, change radio didnt and all of a sudden at 12.00 (1 hour 23 mins ago it worked. I don't think its network related as my gf is on same carrier and her 3g was fine.

I think its perhaps because my voltage was too low so let's see now at 735mv for 192 slot :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dominatore22:
It's juice defender ^_^ turns on and off it in deep sleep for sync all
[Samsung Galaxy Nexus] b1337:
No mods just a charger :p
[Samsung Galaxy Nexus] gianton:
Great work Franco, best battery life since I got my GNex!

2nd full discharge circle after I flashed the kernel. ROM is AOKP 1030 nightly with r298 384 GPU at 384/1536MHz max screen off at 537MHz no UV.

View attachment 1448382 View attachment 1448383
[Samsung Galaxy Nexus] Fenvarien:
I use 192MHz@730mV, 384MHz@775mV and 537MHz@890mV absolutely stable since the release of r298 to reduce idle drain.

This kernel provides a fantastic battery life and performance :)

GNex with franco.Kernel / MiNCO ROM v5
[Samsung Galaxy Nexus] psycho2097:
yes, since nov 2011 ! :)

you definitely need to turn it off, i dont know what kind of idling u r getting, but I get 9ma(0.5%/hr) with both wifi n sync on. Additional software is really not needed. You are actually wasting significantly more battery by repeatedly switching it on/off. Its well documented.

dooooooodeeee.........whoa!

---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------

I m not really getting this, I thought the whole point was to reduce no. of states, so as to reduce energy wasted due to frequent state switching. Can sum1 pls explain to me the benefit of 537mhz, if its not too much trbl...
[Samsung Galaxy Nexus] Elganja:
can't wait!

i do have a question about the new kernels... when we go from 11 to 12, what all needs to be done.

i.e. does davlik, cache, or battery stats need to be wiped?
[Samsung Galaxy Nexus] franciscofranco:
No, nothing is needed, the caches have nothing to do with the kernel. Although you can delete the caches if you want, but its not mandatory.
[Samsung Galaxy Nexus] Elganja:
interesting... thanks. It will make the upgrade even easier!

i hate to ask again, but you touched on caches, how about battery stats? or is that more of a rom oriented thing then kernel?
[Samsung Galaxy Nexus] franciscofranco:
People always been asking me about that, but I never answered. I'll tell you, I never wiped a single battery stat file since I have an Android (December 2010).
[Samsung Galaxy Nexus] Elganja:
good enough for me... I'll follow your lead ;)

thanks for all your hard work franco!
[Samsung Galaxy Nexus] chrisexv6:
This is similar to an issue I experienced with my Fascinate running Froyo and GB: for some reason if GPS is enabled, when the phone boots up Maps gets a partial wake lock and wont let go.

The workaround I found was to open Maps then close it, that gets rid of the wake lock and associated battery drain. So give that a shot.

There used to be a good app out there called Root System Tool, but any old terminal emulator will do.....open up a terminal prompt and type "dumpsys power" (without the quotes). The last thing that you'll see on the screen are any wake locks.

I think LightFlow is killing my battery as well...........Android System usage was high last night, and the "wake time" was almost 5 hours, after letting the phone sit idle for about 7 or 8. Its ashame, I really like the app but not if its gonna kill my battery.....cant quite understand why it keeps a lock like that on the phone, since the phone in stock form performs the same basic functions without having wake locks.
[Samsung Galaxy Nexus] Wingzer:
Currently at :

1day, 13 hours, 24 minutes.

46% discharging.
[Samsung Galaxy Nexus] Thracks:
Hey, Franco. I looked into the battery drain issue, and it looks like it persists across multiple ROMs and kernels. The phone reports going into deep sleep, but worker threads in the Android OS process keep the phone from going to its lowest sleep state: Android OS remains the #1 consumer of power, phone idle barely registers in battery stats, and the Android OS process reports a wake time of 25% (or more) of the total phone-on time.

Definitely not related to your kernel. :) Carry on.
[Samsung Galaxy Nexus] franciscofranco:
Eheh I already knew that. Although I have almost no drain in idle, 0% over 9 hours, yesterday 1% over 7h this last night. And during normal usage it's fantastic too, I don't complain a single bit.
[Samsung Galaxy Nexus] chrisexv6:
So yours does it too, but below Franco says his doesnt. What ROM and kernel build are you on, and what apps do you have installed that might be an issue?

So yours DOESNT do it....same question as above :) what ROM and kernel (hehe) are you running, and what apps that might keep it running in the background.

I too have high Android System usage, but I *think* Ive narrowed it down to LightFlow. Have to grab a terminal emulator so I can run some dumpsys commands to verify that though.
[Samsung Galaxy Nexus] Thracks:
What ROM/radio/bootloader do you use? I have to say I'm very jealous of your battery performance. This battery issue is driving me insane.

//EDIT: I'm currently running a 100% app-free install of AOKP. I also tried Codename Android and Bigxie. All of them do this drain thing, so I'm beginning to wonder if it's bootloader or radio-related.
[Samsung Galaxy Nexus] PanBongo:
yeah would also like to know mr. franco :)
[Samsung Galaxy Nexus] franciscofranco:
Ok. I use this:

Rom: Milestone 1 (gonna update later today to 2)

Kernel: nightly 12

Baseband: XXKK6

Bootloader: KL01

No apps running at the background that could **** my battery, I have a tight app control xD
[Samsung Galaxy Nexus] aron7awol:
If you go into Light Flow General Settings and set the Notification Method on Battery to be either "Show Latest Only" or "Show Highest Priority Only" it should eliminate the need for Light Flow to be waking your device to change colors when there are multiple notifications.
[Samsung Galaxy Nexus] luffyp:
I think he also has the high keep awake from Android OS issue, it just doesn't affect his battery draining much. The issue maybe related to some drivers not sleeping properly and the only one who can fix it maybe Google themselves. Franco, if you don't mind can you post the screen showing Android OS usage in the settings/battery?
[Samsung Galaxy Nexus] pmicho:
Where can we find the Milestone rom? On Rootzwiki.
[Samsung Galaxy Nexus] definator:
http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-milestone-2/
[Samsung Galaxy Nexus] franciscofranco:
There you go.
[Samsung Galaxy Nexus] bradm23:
Franco, I am a little curious to learn more about your setup. Rom? Kernel version? Hot plug? Any other battery saving measures ?
[Samsung Galaxy Nexus] razzbaronz:
See 5 posts before you...
[Samsung Galaxy Nexus] 15israellai:
Don't use it, franco probably saves double the battery that JD does on stock.

Transmitted from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Yup unless you have wlan_rx_wake locks that you can't cure you do save more leaving it on. Happy to report my idle drain was back at 0.5%/h this morning too.

CPU states aren't the same thing as frequency slots. Google Ezekeel's documentation for wheatley governor for a good explanation. One possible benefit of 537 that I'm testing is as a screen off max, since it is fairly lower in voltage than 729 but might still have enough processing power to avoid hurting race-to-idle.
[Samsung Galaxy Nexus] psycho2097:
Ah....thanks.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Has the recommended scheduler been changed to ondemand? I thought I saw where franco did some read/write tweaks to ondemand?

Thanks,

RF
[Samsung Galaxy Nexus] Schneewitzchen:
ondemand isn't a scheduler...ondemand is a governor.

I think osmosis mentioned that in previous builds the preferred scheduler was bfq. Franco makes deadline for default scheduler...and yes he tweaked some stuff to prioritize reads over writes.

https://github.com/franciscofranco/Tuna_JB_pre1/commits/4.1
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Yeah, typo, I meant deadline. Thanks.

RF
[Samsung Galaxy Nexus] mrdevil_25:
ok i didnt take screen shot of those one, i will keep monitoring my battery status and take screen shots again.

Thanks for the response!
[Samsung Galaxy Nexus] slvrarrow:
Loads of CM10 wifi kernel patches here https://github.com/cyanogenmod/andr...mmit/b4a0292089064fc2f37c874258d64ad902d9c3c0

Don't know if its of any use but theyre fresh today.
[Samsung Galaxy Nexus] daralph:
Hey Francisco,

298 is just amazing, thanks!

Take a few days off, the timing of 4.2 couldn't be better for you to start the #300series.

Not that much (student;)) but have a beer on me.

... 6012805
[Samsung Galaxy Nexus] 11768:
Curious that why is it that sometime even though the load is 100% yet the step still goes down to 386mhz / 729 mhz / anything lower than the supposed one and cause lag.

For example, sometimes during video recording (media profile is stock, no higher bitrate, etc) I notice it goes down to 386mhz even though the load is at 100% and cause lag (freeze). The replay of the video also confirm that it does indeed skip some frame (freezed).

Does not relate to camera alone only. In other cases like during launching of app, loading heavy website, etc.

Using CNA 3.8.0 + r298 (previous version has this problem too) :(
[Samsung Galaxy Nexus] nuwan32:
Try lowering go high-speed load and above high speed delay.
[Samsung Galaxy Nexus] Wh1t3Rose:
I seem to be losing 1.5% per hour during idle. Would my Nexus Live Wallpaper cause this idle drain?

•_•
[Samsung Galaxy Nexus] 11768:
I am using the default settings from r298, even the old setting which hispeed load of 50 face that occasionally. I think my only solution is to increase the min to 729mhz
[Samsung Galaxy Nexus] johno86:
Check your battery statistics to see which app is draining it..
[Samsung Galaxy Nexus] Langduscher:
just.wow :D

r298, 192-1228, performance governor, brightness @~60%
[Samsung Galaxy Nexus] SUTHRNFRIED:
Phone did a weird thing today and has stayed on 384mhz and barely went into deep sleep. No rogue apps running or anything like that. Its very strange...any thoughts? Its never done this. 298 nightly 384 GPU using osmosis/yellow setup.
[Samsung Galaxy Nexus] psycho2097:
thats just illogical...hows that happening? hows that even possibl?

need bbs screenshots to determine the cause.

whats osmosis/yellow, btw?
[Samsung Galaxy Nexus] androidkid311:
How Looooool! Performance governor as well.:-\ and such high brightness...
[Samsung Galaxy Nexus] Hatshipuh:
A similar thing happened to me recently too. While browsing, the screen went black and only a battery pull helped.

Restart after battery pull didn't work, it died during the boot up sequence, a sign of an empty battery.

After charging a bit it boots just fine again, but the battery stats are funny.

298 running on all default, Codename Android 3.8.0.

View attachment 1463718
[Samsung Galaxy Nexus] SUTHRNFRIED:
Its users Osmosis and yellowdie's current interactive settings and freq settings. Its been running fantastic until today oddly. Maybe I just need to reboot and give a new charge cycle. Screens are attached but not battery batt stats. I've never needed it so that's why I don't have those screens. The 192 freq was just set 45 mins ago. All other settings have been active all day.
[Samsung Galaxy Nexus] Langduscher:
Ask The Boss Man, not me :D I'm surprised as well, that's why I posted 2 cycles, to show it's no fluke :cowboy:

Try my settings for yourself :)

My phone's FASTTTTT and ridiculously battery friendly with my current set up :victory:
[Samsung Galaxy Nexus] Astug:
Any particular reason as to why screen off is set to 729 as default? I set it to 384 a few days ago and haven't had any probs.
[Samsung Galaxy Nexus] swayjd:
Don't be ridiculous, with performance governor that is simply impossible with a standard battery. And that's that. There is no trying anything. Avatar fits though.
[Samsung Galaxy Nexus] thedirtchamber:
Hey guys. Quick question: does this kernel work on stock 4.1.2 rom? Thanks. :)
[Samsung Galaxy Nexus] chickentuna:
Yes. You should seriously consider reading the 1st page

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tetrakinitis:
Yes
[Samsung Galaxy Nexus] thedirtchamber:
Sorry, I was reading the text from the downloads section and it says 4.1 ONLY, so I thought I should ask. :) Thanks, flashing right now.
[Samsung Galaxy Nexus] Langduscher:
I don't post often, and when I do, it's no bull ****

2100mah battery though - I'll give you that one (forgot to mention). Rest is what it is. Don't care for your opinion on these facts. Try for yourself, then report back. Gsus.... :laugh:

edit: you not believing it says something about you - not about me ;)
[Samsung Galaxy Nexus] Leegalaxy:
Me too actually, I was on my phone yesterday listening to music when it suddenly stopped play back. I thought the app was just buffering but it had actually turned off completing. I tried pulling the battery but that didn't work. I had just taken a screen shot of the battery life to post here because it was at 45% after 12 hours.

I took out the battery again and tried a different battery which worked. Couldn't get a last_kmsg.

Never had this happen before. Only thing differing on my set up is that I'm trying out the 4.2 leaked keyboard.
[Samsung Galaxy Nexus] pkgnex:
Random Shut-downs

Franco,

Just want to let you know I've had three random shut-downs since r298. I would put the phone down (nothing running), come back 10 minutes later and it was off. Not a reboot... phone just shut itself off. This had never happened to me before on you kernels and I've been using almost every nightly since r231.

I was running the stock settings when this happened, except screen off max was set to the new 537 slot. Starting late last night, I changed the min frequency to 384 instead of 192 and it hasn't happened again, but I'm not sure if the 192 slot was the cause... It was just my best guess.
[Samsung Galaxy Nexus] SUTHRNFRIED:
I doubt the keyboard has anything to do with it. I do know Franco has stressed many times about using lower frequencies will cause music to crash. Make sure screen off is set at a high enough value and I wouldn't mess with UV unless its either 192 or anything over 1.3. Let SR handle the rest.
[Samsung Galaxy Nexus] yellowdie:
Google's defaults are 729, and rightly so. Search the threads for 'race to idle'. Basically, if you limit how much your processor can do when the screen is off, then when the phone has to finish something before going into deep sleep, it's gonna take longer to finish it at slower speeds; therefore, you're going to spend more time with the CPU running and less time sleeping, so battery is used up more by having a lower freq. BUT then Franco comes along and says "Ya know what, Google? You were close, but you're just not quite as smart as I am." Thus, Boss Man blesses us with a step between the two that gives you the best of both worlds: it's fast enough to finish quickly, but uses less power (voltage) than the higher option. So, as far as I can see (and Franco and osm0sis) 537mV has become a fantastic (probably perfect) 'max screen off freq.' By default 729MHz is clocked to 990mV by SR, and Franco manually set 537MHz to 900mV. So that's a pretty good savings in the long run, but it still runs just as fast. That's also why I have 537 set as my input_boost_freq as well. I know Franco was testing that, but I haven't heard his results yet.

I believe you; makes sense with an extended battery. I get 4 hours with a stock battery by using 1036 as my max and it's just as fast. Did you actually mean Performance governor? As in your CPU is running at 1.2GHz nonstop? Because that basically takes all the settings, all the tweaks, all the research and just throws it out the window. Doesn't matter if you're running 192MHz as your min or anything else you change. :) Just seems really unnecessary to me. But that's me. You can totally run whatever you want, and the fact that you can get those type of results running Performance gov is impressive. Props to that. :laugh:
[Samsung Galaxy Nexus] slvrarrow:
is a higher screen off freq beneficial for battery life if you play alot of music/tunein with screen off?
[Samsung Galaxy Nexus] yellowdie:
Negative. Lower, but again not too low. 537 is perfect. :)
[Samsung Galaxy Nexus] AutomaticFailure27:
It's a "race to idle" issue. That's only as high as the frequency will go when the screen is off. The debate is that the higher the frequency, the faster it can get the process done and go back into deep sleep. Changing it lower will not harm it, but it will actually take longer to process information, thus in turn actually using more battery.

Plus, Google has 729/screen off stock. So just leave it.
[Samsung Galaxy Nexus] SUTHRNFRIED:
I hear an echo...
[Samsung Galaxy Nexus] Astug:
Makes sense, thanks guys. I'll set it to 537 aswell.

I tryed 537 as input_boost freq aswell but apps seem to open slower.

I'm running 729 as input_boost and 1036 as hispeed freq now, (the opposite of the default settings), works great.
[Samsung Galaxy Nexus] Hatshipuh:
As for me, I didn't make any changes at all, and left all kernel settings to default, no lower frequencies, leaving everything to SR, and still, went black at around 50% battery and didn't boot up because apparently the battery ran out.

Well let's see if it doesn't happen again.
[Samsung Galaxy Nexus] Raijin:
Shortly after entering the PIN, the phone slows down a bit. The screen flashes and applied my screen color settings.

Is it possible to start the Franco's app during the boot?
[Samsung Galaxy Nexus] osm0sis:
990mV? SR calibrated 729MHz to 1020mV here. :confused:
[Samsung Galaxy Nexus] yellowdie:
Odd... My 729 is 990mV (per Franco's Device Monitor tab) and 1036 is 1090mV. Haven't really checked the others. I have 384 set to 800mV.
[Samsung Galaxy Nexus] osm0sis:
hmm using performance governor and Franco's device moniter tab I set 729 as the max and it says 1020mV. 1036 is 1130mV. Nominal voltages are the defaults - 1150 and 1225, respectively. did you lower your nominals?

Also... franco did you enable some slight SR on the higher frequencies? 1804 with nominal 1450mV seems to be getting calibrated to 1410?

Edit: Narrowed down the issue. anything over 1410mV is paradoxically handled by SR again. Definitely seems like a bug. ;)
[Samsung Galaxy Nexus] Krayvon:
!

anyone using aokp with this kernel? if so, am i missing out or should i stay on cm10 :)
[Samsung Galaxy Nexus] Leegalaxy:
I actually am running all stock Franco Values. No OC or UV. No tweak in screen off frequency.
[Samsung Galaxy Nexus] shawnaye:
I am. All in well. Some don't like AOKP because of the features which may drain slightly more battery. But I've a spare battery for a reason. Hence I love my AOKP setup.
[Samsung Galaxy Nexus] Krayvon:
!

i feel you, i use to love it on my nexus s. i think its time to give my swag another try :P
[Samsung Galaxy Nexus] yellowdie:
I set my values to:

echo "1450 1425 1400 1350 1300 1250 1200 1100 1000 900 800 730" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

But mainly the reason I did that was to satisfy my slightly OCD side. :silly: I used init.d to set my 192MHz slot, so I had to echo out the whole chain, figured I'd use round numbers because I like them that way. But before doing that, I checked the SR running voltages and it was less than what I set, so I figured the only slot that's actually getting UVed by that is 192 and 384. 729 and 1036 shouldn't be affected by the "UVing" there.
[Samsung Galaxy Nexus] osm0sis:
Ah well there you go then, you set them lower than their normal calibrated values so now it's calibrating them even lower.

My OCD compelled me to level out the top end of the list. ;) So that's why I was just doing some crazy OC testing.

echo "1425 1375 1325 1275 1250 1240 1235 1225 1150 900 775 725" > /sys/class/misc/customvoltage/mpu_voltages;

And smoothing out the middle where my manually calibrated meets SR, I just set 1305 and 1228 to near their SR calibrated voltages. All running nice and stable for me so far.