yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Sveke:
So Franco, thanks for getting me 3 hrs of screen on while I bull**** on the phone.
[Samsung Galaxy Nexus] The Nexus Project:
Getting good results on battery life on 156. 1228/384 Hotplug Governor :thumbup::cool:

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] dpaine88:
those of you with battery trouble give 1060 at your max a shot

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dpaine88:
FML... phone won't charge, I'm probably the only one with this issue

actually it does charge but only when off

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] svan71:
Hey guys I dont know if its a rom or kernel issue but with my car radios blue tooth i have to manually reconnect each time i turn the car off or on... maybe its the stereo but anybody have any suggestion? Thanks
[Samsung Galaxy Nexus] Metallice:
FYI francisco 690mV (min limit set to 670mv) ended up giving me a SOD. Stupid notification was blinking and everything. So it looks like SmartReflex isn't perfect. Bringing the min mpu voltage limit back up to 700 as running at 710mV was working just fine all day.
[Samsung Galaxy Nexus] nklenchik:
I don't think anyone's had battery trouble since nightly 18 :P
[Samsung Galaxy Nexus] drawde40599:
I had that issue on build 141 and I was only one, never found out y, just wait for next build or go back one, almost impossible to diag if ur only one ( 156 charges for me ) if u figure it out PM me please I'd like to.no if happens to me agn
[Samsung Galaxy Nexus] coolzjai:
he answered that way just simply because getting too tired of seeing people say the franco kernel causes this and that.

You can report for any issue that you suspected that is caused by the kernel WHEN AND ONLY WHEN after you do the most basic level test, like wipe cache, reflash kernel, and reinstall apps!

BTW, i just wanna blame franco kernel, causes me to keep typing wrong alphabet when replying this post. damn it.
[Samsung Galaxy Nexus] rmcsc:
Quick question: how does the average battery life using Franco's over the stock kernel compare?

I know I'm supposed to read the thread but... 1480+ pages? Really?!

(Not trolling or looking to be; just curious, since I'm new to the Nexus and I've read good things about this kernel!)
[Samsung Galaxy Nexus] moe6:
Franco,

R156 has some serious Wifi connection issues with regards to apps accessing it. Pretty much a quarter of my apps can't get a reliable connection on start, including Play Market(!) sometimes.

It's great otherwise :)

---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------

Try it out and you'll understand quickly :)
[Samsung Galaxy Nexus] Basian Mile:
I have a nice Batterytime here. Nearly 4 hours Display with 2 days running. Around 16 hours 3G on. 15 hours deepsleep when i sleep ;-) and Wifi the rest of the time.

I use slimics 3.5.

http://db.tt/6iUQA5yq

http://db.tt/rciWaqIq

http://db.tt/WpHU8YAA

Send from SGN with XDA
[Samsung Galaxy Nexus] rmcsc:
I was planning on doing it, just wanted to know that.

Holy tuna, that's impressive!
[Samsung Galaxy Nexus] drawde40599:
156

Phone has run perfect all day long playing games internet texting everything 100% out the box Franco settings, 50°c as high as temp got, changed to interactive gov and it shot up to 70°c never seen this high before I was on internet doing less than when was 50°c

