Root [How-To] Overclock your Droid X

[kastleberg]

Everything was going good, then i tried a few different parameters and got this:

# overclock.sh 1175000 77
insmod: init_module '/system/lib/modules/overclock.ko' failed (File exists)

Any ideas?

Edit: sooooo... i think what happened is that a reboot i thought i saw may not have been a rebbot? Maybe im going crazy. I got a quadrant of 1425 with 1175000 70 and so wanted to screenshot it. When tried to run quadrant with drocap ready i got what i thought was a reboot. Figured okay different settings but the old ones appear still in place.

 

[D13]

Everything was going good, then i tried a few different parameters and got this:

# overclock.sh 1175000 77
insmod: init_module '/system/lib/modules/overclock.ko' failed (File exists)

Any ideas?

Do
busybox rmmod overclock
Its in the op

 

[Airmaxx23]

We noticed on the other forums, if you set your speed/voltage too high it'll go into a safe mode (turtle speed) of sorts. Basically making the phone so slow it is unusable. I was getting 0.5 linpacks when in turtle mode!

I tested my phone in 10mhz increments all the way up to 1.2 ghz, and the highest I could get non-turtle was 1160mhz. However, I did get reboots at 1160mhz though and did not have any reboots at 1150mhz.

Would you mind sharing what your settings for "SetCPU" are?

 

[D13]

Everything was going good, then i tried a few different parameters and got this:

# overclock.sh 1175000 77
insmod: init_module '/system/lib/modules/overclock.ko' failed (File exists)

Any ideas?

Edit: sooooo... i think what happened is that a reboot i thought i saw may not have been a rebbot? Maybe im going crazy. I got a quadrant of 1425 with 1175000 70 and so wanted to screenshot it. When tried to run quadrant with drocap ready i got what i thought was a reboot. Figured okay different settings but the old ones appear still in place.

You can "refresh" setcpu by re-detecting the speeds

 

[Airmaxx23]

So what's with the inconsistent Quadrant scores? I usually get around 1280-1300 but once in a while I'll get something in the 800-900 range. Then there is this result from a few minutes ago:

 

[Paycer]

Try putting the phone in the fridge for a bit before overclocking and running another test. DD

I'm kidding, obviously. Awesome score Airmaxx.

 

[Airmaxx23]

Try putting the phone in the fridge for a bit before overclocking and running another test. DD

I'm kidding, obviously. Awesome score Airmaxx.

That's the funny thing, I haven't even done any over-clocking yet. I just find it odd that the scores can vary so much.

 

[D13]

stable at 1.2 ghz with standard voltage
edit: all seems well at 1.2 ghz with 34 voltage

 

[humungus]

Am I the only one who's a little skeptical here? I mean, it seems odd that we can overclock to 1.15GHz using almost _half_ the stock voltage. If this is true, why the hell would Motorola use such a high voltage? Is there any way to verify that the voltages we code in are actually getting enforced?

 

[Airmaxx23]

I have 1 quick question, the instruction say that it will be wiped clean after a reboot. Do all of the commands need to be re-entered or just the one that sets the values?

 

[D13]

I have 1 quick question, the instruction say that it will be wiped clean after a reboot. Do all of the commands need to be re-entered or just the one that sets the values?

nope just
overclock.sh frequency voltage

 

[kastleberg]

I have 1 quick question, the instruction say that it will be wiped clean after a reboot. Do all of the commands need to be re-entered or just the one that sets the values?

Just do the overclock.sh and the values again.

Now, about the voltages, do i necessarily need the other file in here? I am running 1.15 right now at 40. It seems to bw going smoothly for now. What exactly would the other zip file be needed for?

 

[D13]

Just do the overclock.sh and the values again.

Now, about the voltages, do i necessarily need the other file in here? I am running 1.15 right now at 40. It seems to bw going smoothly for now. What exactly would the other zip file be needed for?

