yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Thracks:
Set it to 700-1200MHz, conservative governor, and leave it alone beyond that.

You don't actually want to set the minimum clockspeed to 350MHz for four reasons:

1) Clocking down to (or up from) 350MHz when the device's display is active can introduce stuttering in the performance of the phone. Because the phone spends such a large portion of each charge with the screen off, the impact on battery life by raising the minimum to 700MHz is negligible.

2) Performance counters on Android are constantly monitoring the CPU load of the device to determine the correct clockspeed for smooth performance. If you set the clockspeed to 350MHz, any old task could cause the device to register 100% load and/or sluggish performance. This will cause the CPU governor to shoot to a higher than required clockspeed as an immediately corrective action to maintain device performance. Setting the minimum clockspeed to 700MHz will put the device in a position to more readily handle a task without convincing the governor to ramp the clockspeed. This should conserve power.

3) ARM chips perform a technique called "voltage collapsing," where the operational voltage of the chips is dramatically reduced when there is no active load being placed on the CPU. In this state, regardless of the frequency you're running at, the chip is only using a very small amount of power. At 100% CPU load, 700MHz only consumes 178mV more power than 350MHz, but 700MHz gives dramatically better performance, especially when coming out of sleep to the lock screen. At idle CPU load, this 178mV delta is even smaller.

4) When the phone comes out of deep sleep to perform a sync action with the screen off, the task will take longer to complete at 350MHz than it will at 700MHz. Even though 700MHz uses a touch more voltage, the faster task completion that this clockspeed provides allows the device to return to sleep faster as well. The end result is that 700MHz actually uses less power to wake and act than 350MHz would.
[Samsung Galaxy Nexus] franciscofranco:
THANK YOU! I'll just link this post in the OP, it will save me from answering the same questions again ;)
[Samsung Galaxy Nexus] Thracks:
Just make sure you incorporate my "four reasons" edit, so I don't look like an idiot that can't count. ;)
[Samsung Galaxy Nexus] franciscofranco:
Sure np, I'll change it to "two reasons" ;)
[Samsung Galaxy Nexus] aron7awol:
It all makes sense, but wouldn't all of these reasons also apply for 920 MHz? At what point does the additional power consumption outweigh the benefits?
[Samsung Galaxy Nexus] jaycarag:
The smartreflex settings are included in Franco's app. :)

---------- Post added at 11:20 AM ---------- Previous post was at 11:18 AM ----------

I'm using Google Galaxy Nexus. MinCo v3 ROM + Franco's v241 kernel. ;)

---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------

I guess I wasn't clear enough. I mentioned that I was using 240 then 241. So the 30 hours battery life was measured from 240 then 241. A combination of both. My last full charge was Sunday evening (Manila time) when I was still using v240 then I flashed v241 yesterday. My battery stats during 240 was almost 6 hours with less than an hour of screen time. Sadly, when I flashed v241 the battery stats were cleared. Now, I have 1d 3h of battery plus 1h 45mins of battery time with 241. I'll try to upload a screenshot later after my day job. :)
[Samsung Galaxy Nexus] imtjnotu:
Few minutes even still no other Franco kernel has taken longer then a minute to fully boot... Did it again on the 384mhz kernel same thing.... Sent back and flashed the 512mhz and it booted up normally

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
The user said 240 AND 241. Seems about right to me

---------- Post added at 05:48 AM ---------- Previous post was at 05:44 AM ----------

Very long boots happen all the time. Its a jelly bean thing?
[Samsung Galaxy Nexus] mike216:
I've got kernel info?
[Samsung Galaxy Nexus] nnnnr14:
That means your not running cm10 ;)

sent from my 1.42hz Franco kernel Gnex!
[Samsung Galaxy Nexus] joeyfong:
franco.Kernel under sgs3 cm10 display correctly.
[Samsung Galaxy Nexus] RoscoeDpG:
i never said i had 45 % left? i was just showing what i had got out of the latest one i was running, i think u got me confused with other person
[Samsung Galaxy Nexus] nnnnr14:
Sgs3? We are talking about the Gnex...