Build 156 384 gpu
[Samsung Galaxy Nexus] drawde40599:
Yes but 1300 of the pages r the same question over and over agn, I just did a search for the question u asked, funny to see how many times asked already, try it; )
[Samsung Galaxy Nexus] nklenchik:
Idk if I would say 192 is completely functional yet, I was in PowerAMP and my screen froze but the music kept playing. I had to do a battery pull. This happened once before on 152 I think.
[Samsung Galaxy Nexus] jnr21:
r156 is great. Now my phone can run 512mhz gpu version, few previous 512-nightlys (i don't remember which versions) doesn't work with my phone, now i can even play temple run without any artifacts/freezes.
[Samsung Galaxy Nexus] tcchuin:
That's because franco raised the temperature threshold from 64 to 75.

Before doing that, your CPU would have been throttled
[Samsung Galaxy Nexus] CaspaTheGhost:
Yeah, mine can't handle the 192 slot either. Get the same freezes.

I know the maths says the 729 min should be more battery hungry but I really don't see a difference, but I do notice an increase in performance.

Let's give 384 a whirl today and see how it does on 156.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] moe6:
Not entirely true, there were a few nightly's where I hit well over threshold recently before the threshold change. This was particularly noticeable when on Lazy (in fact, it did not stop until I stopped using lazy before franco went back to ondemand lol)
[Samsung Galaxy Nexus] SkaDiZ:
Ok, guys i might found the cause of sudden high temperature (60 degree above) while doing nothing. This happen on me on nightly 156 just now. The temperature suddenly increase while on idle and stay at 65 degree for a long time (i know it's hot because i can feel the heat in my pocket). From my observation, the frequency stay at max all the time although i didn't do anything at all except monitoring the temp in franco app. It is weird to have max frequency all the time by just monitoring temp, so i decided to look inside the "app" in setting for any running application on the background. I found that "facebook for android" is running 8 services and then i try force stop all of it. After that, i quickly open franco app and continue monitor the temperature. It is a surprise that the frequency quickly drop to min and the temperature started to drop slowly. The facebook services might cause the processor to stay at max hence increase the temperature. Maybe some of you are using the same "facebook for android" but didn't have temperature issue but let me explain first. I usually will only on my data whenever i need to browse internet, fb, etc... So when i finish using facebook, i will off the data and the services started to run without data and causing it to keep on running because my phone no longer transfer data. This process will be never ending hence increase the frequency to max and temperature shooting up when screen off. Maybe i am wrong on all of this but this is what i experience and i would like to share it. Thanks for reading and sorry for my bad english.

Kernel: Franco nightly 156 + 512mhz gpu

Setting in Franco app: Stock (on demand)

ROM: AOKP m5
[Samsung Galaxy Nexus] franciscofranco:
I've been saying for a long time that facebook app is Androids cancer.
[Samsung Galaxy Nexus] SkaDiZ:
+1 uninstall it and solve the temperature problem :)
[Samsung Galaxy Nexus] javi3k:
something similar happend to me whit r156 382mhz gpu on demand, at firts my temp was really good all day, then i was in zone where i really had bad signal so most of the time was changing from hspa from edge, then suddenly my temp went to 63 just using youtube and fb, i was on 386min-10xxmax idk if was too low freq for that moment but was really scary =(
[Samsung Galaxy Nexus] SkaDiZ:
Seems like your facebook is trying hard to load something in its services while you are having slow internet connection... This maybe will cause it's services process to never ending loop loading...
[Samsung Galaxy Nexus] lynxboy:
After uninstalling the app a few weeks ago, my battery life improved by about 20-25%. Just use the touch website or the Friendcaster app instead.

Regards.
[Samsung Galaxy Nexus] SkaDiZ:
So i assume u never face sudden temp increase after uninstall facebook?
[Samsung Galaxy Nexus] javi3k:
noob question if the possibility that having low max freq make temp go high is using a service that is needing more power, like happend to me fb whit bad signal triying to conect like mad xD
[Samsung Galaxy Nexus] SkaDiZ:
I dont think using low max frequency will help in resolving the heat problem because the facebook app keep your processor run at max frequency for a long time... The only thing it can help is slowing down the heating process which eventually will hit 60++ degree at the end...
[Samsung Galaxy Nexus] cchant:
I removed Facebook app a few days ago and battery and heat have been way better
[Samsung Galaxy Nexus] billouetaudrey:
Hi, not sure but you can deactivate notification and it same effect to remove facebook...
[Samsung Galaxy Nexus] cchant:
I had all Facebook sync off before, Since contact sync with Facebook is screwed up on ICS. I just use haxsync
[Samsung Galaxy Nexus] mini21:
Sadly, I have this problem with high temp, but I have not installed Facebook.

Now, I installed 3 different roms, 3 kernels in various configurations - now brought back to the stock rom and checking the temperature will also be so high.

If this does not fix the problem, I'll have to go to the Samsung service to repair it.
[Samsung Galaxy Nexus] SkaDiZ:
Did you wipe/factory reset when u install new ROM? If yes, then try to check under "app" in setting for any application running on background when u having high temp... Or u can try clean install rom and franco kernel but do not install any apps except gapps.. see if this help...
[Samsung Galaxy Nexus] lynxboy:
I take it you didn't read my last (long read) post about temperatures.....

Anyway, I didn't get any sudden changes in temperature, just better battery life after the 'katana' process stopped sucking on my juice.

Regards.
[Samsung Galaxy Nexus] apsis:
Tbd Facebook app often gave me problems in the past, I changed to friendcaster before a few months and it's way more battery friendly and doesn't seen to take up that much memory.

So if you guys are looking for an alternative, I would suggest you friendcaster, it's worth the money. And I don't have any benefits suggesting it to you, just my opinion.
[Samsung Galaxy Nexus] qballe:
me too, im on 154 (512) interactive, 384 1228 SR on ,google official IMM76I

this morning w/O facebook installed i got the cpu running at 1228 in idle, only xda app opened, the only way was reboot and for now no more problems.

my gnex sems to be "colder" on wifi but i think is normal :p
[Samsung Galaxy Nexus] SkaDiZ:
I am sure something is running at the background that makes our cpu running at max but i thought is FB, its not :(
[Samsung Galaxy Nexus] morfic:
On terminal type:

top -m 5

Try to catch it old school

Sent from my GSM Nexus Prime.
[Samsung Galaxy Nexus] kmso:
i really don't think temp is the problem
[Samsung Galaxy Nexus] martin.capeletto:
Franco, i'm having connection problems using wi-fi. It happen after installing 156. I tried in two different location with different routers (in previous versions there were no problem at all).

I'm having 1 or none line of signal (don't know if this can be measure more accurately than line), especially after unlocking the phone. Also, some apps fail sometimes to connect
[Samsung Galaxy Nexus] jnr21:
r156 has decreased wifi voltage, maybe that causes problems to some devices.
[Samsung Galaxy Nexus] franciscofranco:
Yep, that seems possible. I will increase wifi voltage an extra notch for r157.
[Samsung Galaxy Nexus] drawde40599:
No Facebook here,
[Samsung Galaxy Nexus] isinisterx:
Anyone else finding that on demand is a bit laggy compared to interactive?
[Samsung Galaxy Nexus] drawde40599:
so 70°c is the new normal??? Ya no thanks, went back stock settings and its fine agn . I dont use Facebook btw ......
[Samsung Galaxy Nexus] rafael-as:
Finally I can change r121

R156 is great!!!

But my Gnec still does not like min cpu at 384. Data loss and batt drain. No problem I prefer 729
[Samsung Galaxy Nexus] Sveke:
Facebook is for sailors named Lawrence.
[Samsung Galaxy Nexus] franciscofranco:
I prefer 729 as well.
[Samsung Galaxy Nexus] CaspaTheGhost:
Same here. My 384 test today simply confirmed that for me.

Governor wise, Ondemand has been the preference but will give Interactive another go to see how it fairs now.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] coolzjai:
Yeah, noticed the lag when set on OnDemand governor with min cpu as 192Mhz. My first lag happen when pick up a call from idle state.

Increase the CPU speed to a higher step like 384Mhz does help.
[Samsung Galaxy Nexus] yyz71:
I also find interactive to be smoother..

Sent from M5
[Samsung Galaxy Nexus] andrew53517:
Do you guys use the recommended color multipliers in the app (the ones he provides) or do you use your own values? I'm kind of scared to tweak the multipliers honestly. Haha. I know default is 200 across the board but yeah :D

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] Sveke:
I use 200,220,265. I prefer a bright bluer tint kinda like trinity
[Samsung Galaxy Nexus] drawde40599:
Voodoo color is best IMO http://xdaforums.com/showthread.php?p=24783215#post24783215
[Samsung Galaxy Nexus] andrew53517:
Okay perfect! Thanks! :)
[Samsung Galaxy Nexus] mini21:
Of course, I did a full wipe before installing.

