yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metalspring:
Ouch, 70%	brightness will eat your battery life alive, also gps on should technically help because network location uses more battery and takes longer, gps is only used when an app requests location
[Samsung Galaxy Nexus] qballe:
quote, IMHO with 70% brightness your battery life is GOOD :p
[Samsung Galaxy Nexus] metalspring:
You forgot a few settings, first off is which battery you are using, gsm OEM standard, gsm oem extended, non oem extended (include mah), cdma/Verizon/sprint? OEM standard, cdma extended

Also add in 4g (and Wimax for sprint???) for the "used on" line since many cdma gnex users post here since it's the same kernel
[Samsung Galaxy Nexus] zenzip:
so you suggest me to set auto brightness and have gps always on? I've 2 or 3 app that require location, and I use only sometimes...
[Samsung Galaxy Nexus] metalspring:
Not if it's an extended battery...I have the cdma nexus with extended battery but have only 3g for now (no wifi either) and I regularly get 3-4 hours on screen time
[Samsung Galaxy Nexus] gknnn':
I didn't know, why don't recommended?

Well I can switch to interactive or ondemand.
[Samsung Galaxy Nexus] zenzip:
No extended battery I've 1750mA gsm battery ;) and have about 1-30/2hrs of screenon
[Samsung Galaxy Nexus] franciscofranco:
Because hotplug governor already does the job of generic hotplug in its governor code...
[Samsung Galaxy Nexus] gknnn':
so when i choose all two it will be internere each other?

think switching to interactive an let hotplug on
[Samsung Galaxy Nexus] metalspring:
Well, depending on the ROM (most have it), you can adjust the auto brightness settings to be much darker and better on battery, but in general most just keep adjusting manual brightness whenever needed
[Samsung Galaxy Nexus] qballe:
better ? :D
[Samsung Galaxy Nexus] spinkick:
:rolleyes:
[Samsung Galaxy Nexus] franciscofranco:
#4.7.2

* Screen_off_max_freq option added. Since its only supported since r161 its only available for users who run that kernel, or newer

* Add governor view on the widget
[Samsung Galaxy Nexus] wily5150:
Thanks for your help. Between yours and all the other answers I should be able to get it. Thanks

Sent from my Galaxy Nexus using Xparent ICS Blue Tapatalk 2
[Samsung Galaxy Nexus] xyzulu:
What do you suggest as a good screen off max frequency?
[Samsung Galaxy Nexus] franciscofranco:
The default is good. However different power modes trigger different screen off frequencies.
[Samsung Galaxy Nexus] jabbermacy:
Hi guys, just installed M/S 3, using XXLA2 radio, cannot connect to WIFI. All else seems OK, using AOPK build 36. Any ideas??
[Samsung Galaxy Nexus] xyzulu:
729 is the default for me. Thanks for clarifying though, it just seemed a little high to me. Will see how things go.
[Samsung Galaxy Nexus] frankyyy02:
Screen Fade

Been testing a little more with the screen fade issue that have outlined in previous posts - http://xdaforums.com/showpost.php?p=25902641&postcount=15296 -, occuring on 384 and 192 min cpu - SR on, when the Core voltage drops from around 1000mV down to 860mV.

If i watch the franco app voltages, screen starts to fade out and dull just before the Core voltage drops.

Is there a way i can increase the voltages that SR uses to scale between with SR on at all?
[Samsung Galaxy Nexus] Dr Byte:
I was actually thinking about something similar myself... but rather than copying it long-hand from the phone to the forum I had something else in mind...

