CPU speed freakout

[ohgoditsgoingtobreak]

So I was running the latest aospcmod, had the CPU set to 480/122 for weeks now. Last night while listening to Pandora the audio became very choppy, and progressively became worse over 2 minutes or so, so I opened system panel lite and it was showing the Max speed on the cpu was 122MHz... I rebooted it and it ran fine for the first five minutes, then while running the browser it did the same thing. I flashed my most recent nand backup with thunderc, and the problem persisted, so I did a full wipe and flashed harmonica on... same issue... so i restored the entire phone to stock with a
Asadullah's wonderful provram, recovery and all...its still dropping the CPU to 122MHz after 5 minutes of being powered on, even after a complete wipe and different Roms. What the heck is going on? Is this hardware failure? Malware? Gah this is frustrating...

 

[Dk564]

Do you reload the same apps via Titanium backup? If so, Google your most recently downloaded apps (Say, within a week of the problem occurring), and see if they have any Malware associated with them.

Google has just recently removed several infected apps from android market in the past week.

 

[rockneo]

Well first off you should be running 480/122 and secondly you shouldn't be running 480/122, that's your issue if, for some dumb reason youre running 480 set it to 480/480

Sent from my Optimus V

 

[Kreatur3]

Well first off you should be running 480/122 and secondly you shouldn't be running 480/122, that's your issue if, for some dumb reason youre running 480 set it to 480/480

Sent from my Optimus V

Thirdly you did a complete contradiction and made no sense beyond your insult lol.

What he meant to say was "it's advised not to run it below 400 as it will actually eat up more of your battery." Strange but true there is a thread about battery life and overclocking.

 

[ohgoditsgoingtobreak]

Well first off you should be running 480/122 and secondly you shouldn't be running 480/122, that's your issue if, for some dumb reason youre running 480 set it to 480/480

Sent from my Optimus V

What died and crawled up your ass? Re-read then re-write your post, then maybe ill talk to you.

 

[ohgoditsgoingtobreak]

Do you reload the same apps via Titanium backup? If so, Google your most recently downloaded apps (Say, within a week of the problem occurring), and see if they have any Malware associated with them.

Google has just recently removed several infected apps from android market in the past week.

Generally I do, but for troubleshooting purposes I have not used TB, and have left all apps but system panel lite uninstalled. I haven't downloaded anything but AntTek, which turned up clean

 

[ohgoditsgoingtobreak]

Thirdly you did a complete contradiction and made no sense beyond your insult lol.

What he meant to say was "it's advised not to run it below 400 as it will actually eat up more of your battery." Strange but true there is a thread about battery life and overclocking.

Why is the default set to 600/250? Wouldn't setting the minimum the same as max make the system constantly throttle high?

 

[Kreatur3]

Why is the default set to 600/250? Wouldn't setting the minimum the same as max make the system constantly throttle high?

It's weird and I don't totally understand it, I just read the hard work of others. Mmarz, I believe, did the full work up on this issue. All of the roms that come pre-overclocked start at like 480/600 or something. You should read that thread or at least skim it to get more information on it. You can also look at the kernels for pica and bb and see what they are oc'ed at by defaut. They know a lot about the technicalities and are worth listening to.

 

[rockneo]

My post meant, 122/480 is backwards, so it should be 480/122 and then the second part states that you shouldn't be running below 480, you're welcome.

 

[ohgoditsgoingtobreak]

My post meant, 122/480 is backwards, so it should be 480/122 and then the second part states that you shouldn't be running below 480, you're welcome.

That makes more sense. I had it set "properly", and it was running fine at 480 for weeks, however this problem arose when I wasn't even touching the device. Even after complete wipes and Rom/kernel changes the problem still persists. Which makes zero sense since changing the kernel alone should have made the processor speed go back to stock 600MHz, right? And even if just a kernel change wouldn't do the trick, a total wipe and different ROM completely would have! Do you, or anyone else have proactive advice on this subject?


Nice post, I feel the love

 

[Kreatur3]

Some kernels have over clock on by default so a kernel change can change things.

Sent from my VM670 using Tapatalk

 

[ohgoditsgoingtobreak]

Some kernels have over clock on by default so a kernel change can change things.

Sent from my VM670 using Tapatalk

So the chances of this being hardware failure are now high? I can't believe this happened... well at least it still runs.. god-awfully slow

 

[mmarz]

Wow, what's up with the attitudes up in here? We are talking about a teenager's toy after all. Chill.

Every cpu has an optimal clock speed that gives you the best battery life in the same way ever car has a optimal speed that gives you the best MPG. Go faster or slower and you get worse hr/battery% (MPG). From my tests, the optimal clock speed was near 800 MHz.

