yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AirBoss24K:
Noticed a significant decrease in battery life when I switched from 281 to 283. I don't change the phone settings very often and have a similar day to day schedule that wouldn't offset the results and noted that the battery life was better on 281 than 283. Running standard interactive settings.

281 - I got like 2.5-3 hrs of screen time.

283 - I barely made 2 hours of screen time.

Running these nightlies on my Gnex uisng CNA's 3.6.5 ROM release with stock battery.
[Samsung Galaxy Nexus] Magnus_CA:
Does milestone 5 have a 384 MHz GPU or 512? Is there a 384 MHz version?
[Samsung Galaxy Nexus] jcmm11:
Milestone is 384.
[Samsung Galaxy Nexus] I Am Marino:
Keeping 4G on all the time and complaining about battery life is null.

Turn off 4G most of the time IMO, you don't need it for most things and 3G is usually fast enough.

-Brought to you by Marino's Galaxy Nexus-
[Samsung Galaxy Nexus] Jerol7190:
IS it just me or is anybody else not been able to connect to their router since nightly 277?
[Samsung Galaxy Nexus] apaxi:
Why stop there? Go for 1xRTT!
[Samsung Galaxy Nexus] Wh1t3Rose:
WiFi works fine here on both 282&283.

Reboot your router. I know what you are gonna say. My other devices connect fine! Trust me 95% of problems are fixed with a reboot. I'm majoring in networking BTW

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] exzacklyright:
Any reason why my second cpu core is offline?
[Samsung Galaxy Nexus] franciscofranco:
Alright let's play a game (who doesn't love games?). I've been thinking about when should I release Milestone 6 and I haven't hit a consensus with myself. So this time I'll give you, the users, the power to make it happen sooner, or later. All you have to do to is make #francoKernel into the trending tags on Google+. Share it with your friends, family, girlfriend, boyfriend, Obama, NASA, just make it trending. If #francoKernel appears on the trending list I'll drop Milestone 6 in that very second. Show me what you got
[Samsung Galaxy Nexus] Citizen_Snips:
Seriously? We have to advertise you to get a new stable release..?

I don't even have Google+.......****
[Samsung Galaxy Nexus] TEK112:
I really hope that is sarcasm.
[Samsung Galaxy Nexus] Sleuth255:
I'm a few dailies back, however here's my final r281 remarks.

I was not able to reproduce any voice call issues with a land line so it looks like the half-duplex problem I commented on earlier was, in fact, my home VoIP system.

Most importantly:

Today is the second day in a row that my phone has dropped the data connection (blue bars turn grey). This happened very consistently on Milestone 5 and was non-existent on r277. Reboot fixes. I live in a pretty good 4G coverage area but do have occasional 4G-3G, 3G-4G handoffs. My data connection is very active throughout the day due to exchange services.

I'll be leaping off r281 to the current nightly itnf.
[Samsung Galaxy Nexus] al2x:
Francokernel app is FC'ing sometimes with the newest BB Android 4.1.2. Any update on a new kernel for the new update?
[Samsung Galaxy Nexus] Natolx:
I'm not sure if that battery technology is different, but the Toshiba Thrive Tablet fast charges( a/c adapter) its gigantic battery in 1.5 hours from 0-100% and doesn't have any problems with battery health that I can tell.

---------- Post added at 05:46 AM ---------- Previous post was at 05:32 AM ----------

Franco, I am having trouble with your kernels permanently(until I reflash a nandroid backup) corrupting the sdcard partition in some way.

After wiping dalvik cache and flashing your kernel, Poweramp is unable to play music files because the "Folder is missing or not readable" Interestingly, flashing back to my other kernel does not fix this, but going back to the nandroid backup prior to flashing your kernel does.

I have been able to repeat this issue.

Edit:To clarify, this problem occurs even when opening a music file with root explorer
[Samsung Galaxy Nexus] Ma5heen:
Lovin it