...an app (or a function in the Franco Updater) to capture all the important or relevant details into an .xml file and post it on the web automagically on one of those pastebin sites (or DropBox Public folder?) Then, all people would need to do is post the link (which could be copied into the phone's paste buffer ready to post with the XDA app :))

This would naturally include ALL the settings from the FKU app, plus other important data such as the ROM, version, ROM-specific parameters, apps installed, apps running, wakelock data, battery type, radio, carrier info... just no "private" data to identify the individual, such as their gmail address.

Used consistently, it could be a boon to developers and users alike.

At first, I was thinking along the lines of a BASE64-encoded string that would be posted in the forum itself, but the chances are that the format would change too often and future readers would find it incomprehensible.

Edit: or... it could even be a function added to the XDA app itself, with a new forum created specifically for posting "fingerprint" data, so we could simply check a box on an XDA post to "include" a link within the XDA-Developers forum site itself. Hmmmm.....
[Samsung Galaxy Nexus] BrUhNiGGs:
So what would happen if I have my min cpu set to 384mhz but with r161. I'm not sure how it exactly works. Does it clock the min up to 700 when in idle?
[Samsung Galaxy Nexus] superbobup:
It limits the Max frequency when screen is off. There was a discussion about it a few pages ago that was very helpful for if you choose high or low values.

Franco, I noticed with r161 my CORE voltage is marginally higher (like +13mv). This occurs at 729 min as it was 1025mv on 160 and now it is 1038 on 161 (not sure about other freq since I only remember 729 min voltage). Just thought I may point it out in case you didn't expect it to happen
[Samsung Galaxy Nexus] fatappel:
Not having my typical great experience with kernel version 161. Been running for the past 12 hours or so and my battery life has been poor compared to previous versions. I've been having download errors where I get "download unsuccessful" messages and when I open my stock web browser I have been getting a blank white page. Running all default franco settings except altered color multipliers. 512 gpu version if it matters and running aokp b36. I just flashed back to 160 which was working great and now everything seems to be back to normal. I have no idea why but just wanted to share my experience. Looking forward to future releases. Thanks for your work franco.
[Samsung Galaxy Nexus] BigBake88:
R160 In my opinion is your best work yet, Franco. I just had a 36hr off charger experience with 3hr 25 min screen on time, consisting of both Wifi and 3G, 15 min of phone calls all with stock battery (1850MaH). Not to mention, I had a bad wakelock (not kernel related) that kept my phone out of deep sleep for some time, so it could have been even better. This is using Slim ICS for CDMA. Great job. I want to try r161, but I do not see how it can get any better.
[Samsung Galaxy Nexus] drawde40599:
My battery is the same, and i dont have other issue u have, but the download fail ya I had that 2, clear the download manager cache and reboot,fixed mine

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

@Franco, u should rename the full-power mode to HAUL ASS!!!

Running beautiful!! No issues phone never gets over 50°c ( your app)

Got 3. hours on HAUL -ASS setting: p

No heat

No SoD

No reboots

Battery great

No issues at all

Your kernel and Liquid RC . Crazyyyy Fast!!

Thank u!
[Samsung Galaxy Nexus] xyzulu:
Battery wise, 161 doesn't appear to be nearly as good as 160 was. Just confirming what others have observed as well.
[Samsung Galaxy Nexus] franciscofranco:
Yep, I did some ****, should now be fixed here:

r162

* Fix USB bugs introduced on r161, specially losing ADB on screen off and some other perks that are now fixed

* Corrected compiler flags

* Removed generic_hotplug and hotplug governor for good as we don't need this anymore. The system does its power management by itself, including shutting down cpu1 during screen_off if it thinks its a good idea. (note to self: open my eyes when reading dmesg logs)
[Samsung Galaxy Nexus] :
flashed 7.1 on AOKP LTE. Kernel is amazing, but I still have the issue where phone lags really bad ocassionally while unlocking the screen. After it's unlocked, it's good to go.

Any ideas?
[Samsung Galaxy Nexus] franciscofranco:
Haven't seen that sorry. Are you using a Live Wallpaper, running SetCPU profiles or another governor different than ondemand?
[Samsung Galaxy Nexus] :
No sir. no profiles or live wallpapers, and I'm using the default governor. Seriously though, your kernel is AMAZING in terms of speed. It's just that one little thing :) Thanks for taking the time to reply
[Samsung Galaxy Nexus] triStateMindgate:
I get that too, not a bad lag by any means but happens occasionally. The keyboard lagging behind with a home key press from the MSG app gets annoying too but not sure if its the kernel or 4.0.3...