For never ending tasks (streaming) it makes no sense to clock faster because you don't finish the task any faster. Like going for a drive to put your kid to sleep, it makes no difference if you go 1 mile or 100 miles. But idling the car in the driveway won't put the kid to sleep. So we cruise at a safe speed. For our phones 480 MHz lets you stream without stuttering. Any slower and the CPU won't keep up and it'll be kicked up to the max speed. If you set the speed too slow, it'll take extra time to complete simple tasks and it'll actually waste more battery. If you didn't have to worry about tasks like streaming, you could set min and max to ~800 MHz and get the best battery life.

When there are no tasks to be performed, the CPU actually goes to sleep and the clock speed doesn't matter. It is for times that it needs to check your SMS's or send a few packets that a sub 480 clock speed will eat up your battery.

Your problem is not a hardware failure. It is probably a bug in software (AOSP's CM7 is an alpha release, meant only for testing). You can try re-flashing it or switch to a stable Froyo rom. Either way, under clocking will only cause you problems.

 

[ohgoditsgoingtobreak]

Wow, what's up with the attitudes up in here? We are talking about a teenager's toy after all. Chill.

Every cpu has an optimal clock speed that gives you the best battery life in the same way ever car has a optimal speed that gives you the best MPG. Go faster or slower and you get worse hr/battery% (MPG). From my tests, the optimal clock speed was near 800 MHz.

For never ending tasks (streaming) it makes no sense to clock faster because you don't finish the task any faster. Like going for a drive to put your kid to sleep, it makes no difference if you go 1 mile or 100 miles. But idling the car in the driveway won't put the kid to sleep. So we cruise at a safe speed. For our phones 480 MHz lets you stream without stuttering. Any slower and the CPU won't keep up and it'll be kicked up to the max speed. If you set the speed too slow, it'll take extra time to complete simple tasks and it'll actually waste more battery. If you didn't have to worry about tasks like streaming, you could set min and max to ~800 MHz and get the best battery life.

When there are no tasks to be performed, the CPU actually goes to sleep and the clock speed doesn't matter. It is for times that it needs to check your SMS's or send a few packets that a sub 480 clock speed will eat up your battery.

Your problem is not a hardware failure. It is probably a bug in software (AOSP's CM7 is an alpha release, meant only for testing). You can try re-flashing it or switch to a stable Froyo rom. Either way, under clocking will only cause you problems.

Ah, a post from "The Man" himself! An honor... thanks for the info, I was just finishing up part three of your research! I have flashed a different Rom twice now, harmonica, and the stock Rom, neither overclocmed, nor undedclocked, and am still experiencing the issue with it dropping to 122. I have tried flashing a re-downloaded 06012011 aospcmod, and tried altering CPU speed with no avail. getprop system.cpufreq.restored = true in adb... not sure why the phone is stuck so low

 

[mmarz]

Ah, a post from "The Man" himself! An honor... thanks for the info, I was just finishing up part three of your research! I have flashed a different Rom twice now, harmonica, and the stock Rom, neither overclocmed, nor undedclocked, and am still experiencing the issue with it dropping to 122. I have tried flashing a re-downloaded 06012011 aospcmod, and tried altering CPU speed with no avail. getprop system.cpufreq.restored = true in adb... not sure why the phone is stuck so low

Try flashing the stock rom and kernel. See if a non-overclockable kernel helps. Are you installing anything after you install these roms? See if the problem happens with nothing but a virgin rom. If it does, maybe it is a hardware issue.

 

[ohgoditsgoingtobreak]

Try flashing the stock rom and kernel. See if a non-overclockable kernel helps. Are you installing anything after you install these roms? See if the problem happens with nothing but a virgin rom. If it does, maybe it is a hardware issue.

I mentioned in the OP that I restored the stock Rom and recovery. I only install system panel lite after flashing, but only after I see the major visual lag that occurs roughly 5 minutes after startup, just to check resource usage and processor speed.

 

[KSmithInNY]

Thread cleaned. Stay on topic.

 

[kylekushman]

sounds like superuser wasn't granting root to your cpu speed app right away...

 

[rockneo]

Is the cpu app on sd? Or, if you were running aosp, try the settings to change the clock speeds. then back to setcpu.

 

[ohgoditsgoingtobreak]

Is the cpu app on sd? Or, if you were running aosp, try the settings to change the clock speeds. then back to setcpu.

I was running aosp, and did all changes to the clock speed with it in the performance settings screen. I've flashed it back on, and in the same place I changed the settings, it says max 600, and min 250, I have ammended them to 600/600, 806/806 480/480 and even 122/122 then back to 600/250, (interactive governor was always selected, if that helps any) still no resolution. Next I'm going to wipe absolutely everything after an sd de-partition, format and forced partition, and do the good ol'e fastboot method. If this doesn't work, I'll admit defeat to hardware failure...