sent from my 1.42hz Franco kernel Gnex!
[Samsung Galaxy Nexus] joeyfong:
Of coz I know we are talking about Nexus, I am using Nexus too, just help my friend flashed the newly cm10 supported franco.Kerenl in SGS3, and found that can display the kernel information correctly.
[Samsung Galaxy Nexus] Wynnded:
I'm guessing that he was mentioning that Franco's Kernel info shows on CM10 on the SG3 in comparison to others saying it won't show on CM10 for the GN....:)

...I think....
[Samsung Galaxy Nexus] prembox:
Music Playback Bug

Roger that. On R240 right now....Google Music app, Player Pro, Double Sync player, all stop after playin a song for a few secs.....I do not know if this bug was present in the previous kernel builds as I didn't check it then. But this is a sure shot bug...I'm sure France might take a look at this .....
[Samsung Galaxy Nexus] DrAk0H:
I"ve used Google Play Music and PowerAmp. There were no problems with music palyback so far... I think that you sould be looking into your rom.
[Samsung Galaxy Nexus] prembox:
I'm on stock, boy.....no changes except that it is powered by Franco 240 512Mhz-Interactive! No OC/UC or any changes to Volting......all default settings!
[Samsung Galaxy Nexus] ectodroid:
Useing poweramp and spotify, no problems on 240 or 241

Maybe try to wipe cache/dalvik?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] steveboss:
Hello, can you tried this kernel on Xperia Neo?

Odoslané z môjho MT11i
[Samsung Galaxy Nexus] prembox:
Whaaaaaaat???....DO NOT FLASH IT ON YOUR NEO...you'll brick it for good!!! THIS KERNEL IS ONLY MEANT FOR Galaxy Nexus GSM International Version!!!
[Samsung Galaxy Nexus] akash3656:
Are you using volume boost? While I was using other kernels, when i plug my 2.1 speakers into my nexus, the audio will stop playing right after a few seconds like you mentioned.
[Samsung Galaxy Nexus] Cutting-TM:
I guess you are using the sound mod to increase volume, right?

Set it to 1 and check, if it stops or not ;)

I had the same problem. I set it to 3 and max volume and the sudden stop came.
[Samsung Galaxy Nexus] steveboss:
OK, thanks...
[Samsung Galaxy Nexus] djjonastybe:
Does anyone know if it's possible to recalibrate the voltages?

My Nexus has:

200mhz - 840mv

400mhz - 840mv

600mhz - 1000mv

800mhz - 1000mv

1000mhz - 1090mv

1200mhz - 1200mv

The fact that 200 and 400mhz are the same and 600/800 I hate.

Or maybe it's because they use the same FUSE each time while 1000 and 1200mhz do not use the same fuse. Which makes it bad for calibration?
[Samsung Galaxy Nexus] Kostas1601:
:S Which kernel should I flash? the franco.Kernel-milestone 4 or the franco.Kernel-r241-512GPU.zip or the franco.Kernel-r241-384GPU.zip ??

I'm running stock Jelly Bean 4.1.1 someone help?
[Samsung Galaxy Nexus] danielvc:
R241, and I should start with 384GPU.
[Samsung Galaxy Nexus] joeyfong:
r241 384/512
[Samsung Galaxy Nexus] Kostas1601:
Thanks a lot guys, what's the difference? is the GPU overclocked in the 512 one?
[Samsung Galaxy Nexus] danielvc:
yes. you can try 512 and see if everything is stable (like playing videogames). if not: switch to 384 (or if you want to save a bit of battery, install 384)
[Samsung Galaxy Nexus] joeyfong:
yeap, 384 and 512 are clock speed of gpu
[Samsung Galaxy Nexus] djjonastybe:
franco let me know when you read this.

I have several frequencies on the same MPU CONTROL FUSE which also causes them to run at the same calibrated mpu voltage

I have this way 1200mhz and 1400mhz running at 1200mv which i believe not to be enough.

On your kernel this doesn't seem to be a issue.

I wonder how you fixed it.
[Samsung Galaxy Nexus] Hanny:
Definition of Popularity.

