yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] GibMcFragger:
Yea, I am sure it's not the kernel either as I have been running all the builds and never had an issue.
[Samsung Galaxy Nexus] drawde40599:
I swear Franco should add a separate link to post stupid battery pics . I like keeping up with this thread cause stuff changes all the time but half these posts r " look at my battery its so great " pictures " all my opinion!!! Yell at me if u want o_O!!
[Samsung Galaxy Nexus] sago62:
I'm convinced! The 123 is the best implementation .... CM9 is extremely fluid .... Bravo Franco!
[Samsung Galaxy Nexus] Diger36:
As you could have read if you really followed the thread, Francisco specifically asked for feed back on battery performance on the rXXX, but I guess you know since you know what is best..., right?
[Samsung Galaxy Nexus] drawde40599:
I've been on this kernel and following this thread since be4 Franco even had the phone: ) so thanks . All I'm saying 100's of questions get drowned out because of pictures and " my battery better than urs ". Not my kernel not my thread but is my opinion, and ur right, he did ask ... but a simple my battery is fantastic I would think would be enough cause no real way of telling how someone is actually using there phone ..... agn my option and thanks for yelling at me . Good day: )
[Samsung Galaxy Nexus] isinisterx:
Do you have the extended battery?
[Samsung Galaxy Nexus] bigeyes0x0:
Bug report:

Kernel involved: M2 up to nighty 121

ROM: irrelevant, 4.0.3 or 4.0.4, aosp built or stock based

Problem: Bluetooth headset disconnect after around 20 to 60 seconds

Reproduce by: Let your phone charge overnight (only tested AC). IOW let it overcharge for a few hours. If you charge to 100% then unplug right after there's no problem. A restart should rectify the issue, too

Related HW: Sennheiser EZX 60, works fine on other phones

Other observations: Popcorn kernel v10 also has this problem. morfic's any1344-404-345-ncg-ndd-ndscl-r2cwf-ctuc-cffo (WTF is this naming scheme) on Apr 4th and faux's 15b3 are fine

Log: Unfortunately I didn't get one when I am still on your kernel, using faux's now. Bluetooth is important for me when I'm going out

Conjecture: The problem might be related with some power down crap patches included in Popcorn and franco's kernels or there're related patches that these kernels do not have

Other note: This post is written with the talking style of HK-47 in the hope that the meatbag named Franco will take notice (I'm replaying KOTOR :D)
[Samsung Galaxy Nexus] franciscofranco:
Eheh that HK-47 was an awesome guy, he fought many battles with me :)

So BT headset just disconnects and it won't power up again until a restart?
[Samsung Galaxy Nexus] bigeyes0x0:
Clarification: It disconnects then reconnect recursively at short random interval around a minute. It drives me insane. IOW, Bluetooth is still enabled, but the connection is unreliable.
[Samsung Galaxy Nexus] Gahh Its Lee:
Finally some feedback. On 121 i went a day using my phone less than usual but still I'd consider it moderate to maybe heavy use? Checked my texts every five minutes or so usually texted back. Downloaded 200 mb or so on 4g. After 5 hours I was at 55% battery where I would usually have switched to my second battery.
[Samsung Galaxy Nexus] franciscofranco:
I have no idea!

r130:

THIS NIGHTLY IS A BIT EXPERIMENTAL AND MIGHT BE UNSTABLE SO FLASH AT YOUR OWN RISK. Nevertheless I haven't got complains yet

* Added roughly 40 OMAP4 power management patches - might help, or not, the battery life

* Reduced voltages of two components used by the screen - might increase screen_on battery life

* Added a patch to Ondemand to improve responsiveness

* Tuned Interactive up_threshold from 95 to 80 to be on par with Ondemand's and thats my sweet spot for battery/performance balance.

* Added an helper to Interactive to acknowledge a request for max frequency before the system is loaded. Might help with a little extra performance and battery

* Increase Hotplug governor up_threshold from 80 to 90 - it's a very conservative governor so we now make it even more aggressive.