I love what you did here, Franco. This kernel fixes the wake cycles and allows the Redemption ROM that I'm using to run butter smooth.

Quick question to you, or anybody browsing this thread. Are there options to undervolt using this kernel? Also I was wondering the pros/cons of undervolting besides increasing the battery life a bit. Are there downsides, is it recommended and most of all, how can it be done using any of these builds?
[Samsung Galaxy Nexus] RonnieRuff:
It is UVd and there are no options to change the UV settings

Bounced off a cell tower near you by ICS and my Galaxy Nexus. Zoom Zoom
[Samsung Galaxy Nexus] fred fredburger:
My phone seems to be hanging on the Google unlock screen after flashing the new kernel. Last night I ran a nandroid backup of my system before switching from bigxie's IML74K ROM to AOKP. AOKP rebooted my phone periodically so I restored from nandroid backup (back to bigxie's AOSP ROM) this morning and all was working well. I installed Franco's market app, rebooted into Recovery, cleared Dalvik cache, and flashed 9.2. When it rebooted it just hangs at the Google unlock screen. I have tried to boot it while it's powered by a wall wart and with no external power. I have also tried to flash a franco nightly from a few days ago and the symptoms remain.

I was running a franco kernel with bigxie's ROM earlier this week and it installed and ran great.

Any ideas? Do I need to clear the "regular" cache and not just Dalvik cache?

Thanks!
[Samsung Galaxy Nexus] HoOnZ:
Default to this kernel is 700MHz/1200MHz but I was able to UV it more to 350MHz with Franco's Kernel Updater which I purchased in the Android Marketplace. Like you I'm interested to know if there's a reason he set the default UV speed to 700MHz and not 350Mhz.

Any drawback for me to UV it to 350MHz using Franco's Kernel Updater?

JOhn
[Samsung Galaxy Nexus] mcampbell:
I think you mean underCLOCK, not undervolt, right?
[Samsung Galaxy Nexus] fred fredburger:
FYI: I also tried to flash the Apex kernel listed in bigxie's ROM thread (here) and I had the same symptom. So, it appears it's not specific to franco's kernels but any. Am I missing something in how a kernel is supposed to be flashed? Like I said, I'm booting into recovery, wiping the Dalvik cache, installing the kernel .zip from sdcard. I seem to be stuck in between "reboot" and "profit." :)
[Samsung Galaxy Nexus] jknisley:
That's underclock, not undervolt. And no, the kernel already undervolts our processor a wee bit, but too many people have had severe stability issues with undervolting it any more than the kernel does automagically.

Underclocking to 350MHz just makes it a little laggy on screen up if it's your base. There's also the possibility of using more power since it keeps having to ramp up to higher states. There's a whole discussion about this GSM thread for this kernel. Since they're both the same, I'd take a look.
[Samsung Galaxy Nexus] fred fredburger:
It looks like the boot issues I experienced was due to ClockworkMod Recovery Touch Alpha 2 (which I had flashed this morning). I was unable to flash the bigxie ROM from the new recovery due to an assert error. Once I went back to the original CWM the bigxie ROM flashed just fine, as well as the Apex kernel and franco's 9.2.

Thanks for your contributions, Francisco! They're greatly appreciated by everyone!
[Samsung Galaxy Nexus] Niviac:
Turning off auto rotate stopped the awake problem for me.
[Samsung Galaxy Nexus] xXJay_RXx:
You're supposed to wipe the cache too thats right under the wipe data option. I'm not sure if that will solve any problems but I always wipe cache and dalvik cache when I flash a new kernel
[Samsung Galaxy Nexus] fred fredburger:
That's good to know. Earlier in this thread someone mentioned only the Dalvik cache, and in the thread for bigxie's ROM (here) it only mentions the Dalvik cache.

I'll be sure to wipe both caches before flashing a new kernel.

