I'm running smoked glass 5.1 with chevy kernel. It was working fine all day yesterday, and today I took my phone off the charger and noticed it was at 550mhz. I opened up setcpu, set it to 1ghz, and as soon as I exited it went back down to 550mhz. I can't figure it out. My profiles aren't making it go down to 550.
I just read this from alldroid.org. This might have something to do with that.
"Re: [ROM.tgz] Smoked Glass v5.0.1 **BIG Update 02/27**
Curious if anyone else has noticed this or not. I've been running the 5.0.1 ROM since Satur Night and everything has been just fine. This am I noticed there was an update to setCPU which I downloaded. However once I installed version 1.5.0 of setCPU there was an issue.
Here is the skinny I use profiles and have mine set to 550Mhz for charging. Before putting it on the charger it was running at 1.1Ghz, put it on the desktop charger and it clocked down to the 550Mhz like it should. However once taken off the charger it would not longer clock back to 1.1Ghz. I tried a battery pull, uninstalling and reinstalling, changed modes in setCPU and then back to autoDetect and nothing, it is stuck at 550Mhz. Low and behold got ticked off and uninstalled it again to reinstall my backup copy of version 1.4.6 of setCPU. Now everything is back to normal changing clock speeds when it gets plugged in, and then clocks back up once unplugged. Curious if anyone else is having an issue with the clock speeds. If so what version of setCPU are you using atm as we may need to report it to the dev of setCPU but before doing so I wanted to see if others are having any issue or not.'
Had the same issue and I mailed the dev of SetCPU. I told him what was going on and this was his response:
The newest update to SetCPU improved i/o efficiency so that refreshing the speed often does not cause the CPU to ramp up to higher speeds like it did before. If the green indicators on the top right indicate the max/min you have set after a refresh, then everything is working properly.'
Hope that helps."
Last edited by bastosero; 03-01-2010 at 10:24 AM.
The problem is that green indicators in the top right are showing the wrong value. So it is indeed getting stuck on the charging profile. Even the notification shows it charging when its not.