• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root setcpu settings

As long as the difference in battery life isn't substantial (mine will only run on performance until it hits 50% battery) I would use performance. We'll see, I really think it will be within 10%. I always thought performance would push the processor the whole time the phone was on, I forgot I can set profiles to control it such as when the screen is off. My screen off setting is 125MHz max, I think that will be the most important as my screen is off the majority of the day.

Bring on the Performance baby!
 
I was using "TempMonitor" and it says "max range: 115.0" so I was not sure if that meant that was the high the CPU could take, but it seems not and it did seem low, but wonder what that means then?
 
115 degrees Celsius

Temps are in Celsius

I can prove it in a mater of seconds - My temps on my phone regularly run over 122 F when I am in the car either listening to music via Pandora or else (and especially when) using navigation.

I have been OCd for 7+ months, and have seen my phone hit 140 F on the CPU (at which point it rebooted) - trust me that is a Celsius temp, not a Fahrenheit temp.
 
I love the idea of running 250/250 when screen off BUT I cannot as I often run a GPS tracking app called MyTracks on runs and rides - 2,3,4,5 hours - and the screen is off so I think the screen off at 250 might be a little under powered to run GPS tracking functions in a map. So, I did 250/550 on demand as it seems 550 is a stock Droid so that should be fine AND cuts half off the 1100 it could be.
 
115 degrees Celsius

Temps are in Celsius

I can prove it in a mater of seconds - My temps on my phone regularly run over 122 F when I am in the car either listening to music via Pandora or else (and especially when) using navigation.

I have been OCd for 7+ months, and have seen my phone hit 140 F on the CPU (at which point it rebooted) - trust me that is a Celsius temp, not a Fahrenheit temp.

ahhh.. that app shows both a C and an F of the current temp and next to the 115.0 it shows nothing so I wrongly, again today, assumed it was in F as an American using that scale. my bad.
 
I love the idea of running 250/250 when screen off BUT I cannot as I often run a GPS tracking app called MyTracks on runs and rides - 2,3,4,5 hours - and the screen is off so I think the screen off at 250 might be a little under powered to run GPS tracking functions in a map. So, I did 250/550 on demand as it seems 550 is a stock Droid so that should be fine AND cuts half off the 1100 it could be.

My thoughts exacty. I just had to make sure the profiles were set to "ondemand" as opposed to performance so that they would be knocked down when needed. When I set the main screen to 900/900 perforance the default that came up for the profiles was performance so it was always at the max. Live and learn.
 
So of i have an 1100 MHz kernel, can i Max at 1100 or is that Not recommended?

I don't see why you couldn't. The first screen in setcpu allows you to set to the min/max speeds. You can set you max to 1100 and you min to whatever you like. I would keep it reasonably close to the max or you will notice a bit of a lag as it goes back and forth.
On the front screen you will also set your govenor settings. I use performance and set it at the max for both min and max but a lot of people use on demand and set a min speed along with the max.
The second tab which is profiles allows you to set profiles for different situations that may overide the fist page settings if needed. Make sure you set the governor to on demand for each profile. For instance I set my charging to 500/250 since I usually plug the phone in while in Navigation. When I ran it at the full 900 my phone got way to hot as it was always drawing at 900 and if I ran it at just 250/250 navigation won't work for me.

You can set your "screen off" screen settings to clock way down when the screen is not in use. I keep mine at 500/250 just in case I want to streem pandora or npr and the screen will go blank. If you set the govenor in the profiles to "ondemand" it will only draw what is needed anyway.

I also have a couple of battery profiles on demand that clock it back as the battery is getting weak.

You can set the priority for each profile which will let the phone know which profile to go to in a situation where 2 or more profiles may be activated.

Hope this helps.
 
asked the question earlier about temp, also curious ...

"for everyone using temp to adjust speed.. are you using > CPU temp or just > Temp I am just using > Temp and wonder if it is better to be using > CPU Temp?"
 
asked the question earlier about temp, also curious ...

"for everyone using temp to adjust speed.. are you using > CPU temp or just > Temp I am just using > Temp and wonder if it is better to be using > CPU Temp?"

