• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Droid X 2.2 Overclock (Kernel Module w/Instructions)

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?

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.
 
Upvote 0
snap20101021_192945.png
 
Upvote 0
finally got 1.2 to run stable on my phone! been 24 hours with no reboots, stress test ran for 15 minutes, and 6 quadrant scores run (3 back to back, 4 hour break, 3 more back to back) averaging 1625. Im happy now. I had a bit*h of a time getting anything above 1.15 to run stable. IDK why...
havent noticed any HUGE changes obviously but pandora and scanner radio stream smoother and it seems like websites are loading a lot faster too (might just be my imagination though)
 
Upvote 0
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?
 
Upvote 0
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?

That setscaling was a joke.

On a testing sidenote....

I was able to run 1350Mhz w/ 66vsel through a setcpu stress test for over an hour. General use proved stable, and so did multiple quadrants.

HOWEVER

Running Pandora & Angry Birds at the same time eventually caused reboot. This is consistently the case, and I'm now working to find a stable 1350Mhz setting. I just wanted to report this, since I was pretty surprised. For really testing stability, then, I think I may recommend Pandora + Angry Birds.

So...

The Pandora Birds Test. Can you pass it?
 
Upvote 0
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.


Last night went well with this setup. Left on the charger over night. Woke up fine this morning. Then about 7:00 this morning got my first lock-up. Had a few more so far this morning.... I guess my phone doesn't like 1.225. Oh well brought it back to 1.2.
 
Upvote 0
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.

That's the problem though, it's not doing that. The white text at the top with the current clock speed seems to almost freeze after doing this. The numbers below do change when i change the sliders, but the "current" number at the top stays locked no matter what scaling mode i select and no matter what i set the sliders to (i.e. i could set both sliders to 400mhz and the top would still say 1300 or 1000 or whatever it was after doing a few OCs)
 
Upvote 0
This 1.35ghz chart has been stable for me over the last 2 days, could probably reduce voltage in a few places, but I am happy with the bat life of this compared to stock.

echo 67 > /proc/overclock/max_vsel

echo 1350000 > /proc/overclock/max_rate
echo 1 300000000 20 > /proc/overclock/mpu_opps
echo 2 600000000 33 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 4 1350000000 67 > /proc/overclock/mpu_opps
echo 0 1350000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
 
Upvote 0
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!!!

When I said use the code, I meant both run and install. Sorry, should have been more clear on that. Well, I haven't gotten that error so not sure what it means. I would say just run the install again and make sure that your using setscalling.sh/setscaling100.sh for every command (where needed). If you mix them, then you will get errors. Oh, if can put out .99c then I would recommend getting JRummy16's app called Droid X/2 Overclock. Haven't used it yet but JRummy makes good products and this seems to be feature packed.
 
Upvote 0
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?
 
Upvote 0
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?

Open your task killer, kill setcpu, run your overclock script, open setcpu
 
Upvote 0

BEST TECH IN 2023

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.

Smartphones