Also for those looking to test waters, Franco's kernel paired with Pete's Bugless Beast is a blazing fast , flawless combo. Best combo for me out of all Roms I have tried anyway.

Amazing work Franco.
[Samsung Galaxy Nexus] franciscofranco:
Damnit. What do you mean with lag? Can you describe it or better, record it so I can see it?
[Samsung Galaxy Nexus] :
I'll try to get a video of it but let me try to explain it better.

When my phone's screen is off, I hit the power to wake it up, i proceed to move the lockscreen ring to the right to unlock, and it stutters a bit and then unlocks. After that initial stutter, everything is fine .
[Samsung Galaxy Nexus] Pliind:
I'm sorry if this has been answered before, but im using bigxie's custom stockrom, and when i flash your kernel i loose root, how do i fix that?
[Samsung Galaxy Nexus] jbdan:
I get it too occasionally. It's when you wake the phone and immediately try to slide unlock it. It's takes a second for it to react. Happened on 5 and 6 as well for me. Otherwise they are super fast.
[Samsung Galaxy Nexus] franciscofranco:
What do you mean lose root? No one has ever got that problem, so its on your end, I just checked and my root is just fine.
[Samsung Galaxy Nexus] hjlow:
no stutter for me in the scenario
[Samsung Galaxy Nexus] franciscofranco:
Increase your minimum frequency to 700mhz and try to reproduce that lag please.
[Samsung Galaxy Nexus] fiftyclick:
Tried testing it a number of times here, no delay at all. My SetCPU is only 700MHz-1200MHz.
[Samsung Galaxy Nexus] triStateMindgate:
If and when it happens to me seems like only after the phone has been idle/sleep for a while, wondering if its just a slight lag when the CPU revs up to wake phone. Haven't seen anyone else have this or notice it maybe its just our chipsets dunno. This isn't even severe or an issue for me but I figured I'd speak up cause I noticed it. Again it happens very rarely to me anyways.

I'll try setting the CPU to 700 and see if I can notice it.
[Samsung Galaxy Nexus] :
There you go, that's exactly what I mean. I've gotten it on Rootzboat and AOKP while using 6,7,& 7.1 :(
[Samsung Galaxy Nexus] akellar:
Fwiw I'm on the same rom and not seeing any lag of any kind.
[Samsung Galaxy Nexus] triStateMindgate:
I'll bet that will solve it.
[Samsung Galaxy Nexus] Redflea:
The keyboard lag occurs on multiple ROMs and kernels.
[Samsung Galaxy Nexus] sefirosu0522:
Just flashed 7.1 and on boot, I have a screen that says Android is upgrading. Looks like it's going through 204 applications. Is this supposed to happen? Again, noob when it comes to kernels.
[Samsung Galaxy Nexus] fiftyclick:
Yes, that happens when you wipe Dalvik cache -- it's a good thing to do when flashing kernels
[Samsung Galaxy Nexus] triStateMindgate:
That's normal when dalvik is wiped.
[Samsung Galaxy Nexus] drawde40599:
try give few battery cycles maybe? I no I always get better battery after a few days of not " crack flashing " being less than. 24 hours to early to comment on better or worse battery (IMO)

---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------

162 Ahhhhh never mind; )
[Samsung Galaxy Nexus] Benji1983:
hi everyone

installed nightly version #163 ?

latest availiable nightly version 162 ????

my franco app is joking me ^^

greetz benji
[Samsung Galaxy Nexus] franciscofranco:
It's r162, but it's 6:11AM and I forgot to change the kernel version before I compiled. I re-uploaded with the correct # now anyway...
[Samsung Galaxy Nexus] xyzulu:
Generic Hotplug not available using r162/163, is that by design?
[Samsung Galaxy Nexus] superbobup:
Do you even read the changelog? Come on man..

Also, Franco, 162 seems to have brought CORE down to 1025. Thanks
[Samsung Galaxy Nexus] xyzulu:
I'll consider myself punished.. sorry.