Hail franco!
[Samsung Galaxy Nexus] franciscofranco:
Because I have a safety routine that every < 1350mV MPU slot is not calibrated automatically by smartreflex. Search my repo.

What do you think?
[Samsung Galaxy Nexus] whittikins:
Franco, what do you think about post http://xdaforums.com/showpost.php?p=30178182&postcount=24971 ? Quoted:

Thanks for the continued work you put into this. The phone is definitely not the same since stock :)
[Samsung Galaxy Nexus] atiartstudio:
Change dramatically the way that I feel my nexus ! Thank you. Now if and the GPS loc indoor would be awesome.
[Samsung Galaxy Nexus] krneki10:
Do you guys use custom power modes or Franco power modes? If so, which ones? I currently have set it to None and I have no idea if I should change that.
[Samsung Galaxy Nexus] LNJ:
I've never used it.

---------- Post added at 12:30 PM ---------- Previous post was at 12:25 PM ----------

So what does input_boost do exactly?

I know what all the other ones are for kinda!
[Samsung Galaxy Nexus] dascjb:
input_boost supposedly makes the screen "feel" more responsive by boosting the cpu freq when a touch is registered
[Samsung Galaxy Nexus] LNJ:
Thanks. How about the other boost?
[Samsung Galaxy Nexus] chugger93:
Go bless this kernel. Things seem to be well battery wise so far. I'm testing some governor settings and other things in the Franco app. But only 83% and I'm doing over 7 hrs so far with 40 some minutes on screen. Good stuff!!
[Samsung Galaxy Nexus] ZiCoN:
r241 is amazing for me..... running 384/1228/ondemand. 12 hours 8 minutes on battery, 3 hours 48 minutes talking on the phone and 1 hour 27 minutes screen on time... That's pretty ok in my book :)
[Samsung Galaxy Nexus] Landara:
Amazing kernel sir but I have switched ROMs. It was epic with JellyBelly but that project has been abandoned. So I moved on to paranoid and its great! But sadly it won't even boot up with your kernel installed. This is a clean install of course!
[Samsung Galaxy Nexus] bat0nas:
Does anybody have BTLowPower kernel wakelock?

Im not even sure this is kernel related. Maybe radio.

It uses my cpu all the time and cpu doesnt go to deep sleep.

Any ideas? Am I the only one with BTLowPower wakelock.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
This kernel + extended battery (3600) = not having to charge for two days sometimes three lol
[Samsung Galaxy Nexus] franciscofranco:
Yes, I'm also very happy with r241 :)
[Samsung Galaxy Nexus] Savant:
Is there a way to get a notification when you're phone is getting hot?
[Samsung Galaxy Nexus] :
r241=♥ :D
[Samsung Galaxy Nexus] dascjb:
I believe that is the boost pulse setting. Has to do with triggering boost when the input_boost function is enabled. From what I understand setting any value to this is not recommended as it will cause the phone to run at the hispeed_freq constantly.
[Samsung Galaxy Nexus] Marcb:
I believe we have a Milestone candidate! :D
[Samsung Galaxy Nexus] franciscofranco:
Thats something I can program into the app I believe :)
[Samsung Galaxy Nexus] whittikins:
Franco do you use stock settings or overclock?
[Samsung Galaxy Nexus] Savant:
Very much appreciated.
[Samsung Galaxy Nexus] franciscofranco:
Stock, I dont need overclock.
[Samsung Galaxy Nexus] Savant:
What tweaks do you use on your own kernel?
[Samsung Galaxy Nexus] sachilleas:
Will you add cm10 support soon? I am using paranoid android and i don't want to leave your kernel for another one!
[Samsung Galaxy Nexus] harmohn:
I'm using r241 with a CM10 alpha.
[Samsung Galaxy Nexus] sachilleas:
I am using it myself with paranoid rom. Apart from a hot boot (once) everything works ok, but i read many complaints about incompatibility.

I think i read in nexus 7 (some days ago) thread a franco's post about supporting cm10 in the future..
[Samsung Galaxy Nexus] ac3theone:
Getting incredible battery life with this
[Samsung Galaxy Nexus] noshet:
Guys, i am new to this and been reading thru a lit lately.

