yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
The freezes in this last nightly are caused by the Hotplug governor. I spent the last 2/3 hours reading code and this is what think is happening:

We have the governors, which control how the CPU frequencies are scaled, we have the generic kernel cpufreq driver and we have the OMAP cpufreq driver that includes all their cpu suspends, late_resumes etc etc implementations. I think the hotplug governor ability of turning off cpu1 on screen off creates a conflict with the OMAP driver, thus creating the freeze. That's what I think so far.
[Samsung Galaxy Nexus] SomeGuyDude:
Fixable?

Note: I haven't had any freezes on my CDMA Nex.
[Samsung Galaxy Nexus] franciscofranco:
Fix is to change to ondemand again, which I have done in #6.
[Samsung Galaxy Nexus] SomeGuyDude:
Well that's more of a workaround. I meant is it possible to keep the "turn off a cpu while screen's off with hotplug" dealie.

Again, I'm not seeing any freezes myself, so I'm just gonna keep rolling with 5 for the time being.
[Samsung Galaxy Nexus] beekay201:
i haven't got any freezes as well. seems nice. listened to music like 10 mins to test didn't notice anything as well... sometimes i'd find stuttering while screen off on sgs (single core cpu) with custom kernels, not here. at least that i can see/hear.

android is snappy. ondemand was fast as well in nightly #4.

edit: colors look better. more vibrant. especially at full brightness. greyish colors at lowest brightness turn almost light purple. i can live with that, they already did that on stock :D
[Samsung Galaxy Nexus] irishrally:
I didn't notice any color changes in #5. There is still a red tint to the whites.
[Samsung Galaxy Nexus] dpaine88:
So the recommended gov is OnDemand rather than Interactive?

that is, if hotplug is giving issues
[Samsung Galaxy Nexus] sirj00:
Hello Franco, Over at Rootzwiki under the zygot2.0 rom your kernel is getting alot of love. So I decided to go for it and they were right. Running your kernel for the last 2hrs has been a delight. It is by far the smoothest I have tried in the last 5 days. It looks to be a keeper. Excellent job. I ran thru 75% of the phones normal steps that you normally use and all works to perfection. Although netflix hd does not. Can you take a look on a fix. thank you and merry xtmas.
[Samsung Galaxy Nexus] fdxgnd:
I'm in no way complaining, but this kernel is the cats ass. I mean it is amazing. Great work sir. Oh yeah, the one problem I have isn't a problem. Gta not working. But with a fix coming I'm staying. Well, wasn't leaving anyway just for a game. But anyways, nice job man. Truly
[Samsung Galaxy Nexus] altimax98:
What I did for GTA was unzip the kernel delete /system/bin and then rezip and flash... worked for me ;-) because honestly this kernel is so dang hot and the colors are amazing and my Nexus has a great screen already. No color issues on it. But this makes it so much better

Thanks for the explanation of that sdcard binary. I figured it was to improve the sdcard speeds but wasn't 100% sure..

For me its GTA > sdcard :-)
[Samsung Galaxy Nexus] fdxgnd:
Damn. Deleted it. Reflashed. Still no go. Any tips
[Samsung Galaxy Nexus] irishrally:
Netflix HD works for me on mcr ir8 and Franco.
[Samsung Galaxy Nexus] jopherr:
franco your kernals are freaking amazing. im like constantly refreshing to hope to see nightly 6 xD. also props to you for not uploading your kernals to multiupload or any of that bull****. :D
[Samsung Galaxy Nexus] irishrally:
Kernel running really well. No lag at all in app/widget drawer.
[Samsung Galaxy Nexus] jkoljo:
That is because the sdcard binary already got flashed into the system the last time you flashed. You can either reflash your ROM and then flash the kernel without sdcard binary, or adb push the original binary into the /system/bin in recovery mode. I gave instructions on how to do it earlier in this thread.
[Samsung Galaxy Nexus] sago62:
142 unofficial... :-)
[Samsung Galaxy Nexus] sago62:
He did well with the official ...
[Samsung Galaxy Nexus] raubkatze:
Then send log to Franco. Using Franco's app eg.
[Samsung Galaxy Nexus] bat0nas:
Hi,