/lazy off
[Samsung Galaxy Nexus] nikulogical:
What's the default min freq on r162
[Samsung Galaxy Nexus] drawde40599:
Unset the " set at boot " settings and reboot phone it will be at default..... Actually if you have the app you can set the cpu mode to none and it'll be default
[Samsung Galaxy Nexus] nikulogical:
Or you could just tell me..
[Samsung Galaxy Nexus] drawde40599:
I think you can handle it alone thanks
[Samsung Galaxy Nexus] nikulogical:
I know how to do it, I don't wanna change my freq either, I haven't been following the thread recently and I just wanted to know whether it was still 384 or if it has changed. Smh..
[Samsung Galaxy Nexus] drawde40599:
I'm driving, I don't no what default is, I'm on full power setting , sorry
[Samsung Galaxy Nexus] Serious_Beans:
Default min frequency is 384. Franco said he will leave that as the default freq in his builds a while back unless you are talking about default screen off freq that is 729mhz
[Samsung Galaxy Nexus] andQlimax:
729mhz is not default screen off freq, is the default MAX screen off freq: p

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] nikulogical:
This is true.
[Samsung Galaxy Nexus] lynxboy:
Struggling to pull myself away from #160 with battery life like this.

Still got 16% to go! That's with using FB and already past 4 hours of screen time. Thanks Franco.

Regards.
[Samsung Galaxy Nexus] castaway1:
:eek:

your settings please? :) min/max /governor etc..
[Samsung Galaxy Nexus] qballe:
could you plese compile this if you want ? :)

http://xdaforums.com/showpost.php?p=26226815&postcount=16167

2 big pictures and a "wow" are not enough :D
[Samsung Galaxy Nexus] lynxboy:
Don't get me wrong, I fully respect scientific attempts of investigating battery life, but there are so many factors at play that a simple list like that is irrelevant in the grand scheme of things!

Mobile signal strength, temperature, apps, color control settings, battery health etc etc..... you'd have to write a pretty exhaustive list to cover it all. I feel sorry for users chasing the 'perfect' balance of settings, it's like chasing rainbows, you'll never find it! Just go with the flow and the results will show.

The most important factor is I'm using Franco's kernel. There is no added Voodoo here. I always get great battery life, but it's been above average on #160.

Thanks again Franco!

Regards.
[Samsung Galaxy Nexus] Bonvaz:
I had graphical glitch with some games and also apps on last nightlies..flashed milestone 3 and is all ok
[Samsung Galaxy Nexus] Treatcon:
Just installed 162 and everything is set to default in Franco app, v4.7.3

729-1228 Interactive

Power Mode "None"

CPU Mode "Dual-core"

no generic hotplug

maximum frequency when screen off "729"

smart flex "On"

I have't messed with any of the voltages so all is set at stock

AOKP 36

[Radio] I9250XXLA2

[Bootloader] PRIMELA03

WOW did I miss anything LOL Anyway calls when the phone is not in use are going straight to voice mail. So phone sitting with screen off, I call it and goes straight to voice mail. The phone does not notify me of missed calls or new voice mails at all until I wake it up.

Flashed back to 160 and calls come through as they should and all notifications work. I didn't try 161 yet since I know for sure that 160 worked. I'll do more testing after work. For now I need my phone to work regularly.

Thanks for all your work Franco!!
[Samsung Galaxy Nexus] msedek:
Dude when ever i activate the usb fastboot charge it works ok but if i reboot the phone with the usb cable plugged it will go MTP Despite the usb fast charge setted up so i have to replug the cable to be able to make the feature to work.. My question its does it sets on boot and if not would be a nice improvement
[Samsung Galaxy Nexus] frankyyy02:
Spent a little more time playing around with the core voltages with the min CPU at 384. For some reason it seems my GPU doesn't like the 886mV. Initially thought it was under powered but when changing the default core voltage table for 153MHz from current 962mV to 880mV and applying values the my screen fading issue disappeared (I believe these impact the upper limit with SR on). The voltage now sits on 830mV instead of 886mV SR on. Not sure exactly why.

