yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
haha. It's been a crazy two days. :) But it's been a blast.

Now, sleep is over, time to get back to work!

Yes and no. Here's what we're thinkin' so far.

THIS POST WILL BE A RECAP OF THE LAST FEW PAGES OF RESEARCH! :)

This was my original settings that I've been using for weeks:

So to make the short hand easier, we kept it in that order and just said: 20000/50/40000/20000 became 20k/50/40k/20k became 2/5/4/2. Make sense?

Here is a breakdown of what they each mean:

This is a good explanation that I wrote back on page 3038:

So Google's default is 10/5/6/2. Lower numbers are all better for performance except min_sample_time (there higher is faster). So our goal is to find a sweet spot.

The default 10 is for "Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load." So we think 10 is too high, but if you go too low, then you'll be using the higher freqs a lot more than you need and it will hurt the battery. So we are leaning towards 6 (60000) for above_hispeed_delay.

The default 5 is for "when the CPU hits X% amount of load, then jump to the hispeed_freq." Again if this one is too low then it will cause the higher freqs to be used more often then they need, so we actually turn go_hispeed_load up a little bit to 7 (70).

The default 6 is for "how long do I wait before

lowering

the clock speed from what it's currently at." So the lower we put this, the better battery will be. We're still trying to decide between 3 (30000) and 5 (50000). Osm0sis is getting more lag at lower levels, and finds the best performance mark at 5. So we turn min_sample_time down a little from stock to help with the battery.

The default 2 is for "wait this long before changing the clockspeeds from what it's at now." While technically 2 sounds better because it's changing more often, Franco believes that by setting the timer_rate to be the same thing as the CPU sample_rate (which is preset at 30000), then that will make the CPU more efficient at switching. So we increased it from 2 (20000) to 3 (30000).

So

TO RECAP

: Using the stuff from above, Google's defaults for these settings are 10/5/6/2 and we are changing them to 6/7/3/3 or 6/7/5/3 (again, still testing that third number for the min_sample_time).

Does that make sense for everyone interested in following along? Any questions? Feel free to try out these settings yourself (the easiest way is with Franco's app or something like Trickster). We want as much feedback as possible on this.

The next kernel release will have the totally tweaked settings for everyone to test without having to change their own stuff.

:):D:laugh::good:
[Samsung Galaxy Nexus] pigr8:
Franco, you provide in your kernel the 230mhz step frequency.. using the same voltage of the 384mhz step? or is it downvolted?

if it's on the same voltage, why should someone use 230 @min freq insted of 384? andvantages?
[Samsung Galaxy Nexus] joaquinf:
Dear franco.Kernel users:

If you are reading this please go back two posts, read and drop a thanks to that. This is how a development thread looks like.

Also when you see osmosis, do the same.

Thanks
[Samsung Galaxy Nexus] nuwan32:
Because you can under volt it more than 384 and save battery
[Samsung Galaxy Nexus] yellowdie:
Dude, that made me smile. :)
[Samsung Galaxy Nexus] venividivici87:
Well.. Many thanks yellow, you have sum up a discussion of 50 posts! Well done!

My little experience: since I've understood the meaning of each governor's option, I use 6/6/3/3.

I'm with custom rom and franco 290, 1305-384 interactive... At least 4h of screen on, even with heavy use and great responsiveness linked to reasonable battery drain.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] pkgnex:
How about 6/7/6/3? I think the lag with 6/7/3/3 may be due to the governor scaling down too quickly and then being asked to ramp back up at the next touch. I have experienced this with embedded code in other electronics, and found it good to try to "debounce" the system by increasing delay times slightly. Battery effect should be minimal as were talking 1/3 of a second, and if "3" is tied to the cpu sample frequency, why not make all the parameters a multiple of 3 to ensure smoothness?
[Samsung Galaxy Nexus] yellowdie:
Makes sense. I'll switch to it and take a look. :)
[Samsung Galaxy Nexus] pkgnex:
It's been working well for me so far... Having the min_sample_time at 3 was very jittery.
[Samsung Galaxy Nexus] Culex316:
I do not mean to derail this extremely interesting convo about interactive governor settings but franco how often do the GPU drivers for our SOC get updated in that OMAP repository? Is it only after every major Android OS update?
[Samsung Galaxy Nexus] creeve4:
I figured I might as well share my interactive settings:

6/5/9/3

hispeed_freq = 729

input_boost_freq = 1036

