The file is attached to the bottom of his post, and I will attach it here as well.
unzip the files and put them both on your sdcard, then run the following in adb or terminal emulator:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/overclock.ko /system/lib/modules/
cp /sdcard/overclock.sh /system/bin/
chmod 644 /system/lib/modules/overclock.ko
chmod 755 /system/bin/overclock.sh
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
That sets up everything you need to overclock. To use overclock, you just run the command:
overclock.sh frequencyvoltage
with 1000000 being the default freq and 66 being the default voltage
It is highly recommended to not go over 96 for the voltage parameter!
so an example:
Code:
su
overclock.sh 1100000 66
results in attempting to overclock to 1.1GHz on stock voltage (this is stable for me).
The mod is wiped clean after every reboot, so it will need to be run again. If you want to wipe it while the phone is running, to say, try another frequency, you can do the following:
Code:
su
busybox rmmod overclock
and proceed to overclock with different parameters.
Device(s): Droid X (rooted)
Previous: LG Ally, LG Voyager
Thanks: 69
Thanked 98 Times in 77 Posts
lol maybe this is the source of the odd benchmarking results that some people were seeing. There was one or two 1.1GHz test results on there. It confused a couple people into making a thread somewhere around here about it.
Glad to see this done. I'll have to try it and post back with my results once I have my phone.
Just ran 1.15GHz/72, gave me a 9.82 Linpack and only 1280 quadrant, before the OC I was steady running 1325 to 1365. I wish I could reboot without losing it, just to see if the score would be any better.
Edit: A quick question, do we need to run everything over again after a reboot, or just "overclock.sh..."?
Last edited by irishpride; August 8th, 2010 at 06:56 PM.
some one needs to get a big break-through in speed like they with the galaxy s because stock the x kills the s but with some simple mods the galaxy s can run a 1500 on quadrant we need to be the first to 2000
Here is my setscaling.sh file that'll use low voltages across the board and is stable for me. Also uses 1.15ghz @ 34 vsel (stock is 66!) and swaps the 800mhz clock for 900mhz since that is more logical.
Drop it in /system/bin, chmod to 755. To load the kernel module do "insmod /system/lib/modules/overclock.ko" first, then execute the below setscaling.sh script.
Device(s): Droid X w/Root & OC -HTC Droid Eris (EOL)
Thanks: 73
Thanked 154 Times in 79 Posts
Quote:
Originally Posted by Hilbe
Here is my setscaling.sh file that'll use low voltages across the board and is stable for me. Also uses 1.15ghz @ 34 vsel (stock is 66!) and swaps the 800mhz clock for 900mhz since that is more logical.
Drop it in /system/bin, chmod to 755. To load the kernel module do "insmod /system/lib/modules/overclock.ko" first, then execute the below setscaling.sh script.
Here is my setscaling.sh file that'll use low voltages across the board and is stable for me. Also uses 1.15ghz @ 34 vsel (stock is 66!) and swaps the 800mhz clock for 900mhz since that is more logical.
Drop it in /system/bin, chmod to 755. To load the kernel module do "insmod /system/lib/modules/overclock.ko" first, then execute the below setscaling.sh script.
Thanks for this. Unfortunately, I can't seem to get it to work. I can overclock using commands like:
su
overclock.sh 1150000 36
but I can't seem to get your setscaling file going. I copied it to /system/bin, chmod 755'd it, I think. (I changed permissions with Root Explorer so that User has R/W/E, Group has R/E, and Other has R/E). Next, I run:
su
insmod /system/lib/modules/overclock.ko
and it gets me back to #
then I try to run:
setscaling.sh
and I get:
setscaling.shUX
: not found
:not found
setscaling.sh: 6: Syntax error: ")" unexpected
I'm uncertain what I'm doing wrong.
EDIT: Fixed. Instead of unzipping setscaling.sh.zip, I'd just renamed it to setscaling.sh. Worked now. Thanks.
Last edited by humungus; August 9th, 2010 at 01:55 AM.
For some strange reason, my Droid just slows down to a crawl if I set the OC higher than 1.1ghz, regardless of the voltage, though admittedly, the highest I tried was 75 for 1.2GHz.
But I modified Hilbe's setscaling script to do 1.1 at 34 and everything has been stable so far (cross my fingers).
Got a pretty nice Quadrant bench too, and it survived an Asphalt HD gaming session.
For some strange reason, my Droid just slows down to a crawl if I set the OC higher than 1.1ghz, regardless of the voltage, though admittedly, the highest I tried was 75 for 1.2GHz.
But I modified Hilbe's setscaling script to do 1.1 at 34 and everything has been stable so far (cross my fingers).
Got a pretty nice Quadrant bench too, and it survived an Asphalt HD gaming session.
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.
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.
Last edited by kastleberg; August 9th, 2010 at 10:55 AM.
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?
__________________
"I know I was born and I know that I'll die, the in-between is mine."
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
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:
Last edited by Airmaxx23; August 9th, 2010 at 11:24 AM.
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?
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?
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?
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?
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
The Following User Says Thank You to D13 For This Useful Post:
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.
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.
The Following 2 Users Say Thank You to Hilbe For This Useful Post:
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.
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?
Last edited by Dulaney22; August 9th, 2010 at 01:59 PM.
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.
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.
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.
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...
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.
Last edited by Airmaxx23; August 9th, 2010 at 04:17 PM.
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)
Motorola DROID X is an Android powered smartphone with a 1GHz processor, huge 4.3-inch display with 480x854 pixels resolution, 8-megapixel camera with 720p motion video capture and many other features. It's the newest addition to Motorola... Read More
[How-To] Overclock your Droid X
