yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] scadilla:
I had WiFi issues with 250 as well. I noticed I could not connect to our 802.1x flashed back 249 and had no problems.
[Samsung Galaxy Nexus] BOY_:
Same here, no WiFi on the current nightlies.
[Samsung Galaxy Nexus] aggrophobik:
I didn't seem to have any issues w/ r250, but handoffs to wifi on r251 don't seem to be working. I I have to manually disable, then enable wifi and it seems to pick up fine.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jonstrong:
Weird. I'm really getting excellent results with franco -- 249, 250 and now 251. I had played with a couple of Trinity, a couple of Air kernels and a few leanKernel releases... I'm consistently having the best results with these franco's -- both with performance, and with battery drain. I seem to be getting about 15 or 16 hours, with something in the range of 3 hours or more screen time, sometimes closer to 4.
[Samsung Galaxy Nexus] :
What's the best screen time you've got with Franco's Nightlies? And do you have the extended 2100 mah battery?
[Samsung Galaxy Nexus] jonstrong:
I never pushed to the limit...so I can't be certain if the rate of battery consumption changes toward the end. I've had these close to 4 hours...but never ran the battery below about 19% over the last few weeks, so I don't know the absolute limit. If I extrapolate, e.g., I might have had 2 hours screen time and 8 hours run time when the battery hit 50% (pretty typical), it appears that I might expect something like 15 or 16 hours with about 4 hours screen time if I push it to the limit.

BTW: this is with typically a mix of Wi-Fi, 3G and 4G/LTE, a few phone calls, several emails and text messages and a bit of web browsing. Also:

using Trickster MOD with the franco nightly

Screen State kernel task scheduler turned on

I/O scheduler = deadline

governor = ondemand

CPU range 230400 to 1228000

Max screen off CPU at 384000

all SmartReflex controls on

Voltages defaulted

Screen:

Content adaptive brightness turned on

Gamma adj = 5

Color profile = franco

Auto brightness = on

...and I'm getting very similar result with GPU 384 or 512 versions - I'm probably not exercising the GPU with my typical use.

EDIT: almost forgot: yes - this is with the 2100 VzW OEM extended battery (been using this since the week they made it available)
[Samsung Galaxy Nexus] :
Oh Wow. Very nice. I should try this out.

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] hawkinsandponcho:
Trying this out thanks.
[Samsung Galaxy Nexus] Alton (Halo 2):
GTA still isn't working for me after flashing the fix
[Samsung Galaxy Nexus] :
Maybe a problem with the ROM?

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] JimmyJayCEO:
I flashed the Milestone 5 kernel last Friday (running the AffinitySeries beta1 ROM and I must say that I am loving the battery life so far. I also set up JuiceDefender and am using the balanced setting nothing else. I have definitely seen improved battery life and nothing went wrong with the ROM. Just wanted to say thanks Franco and good job! :good::cool:
[Samsung Galaxy Nexus] :
Hmm I was getting okay battery life on Milestone 5. But r249 is really good and after 9 hours with some screen time I had 83%.

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] hawkinsandponcho:
Using these exact settings CNA 3.5 and r251 384 GPU I am about 15 hours on battery 1.75 hours screen time and 12% remaining. LTE on, nothing else on (WiFi, GPS, NFC). Not bad. I don't think I used the screen heavily enough today. More testing this week.
[Samsung Galaxy Nexus] wtherrell:
Would you share your settings?

Would you mind sharing your settings? Assuming you are using Franco Kernal Updater. I can't seem to get the better battery life everyone else is talking about.
[Samsung Galaxy Nexus] Hotstuff5964:
vbs-tuna_oth is killing my battery hard. Is this a kernal thing?
[Samsung Galaxy Nexus] johall07:
I'm getting constant fc with the kernel app when trying to select set CPU setting on boot. When I restart the app it will be checked and when you uncheck no fc.
[Samsung Galaxy Nexus] Xfanatic:
Update the app.