Could anybody suggest what are most common settings to use to even more save the battery?

Settings are a bit not clear for me (I'm not a HW or Linux expert). So if you could list most common settings (other than default) - would be great.

So far I set only to turn off one core when screen is off. But didn't notice any battery saving. 21h before installing kernel, same after installing and same after disabling one core.

Thanks!
[Samsung Galaxy Nexus] leelaa:
Set Max CPU to 1036 maybe? I done really know I get good battery with pretty much default, apart from I use lazy governor.
[Samsung Galaxy Nexus] relax24:
Am I right in assuming the best way to save battery is underclock the cpu? E.g instead of using 1228mhz as the max, use 1036mhz ??
[Samsung Galaxy Nexus] danielvc:
best way is to reduce the minimum auto brightness levels. saved me 1 hour of screen on time.

Or use a black theme :-)
[Samsung Galaxy Nexus] relax24:
Thing is, I don't want a non bright screen...defeats the point of having such a nice screen, whereas with the underclock, I don't notice any difference.
[Samsung Galaxy Nexus] raubkatze:
I think you need to read a some pages ago. We're all using a different settings for battery saving. There are many and many variations posted here.
[Samsung Galaxy Nexus] Metallice:
Have you tried using the 384mhz GPU version?
[Samsung Galaxy Nexus] SrTapir:
There's no other way to save big amounts of batt if not's playing hardly with the brightness... so if you don't want a non bright screen.. your only chance will be to buy a bigger batt...
[Samsung Galaxy Nexus] franciscofranco:
Searching the thread works wonders.
[Samsung Galaxy Nexus] Metallice:
In terms of battery savings what I've found is -

Extended Battery > Lowering Brightness > less background syncing > underclock > governor choice (depending on usage patterns) > decent undervolting > turning off haptic feedback and touch sounds > other stuffs I can't think of atm.

If usage is in 1-2 minutes at a time bursts - interactive is best for battery . Usage involving gaming, reading, awake more than 5 min at a time - lazy is best for battery.
[Samsung Galaxy Nexus] relax24:
I tend to turn my phone on and off to check/reply to whatsapp messages so I guess interactive is the best choice for me.

I've tried searching but has anyone got any decent auto brightness levels they have configured? If you don't want to clutter the thread a PM would do too. Thanks
[Samsung Galaxy Nexus] Gahh Its Lee:
I'd love if someone could share with me as well
[Samsung Galaxy Nexus] danielvc:
Last one is 250. Working great for me.

And Franco: loving 141. Man, I only had milestones the past 10 nightlies.
[Samsung Galaxy Nexus] Gahh Its Lee:
Not sure why this happened I think it was the fault of the lazy governor but my phone just had a random reboot when I clicked into a text. No big deal but it came back on with every text deleted off my phone.
[Samsung Galaxy Nexus] raubkatze:
I switched from Lazy to Ondemand today. The reason was a strange battery drain the last night: no wakelocks but for 3 hours I lost 11%. So I think something wrong with Lazy yet.
[Samsung Galaxy Nexus] nklenchik:
Me too I'm not getting this great battery life with lazy either
[Samsung Galaxy Nexus] raubkatze:
Now I think maybe my problem with wifi was Lazy related...

http://xdaforums.com/showpost.php?p=25200314&postcount=771
[Samsung Galaxy Nexus] jnr21:
Liquid 1.3, franco 142, 2000mah batt.
[Samsung Galaxy Nexus] franciscofranco:
r143

* 4 patches reverts for stability

* Another Interactive patch from android-omap-3.0
[Samsung Galaxy Nexus] nikosrs4:
1h20m screen on but with much brighter auto brightness. always data on and 3G on when not on wifi.
[Samsung Galaxy Nexus] leelaa:
I see default governor is conservative, is this one more battery friendly?
[Samsung Galaxy Nexus] franciscofranco:
Conservative default? **** yes, it's a mistake, lemme re-upload.

