Develop Bugs

help needed SETCPU problems

Hey guys im having trouble with my phone when setcpu is running. When ever i come out of lock screen it takes a few seconds to be able to do stuff on my phone, like its waking up from sleep. Also some times i get this message and it has to reboot.
"Sorry activity htc sense (in application HTC Sense) is not responding."
Im running the 2.6.32.15 king # 4 kernel.
My set CPU settings are on 1.15 GHz max and 460800 MHz min. Im running conservative at the moment but it does it on other scaling like performance and on demand. my setting for screen off is 460min 614 max.
Is there anything im doing wrong? or should i be using a different kernel? What kernels are the best? Thanks

I would bump up the lower end to about 600. I have have issues lower than that coming out of sleep.

im running virtuous 2.7
power saving kernel
Main Profile is 245-998 ondemand
Screen Off is 245-384 ondemand
I do not have that problem... but it would be a lie if I told you i didn't before!
I was having this problem you are talking about when my main profile was set to conservative.
EDIT: Back up your setcpu + settings in titanium... Uninstall it (or freeze it) and see if the kernel can run it just fine cause it probably will. Most kernels already have the settings for optimum performance and even the devs who make them (like hydra) say that it will work best without setcpu.
Source: http://www.hydrakernel.net/hydra_kernels_information.htm
"I recommend not using the setcpu controls or governor with these kernels. Let the stock governor do the work. If you have setcpu installed I recommend clearing out the settings before flashing the kernels. You can use it to monitor cpu speeds or an app from the market called systempanel if so desired."

Need a little help

I am new to the setcpu app I am wondering how do I know how much frequency my min and max should be to help my phone out more. Can anyone help me on that plz?
Sent from my PC36100 using XDA App

It will depend on which ROM and kernel you're running, but generally, overclocking doesn't do much good for you. I do however run my Main Max @ 1113 and Min @ 245. I then have a profile set for Screen Off Max @ 245, Min @ 245. This has helped a lot with battery life. This is on CM6.1.1 and the SBC stock kernel.
Also, there are the Scaling options. They will vary based on the kernel you're using. Generally, their names speak for themselves, so pick appropriately. I use Interactive when available, or Ondemand as a second choice. If you choose Performance, you will stay clocked at the highest speed until over ridden by a profile, so don't bother with that one unless it's for testing only.
One thing to think about is that Setcpu doesn't play well with HAVS, so if you're running a kernel with that built in, they will be fighting each other.
Also, if you're running a stock based rom with a stock kernel, you will need to disable Perflock if you want Setcpu to be able to really do it's job. So, while in Setcpu, tap Menu > Perflock Disbaler and attempt to disable perflock. Once it is successful, pick set on boot and close that window. Now Setcpu can work properly and you can start saving battery.
If you're primary goal is to get amazing battery life, I highly reccommend you try some of the new SBC kernels that have trickle charging built in. That's what I've been using since they came out, and it is amazing what a little tweak can do for you. SBC Kernel Thread

Safe under and overclock for Desire Z?

What are the safe/stable clockspeeds for underclocking and overclocking my Desire Z? Also, what app do I use? Like, I don't mind paying for the app (as long as it's not too expensive)
Sent from my HTC Vision using XDA App

SetCPU can be used to overclock if you're rooted. Depending on the ROM and Kernel combination, overclocking to about 1.3ghz is usually safe. Some go up to 1.5ghz or even 1.8ghz, but are often quite unstable depending on other configurations you have in your ROM.
As far as underclocking goes, some custom kernels clock all the way down to 122mhz, I've been using a streamline5 kernel on CM7 (which offers 122mhz min) and haven't had any ill effects with this.

I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App

zaghy2zy said:
I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
No, there's no need to set a particular clock speed. Just whatever works for you. I wouldn't recommend going under 800mhz, as the phone will really really bog down even with normal use.
I haven't used that particular ROM, but I'm assuming anywhere around 1.3ghz should be safe on the upper limit. Like I said before, anything above that might start to cause issues. You might also want to consider the battery life implications of severe overclocking.
You can change the clock speed any time you want. If you're having wakeup or heat or any other issues just go back to SetCPU and change the max clock speed again. You can also use profiles in SetCPU to change the clock speed when the phone is overheating, or when the screen is off, or when the battery gets to a certain %. There are tons of posts detailing how others have setup their SetCPU profiles.
One last note, don't forget to check the box for "Set on Boot" in SetCPU, this way your changes aren't undone on reboot.

Thank, I think I got everything I need to know in your last reply

I'm on CM7, with the CM7 kernel, and clocked in at 1.5GHz, and have no problems, and the rom is super fast. And I use SetCPU.

SetCPU... is it needed for CM7?

I searched for answers but didn't get satisfactory results, so I wanna ask my G2 peeps.
CM7 has an OC daemon, right?
Since it does, is SetCPU still needed?
How does one configure the OC daemon with profiles for screen off, battery>50% etc etc?
I am running CM7.1

convolution said:
I searched for answers but didn't get satisfactory results, so I wanna ask my G2 peeps.
CM7 has an OC daemon, right?
Since it does, is SetCPU still needed?
How does one configure the OC daemon with profiles for screen off, battery>50% etc etc?
I am running CM7.1
Click to expand...
Click to collapse
CM7 does have an OC daemon but it does not have profile settings like SetCPU. Most feel that using profiles kills the battery faster than not using profiles as the device is having to poll the system so frequently. If you just set the min and max speeds, you'll be fine.
Sent from my HTC Vision using XDA App

Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Because the only reason I have setcpu is to set the profile so it goes to 500/200 mhz screen off...

I think the CM7 included OC/UC manager is pretty darn good. I wouldn't worry about using SetCPU it'll just interfere.
convolution said:
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Click to expand...
Click to collapse
Yes. You can see the exact way that each governor works, but that's pretty much the case with ONDEMAND.

