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
My sensation is currently overclocked at 1.73ghz, and according to a temperature widget I have it seems to hover between 25-45 degrees. I can only find the one temperature reading, so I think this will be the battery temp. I've set setCPU up to run at 1.73ghz below 35 degrees, then come down to 1.5ghz above it. If it gets to 50 degrees, it's then set to drop to absolute minimum and play a warning sound. I've also set it to drop to minimum when the screen is off to save power if the phone doesn't sleep, and to not exceed 1.2ghz when on charge or during a call. None of them are fixed, they're set to intellidemand or whatever it's called.
Do these settings sound reasonable? What sort of temps would be deemed as normal? I don't want to shorten the life of the phone if I can help it.
Also, if this temperature reading is just for the battery, what would I need to monitor CPU temperature too? Is there an app available so I can actually log the temps to see what happens when playing games, etc?
Sent from my HTC sensation using Tapatalk
Anyone?
Sent from my HTC sensation using Tapatalk
System tuner pro shows CPU temperature and does logs.
Matt
Cheers, I'll give it a try.
What sort of temperatures are acceptable before I risk the CPU's lifespan?
Sent from my HTC sensation using Tapatalk
Why do you need these over clock speeds? They will only ultimately increase temp, burn excessive battery and reduce the life span of your device.
Use common sense, these speeds are only worth using for bench mark tests
Personally anything above 43 is to hot for my device, although not same as yours, you can use set CPU to throttle down at this temp
Swyped from my Desire S using XDA Premium
I mainly wanted to overclock since the normal sensation was underclocked in the first place, the sensation xe runs at 1.5ghz and the CPU is the same. So I wanted at least that. What I'm wanting to do now is find how quick it can be before it starts running too hot. Just wondering what's considered too hot in the first place.
Sent from my HTC sensation using Tapatalk
My web browsing is much better (faster and smoother) at higher clockspeeds and performance governor. So that's why I run higher speeds. I use my phone for internet stuff more than anything else.
matt
Mine seemed smoother too, for normal use and for my emulators. I found a problem though, setCPU wouldn't let the phone sleep so my battery went from 85% to dead overnight! It also seemed a little unstable even when turned back down to 1.53ghz, so I've uninstalled it and it's now running 1.53ghz just from the kernel. Runs perfectly now and battery life is back to normal. No noticeable difference in performance going from 1.73ghz down to 1.53ghz either, but now the battery temp seems to top out at 35-40 degrees or so, so about 5-10 degrees less than when it was set higher. I'll still give that app a go though so it can monitor and log temps while I'm playing games, etc.
Sent from my HTC sensation using Tapatalk
I have been noticing bad battery life recently and I checked my setcpu settings and for some reason my phone never goes below 602 MHz. I have my profile set to 389 as the lowest frequency. I was wondering if anyone knows the problem and if there is anything I can do about this.
Sent from my LG-P999 using XDA
Bump
Sent from my LG-P999 using XDA
there was another thread (Here) about 5 days before you posted this. Read that... this is just part of what i posted:
this phone (and alot of newer ones) are using an idea called Race to idle.
this means that the cpu will kick its cpu speed up higher than it needs to get things done faster, so it can get back to a low power idle state faster.
In reality your cpu is really going in and out of sleep states hundreds or thousands of times a second, the frequency is just kicked up so that it can spend less time computing, and more time sleeping.
for the hell of it try downloading an app that shows you cpu usage in %
that number is the amount of time that the cpu is in a fully awake state vs being in its first stage sleep state, LP1.
if nothing happens for a bit longer than it will go into an even lower power state called LP2. frequency can still be set to a higher number (like 600mhz or even 1ghz) but the cpu is actually not doing any calculations. its sleeping till something needs it.
also, changing cpu speed takes a long time (cpu wise), the cpu has to pause, change speed, then wake up. so the less it does this the less lag you have.
Click to expand...
Click to collapse
Hey everyone,
Just wondering if deep sleep is working on any of the ICS roms/kernel combo so I can use it.
Also I have searched to no avail, but can someone possibly explain how deep sleep works? Like I know it clocks the processor to very low levels, but is the phone able to 'wake up' when it receives a call/text/email, or do you only use this feature in situations when you do not need your phone (like in class or at work etc) as to keep the battery from draining?
thanks for your time
samsizzle said:
Hey everyone,
Just wondering if deep sleep is working on any of the ICS roms/kernel combo so I can use it.
Also I have searched to no avail, but can someone possibly explain how deep sleep works? Like I know it clocks the processor to very low levels, but is the phone able to 'wake up' when it receives a call/text/email, or do you only use this feature in situations when you do not need your phone (like in class or at work etc)
thanks for your time
Click to expand...
Click to collapse
Harsh kernel goes into deep sleep.. its an idle state it wakes up when you get calls and such its automatic after a certain amount of time with the screen off
DJLamontagneIII said:
Harsh kernel goes into deep sleep.. its an idle state it wakes up when you get calls and such its automatic after a certain amount of time with the screen off
Click to expand...
Click to collapse
so is using setcpu and creating a profile that lowers the clock speed for 'screen off' counterintuitive?
samsizzle said:
so is using setcpu and creating a profile that lowers the clock speed for 'screen off' counterintuitive?
Click to expand...
Click to collapse
no it will lower the speed before it goes into deep sleep.. theres a certain amount of time with the screen off that its not in sleep and thats when the profile will save battery
samsizzle said:
Hey everyone,
Just wondering if deep sleep is working on any of the ICS roms/kernel combo so I can use it.
Also I have searched to no avail, but can someone possibly explain how deep sleep works? Like I know it clocks the processor to very low levels, but is the phone able to 'wake up' when it receives a call/text/email, or do you only use this feature in situations when you do not need your phone (like in class or at work etc) as to keep the battery from draining?
thanks for your time
Click to expand...
Click to collapse
Tegra does not have deep sleep. It instead has low power states called lp1 and lp2. Basically your phone goes into lp1 hundreds or thousands of times a second. actually the "cpu percentage" you see in almost all apps is the amount of time spent in lp1 vs awake.
Lp2 can be considered deep sleep. All kernels support it in this phone. What it does is "park" the cpu. most of the time it only parks one core on this phone, but in times of very low activity it parks both. In lp2 the processor is using so little power it's almost not even on.
While a core (or both) is (are) in lp2. There is something built into it so that if for example you get a call, the radio will wake the cpu up and it well resume working.
about screen off profiles, in my opinion they are useless.
Processors use a technique called "Race to Idle" basically it takes way less power for the cpu to go up to 1ghz, do its work very quick, then go back to sleep, then it does for it to do the work slowly at 216mhz. Because of this you should never limit your cpu to a lower speed. Nvidia spent a lot of time and money researching how to do these things power efficiently, and limiting the cpu lower only makes the cpu fight itself.
Sent from my LG-P999 using Tapatalk 2
^ give this man his thanks!
This is why I love this community, so informative and helpful.
Klathmon said:
Tegra does not have deep sleep. It instead has low power states called lp1 and lp2. Basically your phone goes into lp1 hundreds or thousands of times a second. actually the "cpu percentage" you see in almost all apps is the amount of time spent in lp1 vs awake.
Lp2 can be considered deep sleep. All kernels support it in this phone. What it does is "park" the cpu. most of the time it only parks one core on this phone, but in times of very low activity it parks both. In lp2 the processor is using so little power it's almost not even on.
While a core (or both) is (are) in lp2. There is something built into it so that if for example you get a call, the radio will wake the cpu up and it well resume working.
about screen off profiles, in my opinion they are useless.
Processors use a technique called "Race to Idle" basically it takes way less power for the cpu to go up to 1ghz, do its work very quick, then go back to sleep, then it does for it to do the work slowly at 216mhz. Because of this you should never limit your cpu to a lower speed. Nvidia spent a lot of time and money researching how to do these things power efficiently, and limiting the cpu lower only makes the cpu fight itself.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
will overclocking effect the ip1 and lp2 states?
jwalker3181 said:
will overclocking effect the ip1 and lp2 states?
Click to expand...
Click to collapse
the short answer is no, not really in any way that will matter...
the long answer is yes, let me explain:
it may actually increase the amount of time that the CPU spends in these states. on the other hand, if the kernel developer messes with these threshold values that determine some of these states, it may actually increase the amount of time one core spends in lp2, but reduce the amount of time the other core spends fully awake.
either way, its a balancing act that the kernel devs do, and they seem to have a pretty good hold on it.
Klathmon said:
the short answer is no, not really in any way that will matter...
the long answer is yes, let me explain:
it may actually increase the amount of time that the CPU spends in these states. on the other hand, if the kernel developer messes with these threshold values that determine some of these states, it may actually increase the amount of time one core spends in lp2, but reduce the amount of time the other core spends fully awake.
either way, its a balancing act that the kernel devs do, and they seem to have a pretty good hold on it.
Click to expand...
Click to collapse
I feel like you've got all the answers, man. I learn a bunch reading your posts.
Caliyork said:
I feel like you've got all the answers, man. I learn a bunch reading your posts.
Click to expand...
Click to collapse
Android is my hobby, i spend an insane amount of time pouring over data sheets, source code, and manuals. Honestly I'm still fairly new to Android, but I've been programming for years so that helps
And for some reason even i don't know, i kinda like answering questions on this forum
Sent from my LG-P999 using Tapatalk 2
Caliyork said:
I feel like you've got all the answers, man. I learn a bunch reading your posts.
Click to expand...
Click to collapse
+1 im glad klathmon is in our forums
Sent from my LG-P999 using xda premium
I am running cm9(beast mode wifi calling one ) atm but I have a heat issue with my phone around the camera and speaker area where the phone is really hot but by the battery n bottom half it is much cooler.
is this normal for you guys? N gals? And even if I turn of the phone n it cools to 91 is shoot back up again
Sent from my SGH-T959V using xda app-developers app
I'm running on demand btw and around of charge 98-113 charging 109-123
Sent from my SGH-T959V using xda app-developers app
idunno why but we have the same problem..
i think that the reason why it heat up is because you overclocking it?
when i set it max it really heat up quickly.
Install betterbatterystats and see how much CPU you are using and on what.
Sent from my SGH-T959V using xda premium
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
dgmoodey said:
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
Click to expand...
Click to collapse
i do that but it goes to 200 mhz never 100
xtrem88 said:
i do that but it goes to 200 mhz never 100
Click to expand...
Click to collapse
That's a 'feature' of the ICS+ kernels. While 100MHZ is the minimum, if it's actually set to that, the kernel is set to go back to 200MHZ anytime it gets the chance. You can watch this happen if your scheduler/governor app actually updates on current min/max speeds. ROM Toolbox PRO, SetCPU, ROM Control, and CM's Performance controls all display this shifting, though with luck you can sometimes get it to stick at 100MHZ. It just takes some persistence.
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
airfluip1 said:
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
Click to expand...
Click to collapse
well i left i think it was kj2 and flashed lb6 and i started using greenify hasn't really happened now
No to open another thread I have a Android backup issue any suggestions?
And power managed is on even though wifi is off
Sent from my SGH-T959V using xda app-developers app
I never got my phone to go into deep sleep when I selected ondemand (or maybe it was ondemandx). I would try a couple of the other governors & see if that would help.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
OndemandX gives me good sleep, but forces the phone to minimum speeds when the screen is off. That tends to cause issues if I'm trying to use GPS or music without the screen burning.
As to what will work best... that depends on unique your phone, its apps, any tweaks that have been made, and your specific combination of scheduler/governor settings. I'm a fan of SIO, but sometimes the tweaks make that (and deadline) stick at max MHZ, in which case noop is great. At various times, I go with any of the SA2-based 'intelligent' options (SavagedZen, brazilianwax, SmoothAss, or SmartAssv2) or the OndemandX/Conservative basic sets. The others have gotten stuck more often and tended to allocate more processor than I think it needs.
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
FBis251 said:
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
Click to expand...
Click to collapse
That's usually the one I always fall back on too despite new ones all the time and everything, it's my default now on any ROM.