I'm really happy with the performance of this 241.

Been running it in OTA JB from bigxie.

Just wondering on the settings where I could get most battery life with this. Been reading a lot but no definite answer.

Some I get best with interactive, sometimes with ondemand....

Also do u guys stay in bfq or in deadline?

I'm now running everything in default.

Thanks in advance.
[Samsung Galaxy Nexus] Savant:
I like em all but I use deadline and interactive . I like to experiment to see what are the best settings but everyone's different.
[Samsung Galaxy Nexus] JkdJedi:
Where can we change the IO at?
[Samsung Galaxy Nexus] Mattymat:
Yeah, you can using Rom tool box in the kernel settings.
[Samsung Galaxy Nexus] qsec:
It would be nice to be able to save a couple of different color settings in color control that you can set individually. And then just click on them to apply them.

Now when you are trying different settings its hard to se the difference because the time it takes to change.

I think this has been mentioned before.

Cheers and keep the good work up.
[Samsung Galaxy Nexus] atiartstudio:
Franko is it possible to have this optimization embedded in the kernel.http://jsharkey.org/blog/2010/07/01/android-surfaceflinger-tricks-for-fun-and-profit/
[Samsung Galaxy Nexus] yumeul:
hi Franco... it would be nice to add an option to change I/O in your kernel app
[Samsung Galaxy Nexus] slvrarrow:
Why would you want to change from BFQ? Its that thats made this so much smoother since 240
[Samsung Galaxy Nexus] Antob125:
I've been running 729-1228 Wheatley for a while now but I've been hearing such good things about interactive that I wanted to try it at 729-1228. Should I change anything in governor control or just leave as is? Any recommendations would be appreciated.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RevengeFNF:
Google says that Interactive is the new Default because of Project Butter. So i guess we should stick with Interactive.

I use mine at 384 -1536. I don't see any visible difference in battery life using 1228 or 1536 and the phone feels snappier in some occasions.
[Samsung Galaxy Nexus] RayGarden:
MoDaCo Jr5 (JRO03D / 4.1.1 with Franco's #241

Is anyone having Experience with MoDaCo's Jr5 ROM in combination with Franco's #241 Kernel?

I'm NOT having this Amazing Battery Life..... yet !!!

=====================================

Running #241 - 384 mhz

- Ondemand / 350-1536 / no undervolting

- 729 max screen off / turn thermal throttle off / turn fsync on (both checked)

- color control 146/160/205 -4/0/5 / -5 / 1.0

- Smart Reflex On for all (MPU / IVA / CORE)

* Brightness 50%

* GPU Rendering for 2D = checked

Current Baterry Consumption: 4 hours on Batt, 32 min Screen On, 82% left

Waiting your comments.

Thanks
[Samsung Galaxy Nexus] derPianist:
Turn Thermal Trottle Back On first and Disable GPU Rendering.

It causes more problems than anything.

Go interactive with max 1036mHz and set Screen Off to 300mHz.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] RayGarden:
OK Done. Let's see how it proceed. Thanks
[Samsung Galaxy Nexus] prembox:
I gave my WP7 handset to my wife and picked up G-Nex in July12 for Android's flexibility to customize though its (WP7) the smoothest ever I used...used i9000 before that for 2 yrs!! One of the first things I did was buy Franco's Kernel Updater in my quest to get liquid smooth UI scrolling (like in WP7 and iPhone) on homescreens, app drawer and setting menu etc but I'm yet to get there.....dunno with what settings on Governor Control, GPU version (384 or 512) other settings will help me get there.....darn elusive this is. I've all of it....amazing battery perf, snappiness, perfect color etc but yet to get rid of the Microlags, stutter while scrolling on homescreens, app drawer and setting menu.

Currently I'm on Stock JB (thru OTA over 4.0.4 Yakju) R241-512 Mhz-Interactive CPU Gvrnr, Performance Power Mode, 2D Rendering Disabled and everything else on default settings!!!

