Database Users

[Q] SetCPU causes phone to freeze when used to underclock when screen is off

So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?

rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off

rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.

Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G

I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App

It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.

rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience

murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.

I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.

I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?

same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.

What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.

I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.

mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.

jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.

I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max

CPU isn't scaling - stuck on 100%

Hi all, not sure how to address this, but my battery's been a little crappy lately. I downloaded SETCPU after not using it for ages, and I noticed when i set it that my CPU seemed stuck on the fastest speed. Downloaded SeeCPU and confirmed. So though my min-max is set at 245-986, it's always on 986.
I'm using Kushdeck’s latest w/ the stock kernel (which is the cyanogen kernel), and I even went so far as to wipe all data and re-flash everything...still no luck. Any ideas on how to proceed?

Did you disable the perf-lock in setcpu?
We're comin from a pure power source.

Yes, perflock is disabled. I can lower the cpu speed, but it wont scale. So the default is 998, and typically I'd set the min/max at 245/998. I noticed that the CPU was always at 998, it never scaled down. Now I have the min/max set at 768/245 and it's always on 768. If perflock were disabled I thought I wouldn't be able to change the speed at all, though I may be wrong there...I also tried the perf unlocker in setcpu and it reports that it is already unlocked.
At this point I wiped data, cache, and Dalvik. Re-flashed the rom (deck's aosp rom) , stock kernel, practically no apps installed except setcpu and seePU to monitor usage.

Oh and the governor is the default, I think interactive...

Try another governor like conservative and see. After that I'd try another kernel or download the stock one again in case something is buggered in yours
Sent from my PC36100 using XDA Premium App

Thanks already tried a different governor, tried a tiamat kernel, then said screw it and reinstalled the rom from scratch. Still having the same issue. I may go back to a sense rom to see of that makes a difference.

Hi, I know and understand what problem you're having. I had this on my desire. Run a ruu or flash a pb99img. The problem only happens on non sense roms. This is the only solution to make non sense roms work. Just try it. Good luck!
Hit the thanks button!
Sent from my HTC Desire using XDA App

I ended up flashing back to Myn 2.2 (which is Sense) and it started working again. Thanks!

CPU isn't scaling, not affecting battery life?

Here's an issue I just noticed late last night. My CPU seems to be stuck at max. I've tried different governors, wiped cache/dalvik and reflashed kernel and rom. I also killed all running apps to see if an app was causing it, to no avail.
Here's what really stumps me, my battery life seems fantastic. Not what I'd expect if my CPU is running at 100%. Could there be an issue with detecting CPU speed? As I mentioned before, trying different governors doesn't help with scaling but I notice when I select "powersave" my CPU jumps from max to the minimum value and stays there, still not scaling.
Before someone mentions I did search before posting. Went through the threads, tried the suggestions within and still have the problem. Hence why I'm posting here now.
Am I overlooking something? Any help will be appreciated, thanks!
Edit: My current rom and kernel are in my sig.

so are you monitoring this via setcpu on Decks?

alaman68 said:
so are you monitoring this via setcpu on Decks?
Click to expand...
Click to collapse
Yes I am, is there a known issue?

My understanding is that having both setcpu and the native CPU performance running will result in some conflict. that is probably the problem, but I don't know how to monitor the scaling with the native performance. so i see what you are trying to do.
I never run setcpu on CM7 or Decks because it is built in, but if the battery life is alright, it would appear the built in takes precedence.

Is there a good way to monitor the CPU without setCPU? Thanks

cesjr02 said:
Is there a good way to monitor the CPU without setCPU? Thanks
Click to expand...
Click to collapse
check out "system panel"
edit: or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency.

Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.

My CPU doesn't scale correctly either. Its either running at MAX, Deep Sleep, or 245mhz. Never does it use the in between frequencies no matter what govenor I use(I have tried them all). I use CPU Spy to check scaling and No Frills CPU to change the governor both are from the market.

cesjr02 said:
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
Click to expand...
Click to collapse
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.

alaman68 said:
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
Click to expand...
Click to collapse
Thanks, says the time spent at 499 MHz is 92.51%. I don't think underclocking is the issue. If I overclock to 1113MHz it will peg there as well. Seems to only go 100% when screen is on however according to the system panel app. I'll try your suggestion in (#2) and report back.

Tried reflashing the rom without wiping. Still have the same issue. So odd. I'll try a different kernel just to see if that helps, but I'd hate to part with my 3.3.7 LEE kernel.
Last thing I can think of is doing a full wipe, but I'd like to avoid that if I can.

Definitely experiencing the problem with other kernels. I'm out of ideas.

Did you try tiamat 4.1.0? I'm using it now and the battery life is right there with 3.3.7.
Sent from my PC36100 using XDA App

Did you restore any apps with titanium backup by chance?
Sent from my PC36100 using XDA App

By the way, I appreciate all your help alaman68.
Tiamat 4.1.0 was the other kernel I tried. No luck. Also I've never used titanium backup to restore apps. I'm stumped as to why my CPU won't scale anymore. The Android System seems to be using as much as I allow it.

Trying, you could try a sense rom for a day and check the scaling for a benchmark.
Is there anything else you are running? Undervolting, v6... Anything else?

Not undervolting as my phone never liked it. Nor running V6 or any other scripts either. I'll try flashing a sense rom, see if I have the same problem there. Or else, think doing a full wipe and reflash everything would help?

if all else fails, a clean flash won't hurt. Even get a new download. Gotta ask, did everything properly? you using amon_ra recovery? did you download any new apps when that started happening?

I may just have to. I suppose there's always a chance I made a mistake somewhere, but I've been at this rooting/flashing thing for a long while. Thing is, everything was fine up until I noticed it last night.
I'll do a clean install. I can always nand restore if it doesn't work. (Save me the time to set up everything.)
I'll report back

Did a clean install and guess what, my CPU is scaling again! There must have been a conflict somewhere. Thanks again alaman68 for all your help and suggestions. Sometimes these phones get gremlins I tell ya.

Overclock Cyanogen settings

I have rooted abdroid 2.3.4 with cyanogen 7 and in the settings there is one that i can change the maximum value to cpu...Now is at 998....what value above that is the safest to choose with out the phone have any problem???

depends which rom it is
some can go up to 1.5 and some cant

Can also depend on the phone, I have 2 hd2s, one chuggs along nicely at 1075mhz, the other gives random slowdowns / hangs (4-5 a week,not lots but enough to be a pain) at any setting above 921mhz. Same rom,same installed apps, same data.

Well here are the Phone Info
Model
HTC HD2
Andorid
2.3.4
.......
15.42.50.11U_2.15.50.14
Kernel
2.6.32.15_tytung_r10-gbdfeaac
Mod Version
CyanogenMod 7-05252011-NIGHTLY DESIRE
GRJ22

Anyone?
Sent from my HTC HD2 using XDA App

The best thing to do is scale up gradually, try each step above 998. OC then try it for 24hours, then try a step up and try it for 24 hours and so on. Do not check set at boot though just in case you pick a speed that causes problems.

What can go wrong???How do i see that it cant support a number??We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????

What can go wrong???
It coukd stop booting and require a hard reset/backup restore.
How do i see that it cant support a number??
It will start to give force closes, hang, reboot, feel sluggish..
We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
Do a cwm backup and just try it, worst case scenario is it doesn't boot and you have to restore.

ntisco said:
What can go wrong???How do i see that it cant support a number??We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
Click to expand...
Click to collapse
I would guess that the majority of users are overclocked. I, for example, am running my phone smoothly at 1.2 GHz without problems, but to be honest I scarcely notice the difference with overclocking. Dorimanx's kernel with 1.61 GHz overclock didn't really perform any better than Tytung r14 at 1.2 GHz.
Just do as the others said and try it out whilst making sure to uncheck 'set on boot', but I think any speed should really be fine.
I don't know what the general opinion is on this (some devs say it isn't a good app) but use setCPU in order to create profiles if you want, thus being able to reduce your standby battery drain and stuff like that

In the quandra the info of the phone whrites that the cpu is up to 1190mhz and know is at 998.Is this true?Can it go that much?
If so we can put it at 1113 that its safe?
I know that i ask again and again but i dont want the phone to lose or damage

Youre best bet would be to download setCPU and try different clock speeds . the thing about setCPU though is it has a stress test . So after you set a speed . you can run the stress test to test if its too high a value or if you are safe to run at that speed . just dont tick the box that says "apply at boot"

My phone (currently Dorimanx ROM) is stable at 1536MHz. On Cyanogen it was similar. On 1612 it had freezen for a few times while watching a flash video on youtube. Set it to 1,4GHz, and it should work fine. Phone will not damage, data too. Just as they written above, do not click apply at boot.
And make stress test for more than 10 mins, because I have done it for 10 mins, and as I written, it had freezed during YT watching.

The topest that it has is 1190..that is the last option !!!I put it at 1113 for one day know and i made a profile to go 573 when i close the screen.
Tomorow i try the next option antil 1190 ...and we will see

Tytung r10? Why not upgrade to another Kernel?
I think that's the core issue. Dorimanx kernels i.e. can be clocked solid to 1.2ghz

Oh, I've completly forgotten. I have used Dorimanx kernel with Cyanogen. But it doesn't let you reinstall rom from settings (Factory reset). You need to reinstall rom from zip or restore backup in CWM. On 1190 it will work stable for ever

[Q] Nexus 7 CPU running high

I tried to search for a thread relating to this but couldn't find anything, if anyone knows of one a link would be appreciated.
OK, so I flashed Motleys kernel 2 days ago. Everything was running fine, I had it OC'd to 1.6 and it was super fast and smooth. I had set the governor to "on-demand" to try and save some battery life(over "performance"), and also because it seemed like the CPU would run at full 1.6 constantly if it was set to performance (I don't know if that's how it should be or not, but this isn't the issue). I used System Tuner to OC it like he recommended in his thread.
Yesterday I set it to performance to run some benchmarks, and then continued using it on performance to see how it felt. About an hour and a half later I also started messing with my home screen and apps and ended up accidentally using Quick Boot to take me to the bootloader. After powering it back on I checked System Tuner to set the governor and once I did I noticed, according to System Tuner, that 2-4 of the cores are running at full 1.6 and the CPU usage is from 25%-100% even though I have nothing open.
I flashed my recovery via Clockworkmod Recovery, Motleys kernel is now replaced by the stock kernel, however I'm still having the same issue, but just at 1.3. Any idea why the CPU is running so high, for apparently no reason?
.....
OK, so I just checked System Tuner again and the CPU doesn't seem to be doing as bad now, but it's still all over the place and I don't have anything else open. Here are the times:
Offline - 77%
340MHz -11%
475Mhz 1%
1.2Ghz - 5%
1.3Ghz - 1%
Compared to yesterday when it had said 1.3GHz 79% or something like that (and was running nothing but system tuner).
So, yeah, that does seem a lot better but one thing remains; the CPU usage still jumps up to almost 50% and once again, I am running nothing but System Tuner, so something still doesn't feel right.

I think ondemand governor is causing the CPU to shoot up so often and quickly.(That's all I can think of.) I always use interactive and it's usually the preferred governor. Ondemand is more for people who play lots of games and they need the extra boost. If you game a lot then I guess you should still to it.
Sent from my Nexus 4 using Tapatalk 2