Allons-y
[Samsung Galaxy Nexus] TEK112:
Wipe the apps data and try again.
[Samsung Galaxy Nexus] :
I have :

Max CPU : 1227 MHZ

Min CPU : 384 MHZ

Governer : interactive

Screen Off Freq. : 729 MHZ

P.S. : No color modifications. And stock 1850 Mah. Battery.

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] hawkinsandponcho:
with the newest nightly today i'm trying a mix of these settings and the ones for Trickster MOD jonstrong posted.

using the Snap Black ROM, jonstrong's settings, and nightly 251 I only got about 1 hour and 15 mins of screen time yesterday.

Flashed back to vanilla CNA 3.5.0 due to some SystemUI FC's and flashed newest nightly at 384 GPU and things are looking quite good battery-wise so far.

Thanks all who have posted their settings.
[Samsung Galaxy Nexus] jonstrong:
Yes...both ROM and kernel are going to impact battery. I'm also using the 384 GPU versions from franco. Just flashed 268 and rebooting as I type this. Intrigued by description of "dynamic interactive" - going to give that a try.
[Samsung Galaxy Nexus] hawkinsandponcho:
Yep getting much better life on 262 and 3.5.0, will try 268 as well.
[Samsung Galaxy Nexus] :
What are you guys getting with r268? Screen time? Stand-by? What settings/radios do you have enabled?

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] Xfanatic:
I am currently at 5% and have 28.5 hours with 1 hour 45 minutes of screen time. I am using Affinity Beta 1 and have the 2100 mAh battery.

Allons-y
[Samsung Galaxy Nexus] :
Really? Only an hour and forty-five minutes of screen time? What settings/radios do you have on?
[Samsung Galaxy Nexus] Xfanatic:
I have the newest radios and default Franco with dyninteractive governor. I usually only average somewhere between 2-3 hours on screen time. I think that's acceptable with 25-30 hours on battery.

Allons-y
[Samsung Galaxy Nexus] :
Oh ok,

I also tried the dyninteractive governer. It doesn't get me as good battery with just plain interactive. I think this is because it changes its tunables by the system load. So, when you are using the phone it raises the CPU usage. The interactive will give you better battery life I think. Switch to interactive for a day, set the Min CPU to 384 Mhz, and the Max CPU to 1200Mhz, for a day and tell me how it goes. I think you'll get better results. I'm also thinking about getting the 2100 Mah. Extended Battery. Is it better than the stock battery?
[Samsung Galaxy Nexus] Xfanatic:
I have used the interactive governor on previous nightlies and get the same results. I have used several different ROMs, and when I first got the larger battery I was running stock and was seeing the same battery life. I will say that this charge probably could have yielded better on screen time but I have the brightness all the way up. I usually keep it at about 25%. I will drop it down and report back in a few days.

Allons-y
[Samsung Galaxy Nexus] jonstrong:
I've been trying dyninteractive and my impression is that it eats battery faster than ondemand or interactive. Going back to ondemand with CNA 3.6.0.

Sent from a Galaxy Nexus far far away...
[Samsung Galaxy Nexus] :
Same here. Its just how it manages the CPU.

~Sent from my Galaxy Nexus VZW

---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------

Sweet, can't wait.

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] bigbear6708:
So far on 268 running on 1228/240 interactive, i am at 50 percent left with 1 hr 40 min screen time. Wifi whole time.lots of my kids playing angry birds today. Stock battery
[Samsung Galaxy Nexus] jonstrong:
Way too early for anything conclusive...but of course I'm trying to figure this out as I go...

Dyninteractive sounds great, and was very responsive, but seemed to drain the battery faster than I had expected. Ondemand was responsive...but when I looked at CPUSpy, it seemed that only the bottom two and top CPU slots were being used -- two intermediate speed slots never seemed to be used. Battery life still didn't seem to be as good as I expected based on earlier franco experience.

