yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Akerskuuug:
Just wanted to report that everything is working perfectly on my phone with #140.

The heat problems are gone (as expected). Did some gaming as well to confirm this.

The phone feels as smooth as always, trying lazy governor to see what it does for battery life.

Thank you for this kernel!
[Samsung Galaxy Nexus] drawde40599:
voltage

So ... to every1 messing with voltages and this and that, what benefit r u guys getting?

Here's my stats --- 384/1228 interactive gov, logger off, screen 75% brightness , GPS on, data on 100% of the time wifi maybe 4 hours, 300+ texts a day, few phone calls, internet, data sync Gmail only 100% of the time and I'm getting 3.75-4.25 hours screen on time almost every day . Stock battery, over 6 h with 2000 Samsung extended battery .

Is the messing with voltage headache worth it?? Yes every phone different but looking at the 100's of pic here I see no benefit messing with Franco settings or em I wrong?
[Samsung Galaxy Nexus] Bisazz:
Personally, I notice a difference, however my usage isn't very normal.

Never gone a full day without UV, but whenever I forget, I usually change it when I notice the increased drain.

Basically my use for the day is 9-10 hours music, 1.5 hours screen on, 1 hour on 3g, rest of the time with data disabled.

Usually within the first 4 hours, at the start of my break, I usually have 90% battery, with ~2%/h drain according to BatteryDrain. Without UV, i'll usually be at 87-88%, with 2.4%/h average drain.

Haven't really used my phone with screen on without undervolt in a while, so I can't comment on that.
[Samsung Galaxy Nexus] aleve1983:
For me uv cpu core and iva don t work in 140
[Samsung Galaxy Nexus] Moz007:
The lazy governor is better than interactive for performances and reactivity ?
[Samsung Galaxy Nexus] jhericurls:
For you its not worth the headache, but for some people they don't get such good battery and every bit helps.
[Samsung Galaxy Nexus] ragnarokx:
Sure seems that way. I'm loving the hell out of Lazy.

Funny, it always was so choppy on my Nexus S. Go figure :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] schizophrenia:
yes, just like i never can reach over 2.5 hours screen on time

and standby time can never get past 14 hours on 3G data with normal usage (less than an hour screen on total)
[Samsung Galaxy Nexus] Aeleks:
Thanks for the awesome kernel and app!

Using both for a long time now, and they are great.

The only thing i don't really understand are the governors.

Is there a post that explains the various governors? The wiki is outdated.

Which governor should i use for maximum battery lifetime? I don't game or run CPU intense stuff, so don't need a lot of performance (max 1200 mhz).

Thanks!

Aeleks.
[Samsung Galaxy Nexus] Benji1983:
hey how is it possible you only get 2k ?

and me running aokp #32 franco kernel #140 /512mhz, lazy govenor,384-1344 Mhz

franco is the best man for gnex

thx you so much for your hard work (but i miss franco turtle :-( )

i got this almost 3500 points

http://s1.directupload.net/file/d/2866/icwfrg6l_png.htm

@ franco i got an little issue maybe not kernel related but maybe you can halp ^^

http://s1.directupload.net/file/d/2866/fnpdjgm5_png.htm

greetz benji1983
[Samsung Galaxy Nexus] schizophrenia:
not need anymore
[Samsung Galaxy Nexus] Benji1983:
thx for pointing me this i fixed the linx :-)
[Samsung Galaxy Nexus] leelaa:
Franco i googled info about interactive and ondemand governor, and i read that ondemand saves a bit more battery than interactive. Is this still the case with your kernel as you have made tweaks to both.

140 is working great also.
[Samsung Galaxy Nexus] nklenchik:
What is that based on, ondemand?
[Samsung Galaxy Nexus] raubkatze:
Yes - http://xdaforums.com/showpost.php?p=25064087&postcount=12975
[Samsung Galaxy Nexus] Mrc527:
I've recompiled the 140 version, with CIFS and external WIFI support too! :p

Look at here:

http://www.kernel-xp.net/index.php/en/progetti/20-galaxy-nexus-kernel