Edit: Done.
[Samsung Galaxy Nexus] niallmcg:
Love the kernel...but since I got #142 (officially of course) device hasn't been sleeping well and getting high media server drain

1.anyone got this problem?

2.anyone know how to find out what it is??

3.anyone know how to fix

Any help will be greatly appreciated and I apologize for my stupidity in advance

sent from my AOKP flavored NEXUS powered by FRANCO
[Samsung Galaxy Nexus] Metallice:
You said there were no wakelocks? Well that means your cpu was in deep idle the whole time. The governor doesn't effect idle drain in any way. The biggest factor for battery life during deep idle is signal strength. If there were no wakelocks that's pretty much the only factor.

Again, the CPU governor has no effect on this issue. Governors affect the CPU and how it scales to different frequencies and suspends. It has no relation to wifi.

I'm sorry but your problems aren't as simple as switching governor. It sounds like you have some issue with your radios/signal/wifi etc.
[Samsung Galaxy Nexus] leelaa:
Haha OK thanks mate.
[Samsung Galaxy Nexus] Metallice:
Try force stopping and clearing the data for media server, media storage, etc. That worked for me before.

Edit: According to TyroneLT uninstalling the recent facebook update fixed this issue for him.

Might be the cause for others' sudden battery issues.
[Samsung Galaxy Nexus] apsis:
@jnr21

Can you provide some more information? What screen brightness, which governor, which frequencies, undervolted?, smart reflex active ? , hotplug mod active?

Cause I'm on the same setup and I'm getting less on screen time. I'm also using the 2000mah battery.
[Samsung Galaxy Nexus] jnr21:
30% brightness, interactive gov, no uv, smartreflex on, hotplug off, cpu 729-1344mhz, 3g and wifi allways on, 384mhz gpu. I allways get 5-6h screen time with franco kernels :)
[Samsung Galaxy Nexus] dpaine88:
What is the benefit of running 729mhz vs 384mhz as a minimum speed?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
I have been running a max of 1344mhz and a min of 729mhz with interactive gov. for a few months and haven't noticed any difference. I get good battery life and amazing performance. Your best bet it to just try both out for a few days each and see what works best for you.
[Samsung Galaxy Nexus] mistermojorizin:
once core voltages drop, this kernel is a beauty: fast, excellent battery, and most importantly low temperature. but now i'm scared to accidently reboot the phone, because then they'll increase for another 24 hours.
[Samsung Galaxy Nexus] raubkatze:
Ok ok... It's theory and I absolutely agree with you. But practice showed that someone had reboots (Franco wrote about), someone had battery drain more than usually etc... What about me I have not any problems after I switched to ondemand.

It's not important for me how it should work but very important that it worked without any issues.
[Samsung Galaxy Nexus] dpaine88:
Flashed 143 and now I'm not getting any deep sleep. Better battery state is not showing any wake locks.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
I've had similar issues in the past and it was caused from bouncing around from different kernel's (developers). Full wipe, or maybe flashing the reset kernel floating around ( search google for ---4.0.3 or4.0.4 reset kernel depends on which version you're running )fixed it for me.
[Samsung Galaxy Nexus] raubkatze:
Reboot, open some apps, wait for a several minutes and then check CPU Spy and BBS.
[Samsung Galaxy Nexus] drawde40599:
Deep sleep working for me build 143
[Samsung Galaxy Nexus] dpaine88:
Flashed milestone 2 and still no sleep. Must be a ROM issue with Liquid

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
I'm running liquid 1.3 and version 143 my phone deep sleeps just fine
[Samsung Galaxy Nexus] raubkatze:
I'm using Liquid. I tried M2, r142 (as it stock for LS), r141 and now r143. Deep sleep works here.
[Samsung Galaxy Nexus] emerica243:
Where do you go to turn SmartReflex on?
[Samsung Galaxy Nexus] zephiK:
franco kernel app.
[Samsung Galaxy Nexus] raubkatze:
SmartReflex is on by default.
[Samsung Galaxy Nexus] emerica243:
I dont see any options for it at all
[Samsung Galaxy Nexus] raubkatze:
franco.Kernel Updater > Calibrated Voltages > Disable Smartreflex
[Samsung Galaxy Nexus] kout:
Deep sleep not working either here with r143.

CNA 2.0 RC, it worked with r141
[Samsung Galaxy Nexus] raubkatze:
Deep Sleep on LS 1.3
[Samsung Galaxy Nexus] drawde40599:
Ya mine works 2 100% its there phones not the kernel
[Samsung Galaxy Nexus] Benji1983:
Ans this ins my deepsleep

103% wow

Greetz benji

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] myrdog:
Has anybody started playing around with the governor control in Franco's update? I'm surprised everyone hasn't been all over this to try and tweak!