I'm going back to interactive to see how that does. From the little reading I've done, my impression is that it won't necessarily ramp up to the top speed immediately when the device is used -- perhaps a more gradual ramp up...? Perhaps a bit more conservative than ondemand?

Time will tell...
[Samsung Galaxy Nexus] moos3y:
Codename Android 3.5.0

Franco Kernel Milestone 5

[Default settings - 1228/384 Interactive]

Newest radios FF02/FG02

2100mah extended battery (edit)

~11 hours of battery life

~4.5 hours of screen time

My usage consisted of being on Facebook, Instagram, Twitter, Chrome browsing, and on reddit (Baconreader) + Major Mayhem game time
[Samsung Galaxy Nexus] :
Agreed,

Dyinteractive doesn't offer as good battery life as the normal interactive.

---------- Post added at 08:07 PM ---------- Previous post was at 07:53 PM ----------

Hmm... that's impressive. Do you have the extended 2100 Mah battery?
[Samsung Galaxy Nexus] moos3y:
Yes, I do :)
[Samsung Galaxy Nexus] jonstrong:
franco #273 up. Minor changes it seems - reduced number of steps on 512 GPU version (eliminate 384).

No impact on me, but I like to keep up to date...just flashed... :)
[Samsung Galaxy Nexus] iviustang50h:
Wow - I can barely get 2.5 hours with the 2100 battery. I am using a different ROM, but would that effect battery life that much? My brightness is at 50% by the way (I disable auto); what's yours?
[Samsung Galaxy Nexus] TEK112:
The ROM is a huge part of it. Changing roms for me with Franco's kernel has literally been the difference between 1hr and 3hrs of on screen time.
[Samsung Galaxy Nexus] iviustang50h:
Jeez, I had no idea. I have flashed almost every ROM out there (except Codename, go figure) and the impact on battery life was negligent. I'll give it a go, though, especially if I can eek out some more battery life. There are so many great and smooth ROM's and kernel combinations that now my main focus is battery life with the screen on. Thanks for the advice.
[Samsung Galaxy Nexus] I Am Marino:
As JB ROMs mature, my battery has decreased viciously, I used to pull 5+ hours screen on, now I can't pull 3, no matter what combination I use.

And all of these high screenshots are wifi only, anyone pulling 4+ hours with mostly 3G, if so, what's your combo?
[Samsung Galaxy Nexus] exzacklyright:
I can't pull 3 hours either
[Samsung Galaxy Nexus] SomeGuyDude:
I've never pulled 5+ hours of screen on time with ANDROID, let alone this device. :confused:
[Samsung Galaxy Nexus] I Am Marino:
ICS was way better than JB in battery.
[Samsung Galaxy Nexus] hawkinsandponcho:
flashed back to milestone 5 from the more recent nightlies to see if i could get close to what these other people say they are getting for screen time.

and yep, 2.5 hours is pretty much the max.
[Samsung Galaxy Nexus] iviustang50h:
Last night I achieved nearly 3 hours of on-screen time and 17 hours of battery life; this was using r268-384. Has anyone tried any of the other nightlies since that one? I'd like to flash one and try, but I'm worried battery life will be worse. Has anyone had great battery life with any of this week's nightlies?
[Samsung Galaxy Nexus] jonstrong:
I tried 272, 273 and 275 installed. My impression is that they may not have been making as good use of the different CPU slots as 268. Now, with 276 installed for a few hours, as I peek at CPUSpy, and I can see that the kernel is making very good use of the slots:

1228 mhz - 1%

1036 mhz - 1%

729 mhz - 2%

384 mhz - 7%

230 mhz - 12%

deep sleep - 74%

This is exactly the kind of usage curve that makes sense to me. This is with #276 and the Interactive governor, and similar to what I was seeing in 268. I'll give it aday or so to see how it does - but this is very promising.
[Samsung Galaxy Nexus] kuronosan:
Anyone else having issues with wifi on cm10?

