Can anyone elaborate on the scaling settings in set CPU?
Some are obvious......powersave etc
Conservative
Userspace
Ondemand
Powersave
Interactive
Performance
I think its clear performance scales the CPU to highest speed. Powersave to lowest. But all the others seem to be the same. Is conservative a step up from powersave?
I can't find a thread that does a good job at breaking this down by the numbers.
Thanks to who ever points me in the right direction!!!!
Sent from my PC36100 using XDA App
Rtfm, jason.
Always wanted to say that
It's been a while since I checked but iirc the main difference between them is how quickly and aggressively the speed goes up and down. I read it on the help or about link in the app itself.
I did a simple Google search last night and found my ans.
Conservative vs ondemand is the answer for me.
Conservative scales up incramentaly as neded
On demand scales to max from min when needed
For best life with minimal performance hit, it seems conservative is the best scaling setting in set CPU.
Sent from my PC36100 using XDA App
Related
I messed up mine and forgot how they were.
EDIT: as far as profiles and advanced setting
Sent from my Inspire 4G using XDA Premium App
If you want to make it easy you could use the smartass governor and just set your max overclock. If you wanted to make separate profiles you could use conservative for screen off and set it to like 245 mHz and use the ondemand governor for your max overclock speed during screen on conditions and set it to whatever speed you want to run at, such as 1228 mHz. You would need to set up multiple profiles and activate them.
Here is a link to a guide I just found.
http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html
Wolf_2 said:
If you want to make it easy you could use the smartass governor and just set your max overclock. If you wanted to make separate profiles you could use conservative for screen off and set it to like 245 mHz and use the ondemand governor for your max overclock speed and set it to whatever speed you want to run at, such as 1228 mHz. You would need to set up multiple profiles and activate them.
Here is a link to a guide I just found.
http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html
Click to expand...
Click to collapse
Thanks for the reply. And the kernel I'm on (gingerbeast) doesn't have smartass
Sent from my HTC Sensation Z710e using XDA Premium App
Like many parts of the world, here in Australia it can get very hot. I would like to have my Galaxy Note automatically slow down when its too hot. I'm thinking this might mean a CPU governor that checks temp as well as CPU load.
If something like this already exists then does someone know where I can find it?
Otherwise I wonder if its not too hard to modify an existing governor to include temperature based throttling.
Currently I use CPU Master Pro to enable an overheat profile when it hits 49°c but you can get days here where the air is that hot! It needs to keep slowing down if it keeps heating up more. Even CPU Master Pro can't do that.
Sent from my Amiga GT-N7000 using XDA Premium.
Use setcpu profile.
Make a profile in setcpu, set the rule to if over 40 degrees limited cpu from 200 mhz to 1000 mhz. Its very easy
Sent from my GT-N7000 using XDA App
darkinners said:
Use setcpu profile.
Make a profile in setcpu, set the rule to if over 40 degrees limited cpu from 200 mhz to 1000 mhz. Its very
Click to expand...
Click to collapse
I already have that with CPU Master Pro. But i want something more versatile.
Sent from my Amiga GT-N7000 using XDA Premium.
Hey guys will overclocking drain the battery quicker even with stock voltages?
Sent from my Nexus S using XDA Premium App
Different voltages are specified as stock for different frequencies. As the frequency changes, the voltage does too. Running 1200mhz with the stock 1000mhz voltage will probably cause instability and crashing.
Harrb, great post.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
And if increase voltage, the power consumption should also increase.
i haven't played with voltages yet but in my experience the benefits of overclocking are minimal anyway, and they make nexus reboot often and other bad things :/
With the right settings you can get a fully stable and functional overclock, but it is on a per-phone basis due to varying quality of the same CPU during manufacture.
Harbb said:
Different voltages are specified as stock for different frequencies. As the frequency changes, the voltage does too. Running 1200mhz with the stock 1000mhz voltage will probably cause instability and crashing.
Click to expand...
Click to collapse
Currently I'm using icup kernel speedy 5 clocked at 1.4 and its been extremely stable. So what your saying is that the voltages automatically increase when I select a higher frequency, because I did not change them manually.
Sent from my Nexus S using XDA Premium App
xmatrix13 said:
Currently I'm using icup kernel speedy 5 clocked at 1.4 and its been extremely stable. So what your saying is that the voltages automatically increase when I select a higher frequency, because I did not change them manually.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Open NSTools and select Voltage tab. That's the list of "stock" voltages for each frequency.
suksit said:
Open NSTools and select Voltage tab. That's the list of "stock" voltages for each frequency.
Click to expand...
Click to collapse
Thanks
Sent from my Nexus S using XDA Premium App
A CPU governor such as on demand, lulzactive and lazy tells the CPU what clock to be at and automatically change. While reading, it will be at 100 or 200mhz, while playing a game it will be at the maximum clock you tell it to. Saves power this way.
your asian said:
i haven't played with voltages yet but in my experience the benefits of overclocking are minimal anyway, and they make nexus reboot often and other bad things :/
Click to expand...
Click to collapse
yes, usually 1 GHz is enough , UV or OC also may reduce hardware's physical life
OK i have read up a little about live oc, but really i still dont understand it.
In NS tools there are 3 settings.... a % an "oc target low", "oc target high"
As i understand it the percentage is just how much each step of the cpu scaling gets bumped... so if your at 110% @ 1000mhz step it would actually be 1100mhz. And @ 110% the buss speed would be at 220mhz vs the stock 200. (is that correct)
But as far as the other two settings... oc target low, oc target high... what are those?
Really im just looking for a little more incite on how live oc works.
Thanks guys!
You can tell it to live oc within certain frequencies. So if you only want to to be on live oc from 200-800mhz, you can set it to do that
Sent from my Nexus S 4G using xda premium
rocket999 said:
You can tell it to live oc within certain frequencies. So if you only want to to be on live oc from 200-800mhz, you can set it to do that
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
AHHH ok so the min and max are the range in which the live oc takes place. below and above those min and max values it goes back to normal?
how much rise voltages from 1300cpz/100liveoc to 1320cpu/110liveoc?
Bus OC don't work at all. I've tried 3d benchmarks with and without this and there are not difference
Sent from my Nexus S using Tapatalk 2
raulillo88 said:
Bus OC don't work at all. I've tried 3d benchmarks with and without this and there are not difference
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
you must not be doing it right or applying works for me
EDIT: you do realize it will only over clock the freq of the low target and high target.
For example you run your benchmark and your cpu settings are going to be affected on the I/0 scheduler and cpu governor.
if i run Sio ~ On-Demand @ 100/1000 and my Live OC is 1200/1400 your not going to be using the OC settings because its only designed to, to OC the freq you chose it to.
So to make it work for benchmarking purposes i would run Sio ~ Performance @ 1400/1000 or even 1400/1400 so it would only use those OC'ed freqs. and have the Live OC either 1400/1000 say @ 105% or 1400/1400 @ 105% so it run Straight OC'ed freqs only.
Stempox did a very nice write-up of CPU governors over in Android General ... I thought some of you might find it useful.
http://forum.xda-developers.com/showthread.php?t=1767797
Bump ... as many are playing with new kernels.
Sent from my SCH-I535 using xda premium
Question what governor for KT747 do you think gives best battery life and performance?
Thank you finally I know what those profiles mean other than the obvious performance mode...
fr8cture said:
Question what governor for KT747 do you think gives best battery life and performance?
Click to expand...
Click to collapse
i have tried every govenor/ io scheduler combination on different kernels and always end up back on deadline/ondemand.
It really depends on your needs and usage.
I am running KT747, 192 - 2106, custom voltage table, SmartassV2/sio -- Synergy.r71.
SmartassV2 can ramp up very quickly to meet demand and also attempts to ramp down quickly when demand lightens. You get a performance bias when you are interacting with the phone and a powersave bias when you are not.
As schedulers go, I figure simpler is better ... sio, all the way.
Sent from my SCH-I535 using xda premium