I posted this issue on the official issues page but it was deleted because apparently nobody else in the entire community (Google Code) has this problem after it being posted for only 5 min. SetCPU is freezing my tablet on startup right after the message "SetCPU has been granted Super User Permissions". I had o/c'd to 1.512 ghz not even the full o/c but this keeps happening. I was finally able to uninstall setCPU and no further issues. Has this happened to anybody else?
I had a problem where it would freeze right after setcpu received SU permissions. Turned I I fixed it by changing my min to anything but 432mhz... I only had a few seconds to switch the settings on boot before setcpu would lock up.
I've had the problem, set settings at boot cause of the freeze and restart. I'm going to try a different program. It would be nice to see smartass as an option also
Sent from my LG-VM670 using Tapatalk
I had to completely wipe and reflash the alpha. It froze even after disabling setcpu
I unchecked the "set on boot" which seems to have fixed for now but did have to reinstall due to other so-called "fixes" I have found to be useless in "other" forums.
sent from my HP Touchpad powered by CyanogenMod 7.1 alpha
Your not alone...I had the same issue with Set CPU. I just have to leave the "Set at Boot" unchecked...and thus manually set it each time I reboot. but, hey...that's to be expected for an alpha version.
Related
I'm running KaosFroyo v36 and I can't get the overclock widget to move past 710. If I set it to 768 and save it I get the "Superuser access granted to overclock widget" and it says the change was successful but it stays at 710 no matter what. I have my min set at 245760 and max set at 768000 for the "screen on" frequency.
If I go back in, it shows the slider back at 710400 again. This is the first rom I've used that has overclocking in it so maybe I've just done something wrong.
Try SetCPU: http://forum.xda-developers.com/showthread.php?t=505419
I had the same exact issue. The developer emailed me saying he isn't sure what the problem is caused by.
I switched back to setcpu.
Ok I installed setcpu and set to 768 and set to autoconfigure at boot. A few moments later the phone hard locked. I rebooted but couldn't get to setcpu before it locked again.
Thank goodness I was able to use my l33t linux skills.
I booted into recovery, accessed the phone with adb and found the preferences xml file for setcpu and renamed it.
After rebooting all was good.
Stonent said:
Ok I installed setcpu and set to 768 and set to autoconfigure at boot. A few moments later the phone hard locked. I rebooted but couldn't get to setcpu before it locked again.
Thank goodness I was able to use my l33t linux skills.
I booted into recovery, accessed the phone with adb and found the preferences xml file for setcpu and renamed it.
After rebooting all was good.
Click to expand...
Click to collapse
Don't use the set on boot setting till you fond out what speed your device can handle. I did the same I set it to 800'somthing and ran for a min then locked up and could not keep the phone booted long enough to change settings so I had to remove it through adb. Each device seems to be stable at different speeds. Mine is stable at 768 or 780 but I only ran at 748 and now I don't use it at all. I can't find a difference between those speeds and 710 , so if I decide to use it again it would be to underclock profiles fr better battery life.. ohh and overclock widget if set to a speed your phone can't handle than it will drop speed
Sent from my KaosFroyo-v37 using XDA App
Pretty simple problems, and I am not that tech illiterate, so I am really puzzled.
First problem that is occurring is 'Set frequencies at boot". I have it set for Medium voltage, 1.15GHz. The problem is that when I reboot to implement the settings, upon reboot it goes back to stock settings, of max 1GHz. I have the slot checked for "apply on boot" feature selected. My profile settings, for screen off, battery<, are always saved.
Second problem is it sometimes keeps my profile of "screen off" on when I unlock the phone, and the profile is at at max and min of 300 MHz, so it's not like there isn't enough juice there to update it upon re-awaking. When I plug in the phone, it goes to the profile of charge/full, which is what I though it would be at when unplugged until the second profile of battery life kicks in.
Mine does the same. You need to create a Screen On profile.
Try redoing the set frequencies on reboot and see if that helps. If not try uninstalling and reinstalling the app.
Sent from my DROID2
I have never experienced a true on boot set frequency. I always thought it would set that when my phone started up when I hit the power button and make it boot faster and what not but its for when the android os starts up it should implement the set frequency...when you first "log in" to android and the phone starts booting all the apps, the oc program you have installed is waiting in line to be opened and allowed by super user to run so it might take a few minutes for your frequency to be implemented. If that's not working at all even after a minute or two then un-check the option for set at boot and restart the phone, then check it and restart the phone and see if it has changed.
Sent from my DROID2 using XDA App
Still having problems. Sometimes the problem is that it is not switching from the Screen off profile when the screen is on. Sometimes it is on the right profile but will not throttle up the CPU until I mess around in SetCPU a little (or else it takes a long time). It seems like after I get the "SetCPU has root rights" message it will start working, but sometimes it is not needed.
any1 elese
Paulb787 said:
Still having problems. Sometimes the problem is that it is not switching from the Screen off profile when the screen is on. Sometimes it is on the right profile but will not throttle up the CPU until I mess around in SetCPU a little (or else it takes a long time). It seems like after I get the "SetCPU has root rights" message it will start working, but sometimes it is not needed.
any1 elese
Click to expand...
Click to collapse
Not having problems myself. Curious, what governor are you using? You shouldn't use profiles with some governors.
I know tons of people use setcpu and and it works for them.......but the few times I have tried it, I always have problems with it. I use os monitor to change gov settings and usually do not mess with anything else.
What kernel and also what was said previously. Having a screen off profile can conflict with the goveners already optimized routine causing lag. Using smartass I don't set any profiles just my Max frequency and governor.
Sent from my ADR6400L using XDA App
Paulb787 said:
Still having problems. Sometimes the problem is that it is not switching from the Screen off profile when the screen is on. Sometimes it is on the right profile but will not throttle up the CPU until I mess around in SetCPU a little (or else it takes a long time). It seems like after I get the "SetCPU has root rights" message it will start working, but sometimes it is not needed.
any1 elese
Click to expand...
Click to collapse
I had these issues with most of the BFS Kernels. So I am using Adynalyn's 4.4.2 and have had no issues at all.
I just put cyanogenmod on my g-tablet and it keeps shutting off after only 10 or 15 mins of inactivity. Anyone else experience this or know how to fix this? I tried lowering the CPU speed to 1.2 gHz but that didn't seem to fix the issue either...
I am having the same problem and just installed the .41 kernel to see if it helps. I'll let you know if it helps.
Sent from my GTablet using Tapatalk
Ok cool thanks!
Check you WiFi settings. I noticed the same problem when I first loaded my tab. Someone recommended trying this... Go into settings>wireless & networks>WiFi settings, then press menu>advanced. Change the WiFi sleep policy to never.
Since doing this I haven't noticed the problem. Doesn't seem to affect battery life so I'm going to stick with the change.
I tried .41, .42, and .39 and the problem continued. I tried the "never sleep" setting you described and so far it seems to be working. Thank you so much! I am reinstalling .42 with this setting hoping its all good.
Sent from my GTablet using Tapatalk
I've noticed this happens more when I use the power button to put the tab to sleep. If I use "go to sleep" from the power controls in the notification drop-down I don't seem to have a problem. But I haven't really let it sleep for a while afterwards,.
I noticed this happening AFTER I messed with the CPU settings in the CyanogenMod/Performance settings section. I didn't see it happen again after I reset it to defaults.
hi
i have been running my streak at 1.19ghz for a week, with no probs, but today for about 40 mins the device was kind of stuttering, i checked my set cpu , and it was showing as constantly at at 1.19gz.
i have set cpu app, on demand frequency, min 245, max 1190, it was stuck running at max until i turned on my data and done a few google searches, went back to the setcpu app, and it was back to normal, at 245, only rising when i touch the screen
any ideas what it was???
anzhar said:
. . . .
any ideas what it was???
Click to expand...
Click to collapse
Since it stopped when you turned on data I would speculate that an app was repeatedly trying to access the 'net or sync. You need to figure out which app wasn't playing nice (and nuke it). Of course it will be an app that you really need/want.