Franco, others...any thoughts??
[Samsung Galaxy Nexus] franciscofranco:
You did pretty much everything you could I believe. Try a little overclocking to 1.3 or 1.4ghz.
[Samsung Galaxy Nexus] The Gingerbread Man:
Prembox, try this rom http://xdaforums.com/showthread.php?t=1790532 as Franco is too humble to suggest it himself :rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
Hahaha well said :)

Sent from my Rasbeaned Galaxy Nexus powered by Trinity.
[Samsung Galaxy Nexus] whittikins:
In governor control, what is your min_sample_time? Bump it to 60000 or 80000.

EDIT: Also, get on a custom ROM for JB 4.1.1 asap! As suggested above, this one is really good: http://xdaforums.com/showthread.php?t=1790532
[Samsung Galaxy Nexus] bradm23:
Does anyone know how to get the colors the same as Trinity? I have been switching back and fourth. Francos seems better for performance however I miss trinitys colors
[Samsung Galaxy Nexus] thegtfusion:
Erhmm just set the trinity color values in the franco kernel app...

red and green: 135

blue :214

thats all ;)
[Samsung Galaxy Nexus] ledionkoci:
And the other values???
[Samsung Galaxy Nexus] bradm23:
Seemed like it was a little different. I know trinity doesn't use the omap4 gamma adjustment, however how can not use this after selecting a value? Also, what is the Trinity contrast used?
[Samsung Galaxy Nexus] osm0sis:
Check the Galaxy Nexus Collaborative Optimal Color Settings thread. We've got a lot of color settings collected in the open spreadsheet, including Franco and Trinity defaults. Feel free to add your own if you find something different that works well.
[Samsung Galaxy Nexus] t0wlie:
Contrast is -24
[Samsung Galaxy Nexus] chugger93:
So I posted this yesterday

http://xdaforums.com/showpost.php?p=30224513&postcount=25041

here are my battery stats finally again after the battery is drained.

Wow I made it far!!!
[Samsung Galaxy Nexus] bradm23:
Thanks for the info. One last question, is there any way to deactivate omap4 gamma control?
[Samsung Galaxy Nexus] The Gingerbread Man:
Stock value is 1.0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Tarun95:
Do u guys have any option enabled in developer options which improves performance ? And gpu rendering ? Check or uncheck ?
[Samsung Galaxy Nexus] meanwhile:
Omap 1.0

Trinity - 5

---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------

And

0,0,0

That's best for me, though blue 205
[Samsung Galaxy Nexus] osm0sis:
1.0 is the same as off in terms of screen, but to fully deactivate (for eg. to remove the flicker/glitch as the app sets omap4 gamma during boot) you have to clear data + cache on Franco app.
[Samsung Galaxy Nexus] nikulogical:
Try a different rom and different launcher like nova beta.
[Samsung Galaxy Nexus] Tarun95:
Try this. Set hispdfreq to 1036800 and hispdload to 90.
[Samsung Galaxy Nexus] zybertooth:
Just my observation for 240 & 241.. Ondemand tends to react more (to use higher frequencies) than Interactive. Shouldn't it be the other way around?

Setup:

- Paranoidandroid 1.98 (CM10)

- Franco 241-512 (729-1536)

- Everything default except for change governor & min/max

- Reset CPU Spy before playing Death Trigger for each governor

Ondemand:

View attachment 1262765

Interactive:

View attachment 1262766
[Samsung Galaxy Nexus] The Gingerbread Man:
You have the same as me :cool::thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mattymat:
I believe cm7 had that, but I could be wrong. I remember using a Rom on my vibrant that included those settings.
[Samsung Galaxy Nexus] franciscofranco:
They are only presets, every one can do it using the color interfaces available.
[Samsung Galaxy Nexus] superbobup:
I think this is due to Franco doing something with the Power HAL in his kernel to use the mid/low freqs more on interactive...don't quote me on it tho :p
[Samsung Galaxy Nexus] loudaccord:
FF 241 and Liquid 2.0 beta2 is a winning combo for me. Best battery I've had in some time and it's super responsive. A++ I don't see changing anything for some time.
[Samsung Galaxy Nexus] TEK112:
Until 242 and then Liquid 2.1...lol