One thing it does is change the 800 mhz value to 900 so for you it would go
300,600,900,1150
Not sure what else it does

 

[Hilbe]

As mentioned on the other forum, I was having issues getting the overclock.sh to set the voltages at load time. You need to review your /proc/overclock/mpu_opps after running it. setclock.sh seemed to work through as well as the setscaling.sh.

 

[kastleberg]

I believe I have the setscaling.sh going properly. I am new to all the command line stuff so I'm not sure if I got it right. Is there any way to tell?

 

[Hilbe]

I believe I have the setscaling.sh going properly. I am new to all the command line stuff so I'm not sure if I got it right. Is there any way to tell?

To tell if your frequencies/voltages are set right, do:

cat /proc/overclock/mpu_opps


I used these results to discover overclock.sh (or the kernel module itself) wasn't working right. Try it out yourselves...see if voltages don't get set on a fresh boot.

 

[D13]

To tell if your frequencies/voltages are set right, do:

cat /proc/overclock/mpu_opps


I used these results to discover overclock.sh (or the kernel module itself) wasn't working right. Try it out yourselves...see if voltages don't get set on a fresh boot.

So does this mean the OC will last through a boot or am I misinterpreting it.

 

[Dulaney22]

I'm slightly confused by some of this. I'm getting good scores just from rooting and using freezing with TiBackup. I've also employed autostarts and tweaked those settings. The highest result I've seen is 1308, but consistently post 1260-1280.

Being new to all this, do I correctly understand that I can run a higher clock speed at less voltage, which I assume would yield better battery life?

 

[Hilbe]

So does this mean the OC will last through a boot or am I misinterpreting it.

It will not until we edit the startup scripts to load the kernel module and run setscaling.sh. I want to run it for a few days before I make any startup script changes that could cause my phone not to boot.

 

[D13]

It will not until we edit the startup scripts to load the kernel module and run setscaling.sh. I want to run it for a few days before I make any startup script changes that could cause my phone not to boot.

Awesome sounds good

 

[Hilbe]

I'm slightly confused by some of this. I'm getting good scores just from rooting and using freezing with TiBackup. I've also employed autostarts and tweaked those settings. The highest result I've seen is 1308, but consistently post 1260-1280.

Being new to all this, do I correctly understand that I can run a higher clock speed at less voltage, which I assume would yield better battery life?

I have gotten some high 1300s in Quadrant and 9.5s in Linpack on 1.15ghz @ 34 vsel. The stock settings are 1.0ghz @ 66 vsel. So we're using substantially less voltage. The setscaling.sh script I posted above lowers the voltages across the board. I haven't been running overclocked long enough to know how good/bad it impacts battery, but supposedly lower voltages = less battery use.

 

[Airmaxx23]

I ran the cat /proc/overclock/mpu_opps command and the voltage did not set to the value that I wanted. What can be done to get it to save?

 

[Hilbe]

I ran the cat /proc/overclock/mpu_opps command and the voltage did not set to the value that I wanted. What can be done to get it to save?

setscaling.sh and setclock.sh have worked for me. setscaling.sh is the preferred since you can set the vsel for all frequencies. I posted my 1.15 ghz setscaling.sh many posts above...

 

[Airmaxx23]

setscaling.sh and setclock.sh have worked for me. setscaling.sh is the preferred since you can set the vsel for all frequencies. I posted my 1.15 ghz setscaling.sh many posts above...

What would be the commands for using both? This command line stuff is new to me so I apologize in advance.

 

[Hilbe]

What would be the commands for using both? This command line stuff is new to me so I'm apologize in advance.

setscaling.sh takes no parameters
setclock.sh mhz vsel

So just "setscaling.sh" and "setclock.sh 1150000 34" for example. One note, both assume overclock.ko has been loaded. So after a reboot, you must do it as follows:

insmod /system/lib/modules/overclock.ko (loads kernel module here)
setscaling.sh (or your setclock.sh)