I went with 30k for the timer_rate to coincide with the CPU sample_rate. The others are multiples of the timer_rate. My reasoning on the higher min_sample_time is that 90k allows for 3 samples (with a 30k timer_rate) and more time for the CPU to get things done before it tries to drop.

What would be really nice is a function that averages the sampled load values taken during the time period defined by min_sample_time and uses that averaged value to determine if it is acceptable to drop the freq.

These settings provide a really smooth experience for me.

It seems to me that values for above_hispeed_delay and min_sample_time should be multiples of the value used for timer_rate. Having a timer_rate = 20k and a min_sample_time = 50k means that 2 samples are taken, 10 ms pass, then the freq is dropped or not. You would get the same result (minus the delay) by using a min_sample_time = 40k.

P.S. I've really enjoyed the ongoing discussion about these settings :good:
[Samsung Galaxy Nexus] osm0sis:
Holy smokes, great summary post yellowdie, it was a fun 5 pages last night. :laugh: Also thanks to joaquinf, you're right, and it feels great to get some real action here and get in on it. :)

I'll keep this short! :p But it's also worth mentioning to everyone who is testing based on yellowdie's post and our new tunables that you should be using r294-test and set your min to 192MHz in order to really feel the differences. :)

So this morning I lowered my hispeed_freq back to the default 729 so I could really get a better feel for the differences myself, and honestly everything feels a little jittery at 192MHz, and things do seem okay at 6/7/5/3 and 6/7/6/3, but I still noticed some definite improvement with both 6/7/5/2, and 6/6/5/2. Bumping the timer_rate up to 30k to 6/6/5/3 actually might help avoid just a little bit of jitter, but I definitely like go_hispeed_load at 60%, and min_sample_time at 50000.
[Samsung Galaxy Nexus] bradm23:
Wow, can't wait for the next nightly! All this researching and testing has really intrigued me.
[Samsung Galaxy Nexus] 15israellai:
Those pages were a tl;dr for me, so I really thank yellowdie for explaining everything. Especially to a non-geek like me :P

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] franciscofranco:
The last 5-10 pages have been a total blast. I agree with joaquinf, this is what a development thread should look like! I told it last night to minooch when we were talking on gtalk and I say it again: theres no device like a Nexus to work on thats why I'm gonna stay ONLY on the Nexus line from now on. Thanks guys.

Like I said before its not a rule to have everything a multiple of CPU frequency transition latency value (in this case 30ms), but it makes sense to me that it works like that. Yes I think I prefer 6/7/6/3, lowering min_sampling_timer will just make the device jump frequencies even more because it won't stay at higher frequencies so often.

I have no idea. GPU drivers come from Imagination. This is a 2 year old GPU so I wouldn't be surprised if they stopped developing better drivers and focus on the newer 543 and 544.
[Samsung Galaxy Nexus] Dragooon123:
My speaker volume level suddenly went down with r292 from r290
[Samsung Galaxy Nexus] boki2911:
go to r295......
[Samsung Galaxy Nexus] yellowdie:
The logic behind bumping up to 9 is good for performance, but it means you'll spend longer at higher freqs. That could have a toll on battery in the long run. Although we're talking milliseconds, in the whole battery cycle, it adds up to mins and hours or extra power used. BUT, you may be right about giving it longer to finish tasks. That's basically the "race to idle" debate about setting the screen off max to 3xx or 7xx-- higher means your phone finishes it's task faster and goes into deep sleep sooner. So it could be the same principle here. If the min_sample_time is 9 vs 5 vs 3, we're giving the phone more time at higher freqs to get things done, then it can ramp down when it's not being used. Interesting stuff here.

Definitely agree that people need to be using the r294 test to be trying this stuff out properly. You can find it here.