There is no end!
[Samsung Galaxy Nexus] zybertooth:
So you've observed it as well?

Looks weird then.. almost like Conservative?

Game-wise, i think ondemand feels better.
[Samsung Galaxy Nexus] cyanoviper:
franco, i dont really know if its kernel related or not but: do you happen to know if address space layout randomization (aslr) is implemented and working in the latest jelly bean builds? thank you in advance!
[Samsung Galaxy Nexus] JarGnex:
Fransisco I'd like to have some color presets in my app , is it possible ? Thanks

Oh and the latest kernel rocks ! :)

Sent from my Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] franciscofranco:
There are a lot of planned features, that being one of those.
[Samsung Galaxy Nexus] superbobup:
I haven't experienced it as I'm not running FK at the moment. I've read all the pages and IIRC it had to do with the Power HAL. Try a search for 'HAL' and some useful posts may come up :)
[Samsung Galaxy Nexus] whittikins:
This is definitely bugged. I experienced the same issue. Here's what I did to solve it:

- remove all apps and init.d scripts that change CPU/governor settings (including Franco's app)

- wipe cache

- flash the kernel that came with your ROM (or flash the ROM if you don't have the individual kernel)

- flash Franco's kernel

- install Franco app

I don't know WHICH of these steps actually fixed the problem, but the whole process worked for me. Mine was stuck on the 700 mhz frequency when using Interactive, which it definitely should not do. Hope this helps.
[Samsung Galaxy Nexus] eddie_gordo:
I have just noticed something that I would love to see in the Updater app, while I was playing a bit with the cpu settings. Instead of just having a Create/Delete custom power mode, we should have an Edit custom power mode. :) This way I wouldn't have to be creating custom power modes every day and getting an enormous list of "daily driver 1", "daily driver 2", "daily driver n". :) I would be editing only the one I am using as a daily driver. :) If you have the time, Francisco, it would be great! :D

Other than that, 241 is still rocking my GNex! :D Keep it up.
[Samsung Galaxy Nexus] The Gingerbread Man:
If you keep up like that youl be up for 9 hour screen on time :what:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nav200:
May I know what ROM and which version of Franco kernel you are using?
[Samsung Galaxy Nexus] bradm23:
Does anyone have any info on how to get rid of modem_USB_gpio kernel wake lock? Eating up about 6 minutes of wake time in about 6 hours of standby
[Samsung Galaxy Nexus] hotnikkelz:
I'm getting awesome battery life with lazy governor 1036 729

Color settings 200 215 280

-2 0 10

Cab disabled

Trinity -23

Omap 1.0

I get barely 1 percent drain an hour
[Samsung Galaxy Nexus] k_nivesout:
241 has been running great for me, with the exception of two small issues:

Settings>storage results in settings FC.

Kernel info in "about phone" menu shows "unavailable". I remember getting the settings FC with storage menu on lean kernel a few exps ago, Imoseyon seemed to fix it with the newest releases.

Toro / CM10 Jellybro 8/15
[Samsung Galaxy Nexus] eddie_gordo:
Settings -> Storage doesn't have any problems for me. Also, the unavailable on CM10 is a known issue and it seems to be ROM related, not Kernel related. I'm on AOKP and in About phone I can see the Kernel info just fine. :)
[Samsung Galaxy Nexus] k_nivesout:
Thanks, I wasn't 100% sure if the "unavailable" thing was on the ROM or kernel side. For the storage settings FC, like I had said, it was something I experienced on lean kernel before and an updated kernel fixed the FC, so didn't know if there was a fix that might be able to be done on the kernel side. Or maybe just a CM10 issue?
[Samsung Galaxy Nexus] Dattack:
I was getting unavailable with other roms but it is showing up on Xenon HD.
[Samsung Galaxy Nexus] nnnnr14:
All the time I was oc'ed no WiFi just straight up 4g

sent from my 1.421hz Franco kernel Gnex!

---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------

With your colors all over 200 you can burn out your display very quickly.

sent from my 1.421hz Franco kernel Gnex!