• 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)

Anyone looking to undervolt, doesnt look like you can get as low as 2.1 I have had automatic restarts on a couple tries right after running setscaling.sh.

EDIT: Dropped it down 5 for now to test. When I cat mpu_opps after running everything I get

vseld=62 vsel=51 for 10000000
vseld=58 vsel=45 for 8000000
vseld=48 vsel=33 for 6000000
vseld=33 vsel=22 for 3000000
I dont remember it appearing like that, should the vseld be the same or is that the original?
 
Upvote 0
Just tried the one above with -5

echo 51 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 600000000 33 > /proc/overclock/mpu_opps
echo 3 800000000 45 > /proc/overclock/mpu_opps
echo 4 1000000000 51 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

I initially for my 2.1 had


echo 34 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 500000000 26 > /proc/overclock/mpu_opps
echo 3 800000000 30 > /proc/overclock/mpu_opps
echo 4 1000000000 34 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 500000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

Which ran fine
 
Upvote 0
Code:
echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /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

tried using this, no luck.. locks and reboots on me.. too extreme on the voltages?
 
Upvote 0
Code:
echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /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

tried using this, no luck.. locks and reboots on me.. too extreme on the voltages?

i've had one lock up so far on this setup
anyone else got something stable?
 
Upvote 0
What volts are you trying, I'm about to try

22,33,43,47

I'm at 25,35,45,50 atm let me know if that works out for you. I am playing around to see if this is stable enough before I drop again.

First one didn't work = instant reboot

Tried 25, 32, 43, 48 = instant reboot

I'm going to play around with it a little more tomorrow, I'm done for tonight.

Maybe I am doing something wrong, I am trying to go to 1.1GHz with the lower voltages. Someone mind posting what my setscaling.sh should look like
 
Upvote 0
I'm looking forward to hearing how effective undervolting will effect battery life. I just hope people don't undervolt, then lay their X on their night stand asleep for a week and then report back that they're getting CrAzY battery life!?!?!

Don't worry once I get mine stable I will give real world results, I can't leave my phone alone for a day even if I tried, LOL
 
Upvote 0
Code:
echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /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

tried using this, no luck.. locks and reboots on me.. too extreme on the voltages?


You have to play around with things a bit. Settings are not always going to transfer from one DX to the next. It was discussed extensively under 2.1, that there is a good degree of variation from chip2chip/phone2phone as to what these things can handle. You must become one with your X! LOL

Seriously, though... Your freeze/crash/reboots could be from any of the 4 frequency slots having too low a voltage for the frequency it is set to. It is good to use the first page in SetCPU to lock your processor at a certain speed by setting both sliders to the same frequency or by using the performance governor, and test out each of your frequencies with stress test.

I'd also suggest starting from setscaling100.sh and working your way down in voltage, in increments of 2... get a crash... do the previous stress test tip, and find out which slot crashed you.. just keep honing in on what works.. might take some time getting it all the way there...
 
Upvote 0
anybody notice any big changes with the OC?

Yes, its surprising what a few hundred Mhz will do. CPU intensive apps are running much faster. Like Titanium Backup for example, it flies through backing up/restoring batch apps.

I <3 OC and the people who say its not needed must not know how to do it :)

I'm kidding of course, but I just dont understand why some ppl are so against overclocking. Its always made my phones faster and perform better.
 
Upvote 0
I'm running @ 1.2Ghz with 68 vsel. didnt change anything else.

Thats a pretty big jump on the vsel, sounds like it will drain your battery pretty quick if you use your phone a lot.

Edit: Gonna giver her a whirl, I have the extendo so I'm not too worried. Just be nice if we could find something super stable, so far I haven't even came close.

Edit: -- Nevermind no dice going to try more at 1.1 @62 everything else the same seems good for tonight. (boo)
 
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