So you still feel that 5/2 is faster. But I think Franco and creeve (the post a quoted here) may be right about keeping the multipliers lined up. It makes sense about the wasted time (5 and 3 are basically the same when there's a 30ms cycle time). I think I'm leaning towards 6/7/6/3 as well. But Franco, what are your thoughts on creeve's min_sample_time of 9?

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

haha. We're trying, we're trying! :D But trust us, it'll be GOOD!

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

Poor GS3 people... :( lol. Now I feel bad for them. :p
[Samsung Galaxy Nexus] pkgnex:
So you still feel that 5/2 is faster. But I think Franco and creeve (the post a quoted here) may be right about keeping the multipliers lined up. It makes sense about the wasted time (5 and 3 are basically the same when there's a 30ms cycle time). I think I'm leaning towards 6/7/6/3 as well. But Franco, what are your thoughts on creeve's min_sample_time of 9?

Personally, I could buy min_sample_time of "9" being workable. I think the consensus is that "3", or at least being less than two multipliers of the timer rate, is not ideal.

BTW... which of these parameters does Jellybean's "Project Butter" manipulate, if any... or is that only now happening with the Dyninteractive governor in Franco's kernel? I've been confused about this for a while now and don't recall seeing a definitive answer...

Thanks everyone for the great contributions today!
[Samsung Galaxy Nexus] yellowdie:
Project Butter (as far as I'm aware) sets those values as defaults (10/5/6/2). I don't know if it changes them actively. And Dyninteractive basically takes some of these factors into consideration and edits them as it goes. I'm sure Franco could tell you exactly which ones it changes. But I'm not sure what he's gonna in Dyninteractive in the next release. We'll see. :)
[Samsung Galaxy Nexus] :
What is the 6/5/9/3

I use franco kernel with stock values. But i would like to try your custom settings.....

Thanks.

Update: looked back a few pages found my answers.
[Samsung Galaxy Nexus] sunra0815:
Sorry for pushing my request :o

But especially the Nav-Buttons could response a bit better.

I´ve found this thread:

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

... and it would be great to have an option to improve the sensitivity on the GNexus too.

Regarding to the governour tweaks I´ve found a good thread:

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

Maybe usefull for the F.A.Q. section in the op?
[Samsung Galaxy Nexus] franciscofranco:
r295 is up.

Touch sensitivity is fine in the GN and thats for a different touch panel than the GN.
[Samsung Galaxy Nexus] yellowdie:
AUTFLASH ISN'T FAST ENOUGH!!!!!!!!!!!!!!!!

Thanks, Boss Man! Clearing my settings and flashing now.

Edit: Nice changelog. :)

Edit 2: Did you warn Minooch that his server was gonna break? ;)
[Samsung Galaxy Nexus] bradm23:
Is min gov suppose to be 192 by default? I remember talk that the newest tweaks are suppose to be used with 192
[Samsung Galaxy Nexus] franciscofranco:
No one said that. We were using 192 as min because its slower and it was easier to spot for real world changes in the settings.
[Samsung Galaxy Nexus] yellowdie:
Franco, wasn't r294 384 only? So we should be using r295 with 384 to truly test the differences, right? Those who want to use 512 can use it later, but should test with 384 first.

Dude, Franco, you just hit 17,000 Thanks. lol. Insane! :D
[Samsung Galaxy Nexus] Flav106:
Hello Franco,

Any news about getting usb audio working with Audio DAC ?
[Samsung Galaxy Nexus] pkgnex:
Not to beat a dead horse here, but I recall that "Project Butter" dynamically altered some of these parameters based on user inputs (scrolling, pressing, cpu load, etc.). Back in the pre-dyninteractive (~r230) days, I could even SEE IT in Franco's app - both with his kernal and imoseyon's. The values would look as the defaults you described initially, but if you swiped the screen or opened a high-load app and quickly returned, they would change - of course I can't remember what to (doh!). It was like being in the current "device monitor" tab with real-time refreshing of values, but in the governor settings.

Somewhere along the line, either from Franco's App updates or kernal governer re-writes, I was no longer able to see this in the governor control settings - at least not with Franco's kernel. I haven't been on IMO's kernal for months, but now I'm tempted to flash it and see if I can replicate this... unless someone can confirm or deny what I experienced was "real."

Anyone?
[Samsung Galaxy Nexus] tibere86:
r295 is surprisingly responsive running a min of 192. I have always used 384 with past nightlies as 230 resulted in sluggish behavior. Another great nightly Franco.
[Samsung Galaxy Nexus] grey.ghost:
Runs pretty sluggish to me. I'm on 512 though, will try 384 for comparison.
[Samsung Galaxy Nexus] yellowdie:
I'm not sure exactly. I think Franco took all that and made it separate in DynInteractive and then made the normal Interactive that we can manually set.

Same here. I never went below 384 until I started testing this setup a few days ago. But I think I may work well. :)
[Samsung Galaxy Nexus] BigBake88:
That's because it is injected with Franco black magic...
[Samsung Galaxy Nexus] jcmm11:
It's not the cpu sample rate that's preset to 30000. It's the transition latency. And I'm fairly sure that that number represents the max latency, but that depending on how big a change is involved latency may be lower.