Thanks!
[Samsung Galaxy Nexus] sinik420:
you'll also meet people that tell you to do this when flashing a new rom and others who never do a wipe lol its always safer though sometimes gets tedious for some people. just dont forget to reflash the kernel after flashing an update if you do nightlies, if you do this then wiping dalvik is unnecessary
[Samsung Galaxy Nexus] hajabooja:
Just flashed the latest and is running great. Just wondering if everyone is sticking to the Conservative governor? I typically go with Interactive, but Franco seems to be really recommending the default Conservative. Seems to be really quick even on Conservative.
[Samsung Galaxy Nexus] RonnieRuff:
Just will nit do much since the voltage T 700 and 350 are almost the same. He said it was more stable. I tend to follow his leads.

Bounced off a cell tower near you by ICS and my Galaxy Nexus. Zoom Zoom
[Samsung Galaxy Nexus] bowsersoulstar:
Moved over to Franco's 9.2 build and a brand new freshly wiped and flashed ROM (AOKP build 13).

Since I had so many variables on why my battery life sucked so bad previously, I decided to go get off my lazy ass and start fresh.

Still testing but by far, this has been the first time since I got a GNex where my screen-on graph almost is parallel with the awake graph in the battery stats. Basically, I had stellar battery performance. Even in my work office, where reception is usually shoddy, battery drain on idle was great.

My real test will be when I sync Exchange. It wasn't until last few days where I read and read about kernels/roms/battery... I realized a lot of people had bad battery life with Exchanged set on PUSH. This is something I do regularly and had no idea its a potential battery chugger.

So without Exchange, it seems I get stellar battery. In other words, the kernel is awesome and everything's been running smooth and stable so far. Going to be traveling a bit throughout the state today so turning on Exchange sync today wouldn't be a good test since I'd likely go through multitudes of different reception quality.

If somehow after syncing Exchange, I still get great battery, I finally found my working combination.

Either way, thanks Franco for the awesome build you have so far.
[Samsung Galaxy Nexus] donlad:
The reboot function in GummyNexus 0.4.2 does not work with nightly 9.2

EDIT: Please ignore. It must have been a fluke but it's working now.
[Samsung Galaxy Nexus] notphilip:
Awesome kernel, bought the donation version to support you!

What roms are you all using with this? I really want to get my battery drain down to 1%/hour while idle. I'm using gummynex 0.4.2 now with this kernel, juice defender on balanced profile, 4g disabled, location services disabled, nfc disabled, bluetooth disabled, and wi-fi on.
[Samsung Galaxy Nexus] 2015Ducatimulti:
I must be doing doing some thing wrong, I wipe cache, wipe dalvik, and installed the kernel and my phone won`t boot, just sits at the google screen, I`m rooted and unlocked bootloader, any advice?
[Samsung Galaxy Nexus] sinik420:
Posting rom would help
[Samsung Galaxy Nexus] kevguillot:
Oh well hell didn't know that screen was available. I'll do it next time.
[Samsung Galaxy Nexus] bleeeeeeek:
Purchased it today with no problem..
[Samsung Galaxy Nexus] psohn:
I have the hotplug enabled but I'm not noticing any battery change. I'm running AOKP M2 & Juice Defender with the conservative governor 700/1200. I have the VZ LTE GN.

Anyone else have the same experience or are you seeing significant savings?
[Samsung Galaxy Nexus] Flip35:
Quick question guys is build 12 has good batt life also? reason I am is because build 11 is awesome with battery life n smooth and I've seen build12 is Been out so I haven't really seen anybody has been complaining about batt
[Samsung Galaxy Nexus] sway40:
This is stupid question and ive looked for the post and on my phone, but how do you enable hotplug???

~ Sent from my Galaxy Nexus running Cm9~
[Samsung Galaxy Nexus] sinik420:
reading op

* Hotplug cpu1 is implemented somewhere else:

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

cpu1 does not shut down on screen_off: echo 0 > /sys/module/dsscomp/parameters/hotplug_enabled
[Samsung Galaxy Nexus] Rules.r:
Good evening (subjectively) all.

