Related
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
Just as the title says, but here's some more details.
I have my cpu set to 1.1Ghz during the normal day 245Mhz min.
I have my widget on my homescreen and a custom profile set for when the screen is off for 368max and 245min.
When I turn my screen on and unlock it, it lags on my screen and says 368 max, then it jumps to the 1.1 and everything is fine.
It seems to lag there longer than it used to, has anyone else noticed this problem.
I used to have Pershoots Kernel on 6.1, do you think if I put Pershoots Kernel back on it will eliminate the lag and switch to 1.1 faster than it does now?
Just some thoughts and advise would be great, thanks guys.
Sent from my HTC Vision using XDA App
I would ditch setCPU and use CM's built in overclocking settings. set your clock speed to whatever you like and use the ondemand governor.
your screen wake lag will almost certainly disappear and I bet your battery life doesn't change a bit. you can play around with it, of course, and find what's best, but I have found that since CM introduced built-in overclocking, it is more functional to use it instead of setCPU. my battery life hasn't changed a bit, partly because when the phone is in an idle state it is underclocked by default, and also because I don't have setCPU constantly having to think to make changes to my clock speeds and governors based on what profiles I've set up.
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!
Since upgrading to KitKat, my phone will reboot (not instantly - after some time) whenever I use any governor other than interactive.
This is with any 4.4.2 ROM, even after full wipes..
Anyone else noticed this with KitKat? If you want to test - please change your governor to ondemand - use your phone normally (may take a while) but after some time the device will freeze and reboot.
Is this normal? Upon restarting the governor will revert back to interactive
Any advice will be much appreciated folks.
Mine does the exact same thing with ondemand governor no matter what rom I'm on. I thought my phone is just messed up. You are the first person I've heard has the same problem. I really don't know why its like that?
Sent from my SM-N9005 using XDA Premium 4 mobile app
same here
I am currently running 4.4.2 stock with BeastMode kernel from freeza and the ondemand governor causes stutter and a reboot after a few minutes of using the device.
As I recall, this also happened on the stock kernel.. the interactive governor appears to be more stable, but it does seem to take a greater toll on the battery.
No matter what voltahe settings(+/- 100mv) I use with the ondemand I keep getting the same results.. weird
By chance is knox included in these roms?
I had the same problem on stock where phone rebooted constantly, tried everything until I fully uninstalled Knox and it has since stopped.
I always have my CPU governor set to ondemand.
I am running stock on my note but have deleted everything concerning knox on system/app. The problem still persists...
Hmm that's really odd.... have you tried using link2sd and searching for knox just in case it left anything behind? Providing you are rooted.
Sent from my SM-N900 using XDA Free mobile app
I just tried that and no knox to be found... I do not know if it has to do with the "silicon lottery" in which OC and OV doesn't play well with some governors. .
Anyway I stuck with interactive and it has been solid so far... my major concern now is fixing that persistent "Cell Standby" battery drain that persists even on airplane mode.
Guys, currently when i try to use ANY custom rom, N or MM... i cant control properly the maximum frequency of the cpu, this happens is ANY rom, i repeat xD
mpdecision / and another hotplugs turned off, but still cant control it.
same with custom kernels, disable hotplug, select maximum frequency about 1200-1400 it works for some seconds, but then it starts to scale down to 800mhz, and stay in the range between 1094mhz and 800 mhz. the device gets laggy as hell, to the point where i cant play poke-go or even other games, and chatting/browsing becomes a terrible expecience.
already tried to turn on "performance mode" on battery menu, and even tried to use hotplugs, but with no sucess.
if any of you had this trouble and managed to fix it, plz help me :crying:
I have this too, it's horrible, it makes the device so much worse
igorinolw said:
Guys, currently when i try to use ANY custom rom, N or MM... i cant control properly the maximum frequency of the cpu, this happens is ANY rom, i repeat xD
mpdecision / and another hotplugs turned off, but still cant control it.
same with custom kernels, disable hotplug, select maximum frequency about 1200-1400 it works for some seconds, but then it starts to scale down to 800mhz, and stay in the range between 1094mhz and 800 mhz. the device gets laggy as hell, to the point where i cant play poke-go or even other games, and chatting/browsing becomes a terrible expecience.
already tried to turn on "performance mode" on battery menu, and even tried to use hotplugs, but with no sucess.
if any of you had this trouble and managed to fix it, plz help me :crying:
Click to expand...
Click to collapse
Using late autumm kernel with L speed... You can install it from play store and set it to performance mode
I also face this problem a lot