has anyone else seen issues with setCPU after changing the scaling once or twice? Last night i had gone from 1.1 to 1.3 then back down to 1.0 for tests and after i told it to clock to 1.0 setCPU said that it was running at 2.6...which makes no sense at all. Is this just some UI bug, or something else?
Correct me if I'm wrong, but how can you run voltage above the max vsel and how can your min clock speed be something that isn't a setting in your scaling?echo 70 > /proc/overclock/max_vsel
echo 2000000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 48 > /proc/overclock/mpu_opps
echo 4 2000000000 OVER9000!!!!!!!!! > /proc/overclock/mpu_opps
echo 0 2000000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table
note: plz don't try actually running that...
Correct me if I'm wrong, but how can you run voltage above the max vsel and how can your min clock speed be something that isn't a setting in your scaling?
Here are my settings (thanks to thefamousmoe). I have had them running for about 2 hours now. It survived a couple rounds of Tank Recon 3d.
echo 65 > /proc/overclock/max_vsel
echo 1225000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1225000000 65 > /proc/overclock/mpu_opps
echo 0 1225000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table
1686 on Quadrent. Going to leave it like this for a few days and see how it does.
Once you make changes to the setscaling if you move the max, min sliders in setCPU it seems to make things change to the correct values.
The Pandora Birds Test. Can you pass it?
Have you tried clearing cache and killing tasks before running the script? Might help a little bitIs there any hope for our "release day" X's going over 1.15 or is that all we can hope to get? Mine turtles bad or completely locks up with anything over that.
Post up your valuesdidnt work for me. the highest i got to work for me is 1.12ghz and thats it. does it have to be a certain voltage for each level or can i over shoot the voltage and have it work still?
I'm a newbie! When I run SetCPU, my max shows 1000000 and my min shows 300000. My Quadrant scores range from mid 1200's to high 1400's before overclocking. I followed your instructions to the letter. I overclocked my max to 1250000/60, saved the settings and clicked "execute". After overclocking, I'm getting the same type of results. I noticed in your instructions you didn't mention anything about the "Run Instructions". When I tried to follow those instructions on Better Terminal Emulator, I get an error that says "No such file or directory/#".
Am I doing something wrong? if so, what? BTW, I am on Droid X with 2.2 OTA, Rooted and Deodexed (I think Deodexed).
Please Help!!!
I'm having an issue, and it's making me wonder if I've done something wrong.
Yesterday, when I first started messing with all of this, I was just trying to undervolt. It seemed like that was working when I would get reboots for setting the voltage too low. When I'd fire up SetCPU, I could see the speeds changing back and forth (between 300 and 1000).
Today, I decided to try overclocking, but no matter what I do, the speed seems locked at 1000. It doesn't scale, and even if I set the max to 1300 and try to lock it at that with SetCPU, it still stays at 1000.
Any ideas?
not sure if it will make a difference but just curious weather you were streaming pandora through 3G or on Wi-Fi?
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.