why most of lineage os roms uses interactive governor
it'll make device faster on some old devices
but it's not good for battery life
ondemand governor is fast enough for many devices in these days
why we're using it?
Related
What is your personal opinion on best governor and I/O scheduler?
I prefer BFQ and Wheatley (on omega3 kernel)
Anyone know which other custom kernel support Wheatley? I am running that governor on my S4 and i swear that is the best governor out there... I am trying to find others that have that governor implemented as well.
It's different with every device. Example being on my galaxy s4 ktoonservative governor and row i/o scheduler gives me the smoothest most battery efficient experience. With my nexus 7 touchdemand governor and bfq I/o scheduler give me the smoothest most battery efficient experience.
My goals when choosing governors and I/o schedulers are first and foremost a buttery experience followed by battery efficiency.
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.
The Best CPU Governor for Performance and also Battery life seems to be Interactive or Intellidemand.
For indepth Kernel Benchmarks and CPU Governor tests go to my thread here: http://forum.xda-developers.com/showthread.php?t=2625656
Here are SunSpider 1.0.2 benchmarks to prove the point.
(Lower is better)
ondemand: 1,200ms
intellidemand: 540ms
interactive: 520ms
conservative: 650ms
iPhone 5s:450ms
Conclusion: It is amazing that with this phone we can achieve performance that is close to the 64bit processor of the iPhone 5S. Screw Apple. (Just Kidding) Interactive is the best CPU governor. The end.
Lastly, you may wonder why I only posted Sunspider Benchmark results because that is only a javascript test and doesn't prove how the kernel will perform overall. First of all let me state that those numbers are after extensive testing under numerous different Stock and KitKat roms and Kernel combinations. Secondly, in terms of AnTuTu and Quadrant scores, you can expect them to be the same across all the CPU governors above. But the sunspider can be helpful in gauging browser performance. And since most users browse the web on their smartphones, it is wise to switch away from the default ondemand or ondemanplus which is a much more conservative version of ondemand, and instead use intellidemand or interactive or conservative.
It is interesting that conservative provides good performance and sunspider results. Maybe if you really want to be sure you have good battery life, you should stick with conservative. Although in all honesty, battery life is dependent on your brightness, and subsequently amount of screen on time, and then of course, the amount of CPU intensive tasks you perform like gaming, or Web Browsing. So differences between governors and battery life will be minimal if you do not adjust your user behavior...
I'm using a LS980 Sprint LG G2. I suspect that across variants results should be the same since SoC are based on the Snapdragon 800.
Conservative micro stuttered too much for my liking. Stuck to interactive.
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.
After I flashed twrp and rooted my honor 7, I decided to tweak around in kernel adiuter. I saw the stock governor was ondemand and changed it to interactive because I saw alot of positive feedback on that one. After a couple of days wondering why my battery life was reduced by half and not noticing any significant performance increase I decided to put it back on ondemand. The battery problem was gone.
I really dont think interactive should drain that much more battery so I think its some kind of bug in the stock kernel (using stock B371).
Interactive steps up or down your CPU clock in a snappy way, for ex. it will go from 450MHz to 1000MHz in a single step, but ondemand goes up and down reading the kernel's frequency steppings, interactive scales clock speed over a timer, so it stays on high frequency even if the app needing it has been closed. So, interactive is very responsive than ondemand, but is not battery friendly. Hence the battery drain.