• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [How-To] Overclock your Droid X

Could I just comment here about how awesome and helpful this thread and everyone in it have been? Off topic, but it seems to me that there has been quite a bit of assistance from various people to get this all done. Props to everyone in here. This is what the Android community is all about. :D
 
kastleberg said:
Could I just comment here about how awesome and helpful this thread and everyone in it have been? Off topic, but it seems to me that there has been quite a bit of assistance from various people to get this all done. Props to everyone in here. This is what the Android community is all about. :D
Click to expand...

Yeah it really was quite an adventure:D
 
Should I start a new thread with my guide. I PM'ed Hilbe asking him if he rather post it, or should I just wait for his response. Because there is no way someone is going to find that guide
 
I have 1 quick question. Prior to making setscale run on start up I was using root explorer to go in and edit/change the values of the setscale.sh file and then running the 2 commands again. What would I have to after editing the file now?
 
Airmaxx23 said:
I have 1 quick question. Prior to making setscale run on start up I was using root explorer to go in and edit/change the values of the setscale.sh file and then running the 2 commands again. What would I have to after editing the file now?
Click to expand...

Yeah you can just use root explorer to change the values. I was running 1.2 ghz with 34 but I was getting reboots so I changed it in root explorer rebooted and everything was right
 
droider13 said:
Yeah you can just use root explorer to change the values. I was running 1.2 ghz with 34 but I was getting reboots so I changed it in root explorer rebooted and everything was right
Click to expand...

Great, that's good to know. I wasn't sure if certain commands needed to be entered again or not, it will be nice to just change the values and reboot. Thanks again.
 
Dulaney22 said:
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?

snap20100809_124516.png
Click to expand...

How did you get the stock Android icons with Nextheme?
 
I really appreciate Elkay and Hilbe's efforts with this.

My notes..

I find a 400@23/700@28/900@33/1100@40 scheme to be most useful/stable for myself. 300 is horribly laggy and 400 seems to bring the responsiveness to a useful level. I think voltage requirements will vary for everyone as far as stability goes. My CPU seems to not take the higher clocking as well as some of you have been experiencing, so I think my setting should be stable for most. 900 was a little flaky for me at @30, so I gave it a little more juice.

I had no install-recovery.sh like other have mentioned... I just copied init.goldfish.sh in RE, deleted everything but the top "#!/system/bin/sh" line, added the lines to call my scripts and renamed it to install-recovery.sh. I call my scripts ocmod.sh and oc.sh... I have an ocx.sh which I edit for testing that i run from terminal, but don't run at startup.

install-recovery.sh seems to be related to OTA updates. That being said, I flashed the .604 SBF and hard wiped my phone, so that is probably why I don't have it. Here is a little more about install-recovery.sh... Definately bootloader related...

What I take from the above link is that an OTA update will create a new install-recovery.sh, wiping out the lines we've added to startup our overclcoking scripts. So we'll need to add those lines back after an OTA update.

Battery life with my settings? I dunno... I'll have to see how it goes...
 
FreeWELL said:
I really appreciate Elkay and Hilbe's efforts with this.

My notes..

I find a 400@23/700@28/900@33/1100@40 scheme to be most useful/stable for myself. 300 is horribly laggy and 400 seems to bring the responsiveness to a useful level. I think voltage requirements will vary for everyone as far as stability goes. My CPU seems to not take the higher clocking as well as some of you have been experiencing, so I think my setting should be stable for most. 900 was a little flaky for me at @30, so I gave it a little more juice.

I had no install-recovery.sh like other have mentioned... I just copied init.goldfish.sh in RE, deleted everything but the top "#!/system/bin/sh" line, added the lines to call my scripts and renamed it to install-recovery.sh. I call my scripts ocmod.sh and oc.sh... I have an ocx.sh which I edit for testing that i run from terminal, but don't run at startup.

install-recovery.sh seems to be related to OTA updates. That being said, I flashed the .604 SBF and hard wiped my phone, so that is probably why I don't have it. Here is a little more about install-recovery.sh... Definately bootloader related...

What I take from the above link is that an OTA update will create a new install-recovery.sh, wiping out the lines we've added to startup our overclcoking scripts. So we'll need to add those lines back after an OTA update.

Battery life with my settings? I dunno... I'll have to see how it goes...
Click to expand...

I took mine to 48 and staggered lower settings but still random reboots. I'm gonna play around some more tonight, but for now I just froze the installrecovery file. As to it, I didn't have it and it doesn't seem to matter if it's there as far as general operation goes. I froze it to set back to standard and everything is just as it was before adding it. Heck, all I did was drop it in and it worked. I don't understand why the system would check for a file that may or may not be present?
 
Others that have created different stable settings should post their setscaling.sh files to help the community. Just my 2 cents.
 
Dulaney22 said:
I took mine to 48 and staggered lower settings but still random reboots. I'm gonna play around some more tonight, but for now I just froze the installrecovery file. As to it, I didn't have it and it doesn't seem to matter if it's there as far as general operation goes. I froze it to set back to standard and everything is just as it was before adding it. Heck, all I did was drop it in and it worked. I don't understand why the system would check for a file that may or may not be present?
Click to expand...

