Can somebody please explain the SetCPU governors to me? Normally I would use Smartass V2, but we only have the stock kernel.
The main governors I am curious about are mot_hotplug and hotplug. My phone seems to use a lot of battery when these are enabled, even with underclocked minimum scaling values.
Last night I ran my phone on ondemand at 300 min -300max (screen off profile) and it didn't drop 10%, first increment on battery reading stock ROM). Today while in school, it dropped from about 80% - 20% (using the same profile but with mot_hotplug).
Do all of the other governors manage both processors and hotplug can not?
You might as well use hotplug m8
MattyOnXperiaX10 said:
You might as well use hotplug m8
Click to expand...
Click to collapse
Why? That doesn't make any sense based from the findings I posted.
I'm using mot-hotplug in a week I'll know
Was using ondemand but I read an article where it shows the descriptions. Apparently hotplug behaves very similarly to ondemand but has the capability to turn off the 2nd core if there isn't a lot of workload. I switched to hotplug and so far its shown a significant difference in battery life. However, it may be a placebo as well so i'll stick to it for a week or so and then compare.
*edit
heres a link with better explaination
http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak
evonc said:
Was using ondemand but I read an article where it shows the descriptions. Apparently hotplug behaves very similarly to ondemand but has the capability to turn off the 2nd core if there isn't a lot of workload. I switched to hotplug and so far its shown a significant difference in battery life. However, it may be a placebo as well so i'll stick to it for a week or so and then compare.
*edit
heres a link with better explaination
http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak
Click to expand...
Click to collapse
I use kholks custom CPU governor it seems to be a lot snappier and battery use is good.
There is info in the development forum on here about it and using it.
Sent from my XT910 using XDA
Related
I have mine set to On Demand - Min 200 - Max 800, ive noticed though the scaling only gives me the option of - conservative - On Demand - Performance, im wondering where the remaining Governors like Powersave,etc are?
He he, you are trapped by SetCPU now.
Anyway, if you select Powersave mode you have to manually reboot the device. So it is useless.
Do you think an additional software is needed to underclock I9100's CPU? And please don't get confused by them who claims they get huge battery improvement for this app. You will get the idea after using it anyway.
Regards.
Sent from GT-I9100
Having carried out some tests using SetCPU and then not using it on Cognition ROM i found battery life to be better when i was using it particularly if i had it set to On Demand - Min 200 - Max 800.
I cant see an option for other Governors but im sure ive seen them before in a previous version,or was it another similar app?
I thought SetCPU is just a program and governors come with kernels.
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Quadrider10 said:
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Click to expand...
Click to collapse
anyone?
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
darkghost568 said:
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
Click to expand...
Click to collapse
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Quadrider10 said:
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Click to expand...
Click to collapse
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Snuzzo said:
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
Click to expand...
Click to collapse
Wheatley is epic.
Sent from my Rezound using Tapatalk 2
loonatik78 said:
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Click to expand...
Click to collapse
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
any ideas on how to fix tht?
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
No frills CPU in play store
Sent from my ADR6425LVW using Tapatalk 2
Quadrider10 said:
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
Click to expand...
Click to collapse
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
Yeah. Don't use DSB's kernel. I spent DAYS trying to figure out what his kernel is trying to do as far as governors. I'm not going to talk smack about the guy's work, but I will tell you what I know.
I doesn't appear any of the governors have been tweaked for his kernel. It looks like code was just tossed in there and left however someone else wrote it. For instance, smartassV2 has a sleep_wakup_freq of .998GHz, which is much slower than it should be. It SHOULD be near or equal to scaling_max_freq. Likewise, the max_cpu_load (which determines when the cpu should scale up) is 70, a fairly aggressive number, while the awake_ideal_freq and sleep_ideal_freq are pointlessly high. If I had to guess, these look like parameters for a Snapdragon S1 SoC, not the dual core S3 the Rezound has. No matter what governor you choose, it's only active on "cpu0". "cpu1" runs ondemand no matter what. The reason you have trouble making settings for the governor stick is because the sysfs location disappears and reappears for no obvious reason. It appears when things pop in and out (presumably when cpu1 goes on and off line), things are reset.
Cold hard reality is this: You're NEVER going to optimize any kernel out there to it's fullest potential. Either the options aren't there to tweak, or they behave in inexplicable ways. I can't tell you why DSB's kernel (not to single out a dev or his work, but I'm certain that's the kernel you're talking about) does what it does, but it's so far divorced from optimized on such basic levels you're better off not wasting your time.
As an aside:
After getting a rough feel for what some of these kernels are doing, I'm not at all surprised some kernels have had significant heat and battery drain issues. There are things that simply do not work right or work consistently. The devs shouldn't be blamed for this. These are probably the issues they're trying to work around that they inherited from the sources they're starting from and what makes tweaking them so difficult.
I acutely got everything to work. I'm just trying to overclock the GPU.
Hi all,
I dont know if anyone else has noticed this, but when i put my governor scaling to pegasusq, i can see lags in performance on my droid razr.
Whereas, hotplug mode works without much lag.
Also havent seen much difference in battery life, pegasusq probably gave me a 1 or 2 more hours of usage.
I've read about pegasusq that it works nearly same as hotplug, but with a screen off low processor state. Which is basically what i want, but the performance drops down a bit.
hsyasin said:
Hi all,
I dont know if anyone else has noticed this, but when i put my governor scaling to pegasusq, i can see lags in performance on my droid razr.
Whereas, hotplug mode works without much lag.
Also havent seen much difference in battery life, pegasusq probably gave me a 1 or 2 more hours of usage.
I've read about pegasusq that it works nearly same as hotplug, but with a screen off low processor state. Which is basically what i want, but the performance drops down a bit.
Click to expand...
Click to collapse
I think you got some problem...cause pegasushq is the smoothest governor on mine. Mind that I've installed the module in system I don't load it on boot using script...I got no init.d tweaks beside the undervolt script.
triplex76 said:
I think you got some problem...cause pegasushq is the smoothest governor on mine. Mind that I've installed the module in system I don't load it on boot using script...I got no init.d tweaks beside the undervolt script.
Click to expand...
Click to collapse
And how did u achieve that?
I mean how did u install it as a module?
triplex76 said:
I think you got some problem...cause pegasushq is the smoothest governor on mine. Mind that I've installed the module in system I don't load it on boot using script...I got no init.d tweaks beside the undervolt script.
Click to expand...
Click to collapse
can you post the undervolt script?
Hello all
I have a bit of a small problem. I like to run my phone using the Performance Governor but after a while it goes to 1Ghz on all 4 cores despite me running it at 1.8Ghz. Setting it back seems to correct the issue but in time it goes down again.
I believe it is getting a bit warm and thus it hits a limit and the system auto slows to 1Ghz.
Can anyone confirm this behaviour? It never happened to me before but I have had a few kernel updates and updates to the Omega ROM that could be the cause but I am not sure. Is there a setting where I can tell my phone what temps to throttle at?
Also, I assume all this is down to the Kernel and not the ROMs?
Would like some imput regards where to start my search to return my phone to its previous state as a pocket heater.
Many Thanks
Syl
. I like to run my phone using the Performance Governor
Click to expand...
Click to collapse
Don't use it. Pegasusq is the only one really working for multi-core CPU's with hotplugging and so on.
but after a while it goes to 1Ghz on all 4 cores despite me running it at 1.8Ghz.
Click to expand...
Click to collapse
1.8Ghz is not healthy for the CPU in the long run and will cause overheating which is exactly what you are currently seeing.
Especially since you keep the phone on 100% CPU power all the time (performance governor) which should drain battery like hell as a side effect.
Also, I assume all this is down to the Kernel and not the ROMs?
Click to expand...
Click to collapse
This is down to your settings. Neither rom nor kernel.
- Don't overclock (much)
-Use a good kernel such as Siyah
-Undervolt if the phone remains stable
-Use pegasusq Governor
-Enjoy
d4fseeker said:
Don't use it. Pegasusq is the only one really working for multi-core CPU's with hotplugging and so on.
1.8Ghz is not healthy for the CPU in the long run and will cause overheating which is exactly what you are currently seeing.
Especially since you keep the phone on 100% CPU power all the time (performance governor) which should drain battery like hell as a side effect.
This is down to your settings. Neither rom nor kernel.
- Don't overclock (much)
-Use a good kernel such as Siyah
-Undervolt if the phone remains stable
-Use pegasusq Governor
-Enjoy
Click to expand...
Click to collapse
Hi buddy and thanks for your response.
I am not sure about what you said regarding it working correctly, it gets the best results for any benchmark compared to others so I would be interested in more detail about the specifics of how its not working correctly as I have never been told that. It would be appreciated.
I dont mind the battery drain although I do heed your warning about about longevity of the CPU.
I have been using Siyah Kernel for some time now and I find undervolting a little unstable, for now I am forced to use pegasusq.
Can you or anyone else answer the original question as I still wish to pursue this to a resolve other than not using it.
Many thanks for your time and efforts non the less!
Syl
SyLvEsTeR20007 said:
Hi buddy and thanks for your response.
I am not sure about what you said regarding it working correctly, it gets the best results for any benchmark compared to others so I would be interested in more detail about the specifics of how its not working correctly as I have never been told that. It would be appreciated.
I dont mind the battery drain although I do heed your warning about about longevity of the CPU.
I have been using Siyah Kernel for some time now and I find undervolting a little unstable, for now I am forced to use pegasusq.
Can you or anyone else answer the original question as I still wish to pursue this to a resolve other than not using it.
Many thanks for your time and efforts non the less!
Syl
Click to expand...
Click to collapse
it´s samsung´s based roms related: when the battery temp hits 41C the cpu will throttle. Nothing related with de cpu temp (can be at 80C before throttles).
try CM10.1 and you´ll see what im talking about.
We need a solution for this throttling with samsung based roms
Will the DooMKernel give you better performance (faster) with the same battery life? Thanks for your reply.
That's what i feel with v15 on .757 firmware
Sent from my C6802 using XDA Premium 4 mobile app
Sadman Khan said:
That's what i feel with v15 on .757 firmware
Sent from my C6802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So v15 works better than v16?
It's more stable. Most users are getting random reboots on v16. I experienced them too and so i settled on v15. Works perfectly
Sent from my C6802 using XDA Premium 4 mobile app
do Z1 and z ultra das the same kernel built on doom?
Yes. Dbolivar has ported it unofficially from z1 to Z ultra. So the features shall remain same
Sent from my C6802 using XDA Premium 4 mobile app
I have been benchmarking various firmwares & settings combinations for my own gratification which I may post later - anyhow what I've concluded so far is .757 + Doom Kernel v16 is marginally slower than stock kernel but is better on battery use - more than enough to make up for the performance difference which I doubt you'd notice.
I haven't changed any settings from their defaults so I suspect it's governors that is causing this.
On v15 i got 34648 which is better than the average of 33k ish i get on stock. However i don't trust benchmarks anyway but doomkernel made the OS much smoother than that by stock kernel
Sent from my C6802 using XDA Premium 4 mobile app
I always run mine OCed so yes it is smoother than stock for sure. Not that stock is bad to begin with.
Just noticed stock rom + DooMKernel is noticeably better on GTA San Andreas. The game used to start chugging at times with stock (which didn't seem to be related to graphics settings).
Also DoomKernel uses Ondemand governor by default - anyone know what stock uses? But in any case my theory about governor is out the window.
After many years of observing confirmation bias with users I've come to trust benchmarks more than users reported experiences but each to their own For example I don't believe overclocking that small amount is going to lead to any noticeable increase in smoothness for most applications after you remove confirmation bias. Come to think of it ... it would be nice if there was an app out there that could set up blind testing for user experiences if that's possible.
diji1 said:
Also DoomKernel uses Ondemand governor by default - anyone know what stock uses? But in any case my theory about governor is out the window.
Click to expand...
Click to collapse
Last time I checked, stock kernel was by default using the interactive governor, but AFAIK it's the same as ondemand, except that it jumps to higher frequencies more agressively when the user is interacting with the phone (mostly by a kind of touch / input boost). In latest versions of the ondemand governor, I've also seen an "input_boost" option, so I think the difference is even less clear now.
For a proper benchmark which will be more consistent and easily reproducible across your firmwares and kernels, set everything to performance (i.e. CPU and GPU governors), and disable any battery saving and thermal throttle options in the kernel (beware your phone will get HOT during the testing, avoid repeating it too many times in a row or in a hot weather, or don't do it at all if you don't want to take the risk!). That's how some people get some very high numbers, if not by OC'ing the CPU.
And smoothness and lags are almost all about the governor choice and its fine tuning. For instance, I can't get a totally smooth scroll in some apps with ondemand or intellidemand, even after tweaking the settings; however, with smartassv2 and lagfree, everything is very smooth and battery is also good.
dbolivar said:
Last time I checked, stock kernel was by default using the interactive governor, but AFAIK it's the same as ondemand, except that it jumps to higher frequencies more agressively when the user is interacting with the phone (mostly by a kind of touch / input boost). In latest versions of the ondemand governor, I've also seen an "input_boost" option, so I think the difference is even less clear now.
For a proper benchmark which will be more consistent and easily reproducible across your firmwares and kernels, set everything to performance (i.e. CPU and GPU governors), and disable any battery saving and thermal throttle options in the kernel (beware your phone will get HOT during the testing, avoid repeating it too many times in a row or in a hot weather, or don't do it at all if you don't want to take the risk!). That's how some people get some very high numbers, if not by OC'ing the CPU.
And smoothness and lags are almost all about the governor choice and its fine tuning. For instance, I can't get a totally smooth scroll in some apps with ondemand or intellidemand, even after tweaking the settings; however, with smartassv2 and lagfree, everything is very smooth and battery is also good.
Click to expand...
Click to collapse
Stock kernel uses Ondemand governor by default. It can be changed to interactive/powersave/conservative i think if i remember properly
Sent from my C6802 using XDA Premium 4 mobile app
dbolivar said:
Last time I checked, stock kernel was by default using the interactive governor, but AFAIK it's the same as ondemand, except that it jumps to higher frequencies more agressively when the user is interacting with the phone (mostly by a kind of touch / input boost). In latest versions of the ondemand governor, I've also seen an "input_boost" option, so I think the difference is even less clear now.
For a proper benchmark which will be more consistent and easily reproducible across your firmwares and kernels, set everything to performance (i.e. CPU and GPU governors), and disable any battery saving and thermal throttle options in the kernel (beware your phone will get HOT during the testing, avoid repeating it too many times in a row or in a hot weather, or don't do it at all if you don't want to take the risk!). That's how some people get some very high numbers, if not by OC'ing the CPU.
And smoothness and lags are almost all about the governor choice and its fine tuning. For instance, I can't get a totally smooth scroll in some apps with ondemand or intellidemand, even after tweaking the settings; however, with smartassv2 and lagfree, everything is very smooth and battery is also good.
Click to expand...
Click to collapse
Ah cheers for that info and I'll start doing that on the benchmarks I do. (CPU benchmarks in particular are all over the place presumably due to governors)
That's interesting because it's been a while since I looked at the descriptions of what governors do but I seem to recall ondemand (to put it very simply) ramps up speed very quickly and basically gives high priority to performance over others.
Interactive is faster than ondemand at the expense of battery life as it ramps up the cpu frequency faster
Sent from my C6802 using XDA Premium 4 mobile app