• 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

Hilbe said:
I'm not sure you need the full paths. I see them using chmod in init.rc which is in /system/bin, so I'm guessing "/system/bin" is not necessary. I'd try:

insmod /system/lib/modules/overclock.ko
setscaling.sh
Click to expand...

The insmod would be necessary for both lines, correct?

insmod /system/lib/modules/overclock.ko
insmod setscaling.sh

?
 
kastleberg said:
The insmod would be necessary for both lines, correct?

insmod /system/lib/modules/overclock.ko
insmod setscaling.sh

?
Click to expand...

No. insmod tells it to load the kernel module overclock.ko. Just use it as I pasted it.

insmod /system/lib/modules/overclock.ko
setscaling.sh
 
Hilbe said:
No. insmod tells it to load the kernel module overclock.ko. Just use it as I pasted it.

insmod /system/lib/modules/overclock.ko
setscaling.sh
Click to expand...
Okay then. I'm going for it in RE. If this bombs, I guess someone else can report using desktop while I recover. :D
 
Hilbe said:
I don't want to redo my setup, but reboot and do:

insmod /system/lib/modules/overclock.ko
cat /proc/overclock/mpu_opps

You'll notice the 1ghz slot is 66 vsel.
Click to expand...

So an unrooted phone uses all the same values except for the 1 ghz slot that we're changing?
 
Airmaxx23 said:
So an unrooted phone uses all the same values except for the 1 ghz slot that we're changing?
Click to expand...

If you're using setclock.sh or overclock.sh, you're only changing the top slot. That is why I posted a setscaling.sh with modifications to all 4 slots.
 
Well, I ran cat /proc/overclock/mpu_opps and got /proc/overclock/mpu_opps: No such file or directory. Did it not work?
 
So I added the lines but every time I reboot for some reason the two lines get erased. I am still trying though
 
kastleberg said:
Well, I ran cat /proc/overclock/mpu_opps and got /proc/overclock/mpu_opps: No such file or directory. Did it not work?
Click to expand...

means the kernel module didn't load (insmod cmd). Check your init.rc to see if you see those 2 commands in there.
 
Looks like we're going to have to find another startup script to modify :)

Edit:

I should have done my homework. init.rc is part of a ramdisk. So when you reboot, poof it is reloaded again. We'll need to find another init script that isn't part of a ramdisk. Back to the drawing board.
 
Yep I have tried everything, computer, RE, a little of both, and adding /system/bin on the front of each. It just goes away on reboot:(
 
I'm game. Any ideas? Unless you think that editing it, pushing onto the sdcard and what not would have different results. Droider13, what method were you trying? Hahaha. NM, just saw above post.
 
Hilbe said:
Looks like we're going to have to find another startup script to modify :)

Edit:

I should have done my homework. init.rc is part of a ramdisk. So when you reboot, poof it is reloaded again. We'll need to find another init script that isn't part of a ramdisk. Back to the drawing board.
Click to expand...

Do it...now, tonight, right now:p
I would be glad to help
 
Hilbe said:
If you're using setclock.sh or overclock.sh, you're only changing the top slot. That is why I posted a setscaling.sh with modifications to all 4 slots.
Click to expand...

What are the stock values for the 4 slots prior to being modified?
 
I was looking through the init.rc and noticed it calls a couple other .sh scripts under /system. Why don't you try adding those 2 lines to:

/system/etc/install-recovery.sh
 
After fresh reboot:

$ su
# cd /proc/overclock
# cat mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=34
mpu_opps[3] rate=900000000 opp_id=3 vsel=30
mpu_opps[2] rate=600000000 opp_id=2 vsel=26
mpu_opps[1] rate=300000000 opp_id=1 vsel=22
 
Hilbe said:
After fresh reboot:

$ su
# cd /proc/overclock
# cat mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=34
mpu_opps[3] rate=900000000 opp_id=3 vsel=30
mpu_opps[2] rate=600000000 opp_id=2 vsel=26
mpu_opps[1] rate=300000000 opp_id=1 vsel=22
Click to expand...

Rebooting now. Let you know what I get...

Boom. Samesies. Except, I used the 1125000 45 edit so I have

mpu_opps[4] rate=1125000000 opp_id=4 vsel=45

for top line
 
Hilbe said:
After fresh reboot:

$ su
# cd /proc/overclock
# cat mpu_opps
mpu_opps[4] rate=1150000000 opp_id=4 vsel=34
mpu_opps[3] rate=900000000 opp_id=3 vsel=30
mpu_opps[2] rate=600000000 opp_id=2 vsel=26
mpu_opps[1] rate=300000000 opp_id=1 vsel=22
Click to expand...

How'da do it. Was it the install.sh or another one
:D:D:D:D
Why don't I have that file, am I looking in the wrong place
 
How to do the overclock at boot:

1. Pull file off phone.

adb pull /system/etc/install-recovery.sh

2. Add 2 lines to bottom of install-recovery.sh in text editor on computer, save:

insmod /system/lib/modules/overclock.ko
setscaling.sh

3. Remount /system in read/write:

mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system

4. Push changes to sd card.

adb push install-recovery.sh /sdcard

5. Copy file to right place.

cp /sdcard/install-recovery.sh /system/etc/install-recovery.sh

6. Remount read only /system

mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

7. Reboot
 
You must log in or register to reply here.
Back
Top Bottom