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!!!
Does anyone else think the CPU running at 480Mhz-800Mhz screen on is a bit too high? It's more than capable running at a 122Mhz minimum - heck, even 19Mhz, although it doesn't spend much time at 19Mhz. Also, if perflock is enabled, it locks itself to 245Mhz only when screen off - still seems a bit too high for me, considering there's lower selectable frequencies.
Anyone who's temprooted their device: Are you using SetCPU to change the CPU frequencies/disabling perflock? I have my Chacha running at 800Mhz max / 122Mhz min perfectly fine (running my battery down for a while to see if the battery life benefits) - although occasionally, it still locks itself to 122Mhz even after turning the screen on for about a minute, which I believe is a kernel issue
For reference, the frequency options are: 19Mhz, 122Mhz, 128Mhz, 245Mhz, 480Mhz and 800Mhz.
128Mhz doesn't actually work, and if it's selected, it uses 245Mhz instead even though SetCPU says "128 min"
Unfortunately I can't help you, but I'm totally interested on the subject!
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
really need low cpu frequency?
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Alex C. said:
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
Click to expand...
Click to collapse
True, setting the frequency too low is bad for some devices, but in my personal experience with my Chacha, I can actually run mine at 19Mhz min/800Mhz max and have little to no problems, since it doesn't spend much time at 19Mhz anyways. (I use no SetCPU profiles, as I feel they have little to no benefit on battery life.)
All of this is just a thought though, since HTC set the minimum to 480Mhz with the screen on which seems way too high to me :/
Also, locking the CPU to a single low frequency was actually a bad thing on one of my old devices, a Desire Z, which usually caused wake problems, etc.
semanty said:
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Click to expand...
Click to collapse
600Mhz is possible indeed - the MSM7227 processor that the Chacha uses is actually rated at 600Mhz, but HTC factory overclocked it to 800Mhz. It would require a custom kernel to have 600Mhz added back in
anyone thought of a way to undervolt???? i mean use less voltage for each frequency..am trying to search for kernels to flash but cudnt find any
I am using:
Rom: Insertcoin
Kernel: Bricked 1.5
Could you give me some tips to setup the best way setcpu.
I've seen some guys mentioning setting lowest frequency to around 400 and etc. and I don't know why. Could you give me some advice on setting up the program correctly.
Hi, I personally set the lowest frequency to somewhere around the 500mhz and smaller and set the govenor to ondemand as this will only use the the speed of your kernel when its needed thus, will use less battery.
Why around 500mhz and not 194. And will 5 sec refresh on the widget drain much battery? It's now on passive because I don't want to loose battery on bull****.
SsBloodY said:
Why around 500mhz and not 194. And will 5 sec refresh on the widget drain much battery? It's now on passive because I don't want to loose battery on bull****.
Click to expand...
Click to collapse
I put at 500mhz because sometimes the phone may slow down on its own and I don't think that setting the refresh rate to 5sec will steal much battery because its only a small widget
Any more opinions? Would be nice
Don't set it to 500 minimum. This will lock the phone to at least 500 mhz at all times and will cause substantial battery drain.
Go with 192 minimum or the next step up.
Sdobron said:
Don't set it to 500 minimum. This will lock the phone to at least 500 mhz at all times and will cause substantial battery drain.
Go with 192 minimum or the next step up.
Click to expand...
Click to collapse
+1 on that.
My personal settings (most of the time) are:
Screen On 192/648
Screen Off 192/384
Governer OnDemand
Sometimes I up the frequency if I need to run something heavy, not all that often though.
agreed 192 minimum is much better. if you are having issues with the phone being slow then get rid of sense...
Just wanted to say thanks to the three users above this post as I tried 192mhz and it is in fact a lot better now (please realise I've only just turned 17 and play a lot of games hence 500mhz)
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
I have the same problem too. For awhile thought it was to an app I moved to sd card (walgreens). Wasn't as often moving app off sd card.
Sent from my MyTouch 4G Slide using Tapatalk
m3gz said:
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
Click to expand...
Click to collapse
I've seen this happen as well with various roms as well (including 9.1). I currently am using tbalden's 10.1, and haven't seen it in forever. I don't know if he fixed it, or I've just been lucky.
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
m3gz said:
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
Click to expand...
Click to collapse
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
I keep mine at 1512 too. Low at 192, going to try 384 for a bit. I have not had the problem for awhile though.
Sent from my MyTouch 4G Slide using Tapatalk
Ziida said:
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
Click to expand...
Click to collapse
Thanks for the advice.
I remember having my max frequency at 1512 MHz before so I thought that wasn't a problem.
So far 540 MHz minimum has kept my phone from going blank. I'll try 192 Mhz next
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Saem persun said:
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Click to expand...
Click to collapse
192 MHz worked for me. You can try doing something extreme like what I did to see if it's the minimum frequency. It may decrease battery a bit but it's better than having the annoying black screen. I tried 540MHz as a test frequency.
Not all processors are the equal. So what may work for some may not work for others.
Same problem here. Black screen on Doubleshot with CM 10.1. Made me really concerned when it happened, as I was was reading the hardware maintenance thread earlier today (for fun) so I thought the LCD went.
This is the first time this has happened in the three weeks I had this phone, and I've been on 10.1 for almost a week now.
Because battery life[1] is an issue for me as well, I edged things up only slightly (from 96 MHz to 128), hopefully that will do to the trick. If not, I will try 192 MHz.
[1] Speaking of which, any tricks on keeping battery usage low? I use Deep Sleep Battery Saver which helps out a lot. And I'm selective about my apps (removed Songza because it was hanging around while closed, eating up battery life). GPS stays off, although I keep Wi-Fi and 3G on. It looks like the screen becomes the biggest draw at this point. Any advice would be appreciated.
Since the problem in March, I have upped the minimum frequency to 192mHz. For the longest while I haven't had any issues.
But since I installed my new Anker battery (was on a half-in-the-bag EZO Power 1900mAh), the problem came back, happened twice now, a week apart.
I'm trialing KitKatDS right now, but will probably go back in a week or less due to wakelock (Android OS) issues. Judging by above, when I do I will bump up the minimum even higher. Hard to see the correlation with how the battery will be causing it, but I see no other change.
Upping the lower end frequency seemed to work for a bit but i'm still getting the screen issues. I'm using a 3500mAh battery from China but I'm just doubting that the battery affects the screen.
The correlation of frequency to screen issues could also be coincidental.
m3gz said:
The correlation of frequency to screen issues could also be coincidental.
Click to expand...
Click to collapse
I wonder if the scheduler has anything to do with screen as well, that is, if CM uses a different one from stock?
Sent from my MyTouch 4G Slide using XDA Free mobile app