I've just recently encrypted an HD 2.* ROM on my Nexus. After encrypting the device today, it appears I have no access to the SDCard in CWR.

Can anyone give me any advice? How do I unencrypt (if I must) or fix the situation?
[Samsung Galaxy Nexus] TMFGO45:
I think that is personal preference. Do it, and if you get better battery life with no lag, then keep it. Otherwise, don't worry about it.

Swyped from my Galaxy Nexus (Codename Android 1.1.1, franco.Kernel, NateModz w/ fast glow, Inverted Gapps, Nova Launcher, 1200/350) in Tapatalk Pro!
[Samsung Galaxy Nexus] psohn:
If you get the market app you can enable it by checking a check box.
[Samsung Galaxy Nexus] wayneb02:
what exactly does enabling hot plug do?
[Samsung Galaxy Nexus] Stockmoose16:
I get that the kernel can finish processes faster with a 700 mhz min, but if you're a heavy user, won't this crush the battery? It means that even when you're doing the most basic of tasks, the phone is running at a higher than normal frequency.

Also, I don't understand the hype on this kernel. I'm not getting considerably better battery life than I got on stock 4.0.2 rooted. I drain approximately 4%/hr with the screen off and 4g on. With wifi on and screen off, I drain approximately 2%/hr. Franco said he can go 8 hours with no battery drain in an earlier post. How is that possible?

I've checked my cpuspy stats, and my phone stays in deep sleep most of the time when the screen is off. Also looked at BBS and didn't see any major wake locks.

So what am I missing? How do I get my phone to drain 0% in 8 hours?
[Samsung Galaxy Nexus] mike216:
No the cpu clock is 700 but there are several idle states

Kind of a noob myself but 700 seems good on battery for me
[Samsung Galaxy Nexus] EyeOfTruth:
The easiest way would be to set the min speed for your processor to 350mhz and then use cpuspy and see how much of it lands in that bracket.

I think Franco is running the GSM version and the HSPA+ has better battery life.

If your a heavy user more than likely the 300 mhz wouldn't get used much. Also do you have hotplug enabled and then are you opening the camera after each boot and closing it?

Also have you tried changing your Governor?

2% and hour your phone would last 50 hours

This is from verizons site

Standard Battery – 1850 mAh

SAR: Head: .63 W/kg ; Body .88 W/kg , Product Specific Use: 1.01 W/kg, Simultaneous Transmission: 1.39 W/kg

Standard Battery: Usage time – up to 12 hours; Standby time – up to 150 hrs hours

I want to know how Verizon gets the 150 hrs of standby.
[Samsung Galaxy Nexus] BankZZ:
How do you enable hotplug?
[Samsung Galaxy Nexus] Elganja:
http://xdaforums.com/showpost.php?p=20923642&postcount=1
[Samsung Galaxy Nexus] franciscofranco:
Update is up. Enjoy.
[Samsung Galaxy Nexus] masri1987:
Thank you
[Samsung Galaxy Nexus] BradleyUffner:
I love big updates! Thank you Franco :)
[Samsung Galaxy Nexus] Tree of Knowledge:
So I'm not seeing the camera issue that was affecting battery life in the OP anymore. Does this mean it's been officially resolved?
[Samsung Galaxy Nexus] stevessvt:
Whats a good baseline for UV? Im running 350@800 700@900 920@1000 1200@1100 1350@1200. How much lower is realistic?
[Samsung Galaxy Nexus] TEK112:
Milestone 6 will be out momentarily. As for the app FCs, trying clearing the apps data (you will lose all app settings) and see if it FCs again.
[Samsung Galaxy Nexus] franciscofranco:
It was just a small game for some social interaction, don't see a problem, M6 would get out eventually... geez.

Milestone 6:

* Merged all patches related to 4.1.2

* Fixed the famous data drops by tricking Smartreflex to not overly calibrate certain hardware parts

* Added custom changes to lowmemorykiller driver to force the device to have a certain amount of free RAM to sustain smoothness over the time