convolution said:
CM7 has an OC daemon, right?
Click to expand...
Click to collapse
No, there is no background process (daemon) controlling the cpu min/max.
It only applies the settings at boot, aside from that, it does nothing.
on our devices, there are three (main) files that effect the cpu overclocking:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
writing a value to these files will make the cpu do what you want. (which is what the CM7 controls do)
You can still use SetCPU if you want... all it does is write the values to these files & the kernel handles the rest.
For example, it can be a slightly more convenient method of cranking up the max frequency if you are about to play a particularly cpu intensive game.
I also find SetCPU handy to do a quick check on the "time in state" & "memory" stats
If you want to use the SetCPU profiles, then, as OriginalGabriel pointed out, it could lead to slightly increased battery usage as SetCPU has to remain running in the background monitoring the variables.
If you don't use the profiles, then SetCPU won't consume any battery.
virtuous_oc, andrev_oc & ilwt_oc are a background process (daemon) that react to a change in screen state & write their defined settings to the above mentioned files.
The difference:
SetCPU runs in Android userspace & has to wait for the android system to send out a broadcast intent that the screen has been turned on/off before it can react & write the values to the files mentioned above.
The OC daemons do not run in userspace & detect the change in screen state at a kernel level... they will have written the values to the files well before the intent gets broadcast.
convolution said:
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Because the only reason I have setcpu is to set the profile so it goes to 500/200 mhz screen off...
Click to expand...
Click to collapse
The governor controls how the cpu steps up or down the available frequencies based on the current load.
Each of the governors use a slightly different algorithm in how the cpu steps up or down. (within Max & Min as specified by scaling_max_freq & scaling_min_freq)
The well known governors from the mainline Linux kernel:
Ondemand: at the onset of load, jumps straight to max frequency & then steps down through the frequency table.
Conservative: steps up through the frequencies & back down.
Performance: this governor just keeps the cpu at scaling_max_freq & doesn't scale down
Powersave: this keeps the cpu at scaling_min_freq & doesn't scale up
Also, there are a number of governors that have come about from the Android community, I don't have the time right now to write about all the others that I know of... but can do at a later stage if it helps?
The important thing to note, is that unless you device is staying awake when the screen turns off, the screen off profiles are somewhat pointless, as the cpu effectively gets turned off.
Sorry bout the wall of text... am at work & typed it out in a bit of a hurry... hope it all makes sense

Its not needed but u can use it
Sent from my HTC Vision using xda premium

[Q] Calk's Preset Profiles to save battery question?

Notes about Battery Saver script
Can be used with kernels that have init.d support
It completely eliminates the need for an application to set CPU speeds or profiles
Easily customizable if you use a text editor(scripts located in /system/etc/init.d)
It will set Max CPU speed to 500MHz & Min CPU speed to 200MHz when a sleep
If SetCPU, Overclock Widget, Android Overclock or QuickClock Advanced Overclock are detected, the script is ignored, so it will not affect them
Preset profiles are:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
And just an FYI, even at 800MHz, the phone still operates very well & smooth but the battery saving are the real benefit
Click to expand...
Click to collapse
Does this mean that if I don't use Set CPU or any app that undervolt it, the phone will AUTOMATICALLY drop the CPU speed according to my battery level:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
Another word, it will automatically drop CPU speed to 800 MHZ when my battery level is 35-0% in order to save battery?

It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.

Drumrocker said:
It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.
Click to expand...
Click to collapse
So if I am not doing CPU intensive stuff and just play simple games, email, web surfing phone call, then I am not going to see battery improvement since my CPU probably don't ramp past 800MHZ anyway when I am just doing simple stuff.?

Calk's ROM undervolts the CPU at all speeds so that in itself should help a little with battery life. But you are correct, if you are not doing CPU intensive tasks the CPU probably isn't spending much time at the higher speeds.
There is an app called CPUSpy which shows how much time the CPU has spent in each frequency state.

Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.

Let me research setcpu and play around with it. Thanks again for the quick answers.

clamknuckle said:
Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.
Click to expand...
Click to collapse
The way Calkulin's rom scripts are setup, setcpu gets reset on every reboot, even if you have it set to boot settings. The scripts installed will still take priority and the old rules apply, just to let you know. So you would have to set setcpu every boot for it to work, that or remove the scripts.
Sent from my SPH-D710 using xda premium

Team era... Does the same idea apply to the blazer 2.0 battery saving script? or does tegrak break it?
Sent from my SPH-D710 using xda premium

I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.

I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.

mindgrind said:
I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.
Click to expand...
Click to collapse
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium

Era, what's your suggestion for keeping the battery saving scripts running and getting a 1500 ish over clock when needed... something that can do both without having to physically change setcpu everytime. I basically want to permanently over clock to 1.5 and still save as much battery as possible when i have the screen off or it is charging. Idk if setcpu profiles work on this phone because i know they did not work correctly on the galaxy s. And one final question... what voltages do u run at what speeds on the "desperado" kernel to undervolt efficiently?
Sent from my SPH-D710 using xda premium

TeamERA said:
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
ERA. I wasn't looking to say that you were wrong in any way shape or form. I would be interested to know how you seen this as I am still in the beginning phases of learning the android system. I do plan on writing my own kernal/roms but I was actually sharing what my logical thought process would have been given the apps and system info I had avail.
I have a little ways to go in understanding the structure and FS of droid. Time is everyones enemy. Thanks for the correction again!

I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.

I'm currently running Calkulin's rom v2.5, and even at 41% battery I notice the cpu still hits 1.2 Ghz. Is his script activated by default or am I overlooking something? I also have nothing like setcpu installed.