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

I changed my scale some and have been running/testing it for a little over an hour, no reboots yet. 1.4 GHz at 65 vsel. 2 other Quadrant tests resulted in 1849 and 1876.

1400 / 65
1000 / 45
700 / 34
300 / 30

snap20101019_123149.png
snap20101019_123434.png
 
Ok I've finally got it running stable, I would still like to make a few more changes, but I am going to be out all day today so I'm sticking with this for a while

volts: 23,35,47,60

1.1 GHz

Quad: 1527, 1571, 1580


*Edit

Played with it a little more and seems to be stable here

23, 35, 47, 62
1.2 GHz

Quad: 1648, 1651, 1684
 
What can I do if I did the.step to.lock it in after a reboot. I want to try higher voltages so I can go higher frequencies. Didn't try anything over 1.1ghz. Im sure I just have to delete something and then reboot. But I don't know what to do. Do I just change the setscaling.sh that I have and it will retain after a reboot because I did the "optional" step to keep from loosing oc after reboot?
 
so after putting the extracted files on the sdcard


i do this

$ su
# cd /sdcard/extracted/droidx_22_oc (or wherever you extracted the files to)
# mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
# cp overclock.ko /system/lib/modules/overclock.ko
# cp setscaling.sh /system/xbin/setscaling.sh
# chmod 644 /system/lib/modules/overclock.ko
# chmod 755 /system/xbin/setscaling.sh



then what from there?
also how do i do this in adb? i cd to sdk tools directory first right? then what?
 
Right now I am stable at 1.3 at 63 vsel. I was able to get up to 1.5 working without many random reboots but the vsel was so high it was killing my battery.
 
Im running a stock clock with -5 undervolt on all until 1.15@62 which runs great with a 1588 quad and 16.79 lin. But I cannot get over 1.15 for the life of me. Suggestions?
This is a great set up for speed and battery though
 
ok, so currently i have mine at:

300/30
700/35
900/45
1300/60

the top echo value is at 60

the bottom four echo(s)
1300
900
700
300

for some reason in SetCPU the phone will not run at 1300 mHz unless i have both max and min all the way up. Anyone know why?
 
jonathanmsims said:
What can I do if I did the.step to.lock it in after a reboot. I want to try higher voltages so I can go higher frequencies. Didn't try anything over 1.1ghz. Im sure I just have to delete something and then reboot. But I don't know what to do. Do I just change the setscaling.sh that I have and it will retain after a reboot because I did the "optional" step to keep from loosing oc after reboot?
Click to expand...

To keep it from surviving a reboot I believe you would have to remove the install-recovery.sh file from the system/etc folder. You should not do the optional part until you've thoroughly tested the setting, if you mess something up you could end up in a boot loop.
 
JrzDroid said:
ok, so currently i have mine at:

300/30
700/35
900/45
1300/60

the top echo value is at 60

the bottom four echo(s)
1300
900
700
300

for some reason in SetCPU the phone will not run at 1300 mHz unless i have both max and min all the way up. Anyone know why?
Click to expand...

if your scaling is ondemand then it only goes up to 1300 when it needs to. Running at 1300 all the time is going to wreck your battery
 
JrzDroid said:
ok, so currently i have mine at:

300/30
700/35
900/45
1300/60

the top echo value is at 60

the bottom four echo(s)
1300
900
700
300

for some reason in SetCPU the phone will not run at 1300 mHz unless i have both max and min all the way up. Anyone know why?
Click to expand...

It will only use the 1300 when necessary, unless you have it set for performance.
 
yea i have it set at onDemand, i'm just saying that it only shows 1000 mhz max 300 min under where it says scaling ondemand in setcpu. It might be just how SetCPU is recognizing it now that i think about it
 
JrzDroid said:
yea i have it set at onDemand, i'm just saying that it only shows 1000 mhz max 300 min under where it says scaling ondemand in setcpu. It might be just how SetCPU is recognizing it now that i think about it
Click to expand...

Mine says 1200 max 300 min

did you press menu -> device selection -> auto detect speeds, that might fix it
 
JrzDroid said:
yea i have it set at onDemand, i'm just saying that it only shows 1000 mhz max 300 min under where it says scaling ondemand in setcpu. It might be just how SetCPU is recognizing it now that i think about it
Click to expand...

sometimes I have to restart setcpu to get it to show correctly. Just keep hitting back until it exits the app then go back in
 
JrzDroid said:
yea i have it set at onDemand, i'm just saying that it only shows 1000 mhz max 300 min under where it says scaling ondemand in setcpu. It might be just how SetCPU is recognizing it now that i think about it
Click to expand...

Are you sure the settings actually went through? I had the same problem, I had to use root explorer to "execute" the setscale.sh file and then it was showing up properly in setCPU.

Edit: you can use the terminal or abd, to check that the settings went through, by entering the following:

cat /proc/overclock/mpu_opps
 
i did the cat /proc/overclock/mpu_opps and its coming up with my values 1300,900,700,300. SetCpu is now showing correctly thank you=]

edit: soon as i exit setcpu and go back in, max goes back to 1000

2nd edit: my profile was on 1000 for charging, NEVERMIND!
 
Bah, mine doesn't want to go above 1.15GHz, even with a voltage of up to 68 (I wasn't going to go any higher). Oh well.
 
JrzDroid said:
1.4 ! thats pretty sweet, and its stable?
could you by any chance post your full set scaling? =]
Click to expand...

1.4Ghz has since proven less stable than it seemed before. I ran lengthy setcpu stress tests and many successive quadrants to try and push it hard to break it, but what actually ends up causing reboots is just plain old normal usage in apps like xscope and google voice. I'd be messing with it more, but I'm at work for a few more hours. Seems other folks have settled in at 1.3Ghz. That may be the happy medium for those fortunate enough to get into the higher ranges.

Here is the setscaling I was using and will be tweaking from until full, genuine stability is achieved:

Code: 
echo 68 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 49 > /proc/overclock/mpu_opps
echo 4 1400000000 68 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
 
You must log in or register to reply here.
Back
Top Bottom