I've tried searching, but not finding many explanations on things.

Could I bug someone to define the following for me?

above_hispeed_delay

go_highspeed_load (I get this, but is the default 85 out of 200 or 100 since we have 2 CPUs)

min_sample_time

timer_rate

I just want to tinker and try and get things working more smoothly for me, but even a google search of "above_highspeed_delay" got 0 hits.

Thanks!
[Samsung Galaxy Nexus] spinkick:
no deep sleep on liquid here as well. But it does not seem to affect the battery so I'm wondering if its just a reporting issue.
[Samsung Galaxy Nexus] bat0nas:
Franco boot anymation deosn't work :(

I check the checkbox. App freezes for few seconds. Then Superuser says that rights are granted.

And then nothing happens. Aftčr reboot I see google stock animation.

#143 nightly

App v4.3 (downloaded today)

What I'm doing wrong?
[Samsung Galaxy Nexus] raubkatze:
Try it - http://xdaforums.com/showpost.php?p=25226288&postcount=13420
[Samsung Galaxy Nexus] Metallice:
http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] franciscofranco:
Hmm I didnt change anything that would left the device awake.
[Samsung Galaxy Nexus] niallmcg:
Thanks guys for all the help and for the quick response...the reset kernel worked like a charm if anyone wants it for 4.0.4 here's the link http://faux.androidro.ms/ICS-4.0.4-Reset-Kernel.zip

Wipe cache + dalvik flash reset and then flash your kernel of choice Franco #143 **cough cough**

sent from my AOKP flavored NEXUS powered by FRANCO
[Samsung Galaxy Nexus] Benji1983:
did it allready :-(

i flashed r143 twice no good result

i flashed back to 141 works good super deepsleep 19mA drain

flashed back to 143 and deepsleep is s**** :-(

running aokp #33

thats great work im an franco addict but sometimes there are little problem but never mind i flashing r141 right now and im waiting for next release i know it'll be very soon ^^

greetz benji
[Samsung Galaxy Nexus] emerica243:
am i missing something...
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea there should be an option for smart reflex
[Samsung Galaxy Nexus] kout:
Deep sleep is working now, re-flashed the ROM and kernel and it's back .... weird
[Samsung Galaxy Nexus] raubkatze:
I think yes...
[Samsung Galaxy Nexus] drawde40599:
Kool, glad it worked for u, kinda wish it was built into Franco kernel at flash, I no its " fixed" my issues more than once ..
[Samsung Galaxy Nexus] giulio.alfano:
Me too

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] loudaccord:
looks like the deep sleep problem with Liquid is GPS related.
[Samsung Galaxy Nexus] myrdog:
Awesome link, one thing is that like google, that had nothing on this "above_hispeed_delay". Any insight?
[Samsung Galaxy Nexus] raubkatze:
Hmm... I have not problems with GPS wakelocks on LS. And I have GPS is always on.
[Samsung Galaxy Nexus] spinkick:
alright not to muck up the thread its a liquid rom problem for deep sleep. do this to get deep sleep:

---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------

Lol you beat me
[Samsung Galaxy Nexus] loudaccord:
I didn't either until I rebooted a few times... then I got it.

I realize this isn't a Liquid thread but I just figured I'd point out what the challenge was so people don't say, "Francisco, you broke my deep sleep!"

lol :)
[Samsung Galaxy Nexus] raubkatze:
Heh Will trying to get it -)