I hope you enjoy it.

Bye!

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] raubkatze:
r140 (512) AOKP b32

autobrightness

max cpu 1228

min cpu 729

no UV

Lazy governor

Generic Hotplug off

SR on

No artifacts and screen lags. An average temp is 34-35°C. 4 hours after flashing, 32 min screen on - now 92%
[Samsung Galaxy Nexus] StuMcBill:
I have been out of the loop for a while, and just installed 140, so far so good.

I just wondered if anyone had defined any "safe" undervolts that seem to work with most devices that I could use as a baseline to start finer tuning?

Also, the last version I used didn't have any SmartReflex options, should I enable or disable that before undervolting?

Cheers

Stewart
[Samsung Galaxy Nexus] leelaa:
The last version was smartreflex3. Franco has put it back to 1.5 so it now shows you what its doing in the app, i just stick with the smart reflex rather than undervolting, as it does it for you.

And yes if your going to undervolt, disable smartreflex.
[Samsung Galaxy Nexus] Antob125:
Not understanding the few explanations of what lazy governor is compared to ondemand and interactive? I though Franco said interactive ran best with 729-1229 for performance/battery.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] meminiau:
I'm on the latest nightly, speed set from 729 to 1344 using interactive governor. Generic hot plug is set, the rest is set as per the app.... Temp is always around 50C, and I'm not even playing games. Should I be concerned even though I'm not having any issues? Thanks

Swiped on my Gnex
[Samsung Galaxy Nexus] SrTapir:
You don't need to.

With UV you are limiting the higher voltage the CPU can use, with Smartflex enabled, you're allowing the CPU to use even lower Voltage frequencies, because Smartflex limits the lower frequencies the CPU can handle.

They are compatible and you may use both if you want.
[Samsung Galaxy Nexus] jhericurls:
You need to try then both. Some people are getting better battery life with interactive. but when i tried, Ondemand was better for battery. Now on Lazy and doing good so far, if not better than ondemand.
[Samsung Galaxy Nexus] spaceman860:
Here's a good post that explains all governors and more

http://xdaforums.com/showthread.php?t=1369817

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] franciscofranco:
I guess we'll see 3.0.28 after I release Milestone 3. Google's android-omap-3.0 branch just merged linux-stable 3.0.28 into their branch.
[Samsung Galaxy Nexus] lynxboy:
So I tried out the Faux 14m kernel included with AOKP.... Safe to say I'm glad to be back on Franco. I know a lot of users are skeptical over whether there are real differences in smoothness, but Faux lags all over the place. Possibly due to not having the 512 GPU OC, but the general UI and games performance is far below what I'd grown to expect with Franco.

Regards.
[Samsung Galaxy Nexus] siuba:
how come you can set the UV so low?

i did apply new values but never happen to me...always use default value...

is it a bug?
[Samsung Galaxy Nexus] isinisterx:
Don't know if this is rom related or kernal related but I was on Google talk yesterday with a friend on camera and my phone kept crashing. No idea why but just wanted to let you know
[Samsung Galaxy Nexus] Bavilo:
One question...Does the Lazy Governor have "screenoff_maxfreq" enabled? If so, it wouldn't really be a battery saver...
[Samsung Galaxy Nexus] raubkatze:
I love r140 )

Works great for me. Now I can forget about charger again.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bradm23:
140 is the bees knees. Lazy gov is a little slower than usual, however its smooth as anything. Can't wait to see this tweaked little.

PS. Happy holiday folks...:-)
[Samsung Galaxy Nexus] stupidslow02gt:
+1. Combine lazy gov and hot plug gov and call it Franco gov :)
[Samsung Galaxy Nexus] jhericurls:
The drain with lazy gov in sleep is crazy low, my battery graph is very flat.

