yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] SrTapir:
1 Question:

There's any way to remove intermediate frequencies like those between 384 and 1344?

At the end I only use this two, the lower to save battery and wich is sufficient to move the entire ICS and to perform simple and common tasks; and the other one that is necessary when I need performance like when I'm browsing, playing, etc.

This way would be very easy to configure a only and simple (in options) Governor depending on the needs.

If I need performance I only have to reduce the boundary when the high freq is triggered, and when I need batt life the contrary..

What do you think?? :confused:
[Samsung Galaxy Nexus] drawde40599:
http://xdaforums.com/showthread.php?t=1405345 . Don't no what model or rom u use but gsm xxla2 is current euro radio, came with 4.0.4 update

That radio u use was best for me but it don't really work for 4.0.3 or .04
[Samsung Galaxy Nexus] moe6:
Sounds to me like it'd just stay in the highest clock speed most of the time unless it sees no syncing jobs and such.
[Samsung Galaxy Nexus] franciscofranco:
Its a wakelock caused by having the device plugged to your computer usb port.
[Samsung Galaxy Nexus] The Nexus Project:
I agree with your point on "race to idle". The "Best" Governor scaling selection is all about individual users usage patterns. So what's the best for me may under perform/drain battery etc. for you. The easiest thing you can do to apply the best settings for your usage pattern is to learn the intricate differences between governors. Interactive for example dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user but scales much faster to maximum frequency than on demand.

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] mad_vtak:
I am using the CM9 4/29 nightly with Franco Milestone3 kernel, i am just trying to find ways for my radio/signal to stop dropping.

XXKK1: that came with my phone, i have the White GN model

Edit: i posted in that Radio thread to see if anyone else can help. Thanks Drawde for responding.
[Samsung Galaxy Nexus] Metallice:
Well. Shocking results right there :p. Mathematically you can see this too. Battery use increases quadratically. Here. I made this.

Battery Consumption vs. Frequency (using Smart Reflex calibrated voltages)

Battery Consumption vs Frequency (if voltage set at 1000mv for every frequency)
[Samsung Galaxy Nexus] SrTapir:
Was little obvious yes.. LOL

This charts are amazing, no room for any doubts.
[Samsung Galaxy Nexus] drawde40599:
Its 100000% ur radio that's a 4.0.2 radio u have, u probably have the wrong bootloader also might wanna look into that also, bootloader has nothing to due with signal but could possibly effect battery ....I recommend pulling bootloader directly out of Google's image file, Having the " wrong "software could effect ur results with Franco kernel .... https://developers.google.com/android/nexus/images#takju . The radio in there also ....pm me if u need help
[Samsung Galaxy Nexus] Tommebaas:
My sustemui crashed on the latest nightly with aokp 5. But milestone 3 works perfect

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rolear8:
Don't know how to extract the bootloader and the radio... also how can I check what bootloader I have?
[Samsung Galaxy Nexus] drawde40599:
Check ur pm box, don't wanna tie up this thread: )
[Samsung Galaxy Nexus] clepsy:
Tried R151, all fine used gamma 6, the screen looks nice for me, the lower frequency work well; however I'm seeing the same lags that were before m2 such on playing and mkv movie or a heavy game such as gta 3, anyone experience this?
[Samsung Galaxy Nexus] eddie_gordo:
I wasn't able to find the following information: What is the most recent release? M3 or nightly 151?

And where can I find the changelogs? Only in the updater app?

Thanks
[Samsung Galaxy Nexus] axne1:
M3

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] spyz88:
Franco, would it be possible to add Touch Wake to the next version of your kernel?
[Samsung Galaxy Nexus] schizophrenia:
pardon me for being a bit noob

but is this implying turning on Smart Reflex actually drains more battery?
[Samsung Galaxy Nexus] Diger36:
R151. It came out last weekend.
[Samsung Galaxy Nexus] Cutting-TM:
Already being answered, no.
[Samsung Galaxy Nexus] loudaccord:
Might be a dumb question but would this kernel mod work for us?