* Increase Hotplug governor down_threshold from 35 to 40

* Disable generic_hotplug by default

* One or two extra small patches
[Samsung Galaxy Nexus] nklenchik:
Flashing 130, 512 GPU right now. Report back tomorrow with idle times and whatnot.
[Samsung Galaxy Nexus] Gahh Its Lee:
Not sure when this started but the Franco app no longer shows the voltages or anything. Also if I want to use the smart flex system should I have the box for it checked or no?

Checked and unchecked the box a few times and it started to work. Odd kernel seems smooth so far
[Samsung Galaxy Nexus] XLR:
Rom issue. ARHD fixt it already in the latest version.
[Samsung Galaxy Nexus] superbobup:
Seems like the disable 2d accel and deleting the lib file did not do the trick. The "selection lag" occurs even in the browser. When I select any setting option (for example, labs in browser) the icon will light up then dim to about 75% then the screen will transition. This was present in stock and bigxie from...just wondering if anyone has same issue?
[Samsung Galaxy Nexus] jakaka:
are the nightlies again compatible with 4.0.1 or still only with 4.0.3?
[Samsung Galaxy Nexus] alvespt:
hello can i use this kernel with [ROM] Android Revolution HD™ 2.1.1 | High Quality & Performance | GSM | Legendary
[Samsung Galaxy Nexus] aimetti:
read the first post guys

4.0.3 only
[Samsung Galaxy Nexus] Spronx_:
This kernel has been awesome, noticeably better than the apex kernel.

But for now I've had to stick with that one for preference of the UV. I get around 8 hours more from my battery.

On this topic - Franco, will you be re-including a UV script in future builds? build #2 would show undervolt in my setcpu. Was the problem that it was 'showing' UV but not 'really' undervolting?

Keep up the great work! I will come back to this kernel once my extended battery comes along.
[Samsung Galaxy Nexus] alvespt:
Sorry what does uv mean?
[Samsung Galaxy Nexus] jkoljo:
UnderVolt, feeding the CPU less voltage, thus reducing power consumption.
[Samsung Galaxy Nexus] sluflyer06:
Undervolt.
[Samsung Galaxy Nexus] franciscofranco:
Nightly coming later. I'm refining it and testing its behaviour while I'm writing an app to check for kernel updates and some more ****s.
[Samsung Galaxy Nexus] mrroey:
Yes I am having the same issue - well hardly a real issue, but I am noticing the tiny lag when selecting options in the Settings menu. The best way to describe it is that the transitions going from one page to the next are a bit choppy. I am not sure if this was how stock originally was when I first got my GN and maybe I am just noticing it now. This is present in both Mike's Revolution rom and the 4.0.3 ROMs with Franco's kernel. Not a big deal - anyone else seeing this "lag"?
[Samsung Galaxy Nexus] franciscofranco:
As far as I know it always happen, regardless or rom/kernel. I noticed first time I got my GN. Can anyone confirm/not confirm?
[Samsung Galaxy Nexus] sethyx:
Confirmed from 4.0.1 to 4.0.3; on ROMs Stock, MCR, ARHD; and Kernels Stock, MCK, franco.Kernel... :)
[Samsung Galaxy Nexus] mrroey:
Yeah that must be it - my mind is playing tricks on me! Thanks for the clarification guys. hopefully google will optimize this in future builds..
[Samsung Galaxy Nexus] spovat:
hopefully. definitely one of the few gripes I have with ics as well. everything is so smooth and fast that this small detail sticks out.
[Samsung Galaxy Nexus] schrickm5:
Kernel#2 rocks. Big style.
[Samsung Galaxy Nexus] nicandris:
to guys with lag in the settings menu: do you mean it's like a fragment of a second? If so, i think lowering Window animation scale or Transition animation scale to .5 may help
[Samsung Galaxy Nexus] superbobup:
Thank you! Good to know I'm not going crazy :)