Also it spending alot of time in 384MHz. After over 9 hours its spend 90% time between sleep and 384MHz.
[Samsung Galaxy Nexus] Stretlow:
My cpu temp is sticking between 62 and 57 is this going to be bad?
[Samsung Galaxy Nexus] javi3k:
sorry to aks these but i would like get and advise about voltage control i saw a lot of post people in here drop the voltage on every freq but idk is that work for me i cant use franco app my credit card is blocked right i will have to do it whit aokp control rom, which are the stable numbre for these
[Samsung Galaxy Nexus] Antob125:
I have to say Franco, 140 + lazy governor is super smooth. I don't know much about this new lazy governor but it really makes the phone smooth and responsive. Battery life is doing great on 4G as well.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gparmar76:
Where can I download the latest nightly? The download page only goes to 85...I purchased the updater app and that also lists 85 as the latest nightly...I downloaded 121 a while back but now I don't see the current version which I believe is 140.
[Samsung Galaxy Nexus] grumphy:
http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/
[Samsung Galaxy Nexus] schizophrenia:
weird.. i just had 2 random reboots with r140 Lazy governor

but i wasnt able to get a log coz i did not know it rebooted.

just saying
[Samsung Galaxy Nexus] drawde40599:
colors

@Franco would asking for an option to disable color control in ur app be an option? I would like to use the roms color control but your kernel disables them .....
[Samsung Galaxy Nexus] CommanderDuplex:
please don't forget to set the Throttle temp higher ! please :(
[Samsung Galaxy Nexus] raubkatze:
Seriously I'm really happy with this build -)

UI is smooth and quick. There are no screen lags and doesn't matter what launcher (Nova or Apex) I'm using. There is no issue with cpu temp - max temp that I had today was 48°C. I have no problem with kernel wakelocks and on my mind the battery life is in the best traditions of franco.kernel. Especially I like a minimal battery drain when screen is off as it's very important for me.

Franco, thanks again for great work!!!
[Samsung Galaxy Nexus] chlehqls:
What apps do you guys use to monitor battery temperatures?
[Samsung Galaxy Nexus] raubkatze:
The simplest way using Franco's app if you have installed it. Calibrated Voltage tab > MPU Voltage
[Samsung Galaxy Nexus] franciscofranco:
Send an email to CyanogenMod and ask them to fix their ****. I'm not responsible for roms to use their implementation over Ezekeels.
[Samsung Galaxy Nexus] drawde40599:
Hmmmm, i thought was a simple question? Guess not, its not just cm9, breaks most roms . Well whoever's "code " it belongs to, sorry for asking damn . Have a great day; )
[Samsung Galaxy Nexus] nklenchik:
On Lazy, max frequency should be on when the screen is off to get in idle faster correct?
[Samsung Galaxy Nexus] franciscofranco:
Yes because most roms are using CM9 java implementation on their Color Control. I don't support CM9 mods.

Oui.
[Samsung Galaxy Nexus] Mondfahrer:
r140 lazy working rly nice. I'm surprised about my battery drain! Nice work Franco, thanks!

Tapatalk
[Samsung Galaxy Nexus] Metallice:
Franco, I made some changes to the Lazy governor that I believe are better for our phones. I attached my cpufreq-lazy.c to this post if you're interested. Of course, you're free to do whatever you want :).

I changed the sampling rate to 10,000 to match that of the other governors in your kernel. I also modified how "min_timeinstate" is calculated so that it isn't coming out equal to the sampling rate anymore. If sampling rate = min_timeinstate, you're not getting the benefit of preventing frequencies from quickly bouncing back and forth. In Ezekeel's original thread on lazy he had a sampling rate at 10,000 and min_timeinstate to 40,000, so I changed it so that after the calculations it comes out similar to that with a sampling rate of 10,000 with a min_timeinstate of 30,000. At least with my phone, this seems to have helped reduce the "bounce" effect.
[Samsung Galaxy Nexus] leelaa:
Well done franco 140 running great, i can feel a milestone coming :D
[Samsung Galaxy Nexus] Gahh Its Lee:
Any chance you can post a built kernel? I don't have any way to compile.
[Samsung Galaxy Nexus] SrTapir:
Don't know, I began to lower the values till I reached the limit, in the IVA case there were *cracks* at the loudspeakers, in the CORE case reboots and freezes.

