Droid X successfully overclocked

[Hilbe]

Similar to the overclock.sh provided earlier, just edit setscaling.sh in a text editor. Drop it in /system/bin and chmod 755. Here is mine with undervolted (compared to stock) all frequencies, plus changed 800->900mhz slot. Use at your own risk of course, running stable on mine.

echo 34 > /proc/overclock/max_vsel
echo 1150000 > /proc/overclock/max_rate
echo 1 300000000 20 > /proc/overclock/mpu_opps
echo 2 600000000 26 > /proc/overclock/mpu_opps
echo 3 900000000 30 > /proc/overclock/mpu_opps
echo 4 1150000000 34 > /proc/overclock/mpu_opps
echo 0 1150000 > /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

 

[mgf]

ill try setclock.sh

running 1.15ghz at 36vsel results in a reboot after a little bit

 

[Hilbe]

ill try setclock.sh

running 1.15ghz at 36vsel results in a reboot after a little bit

I'm at 34, no reboot yet.

 

[mgf]

ill try setclock.sh

running 1.15ghz at 36vsel results in a reboot after a little bit

I'm at 34, no reboot yet.

mine rebooted when i was getting the other files.

so to use setclock.sh, i put it in /system/bin, then run it after i runeoverclock.sh? but do i just run setclock.sh?

 

[Hilbe]

Elkay,

Is there any way to verify that these voltages are being used? I keep checking the mpu_opps and they show up there. It just seems unrealistic. I'm currently stable at 1.15ghz and 30 vsel (< 1/2 stock @ 1ghz) according to the overclock mpu_opps. This just doesn't seem right, but I will continue.

setscaling.sh:


echo 30 > /proc/overclock/max_vsel
echo 1150000 > /proc/overclock/max_rate
echo 1 300000000 18 > /proc/overclock/mpu_opps
echo 2 600000000 22 > /proc/overclock/mpu_opps
echo 3 900000000 26 > /proc/overclock/mpu_opps
echo 4 1150000000 30 > /proc/overclock/mpu_opps
echo 0 1150000 > /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


mpu_opps:
# cat mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=30
mpu_opps[3] rate=900000000 opp_id=3 vsel=26
mpu_opps[2] rate=600000000 opp_id=2 vsel=22
mpu_opps[1] rate=300000000 opp_id=1 vsel=18

 

[Hilbe]

mine rebooted when i was getting the other files.

so to use setclock.sh, i put it in /system/bin, then run it after i runeoverclock.sh? but do i just run setclock.sh?

Copy all scripts to /system/bin, chmod 755.

The quickest way to get your settings is to just load the kernel module, then load your scales. Here is how I do it after a reboot:

insmod /system/lib/modules/overclock.ko
setscaling.sh

You only have to load the overclock.ko file once, then you can do setclock.sh over and over testing frequencies and voltages.

 

[mgf]

mine rebooted when i was getting the other files.

so to use setclock.sh, i put it in /system/bin, then run it after i runeoverclock.sh? but do i just run setclock.sh?

Copy all scripts to /system/bin, chmod 755.

The quickest way to get your settings is to just load the kernel module, then load your scales. Here is how I do it after a reboot:

insmod /system/lib/modules/overclock.ko
setscaling.sh

You only have to load the overclock.ko file once, then you can do setclock.sh over and over testing frequencies and voltages.

I just did
su
Setscaling.sh
And that worked. I have 900mhz in setCPU. Now can i add more frequencies in setCPU by adding more line to setscaling.sh?

 

[Hilbe]

We haven't been successful in adding slots. I think we are stuck with 4 slots.

My setscaling.sh with 1.15ghz/30 vsel was unstable after all. I got a crash on my browser and then a random reboot. I'm going to start going back up a bit with the values.

Testing this setscaling.sh now:


echo 34 > /proc/overclock/max_vsel
echo 1150000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 600000000 26 > /proc/overclock/mpu_opps
echo 3 900000000 30 > /proc/overclock/mpu_opps
echo 4 1150000000 34 > /proc/overclock/mpu_opps
echo 0 1150000 > /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

 

[blackrain311]

I still cant get anything over 1.15ghz to work or at least to not be slower.

 

[PJ.]

I still cant get anything over 1.15ghz to work or at least to not be slower.

Same. I even got a reboot at 1.15 earlier, so I'm just gonna stick with 1.1 until later.

 

[macatk89]

This all seems rather disappointing... I was hoping this phone would be able to approach 1.5ghz... if y'all are having trouble getting to 1.2ghz, that sucks

 

[Hilbe]

I still cant get anything over 1.15ghz to work or at least to not be slower.

Same. I even got a reboot at 1.15 earlier, so I'm just gonna stick with 1.1 until later.

What vsel value caused the reboot with 1.15?

 

[Hilbe]

I've been running vsel 34 with 1.15ghz for most of the evening using the setscaling.sh I posted on post #113. This seems to be pretty solid with no reboots or browser crashes. I'm anxious to see what kind of battery life we get when using a 1.15ghz / 34 compared to the stock 1.0ghz / 66.

 

[PJ.]

I still cant get anything over 1.15ghz to work or at least to not be slower.

Same. I even got a reboot at 1.15 earlier, so I'm just gonna stick with 1.1 until later.

What vsel value caused the reboot with 1.15?

Sorry man, you're not speaking my language. I just followed the instructions from another site and only change the frequency and voltage values.

So whatever stock vsel value is...lol

 

[blackrain311]

1.15ghz @ 36vsel works perfect but ive been running 1.16ghz @ 48vsel for the last hour and it scores higher on quadrant but still getting 9.6 mflops on linpack. anything else is just as if it were running at 300mhz.