Database Users

Underclocking Problems

Currently running VillainROM 10.3.0 (with Sense UI)
Does anyone get problems regularly on the slightest of underclocking (using SetCPU)?
Min at 245:
- Alarm wont turn off (only snoozes)
- Clock on Lock screen wont update
Min at 128:
- Music player becomes stuttery, took a few minutes for screen to power on to turn off music
Noone else seems to have mentioned it ?
Am I doing something wrong?
And its a bit worrying considering so many custom ROMs come pre-clocked.

Totally a hardware issue. Your phone just can't cope with the lower speeds. Not all can.
Mine will do 19mhz on sleep and wake immediately etc. but most others won't
Villainrom should default to the stock settings unless you install something like setcpu and define oc settings.
Not sure about other roms but I guess they do similar unless otherwise stated.

ah cheers.
i knew that some phones couldnt reach a particular Max clock speed, but didnt know it was a similar case with the Min clock speed too

You should try Cronos Droid. I am having the exact same problem as you on all OC'ed 2.1 roms, except Cronos Droid.
My settings on Cronos:
Screen on: 710 mhz
Screen off: 160 mhz

[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

SGS continually restarting itself

I've got a problem with my I9000, several times throughout the day it will randomly restart itself. It will be quite happily sat idle in my pocket not doing anything, and then suddenly I hear the boot-up sound from my pocket. It's just started doing this since Thursday or Friday I think it was, had nearly 700 hours uptime on it (699 hours ) and then I noticed from my SeePU notification that something was hammering the processor, running it at >90% for more than 10 minutes. Couldn't see any programs running in the background so decided to restart the phone. This is one my problem started.
It's running stock JPY with Voodoo Advance kernal, it was overclocked to 1.2GHz and had some undervolting from 800MHz down, this had been stable for all of those 699 hours, but I disabled the OC and UV yesterday to see if it was that causing the trouble, but even with it disabled the phone's still been restarting.
What would be really great is if there is some kind of crash log for Android (something similar to the Windows Event Viewer) so I can see what's causing this. Does anyone know if such a thing exists, and if it does how I might go about accessing it?
Failing that, anyone know why my phone would suddenly start restarting itself now?

had pretty much the same issue, different kernal and rom... but had an OV/UV that for the most part was stable...
then today was continually restarting.....
solution?
changed CPU scheduler to noop
changed CPU Governor to conservative (Galaxy S cpu default configuration)
Now not restarting at all... and that's with a 1.3GHz overclock... running several benchmarks and no undervolting at all.
I'll let you know if it starts acting up... but interesting that this at least fixed it for me.

Stupid thing has restarted itself twice this morning. This is ridiculous.
I've just set the schedular to noop, can't see an option to set the governor though. Will see if that sorts it.
Would really appreciate knowing if there's a log file or something though

If it was a PC you would say its overheating .
jje

Found an app on the market called OS Monitor that shows all the running processes and what load they're putting on the CPU, it also shows the dmesg and logcat log files.
Thankfully my phone hasn't restarted itself since changing the schedular, but if it does I should hopefully now be able to find out why

quick answer. Reflash the phone .

I guess reflashing and removing some dangerous apps will be good for you phone.

Hmm, well looks like it's given up on restarting itself and is just plain turning itself off now.
Looks like I'm going to have to reflash the stock kernal and see if that fixes it

CM7 and Phiremod 6.3 issue

I got my wife a Nook Color a while back, and installed CM 7.0 n it. It ran fine, and I had it OC'ed at 1100. Since then, I've installed 7.0.3, which gave me a wifi error. I decided to run Phiremod 6.3 (running great), but I have a strange issue.
When i go into performance settings to overclock, it freezes immediately after choosing any speed. I can't even change the governor from on demand to interactive without it freezing. It locks up so that I have to turn it off and back on again. No luck in changing the CPU speed. I never had issues before running at 1000 on previous dalingrin kernels, not sure why its acting up. I did do a complete wipe of system before installing.
Can i try using SetCPU or something similar instead, or should I be looking at something else?

Try setcpu like you said. If u have the time tho, why not wipe the whole thing and try installing phirrmod again?

Tried it again, with the same result. Not sure what's going on there, but I'll try SetCPU and report back. Thanks for the reply.

RampageRR said:
Tried it again, with the same result. Not sure what's going on there, but I'll try SetCPU and report back. Thanks for the reply.
Click to expand...
Click to collapse
So how did Setcpu work out for you?

RampageRR said:
I got my wife a Nook Color a while back, and installed CM 7.0 n it. It ran fine, and I had it OC'ed at 1100. Since then, I've installed 7.0.3, which gave me a wifi error. I decided to run Phiremod 6.3 (running great), but I have a strange issue.
When i go into performance settings to overclock, it freezes immediately after choosing any speed. I can't even change the governor from on demand to interactive without it freezing. It locks up so that I have to turn it off and back on again. No luck in changing the CPU speed. I never had issues before running at 1000 on previous dalingrin kernels, not sure why its acting up. I did do a complete wipe of system before installing.
Can i try using SetCPU or something similar instead, or should I be looking at something else?
Click to expand...
Click to collapse
I had to do a complete wipe of all data...Phiremod is running awesomely

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!