• 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)

Airmaxx23 said:
You need to use root explorer, the script file is located in the system/xbin folder. Change the r/o (top right of the screen) to r/w, then long press on the file and scroll down to edit.
Click to expand...

LMAO, I cant believe I forgot how to do this.. lol been too long.

Many Tanks. :D
 
catalystsupreme said:
For some reason i lose OC after reboot.Why is that?
Click to expand...

That has been discussed. It is a built in safety feature so you don't get stuck in a bootloop after choosing a bad configuration. there is a command to make it permanent but i don't really suggest it. just use gscript to run the overclock commands after a reboot.
 
Anything over 1.1 causes the ugly turtle to appear on my X. I have gone up to 1.2 at 68 and it just about freezes. "All Droids are not created equally," indeed good sir, indeed.
 
Airmaxx23 said:
You could always just flash the 2.2 sbf and go from there...and no, you wouldn't be crazy.
Click to expand...

Oh that's right I forgot about the full 2.2 sbf. Hopefully its got the OTA kernel. Think im gonna do it. Thanks for reaffirming my obsession for the DX isn't crazy
 
What is the highest voltage that should be used, tried doing the 1.61 setup that Fab had and got a turtle (stable but 258 in Quadrant). Should I go any higher with the voltage or lower the freq?
 
So after doing all of the instructions in the original post except for the "optional" part...is the overclocking going to be lost after a reboot?
 
androidb said:
So after doing all of the instructions in the original post except for the "optional" part...is the overclocking going to be lost after a reboot?
Click to expand...

Yes, that way you do not get caught in a boot loop if the voltages are too low or if you get a turtle can pull the battery. I have a copy of the setscaling.sh on my desktop that way I can begin where I left off and don't lose anything
 
This is confusing.. I just ran the 1.61 GHz, and it turtled. 1.3 and 1.4 reboot, but 1.6GHz turtles. Does that mean I need to bump the voltages on the 1.4?
 
finally got to 1.4 with a quadrant of 1902
gonna try 145


and when upping the voltage whats the highest not to exceed? in order for me to reach 1.4 i had to up the max to 70 cuz i kept restarting at 65-67
 
how much is actually significant? from 76 to about 80? Or is that to much?


Currently got this running stable:

Code: 
echo 64 > /proc/overclock/max_vsel
echo 1300000 > /proc/overclock/max_rate
echo 1 300000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 50 > /proc/overclock/mpu_opps
echo 4 1300000000 64 > /proc/overclock/mpu_opps
echo 0 1300000 > /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
 
msburr87 said:
Would I be crazy to flash sbf back to 2.1, then ota 2.2, reroot, reinstll fission, reset everthing to my settings, then finally try overclocking past 1.15 lol? Debating if its worth it?
Click to expand...

Yes you would be crazy because that will brick your phone and make you have to flash the 2.2 sbf, might as well eliminate the unneeded brick
 
tomsfacts said:
Yes you would be crazy because that will brick your phone and make you have to flash the 2.2 sbf, might as well eliminate the unneeded brick
Click to expand...

That would not brick his phone at all. You can easily go from any of the 2.2 leaks back to 2.1 by using the 2.1 .sbf file. Several people, including myslef, have done it without a problem.
 
androidb said:
Does the Set CPU app work after doing this? I am familiar with that app
Click to expand...
Ya, but if you change your clock speed while set cpu is open in the background then it wont go to your new clock speed in the app. Just kill it with a task killer then restart
 
can some1 explain about voltage to freq? like i see a person like airmaxx running 1.4 at 65. but in order for me to run that i have to be at 71. why is this?


also currently testing 142 ...will post quadrdant and settings
 
Ok weird thing...

I run the commands and see that they have taken effect as I can see I am running at 1.1ghz in SetCPU.

After 10ish minutes or so, I unlock my phone, and it is back to stock 1ghz settings... this is without rebooting of course...

WTF? Anyone else notice this?
 
You must log in or register to reply here.
Back
Top Bottom