I've tried it with all the transition and window settings (not combinations, just changed them together from 0.5->1->2 etc) and it doesn't help. Most likely a Google issue but hopefully a fix comes ;)
[Samsung Galaxy Nexus] paOol:
When I tried nightly #2, on rootzboat 4.0.3, I can confirm that i did NOT have that transition lag. In fact it felt so ridiculously smooth that It became immediately noticeable upon switching to a different kernel.
[Samsung Galaxy Nexus] nklenchik:
Keep it unchecked for Smartflex
[Samsung Galaxy Nexus] yungboss22:
On r130, i cannot undervolt. Uv on this version = Freeze and reboot after 5 seconds
[Samsung Galaxy Nexus] franciscofranco:
Works for me.
[Samsung Galaxy Nexus] yungboss22:
Whats your uv settings ?:) and do u have smartreflex disabled ?
[Samsung Galaxy Nexus] stellaryt:
Works fine here.

If the value you set is too low?
[Samsung Galaxy Nexus] leelaa:
Franco wich govenor should work best for performance and battery life?
[Samsung Galaxy Nexus] franciscofranco:
Governor called "IdontKnowTestItYourself" :)
[Samsung Galaxy Nexus] leelaa:
Wow i was just asking no need for that, iv allways used on demand with your kernel, and know youve made changes to interactive iam curious as to how it should perform,
[Samsung Galaxy Nexus] dwang:
I prefer interactive to ondemand. I find it smoother and less laggy. Battery life seems fine as well. I just did 4:30 hours of screen on time today with interactive.
[Samsung Galaxy Nexus] leelaa:
Thankyou sir, i wasnt sure you see as some changes have been made to interactive.
[Samsung Galaxy Nexus] dwang:
This is with r121. Just flashed r130. We'll see how it goes.
[Samsung Galaxy Nexus] SkaDiZ:
Can we use hotplug mode with generic hotplug on r30?
[Samsung Galaxy Nexus] soapinmouth:
Core and iva village are much higher on 130 for some reason
[Samsung Galaxy Nexus] nklenchik:
I don't see why not
[Samsung Galaxy Nexus] SkaDiZ:
Ok thanks. Because before this, it is not recommended to on generic hotplug while using hotplug mode which might cause SOD. So i assume this problem fix?
[Samsung Galaxy Nexus] Diger36:
Nope, stock.
[Samsung Galaxy Nexus] MacDaddyTMT:
Franco hasn't posted anything contrary to his earlier instruction that one should not run hotplug mod and hotplug governor simultaneously, so I think that instruction is still in effect.

And anyway, I believe hotplug governor essentially includes the hotplug mod in it.
[Samsung Galaxy Nexus] sago62:
Happy Easter to all ...peace!
[Samsung Galaxy Nexus] Cutting-TM:
Happy Easter to everyone :-)

I know its to early to say but it seems that my screen off consumption has raised since 130. Can anyone confirm?

Already looked for wakelocks but there are none.

With 121 I had about 10-20 mA with screen off and same config. Now I've 70-100mA.
[Samsung Galaxy Nexus] drawde40599:
I use ur kernel 100% stock, but im interested in ur setup, Care to share your personal setup?
[Samsung Galaxy Nexus] sago62:
Gpu 512,cpu 384-1228,ondemand,hotplug....works fine...
[Samsung Galaxy Nexus] raubkatze:
Flashed r130 (512). 1228, 729, ondemand. Will test it.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] rubino90:
For me won't boot version 130 auto flash my phone goes To bootloop
[Samsung Galaxy Nexus] bigeyes0x0:
Something is weird with #130: IVA and Core voltage are much higher than #121, was at 840mV for me but with the new nighty they're at 1025 and 1050 respectively, sometimes Core is even reported as 0mV. I checked using your app.

About the bluetooth problem: I hope your applied OMAP4 patches will fix it, I'll test it.
[Samsung Galaxy Nexus] mirageromeo:
Hi, I have some question before I flash your kernel on my phone.

If the new ota update from google is come, Can I get the ota update on my phone with your kernel?

Thank you.
[Samsung Galaxy Nexus] inffy:
NO
[Samsung Galaxy Nexus] MultiCulti:
Perfekt wie immer...