The top CORE values are for 384mhz not 512, this last one will need for sure between 50-100mAv more..

Nightly 140 has a little bug I think, the values you set don't apply (only the CPU one's).
[Samsung Galaxy Nexus] macellaio:
Francisco, a couple questions:

1. Have you been following the FIOPS scheduler development? If so, do you think you'll be looking at it's performance for inclusion in your kernel?

2. Have you explored the use of the C4 state in your governor tweaks? Ezekeel makes use of it in his Wheatley governor and I think it's an interesting concept.
[Samsung Galaxy Nexus] ssglackey:
Hope that 140 idle performance will be as good as 135, will report next week :)
[Samsung Galaxy Nexus] Serious_Beans:
Do you plan on adding voltage control for the screen like Ezekeel has on his app? If not do you plan on adding experimental kernels with lower screen voltages? What are they now? O_o THanks!
[Samsung Galaxy Nexus] yoncy:
Pretty impresive for heavy usage .r135 normal settings
[Samsung Galaxy Nexus] Metallice:
Sure. I'll post the one I'm using now, but if Franco has any problem with me posting this I'll take it down ASAP.

It's Franco's 140 and has the modified lazy governor I mentioned before, but it also has Ezekeel's Vibrator control, FSync control, SIO scheduler, and a bunch of other governors I was testing before settling on Lazy.

FYI it has low regulator voltages that work fine on my device, but may cause display issues for you.
[Samsung Galaxy Nexus] Gahh Its Lee:
Thanks how would I take advantage of the other stuff you put in?
[Samsung Galaxy Nexus] Metallice:
If you have Glados Kernel app from market you can use that. Otherwise...

/sys/class/misc/vibratorcontrol/vibrator_strength

vibrator strength (default = factory setting; value must be between 1000-1500)

/sys/class/misc/fsynccontrol/fsync_enabled

enable = 1, disable = 0 (default enabled)

If you want any of these to be set at boot you have to make or add to an /etc/init.d script.

For example - "echo 1500 > /sys/class/misc/vibratorcontrol/vibrator_strength" (no quotes) in a file named 95vibcontrol
[Samsung Galaxy Nexus] yyz71:
WTF!!!!
[Samsung Galaxy Nexus] myrdog:
^^^ What he said. How the hell did you get 5 days out of this!? Do you touch your phone ever?
[Samsung Galaxy Nexus] franciscofranco:
I don't support any troubleshooting from this compile, if users want to use that then they are on their own. But some clarification is needed:

- My kernel has fsync off since day 1

- SIO is added and enabled since a few releases already
[Samsung Galaxy Nexus] franciscofranco:
Dunno. My kernel already has VAUX and VUSIM voltages reduced.
[Samsung Galaxy Nexus] spinkick:
with lazy governor is it best to use 300mhz or 700mhz for your minimum cpu?
[Samsung Galaxy Nexus] franciscofranco:
1 - FIOPS is still too experimental.

2 - It's interesting but I don't like the concept but I respect Ezekeel's idea and thrill for inovation.
[Samsung Galaxy Nexus] Serious_Beans:
What are the voltages at? Anyway to change them with terminal?
[Samsung Galaxy Nexus] franciscofranco:
Nop.

Its 2750 for VAUX3 and 1800 for VUSIM if I'm not mistaken.
[Samsung Galaxy Nexus] franciscofranco:
r141

* Disable Sync framework for now - it seems too experimental and it was slowing the kernel down. I also think it was causing few random reboots to some users which makes sense since in the patch description it says it can give a few kernel deadlocks. Everything should be ok now

* Merged another Interactive patch

* Merged a patch from TI that adds 3 local caches for DSSCOMP that improves reliability, autonomy and efficiency of the module
[Samsung Galaxy Nexus] myrdog:
Been really busy - don't have time to sift through the dozen or so pages I've missed so excuse me if this is repetitive.

Went from 135 -> 140 tonight. Noticing constant dropped signals associated with screen_off.