* Made the launcher unkillable by the lowmemorykiller driver to prevent redraws or widget crapping itselfs

* Added a new governor called dyninteractive - this is similar to interactive in 99% but instead this new governor dynamically adapts its own tunables and settings depending on the system load.

* Increased Interactive governor kernel priority thread for the frequency change task - more smoothness

* Added a new tuneable for Interactive governor called input_boost_freq. Path is here: /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq

* Added all TCP Congestion algorithms presents in the kernel. To check all algorithms run this command on the Terminal/ADB Shell: sysctl net.ipv4.tcp_available_congestion_control

To change the algorithm: sysctl -w net.ipv4.tcp_congestion_control=NAME_OF_THE_ALGORITHM

* BFQ IO scheduler updated from v4 to v5

* Added other smaller but still relevant changes available on my github repository
[Samsung Galaxy Nexus] bigbear6708:
Awesome change log Franco!!! I can dig every single thing in it!!! I have been using you kernel religiously since i found it and refuse to try another as it has been treating me that good...Thanks!
[Samsung Galaxy Nexus] fullmetal509:
Currently running CNA 3.6.5/ Franco 276 Nightly 384gpu.

Do I have to have wipe anything before installing Milestone 6?

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] jcmm11:
Just a note to say that blue bars turning grey is not a dropped connection. Connection is still active, however a connection to the Google servers has been lost, which will probably impact some of your Google services, but normal internet access should be fine.
[Samsung Galaxy Nexus] Jerol7190:
No, i am sure it's the nightly because when I switch back to 277 it works just find, but because the change log wasn't posted i had no idea what was changed.
[Samsung Galaxy Nexus] TEK112:
So.... you're not gonna reboot your router? :confused:
[Samsung Galaxy Nexus] bigbear6708:
Ill tell ya...my wife and i both have gnexus...hers is completely stock,i run franco kernel...latest night currently...when my WiFi goes out, so does hers...router reboot fixes is both 100% of the time
[Samsung Galaxy Nexus] Sleuth255:
True, but its a good way to quickly tell that the data connection may have dropped since Google services don't go down often. In my case I verified that all data connectivity was lost using multiple apps.
[Samsung Galaxy Nexus] ramerco:
Franco,

How does this impact those of us using non-stock launchers or lockscreens? e.g. Nova Launcher and Widget Locker. Can those be added to the "unkillable" list as well?

Thanks for all the hard work, as always!
[Samsung Galaxy Nexus] iluvamk:
Is hotplug option still available? Didn't see it in kernal updater.
[Samsung Galaxy Nexus] jcmm11:
No, and it hasn't been for quite a while. Apparently (IIRC) the kernel will automatically take a cpu offline if it's not needed so the option was redundant and Franco removed it.
[Samsung Galaxy Nexus] murtezahu:
I have the same question. Thanks again for your work!
[Samsung Galaxy Nexus] bigbear6708:
How does everyone like m6???
[Samsung Galaxy Nexus] rjkxb2:
Running amazing on paranoid android. Not that its a huge deal but by far my highest benchmark scores too. So much buttery goodness
[Samsung Galaxy Nexus] davidukfl:
anyone else getting dropped data randomly?
[Samsung Galaxy Nexus] Sleuth255:
I now believe there is a kernel issue with voice calls. I thought it was my VoIP system but I've had 3 instances of this now from various sources. Especially noticeable on M6. Phone rings, I pick up and can hear myself when I talk. It's like the mic is looped to the speaker. The other party can't hear me. Or, I'll call and the other party can't hear me. I do have a VoIIP profile configured on my phone but it is set to Internet calls only, and not set to receive calls. The SIP profile therefore is not normally active.
[Samsung Galaxy Nexus] pedxing:
Yes! Finally! My battery life is back. It's been getting closer and closer, but nothing like aokp and fraco for ics. Now I'm on cna 3.6.6 and Franco milestone 6.