Maybe someone can shed some light?
[Samsung Galaxy Nexus] Timmyfoxeh:
I'm having issues downloading the kernels using the updater app. It displays the progress screen and then is goes disappears without downloading... Auto-flash works though.
[Samsung Galaxy Nexus] frankyyy02:
I have the same issue. Change the download location in settings and it will work.
[Samsung Galaxy Nexus] metalspring:
Had this too, the quick fix is making sure to set a custom download path
[Samsung Galaxy Nexus] qballe:
yes, but is aniway a step to exit to this caos, and maybe in future make somthing of "scentific" in place of "franco rulez" ;)

btw I understand and I agree with you .

Marco
[Samsung Galaxy Nexus] isinisterx:
How can I make the screen more responsive?
[Samsung Galaxy Nexus] isinisterx:
Never mind. 162 fixed it. Thanks
[Samsung Galaxy Nexus] ch33kybutt:
Dim the lights & put in a Barry White cd ...
[Samsung Galaxy Nexus] parkson:
Works every time :D
[Samsung Galaxy Nexus] BigBake88:
Agreed! I do not think it can get much better than r160! Milestone 4 if you ask me!
[Samsung Galaxy Nexus] franciscofranco:
True, but lets gather some feedback on r162 for a few days, Im curious to see if screen off max freq setting helps or not.
[Samsung Galaxy Nexus] loudaccord:
162 is working great for me. I switched from Liquid to BlackIce Kangorade 36 and performance/battery seem to be up to par. Great work FF!
[Samsung Galaxy Nexus] stratoox:
What governor u use dude?
[Samsung Galaxy Nexus] Basian Mile:
i have nearly 4 Days with 2.5h ScreenOn Time now. 158 and SlimICS 3.6
[Samsung Galaxy Nexus] yyz71:
With 162 the scrolling seems smoother.

Sent from M5
[Samsung Galaxy Nexus] Treatcon:
Anybody have problems receiving calls or notifications when the phone goes into deep sleep on 162?
[Samsung Galaxy Nexus] sparkdroid:
I just installed 162 and let the phone sit so that it would go into deep sleep. Called it and the phone rang. I then verified with CpuSpy that the phone had indeed been in deep sleep.

Looks like this is not a problem for my phone.

EDIT: I also just got a notification of an email and the LED blinks (using Lightflow).
[Samsung Galaxy Nexus] BigBake88:
OnDemand...I still think this is the best for both performance and battery. I tweaked the governor a little bit. Sampling rate 50000 and up thresh hold to 95.
[Samsung Galaxy Nexus] Cutting-TM:
162 works great. 10 hours on battery with lots of usage and still 80% left.

Deep sleep at 384 MHz , interactive 192/1200 MHz
[Samsung Galaxy Nexus] BigBake88:
Nice! What's your screen on time?
[Samsung Galaxy Nexus] drawde40599:
Phone, Gmail, and texts working normal here, phone is deep sleeping ( CPU spy ) try flashing agn manualy, from recovery . U could also try clean install ( fastboot stock boot.img ) then flash 162 sometimes" stuff " gets gummed up needs extra push....
[Samsung Galaxy Nexus] chakra:
I have a big performance drop with 162 on the benchmark & tunning app. I went from 22800 with 161 and M3, to 17000 on 162. I am now back on Milestone 3.
[Samsung Galaxy Nexus] RayGarden:
Ehhhhh......Dim all the Light = Donna Summer :D
[Samsung Galaxy Nexus] alphaola:
Not sure this has been mention that the governor control doesn't stick after reboot, it revert back to the default.
[Samsung Galaxy Nexus] Hanny:
not getting it here. ensured phone was in deepsleep and called it and it rang. it is working on both 2g only on and off.

fyi my baseband is SC04DOMKKD.

by the way, on 162 the screen is turning on within 2.5 seconds after charging state is changed (tested with non stock AC charger and cable). thanks franco :)

and removing hotplug for good is a seriously good idea as i was always worrying about cpu_1's health while frequently being forced to shutdown and turn on if one chooses hotplug :p
[Samsung Galaxy Nexus] franciscofranco:
I have roughly 23k with stock frequecies. Besides I know its fine because its the first bench app that I run.