1228

729

Lazy

No UV

Gen Hotplug ON

SR ON

EDIT: Should I try 141, was there any patching for this implemented Franco?
[Samsung Galaxy Nexus] mistermojorizin:
flashing r141 now :)
[Samsung Galaxy Nexus] jeetS:
holy smokes. Im on like the third kernel in as many days! I can hardly keep up! let alone test each one!

keep up the good work my phones flying

flashing 141
[Samsung Galaxy Nexus] Bavilo:
Does r141 include the patches for he lazy governor to manage the "bouncyness"? It seems to work very well
[Samsung Galaxy Nexus] franciscofranco:
Which patches? I only included the original commit for Lazy, nothing more.
[Samsung Galaxy Nexus] Bavilo:
These patches
[Samsung Galaxy Nexus] franciscofranco:
Nop, I didn't. I'll see how they work out on my device and if I think it's necessary I'll include it for Milestone 3.
[Samsung Galaxy Nexus] myrdog:
This makes sense. If the sampling is the same as the mintime, you might as well not set a minimum time in the state. It's changing as soon as it samples no matter how long its been in the state.
[Samsung Galaxy Nexus] Bavilo:
Ok thanks!
[Samsung Galaxy Nexus] franciscofranco:
Aye, I agree.
[Samsung Galaxy Nexus] Antob125:
Franco I know Milestone are usually stock GPU but is there any way when milestone comes out you can make a 512 version. Loving the speed.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
No, I can't have 231651 different versions, sorry =(
[Samsung Galaxy Nexus] bigeyes0x0:
So where're your other 231648 versions?

Jokes aside trying the latest hoping to see my Bluetooth bug fixed. Otherwise I hope it's fixed after M3 with kernel 3.0.28 included. I'm pretty sure that it's a bug in kernel now, as I do not have it in stock, ogdobber and faux's kernels.
[Samsung Galaxy Nexus] drawde40599:
charging

Can some1 please see if there phone still charges after install of 512build 141?? I was just charging phone on build 140 now not working 141? May have nothing to do with the kernel but if someone could check please
[Samsung Galaxy Nexus] 6jaipur6:
After a day with r140 I can say that my artifacts problem is solved. No lags no high temperatures no other problems. Mentioned that hotplugins is of, lazy gov and the rest is default. Thanks Francisco for your great work. With no exaggeration you are brilliant.
[Samsung Galaxy Nexus] StyxJ:
Aw thats what I was looking forward to.

Works fine for me, man.
[Samsung Galaxy Nexus] nklenchik:
Charging just fine with that setup on mine
[Samsung Galaxy Nexus] drawde40599:
Thanks guys, strange charger stopped working had to reinstall backup happened right after 141 install??? Dunno??? Guess just one them things
[Samsung Galaxy Nexus] Metallice:
Franco 141 with tweaks to Lazy.

Sampling Rate lowered to 10,000 (same as previously posted tweak). Min Time In State now calculates to 40,000 (Previous tweaked lazy i posted had it at 30,000). Lazy 10,000/40,000 source attached as well.

