I want to know which one is better for an old phone like LGE510.
I'm using CM7.2 and different profiles in setCPU.
If no governor is better than each other can someone explain me the differences?
oliverm91 said:
I want to know which one is better for an old phone like LGE510.
I'm using CM7.2 and different profiles in setCPU.
If no governor is better than each other can someone explain me the differences?
Click to expand...
Click to collapse
SmartassV2:
Version 2 of the original smartass governor from
Erasmux. Another favorite for many a people.
The governor aim for an "ideal frequency", and
ramp up more aggressively towards this freq and
less aggressive after. It uses different ideal
frequencies for screen on and screen off, namely
awake_ideal_freq and sleep_ideal_freq. This
governor scales down CPU very fast (to hit
sleep_ideal_freq soon) while screen is off and
scales up rapidly to awake_ideal_freq (500 mhz
for GS2 by default) when screen is on. There's
no upper limit for frequency while screen is off
(unlike Smartass). So the entire frequency range
is available for the governor to use during
screen-on and screen-off state. The motto of this
governor is a balance between performance and
battery.
SavagedZen:
Another smartassV2 based governor. Achieves
good balance between performance & battery as
compared to brazilianwax.
its basically quite the same really, im using SmartAssV2 on my LGE510 currently and it does what it says.
Related
Well, a few friends of mine with Sensations asked me "What are all these SetCPU options for?" So, here's some explanations.
CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies.
Ondemand- 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- The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Conservative- 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- 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- Keeps 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- is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 192Mhz (or if your min frequency is higher than 192 - why?! - it will cap it to your min frequency). No need for sleep profiles any more!
CREDIT: http://setcpu.com/#7 & http://forum.xda-developers.com/showpost.php?p=9277771&postcount=2
NikolaiT said:
Well, a few friends of mine with Sensations asked me "What are all these SetCPU options for?" So, here's some explanations.
CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies.
Ondemand- 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- The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Conservative- 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- 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- Keeps 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- is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 192Mhz (or if your min frequency is higher than 192 - why?! - it will cap it to your min frequency). No need for sleep profiles any more!
CREDIT: http://setcpu.com/#7 & http://forum.xda-developers.com/showpost.php?p=9277771&postcount=2
Click to expand...
Click to collapse
The s
Sent from my HTC Glacier using XDA Premium App
So which one would you recommend?
thebigham said:
So which one would you recommend?
Click to expand...
Click to collapse
Smartass, its the best governor, but it hasn't been implemented in any Sensation kernels yet, hopefully Lee or maybe Mike1986 can implement it into their kernels in the future.
Interactive for a good balance of responsiveness and battery life.
Conservative if you're looking for better battery at the expense of responsiveness.
Sent from my HTC Sensation 4G using XDA App
what's different between these "lazy" "ondeman" "smartass" ...etc
i google it and find something , but looks like it is incomplete
...
could someone please explain what's different about them ?
thanks in advance
from www.setcpu.com/#7
CPU Scaling Governors-CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
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.
Click to expand...
Click to collapse
that's what i was saying incomplete...
no explaination of lazy and smartass V2?
qtwrk said:
that's what i was saying incomplete...
no explaination of lazy and smartass V2?
Click to expand...
Click to collapse
because they were just developed. you can find out all about lazy in the nexus s development forums here on xda, since it was developed here on xda for the nexus s(thanks to ezekeel) http://forum.xda-developers.com/showthread.php?t=1276092&highlight=lazy+governor
i'll let you search for smartassV2 on your own
Which one is better??
lazy or ondemand??
al_madd said:
Which one is better??
lazy or ondemand??
Click to expand...
Click to collapse
Lazy is newer and meant to be an "improved" ondemand. Comes down to personal preference really.
063_XOBX said:
Lazy is newer and meant to be an "improved" ondemand. Comes down to personal preference really.
Click to expand...
Click to collapse
I read again lazy thread from ezekeel..He made correction over calculation comparing governor comsumptiom power..
mathkid recomended ondemand on his kernel
morfic tweak conservative governor on his kernel
fransico recomended lazy or smartassv2
iceandfire recomended lazy
there is too many debate on this...wondering if lazy governor really works???
al_madd said:
I read again lazy thread from ezekeel..He made correction over calculation comparing governor comsumptiom power..
mathkid recomended ondemand on his kernel
morfic tweak conservative governor on his kernel
fransico recomended lazy or smartassv2
iceandfire recomended lazy
there is too many debate on this...wondering if lazy governor really works???
Click to expand...
Click to collapse
ondemand or lazy. ondemand has a little more of a kick while lazy is a little better on battery.
simms22 said:
because they were just developed. you can find out all about lazy in the nexus s development forums here on xda, since it was developed here on xda for the nexus s(thanks to ezekeel) http://forum.xda-developers.com/showthread.php?t=1276092&highlight=lazy+governor
i'll let you search for smartassV2 on your own
Click to expand...
Click to collapse
thanks man , this is what i found
SmartassV2 (informal description and comparison with the first smartass)
SmartassV2 is a governor (controls the frequency of the CPU at each give moment) which like the first smartass is generally based on the implementation of interactive with some major changes and the addition of a built in sleep profile (behaves a bit differently when screen is off vs. on).
The smartassV2 improves the very naive scheme which the first smartass had: The first smartass (with the values I set for the hero), would cap the max frequency at 352Mhz for sleep and when screen is on, would do the opposite and keep the frequency at 518Mhz or above. For sleep this was very effective but a bit crude and unclean, and there could be some cases where you would need processing power even when screen is off (something is updating and music is playing and etc.). For screen on, smartass1 was too quick to jump to the max available frequency and again would never go below the 518Mhz, so in a nutshell its was using "too high" frequencies.
SmartassV2, introduce (internally) an "ideal" frequency which is the frequency we are "aiming" for, in some sense. The way I see it is that the "ideal" frequency is a hint to the governor what is a good balance between performance and battery life. Now when screen is on, I set (on the hero) the ideal frequency to 518Mhz which will ensure nice responsiveness but limit unnecessary use of higher frequencies when they are not needed. When screen is off, I set the ideal frequency to 352Mhz (0 will disable the screen state tracking all together). From my testing this will "convince" the governor to spend most of the its time during sleep at the lowest available frequencies. Note, that both during sleep and when awake the entire frequency range (as defined by the "user" - i.e. selected with SetCPU) is used by smartassV2. For example, when the CPU is loaded heavily, the highest available frequency will be used regardless if screen is on or off.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=730471, posted by erasmux
Although I can't really tell a difference in real life, I benchmark lower on lazy vs. ondemand.
It probably has something to do with a forced time within each state for the lazy, which prevents it from switching frequencies too many times.
question... I see all the govener setting in ns tools, setcpu, ect.... just wondering something.... What setting is.used in factory otu roms? lets say a.unrooted nexus s, what is.it natively set at? 100/1000 ? and ondamand? or is.it 1000/1000?
Sent from my Nexus S 4G using XDA App
100/1000 ondemand is the default.... but I always change it to 200/1000 smartassv2 it works best for my phone
Sent from my Nexus S 4G using xda premium
I usually use "ondemand", it seems to work best. Once I decided to try "powersave" and my phone slowed down to a crawl, pretty much unusable. I don't know what that was about, but I definitely don't recommend it...
Jabaculemos said:
I usually use "ondemand", it seems to work best. Once I decided to try "powersave" and my phone slowed down to a crawl, pretty much unusable. I don't know what that was about, but I definitely don't recommend it...
Click to expand...
Click to collapse
Powersave limits the cpu to the absolute lowest frequency at all times. It is not usable for normal operations, except for Setcpu screen-off profiles.
Performance governor is the opposite ; it keeps the cpu running at max frequency (1ghz with stock kernel) and is useful only for speed benchmarks.
The other linux kernel governors are described in detail in numerous threads... All you have to do is search "kernel governor ".
My personal choice is smartassv2 since it's responsive, efficient with battery consumption, and features a screen-off sleep profile.
Ezekeel recommended me lazy with proof screenshots
Governors control how the CPU frequency adjusts. They work like this:
Ondemand: Starts at a low frequency and when there is any CPU activity it uses max frequency. It goes back to low over time.
Conservative: Like ondemand, but instead of using max frequency on CPU activity it uses the next step. It's less responsive than ondemand since it goes like: "100% CPU > Higher Freq. > 100% CPU > Higher Freq..." instead of "100% CPU > Max Freq."
Lazy: Like ondemand but there is a small delay between frequency changes. I use this one.
Performance: Max frequency all time.
Powersave: Min frequency all time.
Interactive: This is a bit complex, actually it's sampling the CPU usage and trying to predict what will come up (I think).
Smartass: It's like interactive, but rewritten. It should give better results.
Default is ondemand 100/1000 and it works pretty good.
Hope I helped.
How do you underclock the htc inspire and what should i set the min and max CPU to I want to my my battery life on my phone a little bit better
What rom do you have?
Ice cold sandwich 4.1.1
Sent from my HTC Desire HD using xda premium
For IceCold you want to go to system settings>rom control>performance. From here you can set min and Max CPU and governor. Under clock would mean that you have to Max CPU set to something less than it would be normally, So set Max CPU something below 1075.
Personally I would set Max to 1075 min to 230 or 122 and then test out a few different governors. Start with ondemand, then ondemandX and then smartassV2 and see how your battery does on each of those as each governor has different properties.
If you meant undervolt instead of underclock, then it gets a bit trickier.
Sent from my HTC Inspire 4G using xda premium
nine zero one said:
For IceCold you want to go to system settings>rom control>performance. From here you can set min and Max CPU and governor. Under clock would mean that you have to Max CPU set to something less than it would be normally, So set Max CPU something below 1075.
Personally I would set Max to 1075 min to 230 or 122 and then test out a few different governors. Start with ondemand, then ondemandX and then smartassV2 and see how your battery does on each of those as each governor has different properties.
If you meant undervolt instead of underclock, then it gets a bit trickier.
Sent from my HTC Inspire 4G using xda premium
Click to expand...
Click to collapse
What are the governors your talking about and whats the difference between undervolting and underclocking. sorry im still new to this and trying to learn
Got this from a forum, which you can to by searching. Not trying to sound snobby, but myself have found out alot by just reading.
Governors:
[*]interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
[*]smartass - Is an improved version of interactive governor
[*]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.
[*]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.
[*]brazilianwax - Very agresive version of smartass
[*]interactiveX - Tweaked Interactive governor by Imoseyon by adding more features like suspend/wake profile
[*]ondemandX - Tweaked and ported from 2.6.38 base Ondemand governor by Imoseyon by adding more features like suspend/wake profile
[/LIST][/INDENT
Those who are facing excessive heating on cm11 on 1.2ghz.
I suggest them to try phantom kernel v12 with -62uV and Intellidemand governor.
In my personal opinion it keeps temperature the coolest and with performance like on demand.
Basically
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors)
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
Click to expand...
Click to collapse
Thanks to
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 for describing all the governors.
Sent from my Hammerhead using XDA Free mobile app