Didn't start until 270s for me.
[Samsung Galaxy Nexus] iviustang50h:
Very helpful - thanks. I look forward to your further findings.
[Samsung Galaxy Nexus] kuronosan:
Regarding the wifi - it seems like it's a cm10 issue as it works on aokp.
[Samsung Galaxy Nexus] :
Agreed, on AOKP it actually works extremely well.
[Samsung Galaxy Nexus] JohnKuczek:
I'm on cm10 9/26 and 275 and no wifi issues. What exactly are you experiencing?
[Samsung Galaxy Nexus] dcorrea:
Color Settings

I just installed Milestone 5 with the latest Bugless Beast release in the hopes of improving battery life. I purchased the updater app mainly to get the color profile options since i plan to leave the governor and other settings at stock. After digging through this thread, it seems that earlier versions of the updater app had Franco's recommended color settings, but the latest version doesn't seem to have that.

Can anyone tell me what Franco's recommended settings are?
[Samsung Galaxy Nexus] jonstrong:
You could cheat by installing Trickster MOD, selecting "franco colors" and seeing what the settings are...

In the franco installer with a newly installed franco kernel, the defaults appear to be:

Color Multipliers: Red 180, Green 192, Blue 200

RGB Gamma: Red -4, Green 0, Blue 5

Trickster MOD set to franco color profile comes up with the same values - so I'd say these are probably right.
[Samsung Galaxy Nexus] I Am Marino:
How's 276 for people?
[Samsung Galaxy Nexus] chrisanthropic:
I'm on 276 (512) and Cyanogen nightlies and got 18 hours battery, 1.5 hours screen on time, and still sitting at 40% battery left yesterday. Using interactive governor and standard battery. Mostly at home on Wi-Fi, but I'm very happy with Franco.
[Samsung Galaxy Nexus] :
So far so good. Been getting pretty awese battery life. Even with 4G and WiFi! I think its because of the voltage changes and bug fixes etc. Can't wait for the next stable build!

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] jonstrong:
276 been very good for me too...loving it with CNA...
[Samsung Galaxy Nexus] :
I'm wondering if CNA is good or AOKP is better... Is the battery life better? Can you give me some stats on your battery life? And, do you have the extended or stock battery?
[Samsung Galaxy Nexus] I Am Marino:
Even without the usual 3 days of testing of this kernel, anything I put with CNA seems to be better battery than AOKP currently.

I was a normal AOKP user and then each build got progressively worse on battery so I'm off it until a milestone comes around.
[Samsung Galaxy Nexus] fullmetal509:
I'm on the same boat my friend

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] :
Alright, what's your usual day on battery?

Ex.

Radios on? (4G, WiFi, 3G etc.)

Standby Time?

Screen On Time?

What build of CNA?

What kind of activity? (Texting, E-Mail, Games, FaceBook, etc.)

Extended Battery?
[Samsung Galaxy Nexus] I Am Marino:
WiFi and 3G.

About a day of standby.

3 hours or so of screen on.

3.6

Texting, some web browsing, tapatalk, taptu.

2100 battery.

These same setups got me almost 5 hours screen on for ICS, since JB, not even close.
[Samsung Galaxy Nexus] notoriousB:
My overclock and governor settings don't persist through reboots. They're always right back to default values after a reboot. On 276 now, latest Franco app, options to apply CPU settings and governor control on boot are checked. Rom is jbsorcery 2.3.

Am I missing something obvious? Or is this by design? Or am I just a moron? Thanks in advance.
[Samsung Galaxy Nexus] nativesmiley:
which kernel has the ability to configure the trinity contrast and gamma colors? im on 276
[Samsung Galaxy Nexus] :
Hmm. Make sure EVERYTHING is checked for sticking on a reboot. If it still doesn't stick, then uninstall and re-install.

~Sent from my Galaxy Nexus VZW

---------- Post added at 09:16 AM ---------- Previous post was at 09:16 AM ----------

This kernel. Lol. Use Franco's Updater app on the Play Store.