What this number represents is how long it takes the cpu to change from one frequency to another.

As far as the other numbers go I've been running at 70% for hispeed load for a long time now, after having played with other values (both higher and lower).

I'm currently experimenting with having all the other time values set to 22500.

Spent quite a bit of time reading, mostly pure Linux, docs on the settings (mostly from on-demand, since interactive isn't in the regular Linux kernel yet) and I've decided to see what these will do.

At the moment I have 2 hours screen time with 36% battery usage, and so far no microlag at all. Need more time using different apps though.

(I'm still on r292 at the moment. I'll switch to 295 after I drain the battery a bit more just to see what happens)
[Samsung Galaxy Nexus] BigBake88:
Is the name of the game to test the Franco settings he shipped with 295?
[Samsung Galaxy Nexus] The Gingerbread Man:
So here's an interesting question which I'm not sure of the answer, so these new awesome gov control settings are configured to work best with 1.2ghz max CPU speed, so if someone were to use a lower max CPU speed say 1.0ghz for instance would it be good idea to divide the current values by say 1/6 (to represent 200mhz drop or 1/6 of max speed) and then lower the values of the

Highspeed-freq and input-boost to 729?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Interesting, I never thought of doing non-even numbers. Hmm.

Yep! :D

No, you can leave the 6/7/6/3 values the same. I was actually running 192-729 the whole time and it was surprisingly FAST!!! Now I've increased my max to 1036. Franco has the input_boost_freq at 1036 and the hispeed_freq at 729. But because I'm running 1036 as the max, I'm going to probably set both of those to 729 (after doing the initial testing). :)
[Samsung Galaxy Nexus] EliasKir:
This. I'll go a step further and suggest an option for automatically applying a lower frequency and lazier governor mode when battery is low. I know this is a longshot but i think it would be a nice upgrade.

If a custom rom gives an option for auto brightness reduction and data/gps/bluetooth off when the battery goes beyond this threshold it would complete a more "green" profile instead of a constant chase of power and speed.
[Samsung Galaxy Nexus] jcmm11:
I came up with that from reading an example in the Linux docs for on-demand. It wasn't a recommended value but since it was an example I figured I may as well try it. It's 3/4 of the transitional delay. I had been ruining with higher values (close to Franco's current values) but decided to try all low values for the moment. My thinking goes that the 70% will keep things from ramping up too fast. Once it gets to that level it will stay there as long as the cpu is being utilized, so you'll still be fine on the race to idle. It will ramp down faster though due to smaller values.

I'm going to load 295 as soon as I finish writing this. Still have to decide on frequency values. At the moment I'm running 384 to 1305, screen off max at 729, input boost 1228, hispeed 1036 but I'm thinking about dropping those down. We'll see.

---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
[Samsung Galaxy Nexus] nuwan32:
Wow didn't even realize 295 was out... Is there any difference between 295 and 294?
[Samsung Galaxy Nexus] yellowdie:
:) Thanks for the input, keep it comin'. I'm actually running 192-1036, and I think for underclocking that low, it will be best to put the input_boost_freq and the hispeed_freq at 729. Still playin' with some stuff there. :)

OOOOHHHHH YEEEEAAAAAHHHHHH!!!!!!!!!!!!!!

:):D:laugh::good:
[Samsung Galaxy Nexus] sruel3216:
i have used a mixture of governor settings with 292 and 295. Honestly these last two kernels have given me great battery life an amazing performance. hasnt really mattered what i ran.

last night i ran:

max1420

min729

interactive

4/6/3/2

hi_speed 1228

input_boost 1228

right now i am running this with just as good results:

max1420

min729

interactive

6/6/9/3

hi_speed 1228

input_boost 1228
[Samsung Galaxy Nexus] Emama:
If I am not messing the settings,

should I flash 295 or just m6?

ps. I just want a better battery life for my aokp b5
[Samsung Galaxy Nexus] yellowdie:
Are you one of the people that started running 729 as your min because I was pushing it for the last weeks? Humor me. Try dropping it to 192 for a bit. I know, it's blasphemy coming from me. But with these latest tweaks, I'm very impressed with how the bottom speeds have handled. That's been the big thing that we've been testing in all this: how to make it snappy but keep the freqs low. :) It's impressive, I have to say.

---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------