Miui 2.4.6 und selbige Einstellungen bei beiden runs :thumbup:

#129

#130

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
Why would you? Hotplug governor already does generic hotplug's job
[Samsung Galaxy Nexus] cr0wnest:
Was playing sonic the hedgehog 4 when i got sudden slow downs while in game. Never happened this frequently before. I quit the game and fired up dead space, it too was suffering from the same thing. I suspect it could be the r121 512MHz GPU thats causing the problem. Back on 384Mhz GPU r130 now and all seems ok so far.
[Samsung Galaxy Nexus] franciscofranco:
Yep I know IVA and CORE is higher. Not a problem though.
[Samsung Galaxy Nexus] leelaa:
Would that not use more battery?
[Samsung Galaxy Nexus] lucas4ever:
Maybe its too early but after 8h of testing b130 its even better than b128. Battery life is great. Im gonna give it few more days to be sure.
[Samsung Galaxy Nexus] franciscofranco:
It shouldnt. Those are the same voltages that are used for 729mhz mpu opp. I did that as an attempt to eliminate the data connection drop bug that exists since 4.0.4 for some users.
[Samsung Galaxy Nexus] Rovian:
Hi Franco,

Is it better to "check" or "uncheck" the Automatic voltage calibration option? whats better for the CPU?

Thanks.
[Samsung Galaxy Nexus] wollyka:
Uncheck it to use smartflex (Automatic voltage). Or if you want to use your own UV settings , check it.

Usually, i UV and keep the smartflex :)
[Samsung Galaxy Nexus] six_dfx:
If the OTA contains a new boot image (as most do), it won't work with a custom kernel.

Just flash the stock boot image, do the OTA, flash custom kernel back and voila.

---------- Post added at 04:57 PM ---------- Previous post was at 04:39 PM ----------

I'm still seeing this on r130
[Samsung Galaxy Nexus] Rovian:
Thanks mate. :)
[Samsung Galaxy Nexus] RensoreK:
There is a 384GPU and a 512GPU, just curious as to if the 512mHz provides no real benefit as stated by Google Devs and consume more battery, or do people actually see any benefit in using that?
[Samsung Galaxy Nexus] Smallsmx3:
Ive come to the conclusion too many people are too busy monitoring numbers and apps and not real world performance. I dont know if its the latest cm nightly or the latest franco kernel but this is the best my phone has responded. My phone lasts longer than a day on one charge so i dont care if i got 4 hr screen on time vs the 3hr 59 min

On the last kernel....great work
[Samsung Galaxy Nexus] mikeandjaimie:
It gives increased smoothness.. If your device supports it, try both and test out some games
[Samsung Galaxy Nexus] dwang:
Regardless of what Google devs say, there is definitely a noticeable difference in performance between 384 and 512.

It's easy to see the difference by going to theverge.com mobile site and just scroll around. The difference will be obvious.
[Samsung Galaxy Nexus] bendirkss:
#121. Never got this before, till I flashed stock.
[Samsung Galaxy Nexus] DonXoB:
My battery is awesome with N130. Since the latest releases with 4.0.4 I had weaker battery. Now everything works fine.
[Samsung Galaxy Nexus] nikulogical:
Screen on time with r130 is definitely lower than r121 for me..
[Samsung Galaxy Nexus] wilskywalker:
@franciscofranco - Hey buddy, just wanted to say thanks for the fantastic kernel, use it with whatever ROM I am running, bought your updater app from Android Market (Google Play) today to support!

Keep up the good work!