http://xdaforums.com/showthread.php?t=1621808
[Samsung Galaxy Nexus] franciscofranco:
You can use that, but I dont like it nor I offer support if 3rd party mods are used.
[Samsung Galaxy Nexus] franciscofranco:
r151 is more recent. Nightlies changelogs are in the app at all times. I only post the nightly changelog once when I release a new one.

r152 should be out today so if you're going to flash a nightly release you can hold yourself for r152 if you want to.
[Samsung Galaxy Nexus] eddie_gordo:
Thanks for the answer and for the advice! :) It is a pleasure having a kernel running on my GNex that was developed by Portuguese guy! :)

Keep up the good work Francisco!
[Samsung Galaxy Nexus] loudaccord:
fair enough, I was just curious on your take. I'll pass on that mod.
[Samsung Galaxy Nexus] ArmanUV:
SOD on 151 right after a call. No UV, Interactive 350-1350.
[Samsung Galaxy Nexus] franciscofranco:
Hmm first SoD report in a while! Pretty sure its not kernel related or I would've been getting a lot of reports lately.
[Samsung Galaxy Nexus] CerB:
R151 running great, 2 hours screen on and still 40 % left. 384-1344 interaktive

Sendt fra min Galaxy Nexus med Tapatalk2
[Samsung Galaxy Nexus] franciscofranco:
r152

* Fix IVA and CORE higher voltage after boot. Now they boot up on the lowest OPP like its on stock kernel. This should increase battery life

* Add 2 VFP patches from android-omap-3.0 Google branch for stability purposes

* Made 384mhz CPU minimum frequency by default to prevent some boot up issues that were rarely seen in a few devices that didn't like the 192mhz step
[Samsung Galaxy Nexus] eddie_gordo:
Flashing as I type. Thanks :)
[Samsung Galaxy Nexus] drawde40599:
I had 2 yesterday never had ever be4 151 posted them when they happened
[Samsung Galaxy Nexus] dpaine88:
Are the voltages correct on Milestone 3? Was the change just related to something in r151?
[Samsung Galaxy Nexus] Metallice:
No. It doesn't.The second graph is just a theoretical model if all the freqs were set to 1000mv which would be impossible anyway. Turning smartreflex off would just shift the line on the first graph up.
[Samsung Galaxy Nexus] franciscofranco:
Milestone 3 still has IVA and CORE boot up on OPP100 because at the time of M3 release I didn't know which commit caused it.
[Samsung Galaxy Nexus] atsavlis:
Franco, what do you suggest are the best frequencies and governor to use with your latest nightly??
[Samsung Galaxy Nexus] dpaine88:
I think he's using the 384-1228 on interactive

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Franco any of the changes related to the heat issue some r having? I haven't flashed 152 yet....
[Samsung Galaxy Nexus] dpaine88:
Francisco, any thoughts on running the 1060mhz as the top slot to save battery without losing performance?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I don't have heat issues. If I can't replicate I can't fix (if theres something to fix, which I doubt).
[Samsung Galaxy Nexus] jpbelli:
I loved 192 mhz, and worked great!

So I won't be able to use 192 mhz from 152 on?

Thanks!
[Samsung Galaxy Nexus] franciscofranco:
1036mhz max will definitely use less power than 1228mhz, but that's obvious :p
[Samsung Galaxy Nexus] franciscofranco:
Don't make things up, no one said that. I only said I made 384mhz cpu min frequency by default.
[Samsung Galaxy Nexus] dpaine88:
Hehe I know , and so far with your kernel performance seems nearly the same as 1200 with 1060

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jpbelli:
I was just asking franco... It was a QUESTION!