Pretty sure Temp is just battery temp. I think it's more likely for the battery to overheat than the cpu. Battery overheat won't damage the phone as much as shorten the battery life. It just depends on what you are wanting to avoid. That said, I set both :p
 
exactly.. what ARE we trying to avoid in overlocking a CPU?

are we worried about battery or CPU temp. CPU temp would seem the logical one?

lots of people above talk about their temp settings, but do not say if they used CPU Temp or just Temp?
 
exactly.. what ARE we trying to avoid in overlocking a CPU?

are we worried about battery or CPU temp. CPU temp would seem the logical one?

lots of people above talk about their temp settings, but do not say if they used CPU Temp or just Temp?

Use both! You do not want either to overheat. My battery temp is set for 122F and my CPU temp is at 115F. I chose 115F just based on info in this thread, I am not positive at what point the CPU temp becomes dangerous. But I do know that you don't want the battery to exceed 140F. The back of the battery says 160F is the maximum threshold, so I would stay far away from that.
 
why 122? because you could not get that damn slider to stop at exactly 120 :)

:D LOL, not exactly. Its already at 122F by default and I feel that is a good temp to drop my processor speed at. I don't hit it often, and sometimes I'll still hit 130F. My goal is stay away from 140F, so I felt 122F was a good place set my ' temp ceiling'.
 
Hello all...I'm new to the forum, but I have been following for a few weeks now since i rooted and it has been a lifesaver. I stopped using the "ondemand" (with a low min and high max)setting as much because it seemed to bog me down and jack up temps. My current profiles are below.

CPU Temp > 51.0C = 400 max/250min (conservative) Priority 100
Temp > 41.5C = 500 max/250 min (conservative) Priority 99
Screen Off = 400 max/250 min (conservative) Priority 95
Charging AC/Full = 500 max/250 min (conservative) Priority 90
Charging USB/Full = 500 max/250 min (conservative) Priority 85
Battery < 30% = 500 max/250 min (conservative) Priority 75
Battery < 50% = 700 max/700 min (performance) Priority 70
Battery < 80% = 1000 max/1000 min (performance) Priority 60

MAIN SETTING = 1200 max/1200 min (performance)

I also have a few profiles in between, but they are turned off right now. So far so good with both heat and battery life.
 
you can really attribute "on demand" to jacking up the temps? It would seem to me "on demand" would save temps. For example, why always be at 1200 when not really doing anything?

also, what does "conservative" really do. again, seems "on demand" - to allow it to choose - makes sense? your the first person here to even mention using it, and curious what you think it means/or does it mean?

much to learn about the nuances of this app.
 
Full SetCPU directions and definitions :)


Some Highlights:

Charging/Full - Set when the phone is charging from any source and when the battery is full while charging (almost makes you wonder why have AC & USB then)
Charging AC/Full - Set only when the phone is charging from a wall plug (AC adapter) and when the battery is full while charging from a wall plug.
Charging USB/Full - Set only when the phone is charging from a computer (USB port) and when the battery is full while charging from the USB port.
Screen Off - Set when the phone's screen is turned off.
Battery < - Set when the battery falls below a certain point. You will also be able to specifiy battery level for this profile.
Temp > - Set when the battery or system temperature rises above a certain point. SetCPU will notify you with a ringtone notification if you check the "Audible Warning" checkbox here. You will also be able to specify a temperature for this profile.
CPU Temp > - Limited to phones whose hardware and kernels support it. Set when the CPU temperature rises above a certain point. SetCPU will notify you with a ringtone notification if you check the "Audible Warning" checkbox here. You will also be able to specify a temperature for this profile.


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.
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.
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.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governo
 
Use both! You do not want either to overheat. My battery temp is set for 122F and my CPU temp is at 115F. I chose 115F just based on info in this thread, I am not positive at what point the CPU temp becomes dangerous. But I do know that you don't want the battery to exceed 140F. The back of the battery says 160F is the maximum threshold, so I would stay far away from that.