:D
[Samsung Galaxy Nexus] nikulogical:
There is a noticeable difference and from my tests I got no differences in screen on time battery. So if your device can handle it, use it.
[Samsung Galaxy Nexus] franciscofranco:
So general consensus is that battery life is improved with this latest version? I've been getting good reports everywhere with 0 bugs.
[Samsung Galaxy Nexus] lucas4ever:
Yeah, battery life very good here and 0 bugs ofc.
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea phones running very well.
[Samsung Galaxy Nexus] drawde40599:
I haven't had 130 installed long enough comment on battery since less than 24 hours ago, unless its the same as 123? Then battery seems same to me as 121 . I haven't had any bugs at all with stock settings and AOKP 30 Rom . Very fast, very smooth, clean...
[Samsung Galaxy Nexus] mikeandjaimie:
Loving it! Smooth as butter, and great battery time. Got just shy of 4.5 hrs screen on with lowest brightness (I'm inside and on wifi most of the day)
[Samsung Galaxy Nexus] franciscofranco:
Nop, r130 is different than the old rXXX. Lots better, I actually started to use Interactive since I made some changes on it, and I'm loving every bit of this current setup it's a shame I have to keep improving the kernel I could stay in this setup forever.
[Samsung Galaxy Nexus] GibMcFragger:
Looking good man! I'll report back on battery life after a day or two of use.
[Samsung Galaxy Nexus] Gahh Its Lee:
How's the battery life on interactive been for you compared to other governors?
[Samsung Galaxy Nexus] lucas4ever:
Is it just me or Interactive gov is much more snappier than Ondemand ? No lag at all in this b130.
[Samsung Galaxy Nexus] franciscofranco:
Still early to tell because I'm 90% of the time with 3G + data enabled so that sucks some battery out of me. Currently I'm with 2h 30m screen on time at around 42% battery left.

True, a bit snappier because I changed the thresholds and added a boost patch from omapzoom.
[Samsung Galaxy Nexus] lucas4ever:
Nice. Will setup this kernel as my most stable one just in case...
[Samsung Galaxy Nexus] drawde40599:
Interactive,ok ima try it, thanks
[Samsung Galaxy Nexus] Gahh Its Lee:
Impressive I never use wifi so I'm always more curious about actual data battery
[Samsung Galaxy Nexus] franciscofranco:
Yeah. Of course I have to run with 50% brightness, there are no miracles. 3G + data + lots of sms + few calls + some wifi + some pictures shooting + random **** through the day. Thats the rundown for today.
[Samsung Galaxy Nexus] pastasauce:
Whoa franco. Wanna share your voltage/gov settings ^_^?

I'm around 3 hours on 3g data.
[Samsung Galaxy Nexus] sago62:
View attachment 991119

With 3,5h of screen.... Perfect!
[Samsung Galaxy Nexus] Stretlow:
Whats everyones opinion on the network your on having an effect on battery?

Only reason I ask is I have been on t-mobile for 8 years, bought my nexus outright and used Franco's Kernels from the start.

Change roms but always have brightness at about 55% and set up the same and I aways, give or take 15 minutes each way get 3 hours screen on time

I have however just moved to GiffGaff that uses o2's 3g900 network, and im current on 2 hours screen time an at 51%

Think this has any bearing?
[Samsung Galaxy Nexus] lucas4ever:
Franco, can u tell something more about battery usage on this pimped Interactive gov? Is it more battery friendly than Ondemand ? Or is it too early to say?
[Samsung Galaxy Nexus] RensoreK:
i know it has some bearing on battery because I'm on Tmobile I get exactly what you do.
[Samsung Galaxy Nexus] nikosrs4:
never thought about that, but it shouldn't happening.
[Samsung Galaxy Nexus] mrfrag1337:
Does Hotplug option drain battery if turning on/off screen is usual?
[Samsung Galaxy Nexus] raubkatze:
r130 (512) doesn't become friends with my device...

I don't know what's problem but for about 4 hours (57 min screen on) of use I lost 43%

Than I flashed r130 (384) and for almost 9 hours (1 h 26 min screen on) I lost only 27%

How is this possible? The same device and kernel (excluding GPU) settings, the same wifi network, just reading mail and standby. Mystic...
[Samsung Galaxy Nexus] blackdub370:
r130 Ondemand 1344Max 729Min No UV, 512GPU battery stock auto brightness AOKP 30
[Samsung Galaxy Nexus] pastasauce:
O_o

Are you 384 GPU ?

I've got my range lower and I'm not getting even near 7 hours. What ROM?
[Samsung Galaxy Nexus] ChongoDroid:
I'm already noticing a lot less wake locks, phone sleeps RIGHT AWAY, also the screen seems to be chewing through a little less power. Too early to tell, but I vote this as the next milestone.

Sent from my francoPhone
[Samsung Galaxy Nexus] blackdub370:
512 and aokp build 30
[Samsung Galaxy Nexus] AdamZA:
I'm having a strange problem whenever I flash any of the recent nightly kernels. since perhaps 116 or one around then...

I get lots of graphical glitches, text sometimes messes up and on other occasions everything just goes fuzzy. A screenshot is attached to show what I mean! I also get freezes when playing games when on those kernels which makes me have to pull the battery...

When I reflash the milestone kernel everything is fine...

Any idea guys? Thanks for any help you can offer!
[Samsung Galaxy Nexus] sert00:
Happy to see improvement in interactive governor..it's my favourite and mostly used on all my devices.flashed r130 an hour ago,let's see how it goes after readin' soo many good and positive feedbacks.
[Samsung Galaxy Nexus] drawde40599:
No disrespect but I can't read cause I don't no that language,but is that sposed to b 7 hours screen on time with a stock battery??? Cause if it is its pretty freaking amazing ur getting double if not triple EVERY single other person . I'd love to no how u managed to do this with a stock battery FUNNY

---------- Post added at 03:14 PM ---------- Previous post was at 03:11 PM ----------

Ur phone can't handle the 512 gpu, flash the 384 version,its mentioned few dozen times. My phone handles 512 just perfect but I miss the 460 option personaly...
[Samsung Galaxy Nexus] pastasauce:
Hey man, I had same problem, am flashing 384 now but, what do you mean "phone can't handle 512". Don't we all have the same phone? What makes one phone able to handle it while another cannot?

Just curious :D.
[Samsung Galaxy Nexus] mikeandjaimie:
They may be the same phones, but are made at different times with different parts batches.. some gpu can handle higher oc, just like some of our CPUs can be over clocked higher. Personally, my CPU can't be oc'd past the 13xx step, but I can do the 512 gpu no problem.
[Samsung Galaxy Nexus] nikulogical:
Got 4 hour screen on tome with r130. First 50% was on demand, second was interactive. I think interactive did more justice as I had less than 2 hours screen on time for the first half.
[Samsung Galaxy Nexus] drawde40599:
Exactly:). My first Gn before I sent in for warranty,couldnt handle ****!! Froze up at anything over 1300 OC 512 would make it freeze before u could blink .... this one they replaced it with can handle anything and everything I throw at it: ) theres a kernels out there u can OC basically as high as u want and I got scarred before my phone actually failed I think I had it up round 1650 + and I stopped but it handled it . That old phone would have caught on fire: ) this one also has never even got warm to the touch even with charger plugged in playing games ...... ( OK bragging a lil: ) )
[Samsung Galaxy Nexus] tcchuin:
Using interactive on r130 makes me feel laggy kb go launcher... Hotplug governor is smoother
[Samsung Galaxy Nexus] AdamZA:
Thanks for the advice. I wasn't even aware that I was flashing the 512 version. Does it say anywhere? I've just been tapping on 'download latest nightly' and I don't get an option to choose which version.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GibMcFragger:
If you use the app to download, it will give you a choice before you start the download. :)
[Samsung Galaxy Nexus] samizad:
And make sure you are using the most up to date version of the updater app. The feature to choose between 384 and 512 MHz was a relatively recent addition.
[Samsung Galaxy Nexus] drawde40599:
No lag here!!! interactive is flying!!! Actually there all flying!: )
[Samsung Galaxy Nexus] Antob125:
I tried interactive governor all day today on 729-1229 512gpu and it felt like screen on drain was more than on demand. Anyone else? Just trying to find the best governor for battery life without losing too much performance.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] NinjaMic:
Derp, nevermind

I didnt refresh the download folder