Is there an app for the S3 that you can start and collects info about your usage and can suggest which governor, scheduler, undervolting (for gpu, cpu) to use? doesn't need to be JB (but it helps!), ICS is ok.
It's very confusing to understand that many things and I just don't notice any difference (for example with pegasusq and lulzactiveq haven't had a single crash) and undervolted the cpu 50mV and everything seems to be running the same so I don't know if I'm doing right or not. The only thing I noticed (and probably I'm wrong on that) is that the phone got hotter when I changed pegasusq for lulzactiveq so I reverted because I have the feeling that the hotter the phone means the more battery drain but my physics is not that good.
Thanks for helping.
My advice is that you ask/request this over at Apps and Themes as it more that section and most likely to find what you are looking for mate
Related
I have found explanations for most of the governors but would be nice to have a better explanation of the governors in particular the Smartass governor. Any kernel devs want to do a nice writeup explaining these.
Thanks.
the thing with governors is that they typically vary by developers and sometimes even by individual kernels. The concept of smartass is to throttle back when not used and ramp up using more slots to accurately match your speed to your usage. Most devs throw their own tweaks into each governor though, specifically the smartass one most
hope that helps a little bit...
Nice development thread!
This is more of a general question (and probably will rightfully be moved there soon enough)
Here it is though
Performance (never use): Keeps CPU at max all of the time
Powersave (never use):Keeps the CPU at min at all times
Conservative (personally suggested): Keeps CPU at lowest clockspeed possible while trying to perform well
interactive: Generally not used
smartass: works like conservative most of the time but locks the CPU at a low clock speed with screen off (depends on the kernel on exacts)
interactiveX: Seen in a kernel for my TB but NO idea what it does at all
Any I miss?
Userspace. Nobody knows what the hell its for.
Ondemand...lowers clock when not needed, ramps up very quickly when needed.
Interactive is very similar in that manner.
smartass can be configured to act like conservative or ondemand. I have it acting more like ondemand.
Standard Linux governors.
Hi everyone,
Like most people I've been trying to find that optimum balance between performance and battery life in my Aria. I'm running CM7.0.3 and the latest version of drowningchild's kernel. With that kernel I switched setCPU from ondemand to smartass, and I can already see the CPU spending most of it's time in either 400 or 480 MHz, but when playing a graphic intensive game it'll go up to 806 MHz and run great.
But, here's the problem. With things like less graphic intensive games, or playing videos, smartass doesn't want to scale up to a useful clock speed, and things get choppy. I switch back to ondemand and everything smoothes out again. I don't want to keep it in ondemand all the time though, because then it's spending half the time in 806 MHz and eating up battery unnecessarily.
So, is there a better governor option for me? Or maybe a way to "whitelist" apps within setCPU, to designate apps that always get the max clock speed?
tl;dr: smartass isn't that smart in certain situations. Is there a better way?
Check out the app "Tasker" in the market. It will allow you to reconfig the governors automatically based on a slew of complex conditions.
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
drowningchild said:
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
Click to expand...
Click to collapse
Hey yea you're right, I didn't notice you had a new kernel out. I'm running 7-5 still but I'll upgrade once smartass is working in the new version.
I've been using "conservative" setting. Although when it initial opens a resource intensive app, its stutters a little, and then compensates by clocking up. I haven't had an issue where a game didnt want to run smooth (also at 806mhz).
I run on demand at 320/768. This to me seems to be a very good combo. The 320 min makes a noticeable difference in responsiveness without much sacrifice to battery. I've found the Max cpu setting doesn't make too much of a difference in most situations.
Sent from my cm7 Aria.
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
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
loockzye said:
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
Click to expand...
Click to collapse
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Dr Goodvibes said:
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Click to expand...
Click to collapse
Thanks for your answer.
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