Your CPU will hit 115 well before the battery gets to 122....just thought you'd want to know.

:D LOL, not exactly. Its already at 122F by default and I feel that is a good temp to drop my processor speed at. I don't hit it often, and sometimes I'll still hit 130F. My goal is stay away from 140F, so I felt 122F was a good place set my ' temp ceiling'.

122 F = 50 C - default setting (IIRC) for temp settings.

you can really attribute "on demand" to jacking up the temps? It would seem to me "on demand" would save temps. For example, why always be at 1200 when not really doing anything?

also, what does "conservative" really do. again, seems "on demand" - to allow it to choose - makes sense? your the first person here to even mention using it, and curious what you think it means/or does it mean?

much to learn about the nuances of this app.

Now that you have posted the actual definitions, does it make more sense?
 
you can really attribute "on demand" to jacking up the temps? It would seem to me "on demand" would save temps. For example, why always be at 1200 when not really doing anything?

also, what does "conservative" really do. again, seems "on demand" - to allow it to choose - makes sense? your the first person here to even mention using it, and curious what you think it means/or does it mean?

much to learn about the nuances of this app.

I have done a lot of experimenting over the past week with the settings I listed and my phone runs cooler, less lag/jerkiness here and there, and no ill effects on my battery life. I was surprised too as I have quite a few profiles and since I OC'd have been using "ondemand" MOSTLY.

You posted the SetCPU descriptions...read them...the system uses resources with the "ondemand" setting. For me, the phone has 3 basic states: 1) Charging 2) Screen Off 3) Me Using It. There really is no need to waste resources as I am basically MANUALLY setting my CPU to those 3 states (for the most part) with speed differences dependent upon battery life %. Under "ondemand," while one app may only max out my cpu (for example) at 700mhz normally...I'm running it at 1200mhz. But my temps have not increased and everything is smooth as silk and snappy.

Every phone is different, I suggest people experiment with it more. I've been pleasantly surprised so far (crossing fingers).
 
I have done a lot of experimenting over the past week with the settings I listed and my phone runs cooler, less lag/jerkiness here and there, and no ill effects on my battery life. I was surprised too as I have quite a few profiles and since I OC'd have been using "ondemand" MOSTLY.

You posted the SetCPU descriptions...read them...the system uses resources with the "ondemand" setting. For me, the phone has 3 basic states: 1) Charging 2) Screen Off 3) Me Using It. There really is no need to waste resources as I am basically MANUALLY setting my CPU to those 3 states (for the most part) with speed differences dependent upon battery life %. Under "ondemand," while one app may only max out my cpu (for example) at 700mhz normally...I'm running it at 1200mhz. But my temps have not increased and everything is smooth as silk and snappy.

Every phone is different, I suggest people experiment with it more. I've been pleasantly surprised so far (crossing fingers).

Excellent rejoinder. I have highlighted the most important part that people need to read repeatedly and thoroughly understand.

This is the exact reason why I shudder when someone asks "What is a good ROM?" or "Which is the best theme?" or "What is the best kernel?"

The answers to these questions are purely subjective, and what works on one phone may not work at all on another - or it may work better.

SetCPU, in that it is playing with a purely subjective matter to begin with, namely overclocking, is another one of those issues that is going to be different from one phone to the next. Here's why:

Not only do we have the hardware to consider - every piece of electronics that is composed of multiple components, all of which that are mass produced, are going to have idiosyncrasies within each individual unit - but we also have individual users who install different applications, root or don't, user one recovery or another, use a stock ROM or not, theme or not ....

With so many variables introduced there is no given with our phones. Some phones like having the low end set to 125 MHz, some don't. Some phones can do 1300 MHz some cannot. Some phones have no lag at 800, some do not.

It is not up to us to judge someone else and their choice of settings - it is up to us to find what is right for us.

Now, as a caveat - yes, asking for guidelines is a good thing - obviously we know that 99.999% o DROIDs out there are not going to his 2.0 GHz. however, once you have those, it is up to you to find the right balance that suits you. If it is Conservative, if it is performance, only you can decide.
 
Back
Top Bottom