I have autorun manager installed to turn off all unnecessary programs that could run at startup.

To test what you wrote, the newly installed stock ROM, I launched the browser at 5 minutes, opened the four cards and I've got 65 degrees, and nothing else (only franko.kernel updater to check the temperature).

From my observation is that the temperature jumps especially when browsing the Internet. It is normal?
[Samsung Galaxy Nexus] rmcsc:
Installed Milestone 3. Let's see how it goes for me. :)
[Samsung Galaxy Nexus] Emilius:
154 is way better then 152 but still not close to 121. I did 10 hours test with both.

Here is 10 hours of 154 192/1228/384 interactive without hotplag and smartreflexs idle test

Here is 12 hours of 121 384/1228/384 interactive without hotplag and smartreflexs idle test. I forget to turn off WIFI.

Even with 2 more extra hours and wifi on, 121 is 100% better on battery life. 154 is way better then 152 but still a lot to catch up with 121. Also with 121 it is possible to get 4h of screen on time. Tonight I will do test with 156...
[Samsung Galaxy Nexus] Meannekes:
hey franco

with the lower min. mV from 700mV, SR set my MPU to 800mV at 384mhz

with r154 my MPU was at 840mV at 384 mhz and not laggy,

is it possible to set min mV back to the one from r154 or add something in your app to configure the min. mV by myself?

except from that problem, its the best Kernel out there