---------- Post added at 02:16 AM ---------- Previous post was at 02:14 AM ----------

Yep )
[Samsung Galaxy Nexus] franciscofranco:
I said it wasnt kernels fault, so there you have it
[Samsung Galaxy Nexus] salym:
after half day use of r143 deep sleep was not good enough moved back to r135 were i get amazing deep sleep 98 to 99% in quick time
[Samsung Galaxy Nexus] aleve1983:
Last kernel have no good score in cpu banchmark
[Samsung Galaxy Nexus] franciscofranco:
Now there's something I really don't care.
[Samsung Galaxy Nexus] Gahh Its Lee:
You use your phone under 30 mins a day?
[Samsung Galaxy Nexus] Gahh Its Lee:
Oops... great kernel though.
[Samsung Galaxy Nexus] myrdog:
Franco,

Been toying with the governor settings today on interactive. I know you said you still needed to make it so they stuck at boot. Right now they clear every time. If you're going to make it so they stick, would it be possible to add in a reset button so you could revert to defaults?

Also, with the current setup the governor control stuff sets the hispeed_freq to 1228800. If I have my CPU set to 1344, is it doing anything unless I go in and set the hispeed_freq to a value about 1344000? Right now the current voltages pane seems to be showing that the addition of this governor control panel is blocking overclocks from actually being overclocked. Can anyone else check? Just set your clock to 1344 and see if it actually ever ramps up to 1344.

Thanks!
[Samsung Galaxy Nexus] drawde40599:
Deep sleep works fine on 143, my phone d sleeps as soon as I shut down screen, ur phone is gummed up its not the kernel, read back few pages ...
[Samsung Galaxy Nexus] chardd23:
What's the recommended governor ?
[Samsung Galaxy Nexus] myrdog:
Search is your friend. Right now, from what I understand, it's interactive if you use your phone in short bursts. Lazy if you use it for 2-3+ mins each time you're on it.
[Samsung Galaxy Nexus] franciscofranco:
Good enough?
[Samsung Galaxy Nexus] tossero:
Maybe... :)

Thank you for your work !
[Samsung Galaxy Nexus] Metallice:
That's in regards to battery life. Interactive will always give better performance if that's what you are looking for. And there is no set boundary like 2-3 min. If your phone goes off and on a lot, you want to reach idle quicker so interactive. During long periods on you want lowest frequency so lazy/ondemand would be better.
[Samsung Galaxy Nexus] salym:
that was after flashing r135 over r143 maybe, but i tested the idle for 24hrs i lost just 3% wifi on but not connected i should say the kernel is awesome
[Samsung Galaxy Nexus] nklenchik:
Do you even use your phone? 99% deep sleep at 27 hours?
[Samsung Galaxy Nexus] salym:
i tested for three days idle (only used to check deep sleep 3 to 4 times) and i lost 10% only because i didn't believe that i just lost 3% for 24hrs

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

thankz for amazing work
[Samsung Galaxy Nexus] notja:
Hello Franco

I can't use GPU 512 because my display grid so but I try to flash every version on GPU 512 first if have display grid I will flash version 384 instead. Until version 141 I try to flash GPU 512 same past but it work not grid display and play game very smooth. Today I try to flash 143 GPU 512 I have grid display again so cloud you have fix anything for this because I would like to use GPU 512 very much.
[Samsung Galaxy Nexus] franciscofranco:
There is no magic, if you can't run 512mhz anymore then go for 384mhz, thats why I spend my time building 2 nightly kernels ;)
[Samsung Galaxy Nexus] FC1032:
Usually a silent lurker, but:

