Related
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Cyanidex00 said:
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Click to expand...
Click to collapse
Actually we could use some hard evidence regarding this. Theories are theories, but actual experience is golden. Maybe you could try some various processor settings are report back?
Well, before I posted this I was using 245/886 underclocked with 245/245 screen off profile. At the end of the day I had an average about 75-80% percent battery life with pretty moderate to heavy usage.
I'm current using 245/1574 overclocked and will report back, with same screen off profile.
And yes, I did wipe battery stats before I started this.
Cyanidex00 said:
Well, before I posted this I was using 245/886 underclocked with 245/245 screen off profile. At the end of the day I had an average about 75-80% percent battery life with pretty moderate to heavy usage.
I'm current using 245/1574 overclocked and will report back, with same screen off profile.
And yes, I did wipe battery stats before I started this.
Click to expand...
Click to collapse
Cool, thanks for that info. Are you finding that forcing a 245 mhz screen off speed is impacting any apps running while your screen is off (e.g. music playing apps)? A couple of weeks ago I tried forcing the screen off at 122 mhz to see if that would help battery life, but I had big problems with music apps stuttering. I didn't play around with the speeds to see if raising the forced minimum to 245 would have fixed the problem. Some kernels advertise as a feature "Max speed - screen off 576MHz" or some other speed, but I don't know if it needs to be that high or not, for app stability.
I personally haven't tried any music or apps running while screen is off, I'll give it a whirl when I get home from work.
I know this obviously will vary from phone to phone, and how the user uses the phone. I'm pretty moderate to heavy usage daily. Hopefully maybe we can compile some data on what works for people.
I have my screen off profile set at 245 and have no problem streaming music from my SD card with the screen off. When streaming from the cloud, I sometimes get a very long pause between songs that isn't there with the screen on. I will try raising my screen off speed to see if that changes anything.
Sent from my Desire HD using XDA Premium App
henrybravo said:
Cool, thanks for that info. Are you finding that forcing a 245 mhz screen off speed is impacting any apps running while your screen is off (e.g. music playing apps)? A couple of weeks ago I tried forcing the screen off at 122 mhz to see if that would help battery life, but I had big problems with music apps stuttering. I didn't play around with the speeds to see if raising the forced minimum to 245 would have fixed the problem. Some kernels advertise as a feature "Max speed - screen off 576MHz" or some other speed, but I don't know if it needs to be that high or not, for app stability.
Click to expand...
Click to collapse
I noticed this yesterday. My screen off is also 245. My music stuttered, but only once (and it was fairly brief).
I raised the screen off speed to 368 and have not had any sputtering or long pauses between songs, even when streaming from the cloud.
Sent from my Inspire 4G using the power of the dark side.
biglittlegato said:
I raised the screen off speed to 368 and have not had any sputtering or long pauses between songs, even when streaming from the cloud.
Sent from my Inspire 4G using the power of the dark side.
Click to expand...
Click to collapse
Good to know, thanks!
Cyanidex00 said:
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Click to expand...
Click to collapse
I use SetCPU at 460/1152 brazilianwax, screen off 122/537 conservative and have good battery life and no issues when playing music w/ screenoff....
Overclocking is almost guaranteed to worsen battery life compared to say if it was at stock 1 ghz or a little less.
With a governor like on demand, its gonna scale from the lowest to to highest allowed as soon as it gets some load on it, eg from 245mhz to whatever Max is (1017, 1075, or 1920 etc), without stopping in between.
Even conservative with fast scaling will probably scale close to Max clock speed pretty quickly under load, so theoretically this should be a /little/ better for battery than on demand, but will not seem as fast and could possibly make the phone seem more laggy. Smartass is very similiar to conservative as it scales depending on a preset % of CPU load. If its set to 70%, when CPU reaches 70% load, it scales to next frequency, when that frequently hits 70% load, its scales again. The version of the on demand governor most of us have in out kernels is the fastest scaling option, which goes from min CPU - straight to max
It's time to Overclock our Phone...
DISCLAIMER: OVERCLOCK IS DANGEROUS FOR OUR PHONES
How to:
1. Now download r151 from Here
2. Put the files of r151 in the root of SD, run HARET.
3. Download SetCPU from Here and install It.
4. Now open SetCPU, And choice "Autodetect Speeds Reccomanded".
5. Allow Root.
6. Press Windows button and choice "Perflock Disabler" and "Attemp to Disable Perflock" and Check "Set on Boot".
7. Now, close the windows and OC our Phone.
My phone under USB and AC run at 825 MHz without Crash, i had tryed to run it at 864 MHz but System Crash everytime. Without USB and AC my phone run at 787 MHz. I Post 2 Images 1. = Normal Clock 2. = 825 MHz Clock.
To Made Benchmark i Use BenchmarkPi.
1. Screen Normal Clock
2. Screen 825MHz
For Other Question:
1. SetCPU
2. -r0bin-'s Post
I did it, it works perferctly !
Upscaled to 825 and min 128
Downscaled to 245 while charging and screen off
Thanks !
doublej4473 said:
I did it, it works perferctly !
Upscaled to 825 and min 128
Downscaled to 245 while charging and screen off
Thanks !
Click to expand...
Click to collapse
My Profiles:
1. Screen Off Min: 19 MHz Max: 245 MHz
2. In Call: Min: 128 MHz Max: 600 MHz
3. Charging AC: Min: 19 MHz Max: 825 MHz
4. Charging USb: Min: 19 MHz Max: 825 MHz
5. Main Profile: Min: 19 MHz Max: 787 MHz
...
Tell me please, does it helps to save the battery in last releace (r163)? I`m asking becouse i try to use Master CPU, and it seems to me that it don`t helps to save energy... But I don`t use profiles, only ondemand settings from 120-600 mHz.
Thanks!
@HTCxxxx
what is the percentage priority by profile?
puxus said:
Tell me please, does it helps to save the battery in last releace (r163)? I`m asking becouse i try to use Master CPU, and it seems to me that it don`t helps to save energy... But I don`t use profiles, only ondemand settings from 120-600 mHz.
Thanks!
Click to expand...
Click to collapse
To PowerSave try 19-480 MHz if Don't need Performance or 19-600 MHz Im Sorry But i Don't Know Master Cpu
doublej4473 said:
@HTCxxxx
what is the percentage priority by profile?
Click to expand...
Click to collapse
In Call is 100
And Screen Off 100 too.
19 Mhz does not work for me. Phone gets unusable slow and dont come back :/
Beside that, underclocking do not have a big influence on the battery consumtion.
Undervolting would be more interesting.
codiak said:
19 Mhz does not work for me. Phone gets unusable slow and dont come back :/
Beside that, underclocking do not have a big influence on the battery consumtion.
Undervolting would be more interesting.
Click to expand...
Click to collapse
Why Unusable??? Yhea, Undervolting can be an Interesting Thing, but i Think if the Volting is too low phone Freeze, and if is too high cpu can have an High temperature if you're stressing cpu and phone can freeze too. But i've noted, when i use a low "screen off" profile battery consumaption is high? why? is a problem of kernel? or is nomal?
codiak said:
19 Mhz does not work for me. Phone gets unusable slow and dont come back :/
Beside that, underclocking do not have a big influence on the battery consumtion.
Undervolting would be more interesting.
Click to expand...
Click to collapse
you are right,i also experienced that 19 Mhz makes phone lazy
i'm also agree about 2nd part..i read the same
HTCxxxx said:
Why Unusable??? Yhea, Undervolting can be an Interesting Thing, but i Think if the Volting is too low phone Freeze, and if is too high cpu can have an High temperature if you're stressing cpu and phone can freeze too. But i've noted, when i use a low "screen off" profile battery consumaption is high? why? is a problem of kernel? or is nomal?
Click to expand...
Click to collapse
you don't need to undervolt it too low,you just need to find the right voltage
try last kernel from r0bin and you will not have high battery consumption anymore
Low Mhz does not lead automaticly to low consumtion.
If you phone has something todo (update something for example) it will get the job done faster with high Mhz and is going fastert to sleep after that.
With low Mhz it takes longer and so can have higher consumtion.
On my HD2 I dont use profiles (like screen off) and it has a very low consumtion on standby/sleep.
If you set a minimum speed when screen is off a11 is not able to go to suspend, maybe
just a quick feedback on power consumption:
it never been so good with r167+drain fix without SetCPU
when I set profiles with low frequency (19 or 128Mhz) it keeps on consuming battery up to 100mA. when i switch SetCPU profiles off, i go to 9mA in suspend mode.
true story
there must be a way to setup SetCPU in a way it doesnt affect too much battery drain in suspend mode, but for the time being i just deactivated it.
tzacapaca said:
you are right,i also experienced that 19 Mhz makes phone lazy
i'm also agree about 2nd part..i read the same
you don't need to undervolt it too low,you just need to find the right voltage
try last kernel from r0bin and you will not have high battery consumption anymore
Click to expand...
Click to collapse
yes i see some improvement, and im happy for it...
(I THINK)
Hi All,
I've understood why CPU doesn't run @ 19MHz or @ 128 MHz...
Go to /sys/acpucloclock and look acpuclk_tbl...In It there are write all frequencies CPU can Run:
245760,400000,480000,600000,768000,787200,806400,825600,844800,864000....
but no Under 245 MHz so if You use a Profile for Screen off From 19MHz to 254MHz, cpu Run everytime @ 245MHz...so there is an high consummation of energy
bye
HTCxxxx said:
(I THINK)
Hi All,
I've understood why CPU doesn't run @ 19MHz or @ 128 MHz...
Go to /sys/acpucloclock and look acpuclk_tbl...In It there are write all frequencies CPU can Run:
245760,400000,480000,600000,768000,787200,806400,825600,844800,864000....
but no Under 245 MHz so if You use a Profile for Screen off From 19MHz to 254MHz, cpu Run everytime @ 245MHz...so there is an high consummation of energy
bye
Click to expand...
Click to collapse
hi
as codiak said earlier lowering CPU(underclocking) doesn't have so much impact on battery life..he also explained you why..if you want i will explain you too
explanation:run CPU at low voltage,open an app or downloading an email,etc= CPU will take time to get to the level app needs,display will stay longer while it CPU will get done the job= worse battery life
Undervolting will have impact on battery life
explanation:run same CPU clock at lower Voltage= CPU will use less power=better battery life
hope it's clear enough for you now,and if anyone else thinks i'm wrong feel free to prove me i'm wrong
P.S. Anyway i asked devs and they will lower CPU to run @ less than 245 Mhz.
Enjoy
tzacapaca said:
hi
as codiak said earlier lowering CPU(underclocking) doesn't have so much impact on battery life..he also explained you why..if you want i will explain you too
explanation:run CPU at low voltage,open an app or downloading an email,etc= CPU will take time to get to the level app needs,display will stay longer while it CPU will get done the job= worse battery life
Undervolting will have impact on battery life
explanation:run same CPU clock at lower Voltage= CPU will use less power=better battery life
hope it's clear enough for you now,and if anyone else thinks i'm wrong feel free to prove me i'm wrong
Click to expand...
Click to collapse
Ok thank you very much!!!
Hi. Trying to understand SetCPU.
There are two things I don't understand. That is MAX MHZ and MIN MHz...
Have seen some screenshots that people only change the MAX MHz. Why? And why not MIN MHz?
UnLucky12 said:
Hi. Trying to understand SetCPU.
There are two things I don't understand. That is MAX MHZ and MIN MHz...
Have seen some screenshots that people only change the MAX MHz. Why? And why not MIN MHz?
Click to expand...
Click to collapse
In essence it's to let the phone run at slower speeds when it can. This helps keep the phone cool and preserve battery power.
When I used SetCPU I used to create profiles to slow the phone down (lower the MAX) progressively as the battery % got lower. I also set it to Lowest/Very low when the screen was off.
Even now on my Sensation I'm at 192/648 screen on and 182/384 screen off. Obviously YMMV, it depends if the stuff you do on the phone works well enough at the lower frequencies. If I find it too low for something I just crank it up.
gol_n_dal said:
In essence it's to let the phone run at slower speeds when it can. This helps keep the phone cool and preserve battery power.
When I used SetCPU I used to create profiles to slow the phone down (lower the MAX) progressively as the battery % got lower. I also set it to Lowest/Very low when the screen was off.
Even now on my Sensation I'm at 192/648 screen on and 182/384 screen off. Obviously YMMV, it depends if the stuff you do on the phone works well enough at the lower frequencies. If I find it too low for something I just crank it up.
Click to expand...
Click to collapse
Thanks man!
Coming from the HTC Desire, where SetCPU was the only to manage the CPU, I have developed a habit of using SetCPU with several frequency profiles and different governors for various situations. For instance, I use battery<80, <60, <40, <30, screen off, temp >40, >50, and a charging profile. For governors I use lulzactive2 for higher frequency ranges, interactive for mid range frequencies and on demand for the lower frequencies. Oh, this is all with the latest matr1x kernel.
Seeing how a lot of ROMs allow extensive controll of the CPU I was wondering if it wouldn't be more efficient to just set a min/max frequency, chose a governor, turn deep idle on (which is off while I'm using SetCPU) and leave it be.
What are your thoughts and experiences on the matter?
/// endmessage / COMPUTOR5000
profile ? that's completely unnecessary...
just set governor and min-max is enough.
we have NSTOOL, so looks like extended ROM controll also not necessary because not good enough compare to NSTOOL , but lots lots ROM has it build-in
I've never bothered with profiles. I can feel if the phone needs a break from the heat and performance is good for me with 100/1200 set and slight undervolting.
Battery life while idling won't change, only while using intensive apps, and with deep idle working and max freq screen off, music playback and the likes drains very little battery.
Try it and see, you need to be comfortable with it.
I agree with qtwrk. Profiles are, in most cases, detrimental. The following is especially true since Deep Idle was implemented: always let the CPU run as fast as possible to save energy. Sounds counterintuitive, but here's why: while lower CPU frequencies in general consume less energy PER TIME than higher CPU frequencies, the faster the CPU can finish it's job, the faster it can return to energy saving states. So in the end, reducing CPU frequency actually uses more energy... Just overclock to save values, use undervoltage to set lowest possible voltage values and go to sleep.
What's the minimum you can set the screen off max frequency so that music playback isn't choppy?
Also, is the phone always idle on screen off, or does music playback, or any other activity make the phone come out of idle, even if the screen is still off?
/// endmessage / COMPUTOR5000
zyrill said:
I agree with qtwrk. Profiles are, in most cases, detrimental. The following is especially true since Deep Idle was implemented: always let the CPU run as fast as possible to save energy. Sounds counterintuitive, but here's why: while lower CPU frequencies in general consume less energy PER TIME than higher CPU frequencies, the faster the CPU can finish it's job, the faster it can return to energy saving states. So in the end, reducing CPU frequency actually uses more energy... Just overclock to save values, use undervoltage to set lowest possible voltage values and go to sleep.
Click to expand...
Click to collapse
Very good point, for exemple cpu at 1000 MHz takes 1100 juices per second and 10 seconds to finish a task, total cost 10 x 1100 (11000 ) juice
If it runs at 1200 MHz takes 1200 juices per second, same task only needs 8.34 seconds, 8.34 x 1200 (10008) juices... this isn't real just number assumption and theoretically appears that way
Sent from my Nexus S using xda premium
I agree with everything that was said here and actually posted about this very topic earlier on in the matr1x thread in regards to the lulzactive settings. People putting settings too much towards battery saving are actually not getting battery savings. They are making the CPU run longer and therefore more cycles and more power. Profiles are a bad idea too. They cause problems.
I decided to ask hear instead of creating new thread, etc.
In the amazing post of droidphile http://forum.xda-developers.com/showthread.php?t=1369817 there's an information about SGS II, that
'energetically efficient' frequency for CPU is 200 mhz
Click to expand...
Click to collapse
(it's Cortex-A9).
And what about Cortex-A8 on Nexus S?
droidphile also says that on Milestone (Cortex-A8) 550Mhz is the frequency used in the calculations based on the optimal energy to run. Don't know what's the source of this info...
This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk
that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.
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
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk
yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.
Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.
On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.