I did a google search and found no good simple explanation of the Lionheart governor. What exactly does it do in more simpler terms.
Is the battery life better than stock but with better performance?
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.To 'experience' Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
Hope that helps
teambestyrandy said:
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.To 'experience' Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
Hope that helps
Click to expand...
Click to collapse
Thanks but that is what I was talking about. I saw this definition on google but I can't understand that definition.
I just want to know where does Lionheart rank among the others in terms of performance and in terms of battery life (especially stock).
Right now I'm using Eugene's kernel with lionheart battery is great for me I get 13 to 15hours with good performance the other governor that would be good on batter is Brazilian wax and savages Zen those two are good to but I prefer lionheart ccause there's performance with good battery life better than stock in my opinion.
teambestyrandy said:
Right now I'm using Eugene's kernel with lionheart battery is great for me I get 13 to 15hours with good performance the other governor that would be good on batter is Brazilian wax and savages Zen those two are good to but I prefer lionheart ccause there's performance with good battery life better than stock in my opinion.
Click to expand...
Click to collapse
Brazilianwax and savagedzen are both derivatives of smartass, which doesn't work with our chipset. If you use any of those 3 your CPU frequencies will tend to stick at max value and not go down
yoft1 said:
Brazilianwax and savagedzen are both derivatives of smartass, which doesn't work with our chipset. If you use any of those 3 your CPU frequencies will tend to stick at max value and not go down
Click to expand...
Click to collapse
no they work fine...
Smartass & the other 2 have no issue with it sticking... however SmartassV2 does stick at Max speed.
eugene373 said:
no they work fine...
Smartass & the other 2 have no issue with it sticking... however SmartassV2 does stick at Max speed.
Click to expand...
Click to collapse
I stand corrected then
Lionheart vs. Interactive, Smartass, Brazillen Wax, Savage Zen?
Can anyone answer this?
How does its battery life and performance of Lionheart under typical usage compares to interactive's, smartass', brazillian wax's, and savage zen's?
You can just say something like, "Under normal and average use, Lionheart generally has a better battery life than abc and better performance than xyz."
h1a8 said:
Can anyone answer this?
How does its battery life and performance of Lionheart under typical usage compares to interactive's, smartass', brazillian wax's, and savage zen's?
You can just say something like, "Under normal and average use, Lionheart generally has a better battery life than abc and better performance than xyz."
Click to expand...
Click to collapse
bump
Related
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
pianoplayer said:
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
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. - SetCPU website
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. - SetCPU website
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 the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. 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.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
SMARTASS GOVERNOR
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 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245. No need for sleep profiles any more!
The performance for each can varry by kernel due to the fact that some devs slightly tweak the governors to their liking. Without any tweaking they should be the same accross all kernels.
Also note that tinys kernel has an interactive X governor and also a smartass 2 governor. These are basicky just tweaked versions of the original governor.
pianoplayer said:
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
Click to expand...
Click to collapse
This is a good resource for governors. It is quite technical though. It doesn't include smartass though smartass is similar to smartassv2.
CPU Governors
Let me know if you still have questions after reading it.
The answer to your second question is no. The build of the governors are about 95% the same between kernels and with the exception of the smartass governors all those listed are stock android kernels.
Interactive should be smoother than conservative or ondemand but similar in performance to the smartass governors.
SmartassV2 is found to give the best performance/battery life combo across the board.
Edit: Good writeup cmlusco. In practice yes, smartassv2 is better all around I think. Interactive from Nexus S/Galaxy Nexus kernel source should be good but I've yet to be able to backport it to work on this phone property. It turns into a performance governor really.
And a side note. If the phone is actually in deep sleep state (reported by CPU Spy) the governor will not really matter then. Only time screen off matters is when it's awake but screen is off. Governor is most critical when screen is on really, so if you go for performance, screen on performance is what matters.
Edit 2: And I read some interesting viewpoints recently on maximizing battery that are different than the minimize CPU speed.
Seen a lot of conflicting comments stating using smartass governor means there is no need for profiles to be setup and can actually be detriment to the battery life and speed of phone.
Is this true or could I benefit from setting up profiles to get my usage optimised.
Below is a quote which will explain you everything about smartass governor
From it's developer:
"smartass governor - 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 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Click to expand...
Click to collapse
which best I/O scheduler and governor for baterry life and gaming
razer1224 said:
which best I/O scheduler and governor for baterry life and gaming
Click to expand...
Click to collapse
IMO Noop is best I/O scheduler since there is not much tweaking needed.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems
.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance
.
But SIO is best optimized for most environments.
As for governor I think Interactive is good but our case OnDemand is tweaked the most and best for games (SmartassV2 is my personal favorite but it's not used by our kernel developers).
A little about OnDemand Governor:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
But it's all up to the kernel developers which governor or I/O scheduler he wish to tweak and modify to bring the best results.
More info: http://forum.xda-developers.com/showthread.php?t=1369817
What are the best options one gaming performance and second for battery performance. I am currently on zen/ondemand.
note 2
IO does not contribute much to every day performance. Most of the governers should scale to max during games so don't worry about that but if you really want max performance just set it to performance. Best battery life is obviously the power saver governer but honestly for every day performance OnDemand or Pegasusq is the best of both worlds
Currently under clocked at 1.2ghz, in combination with aggressive govr and row sched
What about interactive?
I am seriously tired of battery drain so I am now searching for a governor that would balance between Battery Life and Performance. I read this http://forum.xda-developers.com/showthread.php?t=1369817 but actually I was lost in that large number of governors, so Can anyone simply tell me what governor is the best ? I mainly leave WiFi On but Screen On is not usually for a large time ...
amr.reflection said:
I am seriously tired of battery drain so I am now searching for a governor that would balance between Battery Life and Performance. I read this http://forum.xda-developers.com/showthread.php?t=1369817 but actually I was lost in that large number of governors, so Can anyone simply tell me what governor is the best ? I mainly leave WiFi On but Screen On is not usually for a large time ...
Click to expand...
Click to collapse
afaik and base on their details. personally, i use interactive+row on stock then smartassv2/ lulzactive+sio on custom.
SmartassV2:
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.
edit:
Q. "Ok. Enough of explanations. Tell me which governor is for performance and which one is for battery life."
A. Tough question! lulzactive and smartassV2 for a balance between performance and battery. For light weight tasks, lulzactive should be better for battery. And for heavy weight tasks, lulzactive should be better for performance also.
NOTE: It's not so easy to tame luzactive. If you don't know how exactly to do it, stay away from it or you will end up complaining about battery drain!
Click to expand...
Click to collapse
amr.reflection said:
I am seriously tired of battery drain so I am now searching for a governor that would balance between Battery Life and Performance. I read this http://forum.xda-developers.com/showthread.php?t=1369817 but actually I was lost in that large number of governors, so Can anyone simply tell me what governor is the best ? I mainly leave WiFi On but Screen On is not usually for a large time ...
Click to expand...
Click to collapse
I use SmartAss V2 and SIO as governor and scheduler.
Like you, my wifi is permanently on, but screen is not on for long periods, and using this combo since Alpha releases of CM10 onward I have had good results, getting up to 2 days plus on CM10 EOL, and currently on LiquidSmooth 2.9 am getting well over a day from a charge.
Performance is good and LiquidSmooth ROM runs beautifully at stock CPU speeds (I currently use educk's Phenom Kernel ported by Madridii with 370Mb RAM, but have had great results with any Madridii kernel)