Thanks for keeping it up!
[Samsung Galaxy Nexus] brianisme:
Flashing r152 now, coming from r121! Thanks once again for the work!
[Samsung Galaxy Nexus] SkaDiZ:
Sorry if this been asked/answered before... Can i know what is the thermal throttle limit for this kernel? Is it default or Franco did increase it?
[Samsung Galaxy Nexus] willl03:
Hmm, phone rebooted twice after flashing r152 in CWM, wiped dalvik and cache before. Phone booted, loaded launcher, rebooted. 2nd time nova launcher had lost its settings, phone rebooted again after a few seconds. On the third boot the phone stayed up. If this is not kernel related, I have never run into this into previous builds and been using your kernels for a long time, didnt change anything else in my config.

Seems to run well now, weird.
[Samsung Galaxy Nexus] drawde40599:
I understand exactly what you mean if you can't duplicate it you can't fix it, but your kernel is only one out of 4 ive tried giving me and according to ur thread many others heat issues . But nevermind thanks for the help .
[Samsung Galaxy Nexus] wbknox:
will you be adjusting milestone 3 ?
[Samsung Galaxy Nexus] :
Thanks man...I think I can not read ....:confused:

Everything is explained now :D :)I had to miss a line...

Thanks for the reply.

PS:In any case it is the best kernel i've tested
[Samsung Galaxy Nexus] aron7awol:
Updated results w/ nightly #6 UV:

AnTuTu:

Apex @ 1.35 GHz - 6570

Franco #6 @ 1.2 GHz - 6390

Apex @ 1.2 GHz - 6012

Franco #7 @ 1.35 GHz - 6900+? (hypothetical)

Vellamo:

Apex @ 1.35 GHz - 1081

Franco #6 @ 1.2 GHz - 991

Apex @ 1.2 GHz - 970

Franco #7 @ 1.35 GHz - 1100+? (hypothetical)

I'm going to try to come up with a semi-scientific way to quantify the battery savings if undervolted by 200 mV. I hope to have some results to post tomorrow.

Franco:

Thanks for adding the 1.35 GHz step in #7. Do you mind elaborating a bit as to why you think the 350 MHz step is causing the device to wake up out of sleep more often than it would if running at 700 MHz?
[Samsung Galaxy Nexus] :
Ho...What's wrong with me?

If you can see my previous post...

Sorry...noob with GN...but not with Android....

Thanks :)
[Samsung Galaxy Nexus] lupick:
Dear all

with #6 I still have issue with GTA. I've also deleted and re downloaded data files...

How to fix it?

Thx

L.

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] aron7awol:
Apex is a different kernel that supports OC to 1.35 GHz. Franco #6 does not, but Francisco said that #7 will. Soon enough I'll be able to replace the hypothetical numbers with real ones :)
[Samsung Galaxy Nexus] :
It's unfortunate that I had to log onto XDA to get this but it's a bad ass kernel on RomanBB's LTE TORO AOKP rom.

If you have time, consider creating a thread on Rootzwiki.
[Samsung Galaxy Nexus] ro_explorer:
Please, do not remove it from the possible stepping. Put your defaults to 700 or whatever you feel comfortable but leave the 350 as an option. I really need that step, not for "sleep mode" but for some long active runs. It will be sad not to have this low frequency mode available if needed.
[Samsung Galaxy Nexus] MYAbln:
soooo with #7 GTA noww works for meee:D thanks for that, but Modern Combat 3 doesn't work :( on my friends GN with 4.0.1 and also stock kernel works for him! I want to play that gamee...
[Samsung Galaxy Nexus] lupick:
Where did you get #7?

L.

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] jhericurls:
Any chance of adding an 180 option? Im running the imoseyon kernel and the uv is running great.
[Samsung Galaxy Nexus] franciscofranco:
That UV ain't working sorry, thats too low. Try tp set it to 0 and you'll see it won't crash.
[Samsung Galaxy Nexus] ttlycnfuzd:
Francisco - is there a way to verify what/if voltages are actually working on a kernel? for example, I have yours down to:

Is this actually working?
[Samsung Galaxy Nexus] :
this kernel works great, however, on my LTE AOKP rom by RomanBB, sometimes there is a lag when unlocking the phone. Besides that, no lag whatsoever. This is at stock clock speed that the kernel comes with. Is that lag normal?
[Samsung Galaxy Nexus] jhericurls:
sorry, what's tp?
[Samsung Galaxy Nexus] superbobup:
i believe he meant "to" not "tp".