Edit: wrong quote.
[Samsung Galaxy Nexus] Bonvaz:
Hi franco..have you any idea why is happening this on my phone with r161 and r162?I try only those and Milestone 3,and on Milestone 3 I have any graphical glitch like these..so maybe it's one of the last change in the kernel that is causing this...I hadn't make any mods,only governor ondemand and min cpu on 729,but I did it also on milestone 3 and no problems...
[Samsung Galaxy Nexus] franciscofranco:
Run 384gpu nightlies, problem solved.
[Samsung Galaxy Nexus] Sveke:
Looks like your phone doesn't like 512 gpu

Edit:Ninja'd by the man himself
[Samsung Galaxy Nexus] Bonvaz:
sorry,so in the next nightlies will be solved? r162 is not 384gpu?
[Samsung Galaxy Nexus] danielvc:
you have 2 types of nightlys: so download the 3xx version. it wont be solved, because there's no need to.
[Samsung Galaxy Nexus] BigBake88:
@Franco Any chance you can add an option in the voltage section of your app to tweak VAUX3_6030 and VUSIM for added screen on time? It was kind of fun tweaking it using Glados kernel and app, but you kernel just plain runs better! :D
[Samsung Galaxy Nexus] nodstuff:
Here is the fool proof way of sorting your problem.

http://minooch.com/franciscofranco/Galaxy%20Nexus/nightlies/gpu_384mhz/
[Samsung Galaxy Nexus] Bonvaz:
thanks :) so the milestone 3 was 384mhz? thanks guys,love this kernel:)

there is any way to flash the 384 mhz from the app installer instead the 512 one?
[Samsung Galaxy Nexus] BigBake88:
Milestone Kernels are always stock GPU (307Mhz), and someone posted the link for you already to flash the 384Mhz nightlies....

Edit: and yes, the app gives you the option to install either one
[Samsung Galaxy Nexus] Bonvaz:
ok,got it..but my question if from the franco app there is a way to install 384 mhz versions and not the pumped one..:) very useful and smart that app!!thanks for all your help guys

solved thanks guys:D
[Samsung Galaxy Nexus] qballe:
Milestone is ONLY STOK GPU

nightlies : 2 versions 384 and 512 :D
[Samsung Galaxy Nexus] Sveke:
Yes when you hit download nightly it will let you choose 384 or 512
[Samsung Galaxy Nexus] franciscofranco:
Me and Imoseyon ran a bunch of tests and going below X value on vaux3 and vusim dmesg started show error messages so we found a sweetspot and thats what is running now by default with 0 errors.
[Samsung Galaxy Nexus] BigBake88:
Ok, perfect. Thanks for responding back. May I ask what the voltages you are using on the kernel? I think if I remember correctly I got mine down to 2500mv for Vaux3 and 1500 for VUSIM, and didn't notice any screen glitches. Thanks again, Franco.
[Samsung Galaxy Nexus] Bavilo:
For some reason the color multiplier settings still dont stick after a reboot. even with the latest update of the app...
[Samsung Galaxy Nexus] Bonvaz:
+1 :(
[Samsung Galaxy Nexus] ssglackey:
Just missed Sms, LED flashed, but didn't ring. Using 162 (512) on AOKP M5.

Runing full power mode, UV, SR on. Same UV I had run on 999 without issue.

Will try to use another power mode and report back.
[Samsung Galaxy Nexus] BigBake88:
Are you guys running CM9? I think that may have been the issue, and not the app. Someone a few pages back confirmed when they switched from CM9 that they did not have the issue anymore...
[Samsung Galaxy Nexus] opethrocks:
What rom are you using?
[Samsung Galaxy Nexus] Bonvaz:
aokp!:D
[Samsung Galaxy Nexus] Bavilo:
I'm using ParanoidAndroid so yes....CM9.
[Samsung Galaxy Nexus] bradm23:
I also can report many data drops and missed calls since update. This is in a great service area
[Samsung Galaxy Nexus] jcurtis369:
make sure your bootloaders match your radio I've heard that might be the cause of the data drops.