Droid X successfully overclocked

[Elkay]

I've attached another archive with two additional scripts that you install the same way as you installed overclock.sh into the /system/bin folder. The first, setclock.sh, will allow you to change the clock speed and voltage without uninstalling the kernel module every time. You may need to use SetCPU to force the new clock to take effect. The second is a sample script showing how you can modify the entire scaling of the processor. This script doesn't have any parameters, it just execute as it is defined. Feel free to adjust the values as you see fit, or modify the script to take parameters for whichever values you want to be variable. Keep in mind that you should edit any of these scripts ON THE DEVICE, as windows and Linux use different line breaks and the script will not work if you edit in Windows without fixing the carriage returns afterward on the phone.

I've found that when you overclock it too much, it does go into "turtle" mode. Funny thing is when this happens, sometimes SetCPU will show you running *double* the clock rate you selected. Didn't hurt anything *yet*, it was just painfully slow to remove the kernel module. In fact, it was easier to just reboot the phone. I found it was more related to the voltage than the clock rate. It was when I hit this roadblock that I decided not to go any higher myself. Use caution if you want to mess around within and beyond this region.

Ive also noticed that turning on WiFi after OC at higher speeds seems to crash the phone. Any ideas?

Also. The Setscaling.sh script seems to give me a "cannot create" error for almost everything. You say execute as defined as in go into terminal and run the script as is right? (like #setscaling.sh)

You need to run overclock.sh first.

[Hilbe]

You can't just run setscaling.sh. You have to load the kernel module first by running "insmod /system/lib/modules/overclock.ko" then run setscaling.

I still haven't achieved stability yet. Pretty touchy. I haven't found a super stable mhz/voltage yet :/

[Hilbe]

As soon as I type 1200000 into the overclock it does the safe mode of sorts. I am able to clock to 1150000 just fine (reboots of course). I'm trying to figure out the voltage for 1150000 that doesn't result in random reboots.

[Hilbe]

Anyone care to post their stable values? I'm currently semi-stable at 1150000 / 72.

Linpacks in the low to mid 9's (9.3 to 9.4) on average.

[Hilbe]

Elkay,

Have you created a startup script to load the module and settings at boot? Feeling pretty good at 1150000 / 72.

No random reboots yet in 10 minutes, knock on wood.

[hijackerjack]

1225000 75

We need to figure out how to overclock the GPU

[Hilbe]

Here is my speed / linpack.

[Hilbe]

Elkay,

I noticed one thing with the voltages. When I use your overclock.sh to set max_rate and max_vsel, it doesn't appear to set the max_vsel. I have to use the setclock.sh to get it to take the value. See below.


$ su
# overclock.sh 1150000 72
# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=66
mpu_opps[3] rate=800000000 opp_id=3 vsel=57
mpu_opps[2] rate=600000000 opp_id=2 vsel=44
mpu_opps[1] rate=300000000 opp_id=1 vsel=32
# setclock.sh 1150000 72
# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=72
mpu_opps[3] rate=800000000 opp_id=3 vsel=57
mpu_opps[2] rate=600000000 opp_id=2 vsel=44
mpu_opps[1] rate=300000000 opp_id=1 vsel=32

[Elkay]

Elkay,

I noticed one thing with the voltages. When I use your overclock.sh to set max_rate and max_vsel, it doesn't appear to set the max_vsel. I have to use the setclock.sh to get it to take the value. See below.


$ su
# overclock.sh 1150000 72
# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=66
mpu_opps[3] rate=800000000 opp_id=3 vsel=57
mpu_opps[2] rate=600000000 opp_id=2 vsel=44
mpu_opps[1] rate=300000000 opp_id=1 vsel=32
# setclock.sh 1150000 72
# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=72
mpu_opps[3] rate=800000000 opp_id=3 vsel=57
mpu_opps[2] rate=600000000 opp_id=2 vsel=44
mpu_opps[1] rate=300000000 opp_id=1 vsel=32

I'm not seeing this problem. Strange. Are you using SetCPU?

[hijackerjack]

Im also seeing that. Which was probably why 1.235 ghz wasn't working. I just set the vsel to 80 using setclock.sh and it worked. Also, the setscale seems to only give a list of scaling to use but doesn't actually adjust frequencies. When i used setscale, my phone was stuck at 1ghz.

Sent from my DROIDX using Tapatalk