If I understand francisco correctly: if the UV is working properly, then the system should freeze/reboot when you try to force the voltage to a very small level. However, if the UV is broken then no matter what you try to "force" it to, it will still run.
[Samsung Galaxy Nexus] jhericurls:
Well i set 180 to 550 and it did crash. But 575 seems to be working fine.
[Samsung Galaxy Nexus] beekay201:
the man said he's still testin

lol why the change then? mind to share a cpuspy screenie with that? i mean it, but post a pic a bit smaller please. makes it harder to read and follow conversation in a thread, when people are on their phones, on capped data connections. ;)

mine are similar, and they still work fine since UV was introduced (haven't changed almost nothing, latest "closest-to-sweet" point was for 700mhz) - normally faster speeds will require more mv, and slower speeds will require less. still, how much some devices can UV is unbelievable :) i'm almost reaching my device's limits, i think. already found lowest/highest: 850mv@350mhz and 1100mv@1200mhz. If i lower 350mhz to 825mv, i loose gsm connection (modem fails :p), if i set 1200mhz to 1050mv i get lockup, black screen, reboot. :D 2 more to go!

hmm? you can do 575mv@180mhz? where's 180mhz step? i don't have it. is it possible? probably. why should i need it?

// phone and me dialog

can we have 180mhz at 575mv? i don't know if i want to. i'm not sure you keep playing music when screen is off without stuttering, or even wake up when i asked you to.

// phone and me dialog end

nightly#5, fast forward 10hrs nightly#6 stats, light usage, XXKK6

great work Francisco - performance is even better (as far as the eye can see, didn't bench or anything), battery life is starting to get near to my previous device, except on a bigger screen. :thumbsup: :D:D let's see how it goes on heavy usage. last time was 11h 34mins 100% to 0%, with some kernel on 4.0.2 (don't remember right now eheh)

// rant

really digging nova launcher*patiently waiting for cm9-maguro nightlies

// end of rant
[Samsung Galaxy Nexus] aleve1983:
in more kernel same governor not work well, ondemand interactive... if you use cpu spy you can try set ondemand or interactve governor and scrol drawer for few second, after open cpu spy and you can see cpu is much much time on 350 mhz infact scroll is not smoth. i use adw ex

sorry for english, i hope you understand
[Samsung Galaxy Nexus] sloppy1:
voodoo

could you include voodoo control support
[Samsung Galaxy Nexus] nory82688:
This is where I have my voltages set right now with no issues. Does this seem correct?
[Samsung Galaxy Nexus] aquavalanche:
Just installed r152 on Liquid Smooth 1.35..

Will try it and see the difference..

Is it a good idea to put 192 as minimum frequency?
[Samsung Galaxy Nexus] Emilius:
Jusy install BusyBox and franco.kernel app will normally work :o)
[Samsung Galaxy Nexus] dwang:
Any chance of adding 1.5ghz CPU speed?
[Samsung Galaxy Nexus] franciscofranco:
Can you tell me how I can replicate that issue?
[Samsung Galaxy Nexus] franciscofranco:
Yes its planned.
[Samsung Galaxy Nexus] Flukester69:
How about the FC in your franco app when you swipe to settings and when using auto flash? :o Happening for others too. Was kinda hoping you'd notice my earlier post. :).
[Samsung Galaxy Nexus] Culex316:
Maybe I've been really lucky but my device has not experienced any random reboots or odd behavior with any of your kernel builds whatsoever (even with 384mhz GPU), the only thing I noticed about this new nightly build r152 is that the sound is a bit lower than the previous nightly. ( I have stock 4.0.4 ROM)

Other than that the battery life is amazing, I am at 39% and with 4 hour screen time and 15 hour standby time since last charge, and of course, performance is rock solid.
[Samsung Galaxy Nexus] dpaine88:
Care to share your min and Max and gov?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
Min 192mhz max: 1228mhz gov: interactive

I forgot to mention I also have an extended battery (3500mAh) and brightness set to auto, but normally :o sorry if I deceived anyone/got anyone's hopes up for nothing.

But even with the extended battery, franco's latest builds have significantly reduced battery drain to the point where it rivals my old blackberry.
[Samsung Galaxy Nexus] franciscofranco:
Sometimes I miss posts. I don't know of any FC's, but I'll take a look.
[Samsung Galaxy Nexus] johno168:
Franco... Can't seem to download 152 off your website. And it doesn't show the update in your app.

Edit: works but no update through app.
[Samsung Galaxy Nexus] joshdu1125:
Franco, I am pretty new to this kernel, thx for your great work.

I am just a bit confuse about the GPU OC, I thought previously you are against it but now there is a 512 oc option for the nightly and I found a lot of people using it.

Is there any new development that i missed? thank you
[Samsung Galaxy Nexus] drawde40599:
I've tried multiple roms ( including factory ) from full wipes, ( factory reset 3x wipe cache 3x dalvik cache 3x format system 3x ) yes this is definitely over doing it but ..... install aokp m5 is rom atm ( I have tried others ) I've tried flash ur kernel right after fresh rom while still in recovery, I've tried flashing with a reset kernel in-between fresh rom and yours while still in recovery, I've tried let boot up with reset kernel then going back to recovery wipe caches install your kernel, I've tried stock Google boot.img from fast boot before install of your kernel, yes this is over doing it but I've tried everything, but anyways after your kernel installed with your settings I.always leave your settings till I no it works right, everything will be good for say 30 min then it just starts getting hot ur app says 60°c 63°c I mean the glass is even hot, and its just with internet use, this is bare bones rom and gapps nothing else installed ( testing ), reboot don't help and once it dose it, it don't take 30 min anymore it gets up to hot fast, I've tryed cache wipe also while ur kernel installed don't help, I've tried other governor's also same thing hot, I was thinking the phone was broke but other kernels work, I'm using gladios current kernel and with exact same use it never go over 49°c . I dunno???? Started at build 141, everything be4 that worked just fine, I haven't flashed 152 yet but I'm going to later ..... I work on 80,000$$$ cars all day so I understand 100000% that if u can't duplicate the issue u can't fix it . Just don't get it . Radio and boot loader r current, probably would not matter but .... and I'm pretty sure HOT don't show on a log so pointless to send that .....I no I'm a asshole don't mean any disrespect:)
[Samsung Galaxy Nexus] ubernode54:
No. For a processor to run at a given frequency, it requires a certain amount of power. SR is giving the processor the correct (as far as SR is concerned) voltage (and as a result, current) to operate correctly. By forcing a lower voltage, less current and battery drain, but only to within the limits of your hardware. Like over clocking, you can expect to start seeing erroneous operation when pushing the hardware to either limit.
[Samsung Galaxy Nexus] drawde40599:
Oh, and internet use is wifi or 3g/ 4g don't matter ...

Thanks
[Samsung Galaxy Nexus] franciscofranco:
I just tried like you said, fresh rom, no apps, just gapps, stock kernel settings. I plugged it to the USB and ran a few quadrants. Highest I could get was 49ºC. =/
[Samsung Galaxy Nexus] dpaine88:
LOL Forgot to mention the tiny fact your battery is 2x as big as mine

Just messin, thanks for responding so I know now
[Samsung Galaxy Nexus] franciscofranco:
#4.3

* Added OMAP Gamma interface support (only works for r151 or newer because older kernel versions don't have that interface in the kernel). It persists through reboots

* Added a new Interactive parameter on GovernorControl called Boost. Same as OMAP Gamma interface it's only for 151 or newer

* Fixed a lot of bad code through the app to get rid of a black screen hang when the app is installed for the first time, and to fix an FC when accessing ColorControl for the first time
[Samsung Galaxy Nexus] coolzjai:
dude,

to narrow down the heat issue since you still face it on the latest nightly build, i would suggest you to turn off everything that is non-kernel related, to see if you still can feel the heat after 30 minutes. I myself have this issue before M3, and no more after that with a full wipes, and clean up media storage.

1. OFF 3G, WIFI, AUTO SYNC, and GPS.

2. DO NOT install betterbatterystats, cpuspy, and franco.kernel.updater.

3. Leave your phone idle, and see if heat happen.

4. Switch back items from step1, ONE AFTER ANOTHER, see which module causes the issue.

5. report back ^^
[Samsung Galaxy Nexus] BrUhNiGGs:
I noticed one thing that makes my phone hotter than it usually gets; setting the min to 729Mhz. Just a heads up for those who get high temps if thats what they set. Setting it to 384 or lower keeps it at a cooler temp but still hot for me. It's weird, when I was using Liquid Rom I got high temps of 60C. Then I switched to AOKP which made it cooler. But now, it's getting hot again around the 50C with either 384 or 512 GPU.
[Samsung Galaxy Nexus] coolzjai:
Thanks!
[Samsung Galaxy Nexus] franciscofranco:
50C is ok depending on whats the usage.
[Samsung Galaxy Nexus] javi3k:
Idk if was my phone or rom but since aokp m5 and fr m3 my phone got to 70 scare me alot even though my normal temp are around 44 - 54 i live in a hot city tested with other rom and kernel
[Samsung Galaxy Nexus] drawde40599:
Clean up media storage?? at idle (screen off u mean right? )its fine 29°c Franco app only thing besides gapps I had on .. but I didn't think of shutting down those . K kool ima try gota go pay attention to the wife first o_O ,:) thanks appreciate it .
[Samsung Galaxy Nexus] iGoogleNexus:
Love the new OMAP gamma <3

- Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
50 I would call normal, both my Euro and at&t gs2 and my skyrocket do that and the gn basically same thin plastic as those . Its the over 60 when whole phone slows down to a crawl and glass gets hot I'm personally talking about
[Samsung Galaxy Nexus] dpaine88:
I ran 3 Quadrants while plugged into USB and couldnt get it to go any higher than 46C..

Liquid 1.35, stock kernel settings
[Samsung Galaxy Nexus] joeyfong:
Awaiting at AndroidPIT

---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------

Which value are u using?
[Samsung Galaxy Nexus] javi3k:
i got 46 by just messing TT_TT ive never been under 37 iddle from any kernel i guess my phonee is just like my city hot =(
[Samsung Galaxy Nexus] iGoogleNexus:
I'm using the 1.2 :D

- Galaxy Nexus
[Samsung Galaxy Nexus] splus:
I've had EXACTLY the same with r151 running 192 MHz CPU min, and only after I intentionally rebooted the phone. Phone was running OK for 2 days prior to the reboot, liking the new 192 MHz minimum frequency.

I thought the reboot problem was because of low min CPU frequency but since this happened for you with r152 which has 384 MHz minimum by default then maybe something else caused this?
[Samsung Galaxy Nexus] drawde40599:
Ya its very small % of users from what I've seen in this thread . Lucky me; )
[Samsung Galaxy Nexus] tyea:
152 @384 working well on my sprint GN (stock). No high temps, good response, no reboots.

Sprint GN, Tapatalk2
[Samsung Galaxy Nexus] jnr21:
Can you give me some information about those GovernorControl parameters, what is that boost thing, if i set it to 5, is it good? And if i set max cpu freq to 1344mhz, do i need to set hispeed_freq to 1344000?

I'm sorry if these are dump questions, but i think it's good to add some little info to those parameters (e.g long-press-popup like in glados app).
[Samsung Galaxy Nexus] BrUhNiGGs:
I'm getting 55C just by using FB app for 10 min. The glass always gets a little too warm. In just trying to aim for 49C and lower if possible like yours. Don't know how I can achieve that.
[Samsung Galaxy Nexus] alteredmass:
GSM Running Nightly #152 512 GPU No problems at all... loving the OMAP gamma