1100@48??? I started with Hilbe's script, and messed around til i got what worked for me. 1100@34 would run for a good bit, but would eventually freeze or reboot on me. 40 has been working so far. I noticed that if I am at a flaky setting and I run SetCPU stress test with my phone viewing in landscape mode, it will just exit before it switches to portrait which is the view mode that stress test runs in. 1100@34 reliably reproduced this phenomena... 1100@40 will reproduce this maybe 1-in-5 runs... But I have not locked up or reboot with that setting(since yesterday)...

As for install-recovery.sh... It really appears to be OTA update related. It checks the status/validity of your recovery image... I added 'echo "i have a recovery image"' into the else statement at the end and ran it from terminal... It spit out:

mtd read matched size 2048 sha 37dc5be28fe8cdeb61eae1347fdccf2e201af07e
i have a recovery image
Click to expand...

I don't believe we need this running every time we boot our phones up. I'll stick with just running my overclock scripts from install-recover.sh for now.
 
FreeWELL said:
1100@48??? I started with Hilbe's script, and messed around til i got what worked for me. 1100@34 would run for a good bit, but would eventually freeze or reboot on me. 40 has been working so far. I noticed that if I am at a flaky setting and I run SetCPU stress test with my phone viewing in landscape mode, it will just exit before it switches to portrait which is the view mode that stress test runs in. 1100@34 reliably reproduced this phenomena... 1100@40 will reproduce this maybe 1-in-5 runs... But I have not locked up or reboot with that setting(since yesterday)...

As for install-recovery.sh... It really appears to be OTA update related. It checks the status/validity of your recovery image... I added 'echo "i have a recovery image"' into the else statement at the end and ran it from terminal... It spit out:



I don't believe we need this running every time we boot our phones up. I'll stick with just running my overclock scripts from install-recover.sh for now.
Click to expand...

Would you suggest a different place to put the commands that works
 
FreeWELL said:
1100@48??? I started with Hilbe's script, and messed around til i got what worked for me. 1100@34 would run for a good bit, but would eventually freeze or reboot on me. 40 has been working so far. I noticed that if I am at a flaky setting and I run SetCPU stress test with my phone viewing in landscape mode, it will just exit before it switches to portrait which is the view mode that stress test runs in. 1100@34 reliably reproduced this phenomena... 1100@40 will reproduce this maybe 1-in-5 runs... But I have not locked up or reboot with that setting(since yesterday)...
Click to expand...

I was running 1150@48. I haven't dropped the clock speed yet, but will try it later. Just like you, these settings will work for a while, but eventually reboot. Oddly enough, the reboots seemed to occur more quickly, on mine, when bumping up the voltage.
 
Hilbe said:
Others that have created different stable settings should post their setscaling.sh files to help the community. Just my 2 cents.
Click to expand...

Agreed... However, we seem to have widely varying tolerances with this CPU. I can't run the setting that work for you, and Dullaney appears not to be able to run what works for me. Maybe we see how things unfurl, and when we get a good reading of where the less OC'able CPU's fall, release a more "nice" setscaling.sh for people to start and work their way UP in Mhz and DOWN in voltage...

Here is my script...

echo 40 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 23 > /proc/overclock/mpu_opps
echo 2 700000000 28 > /proc/overclock/mpu_opps
echo 3 900000000 33 > /proc/overclock/mpu_opps
echo 4 1100000000 40 > /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
Click to expand...
 
Dulaney22 said:
I was running 1150@48. I haven't dropped the clock speed yet, but will try it later. Just like you, these settings will work for a while, but eventually reboot. Oddly enough, the reboots seemed to occur more quickly, on mine, when bumping up the voltage.
Click to expand...

You should not have to go that high voltage. Not all processors are created equal. As I suggested earlier, cut your losses and go for 1.1ghz
 
Dulaney22 said:
I was running 1150@48. I haven't dropped the clock speed yet, but will try it later. Just like you, these settings will work for a while, but eventually reboot. Oddly enough, the reboots seemed to occur more quickly, on mine, when bumping up the voltage.
Click to expand...

Ok... Sounds like my testing of 1150@50... I think we might be on the lower end of the OC tolerance scale...

A note on reboots... There appears to be a phenomena when overclocking, when your phone reboots, but does so very quickly, bringing you back to the home screen in less than 10 seconds. This does not appear to be a full reboot, as I noticed that the overclock.ko would still be loaded after the reboot(i noticed this before making my scripts load in install-recovery.sh). Not sure what to make of it, just wanted to put it out there.
 
Didn't take long at all. Rebooted while in RE. I don't know what my issue is? I'm wondering if there is a problem with running Launcher Pro, Autostarts, Autokill, etc.?
 
Dulaney22 said:
Didn't take long at all. Rebooted while in RE. I don't know what my issue is? I'm wondering if there is a problem with running Launcher Pro, Autostarts, Autokill, etc.?
Click to expand...

I run Launcher Pro Plus. Android doesn't need a task killer. I still don't get why people run them...
 
You must log in or register to reply here.
Back
Top Bottom