sry for my bad englisch
[Samsung Galaxy Nexus] drawde40599:
Ya if 121 was able to use voodoo color that's the one I'd be using also ( I hate the color on this phone!!! Can't wait to get rid of it!! ) , I THINK Franco has to keep up with Google crap kernel updates what the difference probably is..... 156 working great as long as I don't touch the gov he has default .... if I do I can cook hot pockets with it it gets so hot ; ) I'm still getting 3.75 hours screen on time with it tho so battery is just like 121 for me but the smooth of it not the same as 121
[Samsung Galaxy Nexus] brianisme:
The best battery life with Stock ROM for me has also been r121. Switched back to it yesterday.
[Samsung Galaxy Nexus] Emilius:
Yeah I know. I miss all new features from latest kernel but battery life is most important to me.
[Samsung Galaxy Nexus] Basian Mile:
I dont know with you guys but i have great battery life.

http://db.tt/mMzSzrvr

http://db.tt/Q8UWZAmz

http://db.tt/Rb2R2Lpf

In this battery time i used 154 and flashed 156 earlyer today. All is nice.

Send from SGN with XDA
[Samsung Galaxy Nexus] :
I only flash Milestones and the M3 is great for me !
[Samsung Galaxy Nexus] Emilius:
What I am trying to say with 121 is possible to double up what you did there. I am charging my phone every 48 hours on 121. With 154 my battery life is the same like yours.
[Samsung Galaxy Nexus] BrUhNiGGs:
I'm getting hella good battery life with r156. Using ondemand, 1228 Max 384 min, generic hot plug, and manual UV. The heat issue for me has finally reduced (FOR NOW) will need later testing. Seems that uninstalling "Facebook for Android" did the trick. I ended up getting FriendCaster Pro which uses half of the amount of RAM than the original FB app. And it actually closes when not in use, battery friendly.
[Samsung Galaxy Nexus] Emilius:
What it means "hella good battery life"? Any example?
[Samsung Galaxy Nexus] BrUhNiGGs:
Didn't have time to actually have my battery go to about 5% to show full battery results. I needed to charge my phone for today. But I can tell you for me, I got 1 day 2 hours of battery life, and 2-3 hours of screen time. Which doesn't compare to most who use this kernel but great for me as my battery life has always been ****ty for me even with an extended.
[Samsung Galaxy Nexus] Chad_Petree:
My galaxy nexus is one of those horrible ones who came with a ridiculously yellow screen, basically every website or app that has white looks yellow and the same with everything that its grey, has a yellow tint, now in the Franco kernel update app there's an option called omap 4 gamma interface where there are presets for changing the colors of the screen, but I'm not convinced, they look dull and over saturated at the same time, and the yellow is still there, can you recommend some settings?
[Samsung Galaxy Nexus] franciscofranco:
I cant do miracles. I have to merge Googles kernel branch and r121 still didnt have 4.0.4 merged.

Im getting awesome battery life, and 99% of the users also are happy with the latest release. It you want to use r121 be my guest, thats why I provide older kernel releases ;)
[Samsung Galaxy Nexus] javi3k:
noob question - doing uv can cause high temp ? and if there any trick to fight high temp u.u 60° by just using tune id is burning my pocket
[Samsung Galaxy Nexus] brianisme:
Absolutely Franco :) I wasn't complaining. I'm more then grateful for all the work you put into your kernel and am happy for all the options given to us. Will continue to test new nightlies as they come out.

Cheers mate.
[Samsung Galaxy Nexus] Emilius:
Please don't get me wrong Franco but I believe that one of new features cosign this extra battery drain. I know nothing about staff you do but could we try to disable one by one feature and see where is the problem. I hate to stack with r121 but battery life is everything to me. In my case we talking about 100% diference.

Is it possible to do something like that? I can do testing every night on the same way. Am I acting ridiculous?
[Samsung Galaxy Nexus] franciscofranco:
Nop, but I understand your concern. Im getting a 10% idle drain every 20h so I cant really reproduce your problem :/
[Samsung Galaxy Nexus] stellaryt:
With r154/156 I could still get 3hours screen on and most time for games.Last day I keep my phone on for 1day2hrs with 1.5hrs screen on,wifi 4hrs just like daily use,and before I charged still have 50%battery.

Now I finished charge and begin a new test.(Reflashed rom)

About the temperature,35℃ for idle,45℃ for normal use.(r156)

I can't remember the version which could only use 1% during all night(2G only).But I think the latest version is good enough.

Everytime I think franco did his best and released a perfect build,he would released a better version next day...:D

In last 4-5 public release builds,I could get at least 3hrs screen on with heavy use. I think

it's enough but I don't mind it could better:D

Thx,franco.

