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

Root Droid X 2.2 Overclock (Kernel Module w/Instructions)

So i've been at 1.4 gHz for awhile, had some random reboots, think i'll turn it down till i find more stable numbers. Anyone at a stable 1.45 yet?
 
cowboys4life22 said:
Do not do that optional step, because it will overwrite what clockworld mod boostrap does, which will in effect brick phone, but can still recover via System sbf. We have to find a new way to include that info inside the install-recovery.sh
I tried to include at end of file specified before, but it won't work. Can someone find out how to include in file to get it too work on bootup.
Click to expand...

I had a hunch it might mess something up! Thanks!
 
recovery still functions entirely normal for me. even battefy pull still puts you back into recovery. what exactly do you think that set breaks? cause i did it and nothing seems broken.
cowboys4life22 said:
Do not do that optional step, because it will overwrite what clockworld mod boostrap does, which will in effect brick phone, but can still recover via System sbf. We have to find a new way to include that info inside the install-recovery.sh I tried to include at end of file specified before, but it won't work. Can someone find out how to include in file to get it too work on bootup.
Click to expand...
 
LexusBrian400 said:
I turned this into an update.zip

All you need to do now is run the insmod code and setscaling100.sh from terminal after flashing this.

Beesleys OC Update.zip

After you flash that and reboot..

From a terminal with "su" (#)

insmod /system/lib/modules/overclock.ko
setscaling100.sh
Boom. Done. 1.38Ghz

If your phone cant run that high, edit the values via root explorer.

People who did the OTA should have no problems
Click to expand...

So here's so more fuel for the cpu fire.....I bricked my original X (before the 2.2 sbf leaked) that I got on the second shipment after the first release date (the two week back order).
Anyway, VZW sent me another "refurb" DX that had a build of 39/10. I flashed this zip and couldn't get anything to work down to even 1.1ghz! So having sbf'd back to life the "bricked" original phone I figured why not try it out? So I activate it and flash this, and it's running the 1.38ghz right out of the gate. The build date on this one is 30/10, and it's running rubix 1.0. Just thought I'd post for those curious about build dates/rom's etc. It does appear that all X's aren't created equal. :confused:
Needless to say I'll be keeping the original phone.....
 
JustinD2473 said:
whenever i run the setscaling file it get a whole bunch of errors for "directory non existant" for all the directorys it needs for the overclock.

won't apply any of the settings from the setscaling.sh

the setscaling file and the overclock.ko file are both in their correct folders also.
Click to expand...

I get the same...
 
Ok, so I fixed my installation problem and installed root explorer. Then I deleted the files and re-extracted to my sd card and went through the codes again. This time I edited the file with root explorer and executed it, yet it still shows my DX at stock levels.
 
Carpatus said:
Ok, so I fixed my installation problem and installed root explorer. Then I deleted the files and re-extracted to my sd card and went through the codes again. This time I edited the file with root explorer and executed it, yet it still shows my DX at stock levels.
Click to expand...

I couldn't get that shortcut to work either.

Just do it through the terminal...

su
insmod /system/lib/modules/overclock.ko
setscalingXXX.sh
done!
 
So has anyone tried to do the lowest possible voltages? I have been working on it all day and got pretty good results I think. What do you guys think??

echo 68 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 300000000 14 > /proc/overclock/mpu_opps
echo 2 700000000 31 > /proc/overclock/mpu_opps
echo 3 900000000 42 > /proc/overclock/mpu_opps
echo 4 1350000000 68 > /proc/overclock/mpu_opps
echo 0 1350000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
 
Just for kicks...

5100615655_a89430f9ac.jpg


1.3Ghz with stagefright turned on.
 
Yes I'm in D X. It's a little mod birdman originally discovered. Setting stagefright to true on your build.prop uses a different decoder/encoder for H.264, which drastically ramps up your quandrant scores. Unfortunately it's not really useful because you can't play recorded movies with stagefright on.
 
Does anyone know why the Nexus One gets such high scores on the CPU section? Is Android just optimized better for the N1?
 
When I pushed the install-recovery.sh that was included on first page, it overwrites the one that allows bootloader to work properly. I tried it and I found out first hand it would boot loop, and I needed to use system SBF for 2.2. I tried it a second time to confirm, and had same exact result.
 
cowboys4life22 said:
When I pushed the install-recovery.sh that was included on first page, it overwrites the one that allows bootloader to work properly. I tried it and I found out first hand it would boot loop, and I needed to use system SBF for 2.2. I tried it a second time to confirm, and had same exact result.
Click to expand...

My bootloader, stock recovery and clockwork recovery still work just fine. The original install-recovery script is part of froyo that installs the stock recovery again if a custom recovery is installed over it. Since our stock recovery is never over written this script really has no affect on us. We cant overwrite the stock recovery due to efuse.

I briefly looked through some of the source on koush's bootstrap and didnt see any reference to install-recovery.sh although I admitted was looking on my phone so I wasnt incredibly thorough.
 
Magnum41 said:
So has anyone tried to do the lowest possible voltages? I have been working on it all day and got pretty good results I think. What do you guys think??

echo 68 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 300000000 14 > /proc/overclock/mpu_opps
echo 2 700000000 31 > /proc/overclock/mpu_opps
echo 3 900000000 42 > /proc/overclock/mpu_opps
echo 4 1350000000 68 > /proc/overclock/mpu_opps
echo 0 1350000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
Click to expand...


I've got 66 very stable at 1.35Ghz, but I've needed closer to 20 for 300Mhz... *shrug*
 
Magnum41 said:
So has anyone tried to do the lowest possible voltages? I have been working on it all day and got pretty good results I think. What do you guys think??

echo 68 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 300000000 14 > /proc/overclock/mpu_opps
echo 2 700000000 31 > /proc/overclock/mpu_opps
echo 3 900000000 42 > /proc/overclock/mpu_opps
echo 4 1350000000 68 > /proc/overclock/mpu_opps
echo 0 1350000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
Click to expand...

I'm doing the same as you man. Not very far into it. so far @ 400mhz/ 18(nvm 18 crashed) as lowest clock.

But what do you guys use as a stress test? Just the one built into SetCPU? bunch of quad runs? Daily use? I'm curious.

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