The following was for today while on WiFi but with 4g on. Bluetooth and GPS off. Screen on time included basic browser use, g+, and ereading. So light use but a lot of it.
[Samsung Galaxy Nexus] Grizzly420:
Can someone give me a link or somewhere to learn about the TCP congestion avoidance setting? I think list about GUI but non sure. Just hate messing with settings with no knowledge
[Samsung Galaxy Nexus] Wynnded:
Here's the best.... http://bit.ly/RrbJkO
[Samsung Galaxy Nexus] AirBoss24K:
How are you getting those ridiculous screen times? I'm using pretty much the same thing (3.6.5 and Milestone 6), but not getting numbers like that! Teach me the ways of the fantastic battery O_O
[Samsung Galaxy Nexus] pedxing:
Here are my tips:

1. Set display brightness to auto. Right now I have no other tweaks to the brightness level, just stock.

2. I've got it undervolted to the following. I know smartereflex is supposed to take care of this, but it apears to make a difference anyway:

384 mhz = 850, 729 = 925, 1036 = 1025, 1228 = 1125.

3. I use NFC and Tasker to contol turning on and off various sensors like gps/bluetooth (on in car off everywhere else), wifi (the opposite of gps).

4. Try to control Google Maps as much as possible. Turn off location tracking, sign out of Latitude. If you want to use Google Now for stuff like weather and travel times that fine, but enter your home and work addresses manually. In location settings turn off the last check box for location and google search. Also sign out of the google home page on the stock browser and chrome.

5. Turn off Instant Upload on G+. I still have G+ installed but I use an app called FolderSync to do the same thing but on a schedule I chose to my own private cloud server.

6. Limit the use of updating widgets ...I use only minimal text for weather (2 hour updates) and Agenda Widget+ for calendar.

7. I have 3 mail accounts: exchange, gmail, and another IMAP one. Exchange and gmail are set to push. The IMAP set to sync every hour.

8. Use BetterBatteryStats to determine if you have wakelocks. Optimum awake time is equal to 5% more than screen on /active time. E.g. if your screen on time is 40%, a great awake time is 45%. If it's within 10% that's still good and you shouldn't stress.

9. If you have a lot of wakelocks either a)remove the offending apps, b) try reinstalling them, c) start with a clean wipe and reinstall the rom. This is a last resort: I've been dirty flashing CNA since 3.3.

Good luck!

---------- Post added at 07:58 AM ---------- Previous post was at 07:53 AM ----------

Oh, also: Screen off max is 729mhz.
[Samsung Galaxy Nexus] Grizzly420:
Thank you very much. I found a few links but nothing good. So I appreciate this
[Samsung Galaxy Nexus] sway40:
If you're on just Wi-Fi, you can get screen on time like that, it's not hard. The goal is getting that while on 3g/4g and maybe some Wi-Fi, since 4g is impossible on our phone to get screen on time like that it's up to 3g. I pulled off real world battery yesterday with m6 and got 3hrs screen on time and 18hrs on a charge with 85% 3g use and the rest Wi-Fi, that's decent battery. Stock clock, stock settings, data on constantly at half brightness.

Sent from my paranoid Nexus 7
[Samsung Galaxy Nexus] bigbear6708:
I love me some Franco kernel..but even after a clean install of a new rom, milestone 6 keeps locking my phone up.
[Samsung Galaxy Nexus] notoriousB:
Me too, incoming calls hang my phone completely with M6. I got the calls this morning and the phone would not answer, in one case the phone stopped ringing, hung, and then rebooted. Soothe the phone just kept ringing after i answered and then rebooted. The third i just gave up and yanked the battery.

Something is big time wrong with this milestone. Back to nightly 276 that was on my sd card and no more problems.

Edit: and I'm not on voip, this is regular cell service.
[Samsung Galaxy Nexus] Citizen_Snips:
Milestone 6 works fine for me. Verizon network. I make and get calls everyday. Maybe try the new nightly, r290
[Samsung Galaxy Nexus] TEK112:
Wipe caches and reflash.