• 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

As I mentioned, 1.15GHz at 34 vsel produced a few random reboots (including the weird, 10 second quasi-reboots). At first I kept Hilbe's voltage scales and just decreased the max clock to 1.1GHz, but now I just started using the following scale. I'll report back on stability.


echo 36 > /proc/overclock/max_vsel
echo 1150000 > /proc/overclock/max_rate
echo 1 300000000 24 > /proc/overclock/mpu_opps
echo 2 600000000 28 > /proc/overclock/mpu_opps
echo 3 900000000 32 > /proc/overclock/mpu_opps
echo 4 1150000000 36 > /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
 
I've now been up with Hilbe's script since last night with no reboots. Had to knock it to 1.1 at 34. I also turned off "keep in memory" for launcher pro, did a fresh install of the overclock files and removed autostarts and autokiller. So far so good.

I don't know if it matters, but I put back the stock music player as well. I've read reports that the mod had caused some reboots.
 
humungus said:
echo 36 > /proc/overclock/max_vsel
echo 1150000 > /proc/overclock/max_rate
echo 1 300000000 24 > /proc/overclock/mpu_opps
echo 2 600000000 28 > /proc/overclock/mpu_opps
echo 3 800000000 32 > /proc/overclock/mpu_opps
echo 4 1150000000 36 > /proc/overclock/mpu_opps
echo 0 1150000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
Click to expand...

The above scale ended up _not_ being completely stable. After installing Scrollable ContactWidget Beta and creating a large (2x4) widget, my phone rebooted while attempting to scroll through it. I re-executed the scale and re-created the widget, only to get another reboot. So, now I've bumped my voltages up a bit (see my scale below). I can now run multiple instances of the (2x4) Scrollable ContactWidget without getting a reboot. I think, at least for me, Hilbe's voltages are at the very bottom of my system's tolerances. This is fine for 99+% of use, but every once in awhile my system gets really taxed and gets unstable. Thus, a _WARNING_: I'd be hesitant to load the scaling script at boot until after _heavy_ testing. Especially if you're someone who likes to experiment with themes and thelike. If your system is 99+% stable, there is still a chance that it'll crash under heavy load. If you happen to be replacing your framework-res.apk or system.jar and your system crashes because of low voltage, you might very well end up bricking your X. Of course, you should be able to restore it using the .sbf file, but that's a road I want to avoid if I can.

So, if you're going experiment with low voltages, I'd suggest bumping them back up if/when you're modifying crucial system files. At least until you're _very_ sure your voltage scaling is stable.

Below is my current scaling script. I'll report back on stability.

echo 40 > /proc/overclock/max_vsel
echo 1150000 > /proc/overclock/max_rate
echo 1 300000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 32 > /proc/overclock/mpu_opps
echo 3 800000000 36 > /proc/overclock/mpu_opps
echo 4 1150000000 40 > /proc/overclock/mpu_opps
echo 0 1150000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
 
Any reliable data on battery life yet? It doesn't look like there is much to gain on the processor speed/performance side given the limit on the clock.
 
Alright, I need a little help please. I've gotten the overclocking working, but I am having trouble with the scripts.

When I run the final command "setscaling.sh", I get these errors...
: directory nonexistentreate /proc/overclock/max_vsel
: directory nonexistentreate /proc/overclock/max_rate
: directory nonexistentreate /proc/overclock/mpu_opps
: directory nonexistentreate /proc/overclock/mpu_opps
: directory nonexistentreate /proc/overclock/mpu_opps
: directory nonexistentreate /proc/overclock/mpu_opps
: not found
: directory nonexistentreate /proc/overclock/freq_table
: directory nonexistentreate /proc/overclock/freq_table

I double checked and those directories do infact exist.

What am I doing wrong? Is it a permission issue?

Thanks!!

EDIT - I fixed it. I went into Root Explorer and realized that when I edited the file on my computer, it left an odd character at the end of each line. I erased those characters and everything works fine now.
 
I've now been up close to 2 days on 1100@34 and no reboots. Can't tell that battery life is better or worse, so I guess it's about the same. I am having issues with my battery being read correctly though. Don't know if that's related to overclock or not, but it will jump up and down.
 
sic0048 said:
Alright, I need a little help please. I've gotten the overclocking working, but I am having trouble with the scripts.

When I run the final command "setscaling.sh", I get these errors...
: directory nonexistentreate /proc/overclock/max_vsel
: directory nonexistentreate /proc/overclock/max_rate
: directory nonexistentreate /proc/overclock/mpu_opps
: directory nonexistentreate /proc/overclock/mpu_opps
: directory nonexistentreate /proc/overclock/mpu_opps
: directory nonexistentreate /proc/overclock/mpu_opps
: not found
: directory nonexistentreate /proc/overclock/freq_table
: directory nonexistentreate /proc/overclock/freq_table

I double checked and those directories do infact exist.

What am I doing wrong? Is it a permission issue?

Thanks!!

EDIT - I fixed it. I went into Root Explorer and realized that when I edited the file on my computer, it left an odd character at the end of each line. I erased those characters and everything works fine now.
Click to expand...

That is why you should use notepad ++ it doesn't add these characters
 
--AN IDIOTS TALE--
Maybe someone will read this and not make the same mistakes as me.

OK, so I am really an idiot. Pushed my DX up to 1.2GHz with the survive_the_boot script at startup and got stuck in an endless reboot. Would not make it past the droid eye start up screen.

So, I went to try to get a replacement. They told me it would probably be a refurb (not sure if there would be any refurbs on a phone this new). Don't get me wrong the Verizon employee was extremely helpful and even offered to call my once the phone shipped. But that could possibly take a week or longer.

Well, me not being very patient, went and started looking and found several different instructions on how to flash system with the original SBF file. So, after about 3 hours of searching, I finally found one link with the SBF file that was valid. Installed the necessary drivers, tools, etc and got it to boot up.

Got everything set back up and I am officially giving up on changing the clock speed. At least for the moment. Soooooooooo happy to have my phone back =)
 
Well, just because you ignored all the warnings and decided to go from 0 to 100mph without trying slower speeds first- don't let that stop you from experimenting SMARTLY!

Start at something more reasonable like 1.1 and don't set the changes to automatically start at boot.
 
Alright so Im a real noob to Android, and I'm not looking to mess anything up. So I need some clarification on my seemingly stupid and obvious questions regarding the OP. When it said unzip them to your SD card, is there a specific directory I'm supposed to use? And if so, which one?

Also will I need any specific programs to do it, other than Terminal Emulator?

I tried reading the post by Elkay, but Linux is new to me. I got lost pretty quick in there. Any help is appreciated.

EDIT: Also, Im not really looking much for overclocking, but I want to lower the voltage, seems like you guys are having a lot of luck with that. If there is a simpler way to do that, let me know.
 
I'm having this problem too. well, after the reboot, it should go back to stock (clock speed and voltage) right? ...that is, if i never did the "save after the reboot portion"?
 
^nope. that's on my to buy list alongside titanium backup.

damn, just when i thought i was stable at 1150000 66, i got rebooted from 3dgallery. oh well.

8d1199c2.jpg
 
I got my X replaced and would like to do some testing by changing the overclock.sh values but changing the voltage value does not actually change it. How can it be changed without using the setscale.sh set up?
 
I figured I'd post this so people have an idea what the stock scaling is set at:

10000000 66
8000000 57
6000000 44
3000000 32
 
You must log in or register to reply here.
Back
Top Bottom