[Also includes lowered VAUX3/VUSIM voltages, Vibrator Control, and FSync Control, but that's only because this is also my personal build. Lowered voltages may cause graphical glitches.]

DO NOT DOWNLOAD THIS AND EXPECT ANY SUPPORT FROM ANYONE ANYWHERE EVER. This is only to test out the changes to lazy governor, and if people like it MAYBE Franco will decide to include them sometime in the future if he feels like it. Maybe he won't. Who knows? The man has the right to do whatever the f*** he wants with his kernel.

Now to go get drunk. College beckons.
[Samsung Galaxy Nexus] dwang:
Smoothest version yet. I can definitely feel the difference w the latest interactive governor patch in 141.
[Samsung Galaxy Nexus] ragnarokx:
Is fixing the "bouncyness" supposed to increase battery life? Because I've had outstanding battery life on franco's included Lazy governor, and it is so smooth I'd be afraid that changing any parameters to try for more battery life would increase UI stuttering.
[Samsung Galaxy Nexus] nklenchik:
I'll try it out my dude
[Samsung Galaxy Nexus] ssglackey:
sure I did. Every time I needed the phone. But I didn't browse too much, at work I have a PC and at home ipad. I used it lightly, sms, whatsapp, 1 gmail sync. some photos made, also updated many apps on HSPA.

Most of energy was saved by 2G with data sync only once per hour, 3G olny when needed for browsing & app installing.

I have black themed AOKP b31 used no UV, interactive 384-1.3G, generic hotplug and tweaked auto brightness levels.

Not used wifi, it is disconnecting during sleep. And of course airplane mode during night.
[Samsung Galaxy Nexus] drewlim:
Nice finally 512 running w/o any problems on r141. Was having problems with 512 versions ever since r121+. Thanks franco!
[Samsung Galaxy Nexus] Stretlow:
Going from 140 to 141 has lowered my cpu temp from roughly 57 to 40
[Samsung Galaxy Nexus] isinisterx:
What happened to my vibrate mode using the volume rockers? Its gone!
[Samsung Galaxy Nexus] Gahh Its Lee:
Not kernel related.

On an off note I can almost run 512 gpu now. Not quite but very rare artifacts too bad lol
[Samsung Galaxy Nexus] Stretlow:
Edit; still averaging about 57
[Samsung Galaxy Nexus] siuba:
http://xdaforums.com/showthread.php?t=1610160

IMM76I version out! does it affect franco kernel after update?
[Samsung Galaxy Nexus] drawde40599:
If u flash the update u won't have Franco kernel anymore... u will have stock android
[Samsung Galaxy Nexus] salym:
Any one having deep sleep result on r141, i am using r135 AOKP 32 gives me 1% down after 6 hrs with screen off.

thnkzzz
[Samsung Galaxy Nexus] WillyWonka23:
Why do a lot of you guys not use the generic hotplug option? It seems like it can only be a benefit.
[Samsung Galaxy Nexus] aleve1983:
Uv in 140 and 141 dint work
[Samsung Galaxy Nexus] Stretlow:
I've been browsing this morning on 141 with 1 hour 15 minutes screen on time with 60 percent battery left which means I'm on for about 3 and 3/4 screen on which is a record for my setup.

All my setup is the same, only thing I've changed is i usually run my brightness at 50 percent, because I'm not going out today I've got it on 100 percent.

I've got absolutely no idea what is going on....but i like it.

Stret
[Samsung Galaxy Nexus] nklenchik:
Honestly undervolting doesn't do **** for your phone in my opinion
[Samsung Galaxy Nexus] raubkatze:
On r 141 (512) + AOKP b33 now

autobrightness

1344

729

no UV

Lazy governor

Generic Hotplug off

SR on

No issues found so far. I'm waiting for a full charge to test battery life and cpu temp.
[Samsung Galaxy Nexus] rico13:
ive noticed with this kernel and also with popcorn kernel, intensive games seem to lag quite a bit

with imoseyons exp5 and faux hybrid 16b3, it's virtually lag free

maybe it's something with the cache or background apps are being closed to free up more ram, that may be causing the lags?
[Samsung Galaxy Nexus] :
I always try this kernel again because i bought it before 3 months...always going back to another kernel after one day. Got lags with games too. Sometimes small lags, faux doesnt has.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] raubkatze:
Many men, many minds. I hadn't any lags with games eg in gta3.

Probably you tried 512 CPU OC builds with which your device can't handle correctly?
[Samsung Galaxy Nexus] :
No I always use 384 and dont change anything (govenour orUV)

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Salv0:
R141, same standard settings as 140 ( didn't touch a setting after install )

Aokp 32

It seems slower than the previous :(
[Samsung Galaxy Nexus] raubkatze:
Then try to flash 512. Maybe it will solve your lag issue.

---------- Post added at 01:30 PM ---------- Previous post was at 01:27 PM ----------

In NenaMark2:

r140 (512) - 31.1fps

r141 (512) - 31.2fps