r295! :D
[Samsung Galaxy Nexus] sruel3216:
my values were similar to yours. i usually use 4/5/3/2. after im done testing 6/6/9/3 i think il try 2/7/3/3. i like the race to idle idea. i always seem to have zero lag that way

---------- Post added at 01:39 PM ---------- Previous post was at 01:34 PM ----------

haha no i was using 700 as i min before franco started using 729. i use it for a couple reasons. 1) cpuspy always has the majority of my time at 729 whenever i use a lower value (384 usually). 2) i have never had one sod on my phone at 729. my phone seems to like sods at lower values even though i done even use SR. i just keep the stock values franco sets.

however, i may try 192 since everyone is doing it :cool:
[Samsung Galaxy Nexus] fleischbanane:
295 blows my mind. It's unbelievable fast and rocking stable.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
Cool. Yeah, 192 is the popular thing to do. :p (Just because we're testing it right now). And 192 is specifically controlled by SR now (230 wasn't in the past). So I would try leaving SR enabled and see if you get SODs with this new setup. :) Even if you go back to 729 in the end, that testing will be good to know.
[Samsung Galaxy Nexus] L-ViZ:
hey guys, got a little question.

always have been using ondemand oc'd@1,4ghz. now i tested the normal settings interactive 1,2ghz and it feels faster. under same circumstances the browser felt more response and faster even 200mhz less. anyone got an explanation for that?
[Samsung Galaxy Nexus] yellowdie:
Gotcha!! It was all joke! We haven't actually changed anything in r295!! HAHA. It's actually just the Stock kernel!

I'm totally joking. It's fast, isn't it?!?! :D

btw, half of my office is gone for the day and it's really slow at work for me right now. lol. Don't know if you guys could tell or not! ;) haha

YEP! We sure do! It's right here. :D Enjoy!
[Samsung Galaxy Nexus] The Gingerbread Man:
You can create profiles in an app called set cpu for doing exactly that, if you search hard enough theres a free version for xda users around here somewhere

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] JBNex:
What do the numbers like 2/4/6/5, etc. Mean?
[Samsung Galaxy Nexus] The Gingerbread Man:
This should keep you busy thanks to yellowdie

Sent from my Galaxy Nexus

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Wynnded:
Shorthand. About half way down you can see how it came to be. http://xdaforums.com/showpost.php?p=33161912&postcount=30454

Ninja'd by GB! lol
[Samsung Galaxy Nexus] dracon6ai:
On r295 does SR work for the 192 MHz ? I see it set to 1000mV and it runs at 1000mV while the 384 MHz slot is set to 1025mV but runs at 840mV. I know I can manual bring it down, but was just wondering if it's working as designed stock.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] pkgnex:
I just auto-flashed 295 and my phone was acting weird (laggy / jittery). Then it got so hot I considered trying to fry an egg on the screen to see if it is non-stick as well as scratch resistant;) I turned the screen off and plugged in a charger and it wouldn't charge, either. Rebooted, and problem solved (and running very well, now).

I think it may have been because I have my CPU settings set to be saved on boot in Franco's app, and it was looking for a 230 slot when one no longer existed... and even after manually re-setting the min freq. to 192 it needed a reboot to totally reset itself. I'll be unchecking the "save on boot" boxes in the app prior to auto-flashing new nightlies from now on, and I'll re-post if this ever happens again.

BTW... thanks, Franco, for all your hard work on both the app and kernels lately. HUGE improvement over stock!
[Samsung Galaxy Nexus] joaquinf:
That free version is very outdated he will probably run into weird behaviour. Best thing to do is to support the dev and purchase the app in the play store :highfive:
[Samsung Galaxy Nexus] osm0sis:
Both 192MHz and 384MHz run at 830mV when SR calibrated. So technically there is no point in running 192MHz unless you plan to selectively UV it. We've been running it at around 725mV and it's very stable. 230MHz was hardcode undervolted to 820mV in the more recent builds, so I'm hoping Franco will reconsider hardcoding 192MHz with the same in mind, since people will be running it thinking they're saving power, with no gain whatsoever in reality.

Good news is that in the meantime selectively undervolting it to where it needs to be is easy since all you have to do is put it below the SR calibrated voltage to have it circumvent SR, and you can leave SR enabled to handle the rest of the frequencies.
[Samsung Galaxy Nexus] nuwan32:
It's not the setting on boot, it's normal first boot after a flash it usually gets hot and runs for a while even while sleep so it gets hot. Just don't be scared :p