~Sent from my Galaxy Nexus VZW

---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------

Hmm... I may consider switching, is the performance good? Does it lag at all? Is it the newest build of JB (JRO030?).

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] I Am Marino:
Performance is fine.
[Samsung Galaxy Nexus] :
Thanks, I just switched and I have to say, its doing pretty good so far!

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] tbis:
277 with baked ROM 5 is fantastic.
[Samsung Galaxy Nexus] notoriousB:
Figured out my problem - I had "balanced" power mode selected. That sets the governor and frequencies on every reboot. Turned the power mode off and I'm in good shape! Guess I am a moron! Ha!
[Samsung Galaxy Nexus] snubs:
There might be something funky with the SuperSU detection in the newest app update. It says I don't have it installed, but I most certainly do.
[Samsung Galaxy Nexus] tbis:
+1 don't notice any difference at all with 281
[Samsung Galaxy Nexus] Citizen_Snips:
On 281 it would seem that despite being plugged in to a/c power, my device drains with the screen on.
[Samsung Galaxy Nexus] jonstrong:
I seemed to be losing power quickly on 277...faster than on prior versions. Not sure yet but 281 seems improved. I'm down to 70 pct battery already, but that includes an hour and a half of screen time and interactive use. Also, cpuspy indicates that 281 (interactive) seems to be making very conservative use of cpu speed slots but is ramping up fast enough so that this feels extremely smooth.

Promising...

Sent from a Galaxy Nexus far far away...
[Samsung Galaxy Nexus] vtmike:
Not sure if it's just placebo effect, but it seems snappier on 281. Haven't noticed any adverse effects on battery life either.
[Samsung Galaxy Nexus] jonstrong:
+1
[Samsung Galaxy Nexus] Citizen_Snips:
Idk on pretty much all previous version of Francos since 249 I would have 1-1.5hr screen on time at about 70%. Right now I'm at 73% and I have 32mins screen on time. Same brightness I usually use with the same radios enabled/disabled. I feel like it performs better, but I am noticing a little hit on battery over here. :/
[Samsung Galaxy Nexus] iviustang50h:
Wow, you using the 3800 battery? I have the extended 2100 and would have around 50% left if I had an on-screen time of 1.5 hours.
[Samsung Galaxy Nexus] justen7723:
277 (384) I also thought battery wasn't lasting as long as the past few builds. And I was dropping WiFi.

281 (384) WiFi seems OK now. Not sure about battery yet
[Samsung Galaxy Nexus] :
Flashing r281 as of now. Hope I get the same results! What has been your guys' best screen time on? (With this nightly)
[Samsung Galaxy Nexus] dreitzell78:
I have to say 281 is the best version for me so far as far as performance. Not sure about battery, but I would say it is at least as good as it has been. Much snappier than 277
[Samsung Galaxy Nexus] tbis:
Idle time was from sleeping but 281 is awesome. The battery life and performance is the best I've had for any kernel.
[Samsung Galaxy Nexus] Wh1t3Rose:
Remove
[Samsung Galaxy Nexus] Ammontj:
I'm pretty sure mine has been this way regardless of the Rom or kernel that I use.
[Samsung Galaxy Nexus] Sleuth255:
Battery life on 281 appears to be improved from 277. Granted its the weekend and push email activity to my handheld is low however. A more realistic test will happen on Monday when the inevitable **** hits the inevitable fan....
[Samsung Galaxy Nexus] vtmike:
I prefer 281 over 282. Seems to be smoother performing to me.
[Samsung Galaxy Nexus] EDNYLaw:
Did you echo vfs cache pressure to 300 and low memory killer to 8099, 10132, 20000, 20000, 50000, 100000?