EDIT: Lag here with R156/ondemand. interactive/hotplug/lazy is ok as usual.I don't know is my problem or the governor's.And I tried interactive and lazy last 2 days,I can't say there is a big different for battery.Today I will try hotplug...
[Samsung Galaxy Nexus] Emilius:
Okay, thanks... I guess r121 is mine until I found something better. Time to move on. :/
[Samsung Galaxy Nexus] franciscofranco:
Probably ondemand is a little more aggressive on staying in the lower frequencies than the other governors, thus the apparent lag.
[Samsung Galaxy Nexus] Metallice:
If you people MUST use an old version of the kernel consider trying r133. People had good results with that one and it at very least had the 4.0.4 kernel merged (121 is 4.0.3).
[Samsung Galaxy Nexus] rubino90:
This version 156 is best for me my test with same using ondemand 3 h and i ha ve 20% of battery with lazy governor i arrived with 3h and 40 minutes with same percent temperature ie the same of you :)
[Samsung Galaxy Nexus] Metallice:
To add on to what Francisco has said, on demand and lazy will wait until load gets high to ramp up to max freq. So for a little over 0.1 seconds you MIGHT have lag as the load is sampled and the CPU ramps up. Interactive is more aggressive and tries to get ahead of high load so it will have less lag at the cost of battery.
[Samsung Galaxy Nexus] dpaine88:
For me, SR calibrates higher mV for 192mh than it does for 384mhz
[Samsung Galaxy Nexus] dezvous:
Hey guys, I've been using Franco kernel for a long time and it has been great most of the time but for the past couple months I've seen steadily declining battery life. The last time i remember spectacular battery life i was getting 18 hour total and 3 hour screen time averages.

Today was horrendous though and I'm really lost as to how it could have happened. My phone was only unplugged from full charge for four hours and then it was almost dead. 58% screen usage was the big offender but it was only showing awake for 25 minutes. How could 25 minutes account for 58 percent in 4 hours? I've been at work all day, only thing I've done is look at twitter, send a few texts, and read an article or two on pocket.

I'm on bigxie's 4.0.3 build and have been back when i was getting my 18/3 hour average.

Running milestone 3 with stock clocks and on demand governor. No volt changes. Hot plug enabled. "turn logger off" and everything else is default except color controls.

I just can't figure out what it could be. I know Franco takes such care with his work he wouldn't push out something if it wasn't great. Just trying to figure this out. Any ideas?
[Samsung Galaxy Nexus] franciscofranco:
Something is really broken there. Try a full wipe (data/system), flash a 4.0.4 rom, flash the latest M3 or the latest nightly and see if you can reproduce that problem.
[Samsung Galaxy Nexus] dezvous:
Thanks Franco. Yeah, somehow i must have broke it haha. Well, i will definitely do that but it's been tough for me to pick a new ROM. Got a suggestion?
[Samsung Galaxy Nexus] darkstar2k77:
Franco, Thanks for all the effort. Bought your app!
[Samsung Galaxy Nexus] schizophrenia:
got a noob question.

what are the determining factors that determine the calibrated voltage by SR?

i noted my 192mhz always got calibrated to 820mah and 1344 to 1200mah

but i noticed some of you said your 192mhz got calibrated to as low as 710mah﻿

using r156 512, ondemand
[Samsung Galaxy Nexus] aquavalanche:
Just a little suggestion, I've been using liquid smooth 1.35 ROM.. combined with r121.. the result is very interesting, as I could reach 17 hrs unplugged, 3.5 hrs screen time, with battery 20% left.. sorry couldn't give you the screen shot of it
[Samsung Galaxy Nexus] Metallice:
Ahh oh well accidentally deleted my post and no ctrl-z on the phone... Might as well fill it with something.... can't think of anything.
[Samsung Galaxy Nexus] franciscofranco:
Thats because the released nightly doesnt calibrate that low. Next nightly will do it. I didnt released it yet because Im trying to fix some bugs in the musb drivers that might be doing some ****s or weird wakelocks.
[Samsung Galaxy Nexus] nklenchik:
Yeah I noticed that too. The only thing I had wrong with r156 so far is the screen freezing on 192mhz while playing music. Other than that it's pretty solid.
[Samsung Galaxy Nexus] diggmc:
Hi Franco,

I noticed an abnormal amount of time/battery wasted on musb with 156. No sleep, just 8hours of 196mhz. I flashed back to M3 and it's back to normal.

When I get home I'll try156 again and see if the problem returns

Thanks

Edited: Well that figures! I just put 156@384 mhz back on the phone and it seems fine. I'll leave it for the night and see how thing go.

Again Thanks
[Samsung Galaxy Nexus] isinisterx:
I find interactive 729-1228 is definitely the best in terms of battery life and performance. Anyone agree?
[Samsung Galaxy Nexus] spaceman860:
That's what I use except I use 729-1344

Sent from my Gnex {GSM}