Just flashed the latest nightly this morning about 3 hours ago. On a weelly basis, I have this boring 2 hour lecture, in which I end up playing on my for pretty much the full 2 hours.

I normally leave with a pulverised battery, in the teens. I'm very happy to say that today, same lecture, I ended leaving with 30 and I didn't have a full charge in the morning :) Performance seems more or less the same

Great work!
[Samsung Galaxy Nexus] salym:
i was doing idle test for two days and lost only 6 to 7% of battery
[Samsung Galaxy Nexus] drawde40599:
My phone can handle the 512 just fine, but I run the 384 anyways, can u even tell the difference? I can't, I'm all about speed don't give a..... about battery and I can't really tell the difference ...
[Samsung Galaxy Nexus] notja:
I think if run benchmark such as quadrant in not difference but when play game use a lot graphic such as blood of gorry and samurai vs Zombie I think it have difference GPU 512 is smooth than GPU 384 and GPU 384 sometime is lag but GPU 512 does't lag
[Samsung Galaxy Nexus] drawde40599:
O, OK makes sense , I don't play any games probably y I can't tell .
[Samsung Galaxy Nexus] franciscofranco:
Google just pushed IMM76I kernel patches to their branch, I guess we'll still have another nightly build before Milestone 3.

EDIT: Or not, I already had the patches on my tree ;)
[Samsung Galaxy Nexus] jeetS:
Franco, is 143 the same as your 142 kernel in liquid? Or should i flash it?
[Samsung Galaxy Nexus] franciscofranco:
No, it's not the same.
[Samsung Galaxy Nexus] skdinesh:
Hi Franco, thanks for the great Kernels! Quick question on the color tuning settings, I'm on Liquid 1.3 and color tuning doesn't seem to work on both r142 and r143. Nothing changes when the sliders are moved. Could you point me in the right direction? Thanks!
[Samsung Galaxy Nexus] zephiK:
Franco kernel app.
[Samsung Galaxy Nexus] nklenchik:
Use his app :P
[Samsung Galaxy Nexus] skdinesh:
I did purchase the Kernel app from the Play Store and used that to flash. Same results. When I flash the Imoseyon kernel the color tuning works fine. Thanks for the suggestion.
[Samsung Galaxy Nexus] willl03:
Manage colors from inside the app
[Samsung Galaxy Nexus] psyren:
They meant use Franco's app for colour tuning, not Liquid control. It doesn't work.
[Samsung Galaxy Nexus] skdinesh:
Oh ok, my bad. Thanks for the tip! :D
[Samsung Galaxy Nexus] zephiK:
Yeah that's what I meant :p the app itself is more than a flashing app for the latest nightly.
[Samsung Galaxy Nexus] skdinesh:
Thanks again :) and besides color control is there any other setting that doesn't function using Liquid Contol and needs the Kernel app instead?
[Samsung Galaxy Nexus] drawde40599:
paying attention

Didn't see in the change logs, how long interactive been the default?
[Samsung Galaxy Nexus] The Nexus Project:
3hrs of screen on time so far and I'm @45%. 143= some of the best battery life I've seen so far

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] franciscofranco:
Since r143, I forgot to mention it on the changelog.
[Samsung Galaxy Nexus] hotnikkelz:
this kernel is full of win. I even bought the app to support the dev. I am very pleased. Is it worth overclocking? It is already blazing fast. Which setting is the gpu setting?
[Samsung Galaxy Nexus] javi3k:
im getting a wierd thing now i just flashe liquid 1.3 rom, and now im checking franco app and it show me it high tempo of 60° - 65° at max freqz 1300mhz but im not doing anything idk why its at max, this never happend in 141r

mi running

min 729mhz

max 1344mhz

no uv

all default option from franco app

lazy gov
[Samsung Galaxy Nexus] winner00:
Looks like there's new kernel source in AOSP. Got updated to IMM76I.
[Samsung Galaxy Nexus] franciscofranco:
Read last page