Those were default pre 277, makes a big difference

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] :
Dumb question, but does milestone mean anything? I'm coming from the droid x2, where milestone x2 was a version of the phone with slightly different hardware and one could not flash software designed for it in the droid x2.
[Samsung Galaxy Nexus] EDNYLaw:
No, milestone just means the last stable release. Anything that is not a milestone is a nightly which means it is somewhat experimental and can be unstable.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] gfro9191:
384 or 512?
[Samsung Galaxy Nexus] :
I recommend 384 GPU for better stability and battery life. 512 may have some decreased battery life and some artifacts depending on if your phone can handle it. So, just try 512, and if you like it, keep it. If you don't then just switch back to 384, there's barely any difference.
[Samsung Galaxy Nexus] Citizen_Snips:
I just flashed Franco r282 kernel 384 GPU and rebooted. I got an incoming call and tried to answer it and my phone shut off. It sat at the splash screen for about 2 minutes straight until it started to boot up. The boot animation was extremely choppy during the boot. Real low FPS. Finally booted back up and no matter who calls me or who I call I just hear a high pitched tone coming from my speaker. No one can hear me and I can't hear them. I was talking to a friend on my phone 15 minutes before I flashed this kernel....

Edit: flashed 283 all is working again
[Samsung Galaxy Nexus] Sleuth255:
ok, late results for r281. 20% better battery performance than r277. No noticeable performance changes. Francisco, you did something big to this one. I may go to r283 however since I had a one-sided voice issue while testing the phone side of my GNex. Could've been my VoiP system though. I'll test further using a land line tomorrow.
[Samsung Galaxy Nexus] iviustang50h:
This is good info - thanks for sharing your results.

Adding to this, how has everyone's battery life been, particularly with screen-on time? How many hours of screen-on time can you guys and gals achieve either with the stock battery or the Verizon extended 2100 battery? I should clarify, my question pertains only to the Verizon CDMA GNex. I've seen folks claiming 5 hours of screen-on time, but even while on nothing but Wi-Fi the best I've been able to achieve is 3 hours. I am using the JBSourcery ROM, the 2100 extended battery, the Franco r268-384 nightly kernel and my brightness is at 50%. I do not turn off LTE 4G, GPS or my radios, as that kind of limits the phone being able to do what it was meant to do.

So, if you wouldn't mind, please share your battery life experiences with the CDMA Verizon GNex, particularly screen-on time. And please don't post if you're not using the Franco kernel, as that should be a requirement considering which thread we're in. :) Thanks.
[Samsung Galaxy Nexus] enviouz:
Im on #281-384GPU. Stock battery. Brightness on auto. LTE turned off since i rarely travel into an area that i get lte signal. 4.04 radios. gmail, facebook, skype, hotmail sync every hr. Aokp lockscreen weather syncs hourly. Only widget i run is "rings digital weather clock" on my homescreen which also syncs hourly. Browser, calendar, contacts and google play music are at their default sync settings.

Clock speeds are 230-1228. undervolted by 25mv on all freqs. intreractive gov. trickstermod set for max screen off of 230400. wifi always on.

interactive gov settings as follows

above_highspeed delay: 100000

go_highspeed_load: 99

highspeed_freq: 384000

input_boost_freq: 230400

min_sample_time: 20000

timer_rate: 60000

boost: 0

boost_pulse: -1

The other day i had 4hrs15mins screen on. Bascially all of which was browser.

Yesterday i had 3hrs screen on but with a total of almost 36hrs on battery.

I use apex as my home/launcher. App drawer is 100% transparent (can see my home background looks as though my app drawer is overlayed on background) cube outside for effects and a somewhat flashy home wallpaper.

Rom is snapblack/darkaokp 1.4.1. Gps is also turned on.
[Samsung Galaxy Nexus] D4rkShaDoWz:
I just downloaded this kernel and bought the app, I can't wait to try it out!

Does anyone recommend using profiles (Power save, etc) when using this kernel? I'm looking to get the best battery life possible when commuting every day to school.

I've also noticed a bug in the app that when switching back a profile to "none", the kernel max/min frequencies don't reset back to the default - the only way to get it back is by rebooting.