Related
which of the recent governors gives best performance?
lazy, interactive, smartassv2?
Thanks guys
I just use Ondemand. I've tried others but I always end going back to it.
I've heard interactive is good for performance. I was under the impression that lazy and smartass were more geared towards battery saving.
Sent from my Nexus S using xda premium
I use lazy or ondemand typically.
Follow the leader @corythug
for performance, ondemand with a sampling rate of 15000 and up threshold of 98.
simms22 said:
for performance, ondemand with a sampling rate of 15000 and up threshold of 98.
Click to expand...
Click to collapse
simms, I am assuming this will drain battery faster as the default sampling rate is 40000. Am I correct?
Sampling Rate – An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
i like smartassV2 1200 / 100
Naa Laa said:
simms, I am assuming this will drain battery faster as the default sampling rate is 40000. Am I correct?
Sampling Rate – An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
Click to expand...
Click to collapse
no. itll actually be a little better on battery, a little more efficient than the default. and itll give the ui a little speed boost.
Isn't interactive supposed to be a 'better OnDemand'
I'm thinking it's the opposite, that on demand was an improved interactive, but I could be wrong. I really don't notice much difference between any of them. On lazy and smartassv2 I seem to get more random problems. Really though, what's best questions are left for you to explore and find out. Some people on these threads use their phone for most their computing needs and some barely even use their phone.
Sent from my Nexus S 4G
i use smartass 1200/200 on matrix 10.0 kernal n havent had any issues..i get awesome battery life 18+ hours with light to moderate use
Sent from my Nexus S 4G using XDA Premium App
I'm voting for interactive, I've had great battery life and performance from it fwiw
Sent from my Nexus S 4G using Tapatalk
What's actually the difference? Is there any guide to read?
gellow said:
What's actually the difference? Is there any guide to read?
Click to expand...
Click to collapse
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
SOURCE: http://setcpu.com/#7
I've tried different configurations but always end up going for ondemand.
There is no "best governor", just like there's no best brand of beer. My favorite, however, is smartassv2. Great performance and battery life - probably one of the better compromises.
But I don't drink beer!
Sent from my Nexus S using XDA App
Well I am sticking to one Rom and that's Crisekelo's like in my good 'n old sgs froyo times, but I like to test various kernels, when I have time...
Anyway I never saw a Mod Kernel with so many governors as the AbyssNote kernel, which I am testing right now..
Since there are many users out there that unlike me, already own the GNote for a long time and are way more experienced than me with this particular Kernel, I decided to start this Poll-thread so users can vote on their favorite governor and prehaps elaborate a little about it..
Thanks in advance..
Since Abyss Kernel is not working for my Note (overheat), I' at FM kernel with SavagedZen governor and vr I/0 Scheduler, butter smooth and stable, goes to deep sleep as it supposed to, sharp performance and moderate battery life. I know you prefer Abyss but just wanna let you know how the other kernel is working.
When I was on Abyss I was using abyssplug governor with and without undervolting. Hope you can get Abyss work for you, if you manage to do it without overheat I would appreciate any info.
have fun!
Oops ... you reacted fast ! The poll was not even ready
At the moment I don't prefer any kernel ( Only the rom) and on a device such as the GNote, I have a hunch that we dont need a super-optimized kernel with tons of iterations and that's why I always keep CF-Root and Speedmod handy, but I like the dedication and availability of AbyssNote developer, so I am giving it another try...
Since I have not enough time to play with the GNote as I did with the sgs, I am hoping that the AbyssNote users will give this specific input ....
iceangel1980 said:
"... Abyss Kernel is not working for my Note (overheat), I' at FM kernel with SavagedZen governor and vr I/0 Scheduler, butter smooth and stable, goes ..."
Click to expand...
Click to collapse
Hi betoNL,
just give the Abyss Kernel v3.7 another try. I am really satisfied with ABYSSPLUG governor and the SIO scheduler - great balance between performance and battery life. And it is also butter smooth and stable without any overclocking indeed ;-)
To be honest: I can't understand your problem with overheating. It could have its seeds in an app with unnormal behaviour or a constant hang-up in the background. Maybe you will execute this little turnaround at the next opportunity:
1. Charge your battery to 100%
2. Use a Taskkiller and kill every open task
3. Reboot in Recovery Mode and wipe voltage & battery stats (DON'T WIPE ANYTHING ELSE, PLEASE!)
4. Reboot yours system...
Best regards
[bs]
---------- Post added at 05:53 PM ---------- Previous post was at 05:50 PM ----------
Hi,
great poll... my vote goes to the abyssplug ;-)
Would be interesting to add users choice of the I/O scheduler.
What do you think about that little improvement?
Best regards
[bs]
As I said, I recommend AbyssPlug
I don't understand how abyssplug works. So I don't use it.
I do use lulzactive because it uses mostly my lowest frequency which drains battery the least when not stressed and highest frequency when stressed and basically ignores everything in between. It's been great.
can someone explain how abyssplug works? I've been searching, it only says modified hotplug. That doesn't tell me much.
Originally Posted by mancman
here the exact explanation on RootzWiki:
Wheatley governor
in short words this govenor is build on "ondemand" but increases the C4 state time of the CPU and doing so trying to save juice....
The known ones are really good described here one the setcpu page:
the rest is nice described here:the rest is nice described here:
lazy (http://forum.xda-developers.com/show....php?t=1276092) - is ondemand but with an added option to stay longer on a certain frequency. This is due to the fact that some CPU's dont like too quick freq changes when sampling rate for decision making is set too low. See link for more.
lulzactive (http://tegrak2x.blogspot.com/2011/11...vernor-v2.html) - is basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads. Has, like smartass, a sleep profile built-in. See link for details on exact scaling.
lagfree (http://forum.xda-developers.com/show....php?t=1272933) - seems to be ondemand but with a lessend tendency to ramp up to 100% but rather also use steps available in between 0-100%.
intellidemand (freely translated from http://www.android-hilfe.de/root-hac...-governor.html) - behaves like ondemand when the system is under heavy use, it behaves differently when the system is mostly ideling. That mode is colled "browsing mode" or "browser mode" or whatever. It seems to be some sort of "intelligent" demand sensing/analysing ondemand governor.
smartassV2 - this one should be known. It's the same as smartass(V1) but tweaked. Same code author. I heard one should use smartassV2 instead of smartass when available.
ondemandx - is ondemand with an added sleep profile built-in. I believe all ...X kernels are the default kernels but with an added sleep profile.
AbyssPlug Governor:
Abyssplug governor is a modified hotplug governor
>>Hotplug Governor:
The "hotplug" governor scales CPU frequency based on load, similar to
"ondemand". It scales up to the highest frequency when "up_threshold"
is crossed and scales down one frequency at a time when "down_threshold"
is crossed. Unlike those governors, target frequencies are determined
by directly accessing the CPUfreq frequency table, instead of taking
some percentage of maximum available frequency.
The key difference in the "hotplug" governor is that it will disable
auxillary CPUs when the system is very idle, and enable them again once
the system becomes busy. This is achieved by averaging load over
multiple sampling periods; if CPUs were online or offlined based on a
single sampling period then thrashing will occur.
Sysfs entries exist for "hotplug_in_sampling_periods" and for
"hotplug_out_sampling_periods" which determine how many consecutive
periods get averaged to determine if auxillery CPUs should be onlined or
offlined. Defaults are 5 periods and 20 periods respectively.
Otherwise the standard sysfs entries you might find for "ondemand" and
"conservative" governors are there.
__________________
After goin thru this thread I tried the AbyssPlug governor.
And indeed its good so far.
Me likes!!!!!!!!!
Sent from my GT-N7000 using xda premium
My choice is lulzactive.
Most important things for me are smoothness, fast wake&unlock and gaming performance. I don't care about the battery life that much so it seems a perfect choice for me.
pjm77 said:
My choice is lulzactive.
Most important things for me are smoothness, fast wake&unlock and gaming performance. I don't care about the battery life that much so it seems a perfect choice for me.
Click to expand...
Click to collapse
I like lulzactive, too!
What, no smartassv2 love here ? I found it at least as good as lulzactive for my usage.
My priorities - Fast response after sleep, smoothness, battery.
My governor choices on top were : SmartAssV2 (Currently using), AbyssPlus (Used it, liked it, later will compare to SmartAssV2) and Lulzactive (which is pretty good as well).
betoNL said:
Originally Posted by mancman
here the exact explanation on RootzWiki:
Wheatley governor
in short words this govenor is build on "ondemand" but increases the C4 state time of the CPU and doing so trying to save juice....
The known ones are really good described here one the setcpu page:
the rest is nice described here:the rest is nice described here:
lazy (http://forum.xda-developers.com/show....php?t=1276092) - is ondemand but with an added option to stay longer on a certain frequency. This is due to the fact that some CPU's dont like too quick freq changes when sampling rate for decision making is set too low. See link for more.
lulzactive (http://tegrak2x.blogspot.com/2011/11...vernor-v2.html) - is basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads. Has, like smartass, a sleep profile built-in. See link for details on exact scaling.
lagfree (http://forum.xda-developers.com/show....php?t=1272933) - seems to be ondemand but with a lessend tendency to ramp up to 100% but rather also use steps available in between 0-100%.
intellidemand (freely translated from http://www.android-hilfe.de/root-hac...-governor.html) - behaves like ondemand when the system is under heavy use, it behaves differently when the system is mostly ideling. That mode is colled "browsing mode" or "browser mode" or whatever. It seems to be some sort of "intelligent" demand sensing/analysing ondemand governor.
smartassV2 - this one should be known. It's the same as smartass(V1) but tweaked. Same code author. I heard one should use smartassV2 instead of smartass when available.
ondemandx - is ondemand with an added sleep profile built-in. I believe all ...X kernels are the default kernels but with an added sleep profile.
AbyssPlug Governor:
Abyssplug governor is a modified hotplug governor
>>Hotplug Governor:
The "hotplug" governor scales CPU frequency based on load, similar to
"ondemand". It scales up to the highest frequency when "up_threshold"
is crossed and scales down one frequency at a time when "down_threshold"
is crossed. Unlike those governors, target frequencies are determined
by directly accessing the CPUfreq frequency table, instead of taking
some percentage of maximum available frequency.
The key difference in the "hotplug" governor is that it will disable
auxillary CPUs when the system is very idle, and enable them again once
the system becomes busy. This is achieved by averaging load over
multiple sampling periods; if CPUs were online or offlined based on a
single sampling period then thrashing will occur.
Sysfs entries exist for "hotplug_in_sampling_periods" and for
"hotplug_out_sampling_periods" which determine how many consecutive
periods get averaged to determine if auxillery CPUs should be onlined or
offlined. Defaults are 5 periods and 20 periods respectively.
Otherwise the standard sysfs entries you might find for "ondemand" and
"conservative" governors are there.
__________________
Click to expand...
Click to collapse
Again, it's just a modified hotplug. What's modified about it?
betoNL said:
Oops ... you reacted fast ! The poll was not even ready
Click to expand...
Click to collapse
guess I was in chatty mood
BrainSex said:
\
To be honest: I can't understand your problem with overheating. It could have its seeds in an app with unnormal behaviour or a constant hang-up in the background. Maybe you will execute this little turnaround at the next opportunity:
1. Charge your battery to 100%
2. Use a Taskkiller and kill every open task
3. Reboot in Recovery Mode and wipe voltage & battery stats (DON'T WIPE ANYTHING ELSE, PLEASE!)
4. Reboot yours system...
Click to expand...
Click to collapse
Believe me I don't get it either and I'm pretty upset I can't use that kernel which is so valued by other android users. I was trying your advice and any other I could find in Abyss Kernel thread, nothing works for me. What is really funny I don't have any problems on other kernels. Well maybe I'm just unlucky this way. I'm thinking about getting my Note to Samsung for screen display exchange, so maybe they can do something about overheating too, maybe it's hardware related.
Thank you for your interest and advice
anyone using the app 2nd core and turning on dynamic hotplug?
It rly helps the battery
Might be useless to use along side abyssplug tho since it does the same thing
I use lulzactive, don't care about a little more battery drain
I use too 500mhz minimum speed @ 800mv, with it is pretty strange because 100 and 200 are not stable at that voltage and need 825, so having more speed I use less battery.
You don't use less battery because it's not only determined by voltage. Frequency us also a factor in power consumption, so 100MHz at 825 uses less battery for sure.
Sent from my superior GT-N7000 using Tapatalk
Zamboney said:
You don't use less battery because it's not only determined by voltage. Frequency us also a factor in power consumption, so 100MHz at 825 uses less battery for sure.
Sent from my superior GT-N7000 using Tapatalk
Click to expand...
Click to collapse
There's a post here somewhere here in the gnote forum that shows a study where they explain how 50 and 100MHz do consume more battery cause the CPU gets more stressed and takes longer to perform the task that would take less time and effort to accomplish at a higher frequency (or something like that)
Actually a higher frequency @ same voltage as a lower frequency would consume LESS battery because it will complete the task faster.
Sent from my GT-N7000 using Tapatalk
With my setup only ondemand really worked well, my second core scaling is always set to 2 cores enabled and I have a landscape setting for ADWex and any other governor will give me like 10-15fps when opening the app drawer.
Abyssplug fits my needs: I don't need so much power (no playstation-like games) but I use phone h24, from music to calls, from surfing to calendar/alarm...quite all stuff by BT headset and voice command. Battery drains slower than expected, my Note stays alive 'till night
I have been experimenting with some various governors and have found that interactive and ondemand work best on the nexus 7. My question is which one will have better battery life on the nexus 7? Which one will have the least stuttering? Just curious. Everyone seems to state that interactive will be the better governor, but I tend to notice interactive heats up more in chrome. Anyone else notice this?
Any helps would be appreciated
-Fishwithadeagle
When running low on battery I found conservative with runnable works the best for me. Undervolting by 50-100mV and running custom kernel plus ROM can also contribute. I always turn my WiFi and GPS off when not being used. I would not know of such imperceivable details between Interactive and Ondemand as battery, stutter or heat. Mine reaches 70 degress celsius under overclocked heavy benchmarking load.
For battery life, stick with interactive or conservative.
For less lag and stuttering, use ondemand or performance.
Sent from my Nexus 4 using Tapatalk 2
Wow, you couldn't be more wrong. You have it completely opposite. For better battery life, and not to have your frequency set to the highest value, almost at all times, go with ondemand. If you want less lag, and stuttering, but worse battery life, interactive.
Test it yourself with setcpu, and CPU spy, and you'll see exactly what I'm talking about.
Rootzwiki FAQ: CPU Governors
I remember when Smartass came out a bunch of developers at the Droid X forums where recommending that for better performance than Conservative with roughly equal battery life, so my last governor on MIUI was the updated version of that: SmartassV2.
Now I've flashed Pooka's CM4DX build, and there are three governors included by default:
Ondemand (default)
Userspace
[*]Performance
I installed the last version of Jakesbitesmods for the Droid X found in post #1052 of the official Rootzwiki thread, v19f, and it adds these governors:
InteractiveX (default, recommended by Jake)
Conservative
Finally, from a flashable standalone zip, I added my last preferred governor from MIUI:
SmartassV2
So I have a lot of options. Now, as the Rootzwiki FAQ on governors I linked at the top says:
Rootzwiki said:
Smartass
Theoretically a merge of the best properties of Interactive and OnDemand; automatically reduces the maximum CPU frequency when phone is idle or asleep, and attempts to balance performance with efficiency by focusing on an "ideal" frequency.
Pro: Usually yields higher performance than OnDemand and theoretically has better battery life than Interactive or OnDemand.
Con: Same as Interactive, the CPU will slowly ramp down after it is no longer needed (compared to its ramping-up speed). Might also go too low when asleep (an issue with other governor when a Sleep profile is used in apps such as SetCPU), causing the device to malfunction. Most common example is the screen not powering on when the power button is pressed or the phone begins ringing. Might also effect apps running in the background while sleeping.
SmartassV2
A rewrite of Smartass that is easier for developers to program, and scales down quickly similar to Conservative. It has an "ideal" frequency which it will quickly ramp up to, then more slowly ramp up once past it, and vice-versa for down-ramping. A separate "ideal" frequency is used when the screen is off.
Pro: Same as Smartass, but theoretically better battery life and performance.
Con: Same as Smartass with the sleep state.
Click to expand...
Click to collapse
So, if the theory there holds true, then SmartassV2 should be generally superior to both InteractiveX and OnDemand. But on the last page of that Jakesbitesmod thread, in post #1063, there is a link with a flashable zip of BoostedassV2: yet a further modification of SmartassV2. I found the developer's thread for BoostedassV2, and in that thread, he says this about SmartassV2:
BMc08GT said:
This is based in part on the port done by First Encounter for the DX. I have discovered that it will also compile for the other DROID devices that were available at the time of the port. I went further to tweak the stock smartassv2, as I felt that it was to CPU needy, with the transisition ideal freq at 800MHz!! Not a very good frequency to be set for ideal, at resting awake state. I further dived into the code and changed majority of the other frequencies, and transistions-based on my conservative tweaks made from PowerBoost. I will have the comparison of smartassv2 vs boostedassv2 in the 2nd post.
Click to expand...
Click to collapse
Would this in theory be better for general performance in a Droid X that's overclocked/undervolted? I'm using JBM's preset 1.15GHz settings, so I'm way off that 800MHz optimization. I realize that there's a tension in governors between best battery life and best responsiveness, but I'm curious which of these governors would probably offer the best general combination of the two on an OC'd DX running CM7 like mine.
If yes, I'll go about installing it some other way. That zip for BoostedassV2 is problematic because it searches out and deletes the InteractiveX governor, and it wreaked havoc on some of the core JBM files, because I could not overclock in terminal using JBM. The reference files got deleted. I would considering using SetCPU, but for some reason, on this CM4DX ROM, SetCPU doesn't have the "Autodetect" tab, and I can't clock the max frequency above 1000MHz using that app. Also, it's my understanding that JBM is more battery-efficient since it changes the clock in the boot files, so it doesn't require a constant service to maintain its settings.
Generally, I'm just curious what setup you guys would suggest for OC/governor running Pooka's CM4DX. Thanks.
Hi
I have my G4 unlocked and rooted on 10C, and thought I would try some Kernel Setting experiments using Trickster.
Stock settings use Interactive.
So I tried Userspace but seems that Userspace sets the clock speed to full nearly 90% of the time for me.
So I decided to give Ondemand and read ahead 1024 CFQ a try.
Maybe a placebo? But watching the cpu clock speeds, it doesn't seem to hang up at 1248 like it does in Interactive and drops much quicker back to 384, but equally ramps up quicker too.
I seem to get less battery drain when browsing instead of Interactive 512 CFQ (Stock setting) after a few days testing.
I know very little about kernels on Android, but thought I would share my findings if anyone is interested.
damn i hope root will come fast, i need to have conservative govenor, as it the only one that plays ppsspp tekken well.
the major isue I see is the actual hotplug that keeps all cores always on.
That is pretty strange...LG's devs must be sleeping while our cores are not
Didn't find Conservative in the options. Only Interactive, Userspace, Ondemand, Powersave, & Performance.
Haven't tried Powersave yet though?
johnny8910 said:
Didn't find Conservative in the options. Only Interactive, Userspace, Ondemand, Powersave, & Performance.
Haven't tried Powersave yet though?
Click to expand...
Click to collapse
I wouldn't play with actual governors and let them at their default value until we have a custom kernel.
Thanks, but I am still finding Ondemand seems to give me less battery drain under use such as web browsing.