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

[SimsDelt]

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

Would you pack this up for people for just a 1.1 GHZ overclock. That way a ****** can use the update.zip and then not have to worry about screwing up their phone or putting it in turtle mode.

 

[MrDonBonJovi]

Can you use setcpu to move scale your overclock after you make this edit? I don't want to be stuck on 1.3 the entire time.
Sorry if its a dumb question.

 

[JrzDroid]

Post your setscaling please... would like to compare your vsel's to mine.

echo 60 > /proc/overclock/max_vsel
echo 1300000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1300000000 60 > /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

 

[LexusBrian400]

Can you use setcpu to move scale your overclock after you make this edit? I don't want to be stuck on 1.3 the entire time.
Sorry if its a dumb question.

Yes, you can drop down to 900, 700, or 400

 

[tom108]

i hope you all are using gscript shortcuts to make executing your frequent changes easier.
i used bothe setscaling.sh (overclocked) and setscaling100.sh (stock), created gscripts to run each, then made shortcuts to those scripts on one of my screens so i can execute them on a whim.

 

[Carpatus]

Ok, well first off, thanks for turning me onto notepad++. Will be using it from now on for my other coding processes. Do I need to re-install, mount, etc, because it just ran the line again and it's still not working?

On an unrelated note, for some reason I can't download both vignette and root explorer. I can purchase them but the download fails. However, I was able to download SetCPU a few hours ago.

Still looking for help on either matter.

 

[Airmaxx23]

Still holding strong at 1.4 GHz, I broke the 1900 mark with a Quadrant test this morning.

 

[Piiman]

This is all new to me.. but I've worked up to this:


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

Hope it helps. 1750 score (which doesn't mean a whole lot to me). Seems stable so far (which means a whole lot to me)...

Well I'm totally confused. The op instruction just seem to be a method to get this stuff on the phone. What do the files do ? more specifically what are the parameters and what do they mean? For example what does this line actually mean
echo 4 1300000000 64 > /proc/overclock/mpu_opps

Why do we have 4 of them? How do you know what the final speed is? Once you edit this file I assume you have to execute something ??

I've installed beasly's Oc zip but now what? I'm feeling extremely stupid today.

 

[tom108]

Well I'm totally confused. The op instruction just seem to be a method to get this stuff on the phone. What do the files do ? more specifically what are the parameters and what do they mean? For example what does this line actually mean
echo 4 1300000000 64 > /proc/overclock/mpu_opps

Why do we have 4 of them? How do you know what the final speed is? Once you edit this file I assume you have to execute something ??

I've installed beasly's Oc zip but now what? I'm feeling extremely stupid today.

if your phone can handle beasly's 1.38 settings (you will find out if it does not reboot.) goto terminal emulator and type:

$ su
# insmod /system/lib/modules/overclock.ko
# setscaling.sh


the reason there are so many numbers is it give the phone options to throttle down the clock speed to lower rates when faster speeds are not needed.
you can find the file to edit in system/xbin/setscaling.sh
edit that file to find the right match for your phone if needed.

 

[JrzDroid]

Still holding strong at 1.4 GHz, I broke the 1900 mark with a Quadrant test this morning.

how long now?
got some purty setscaling setup you could show?

 

[Airmaxx23]

how long now?
got some purty setscaling setup you could show?

It's been running for 24 hours now with no reboots. Here is the scale that I've using.

echo 65 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 65 > /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

 

[kishin14]

Still holding strong at 1.4 GHz, I broke the 1900 mark with a Quadrant test this morning.

I'm so jealous but good for you man. I love seeing higher and higher quad scores since it continues to highlight the potential of the droid x (even if it's not mine).

Unfortunately, I'm in the camp with folks that can't oc past 1.2. I can do 1.25 at 68 vsel but it will eventually freeze and reboot. 1.3 won't even work for one second before it freezes.

Here is my current (seemingly stable) setup running at 1.2ghz:
echo 68 > /proc/overclock/max_vsel
echo 1200000 > /proc/overclock/max_rate
echo 1 300000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 50 > /proc/overclock/mpu_opps
echo 4 1200000000 68 > /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

However, I also ran essentially the same setup but with the max set at 1.175ghz at 64 vsel with no issue.

While I'm all about speed, I think I might go back to the 1.175ghz setup. It's only a little slower (1591 quad score versus 1643 at 1.2ghz) but uses less voltage, which will probably better on my battery.

Besides, I did this primarily for better mp4 playback using rockplayer, which plays most of my files fine but does get choppy with certain rips I've made. I played one of the chopper rips a 1.175ghz and it was choppy for just the first few seconds and then played fine the rest of the way (versus intermittent choppiness at stock 1ghz). I'm okay with that for now.

 

[Piiman]

if your phone can handle beasly's 1.38 settings (you will find out if it does not reboot.) goto terminal emulator and type:

$ su
# insmod /system/lib/modules/overclock.ko
# setscaling.sh


the reason there are so many numbers is it give the phone options to throttle down the clock speed to lower rates when faster speeds are not needed.
you can find the file to edit in system/xbin/setscaling.sh
edit that file to find the right match for your phone if needed.

thanks but I'm the kind of person that likes to know what something means and I have no idea what this means
900000000 50 > /proc/overclock/mpu_opps
I'm assuming the 900000000 is the mhz ? what's the 50 ? and what's all this mean /proc/overclock/mpu_opps

I'm going to run beasly's now though if it doesn't boot then what should I do? Since I don't know what those numbers mean I don't know what I should change or what to change them to. Did I miss that somewhere?

thanks

 

[Airmaxx23]

thanks but I'm the kind of person that likes to know what something means and I have no idea what this means
900000000 50 > /proc/overclock/mpu_opps
I'm assuming the 900000000 is the mhz ? what's the 50 ? and what's all this mean /proc/overclock/mpu_opps

I'm going to run beasly's now though if it doesn't boot then what should I do? Since I don't know what those numbers mean I don't know what I should change or what to change them to. Did I miss that somewhere?

thanks

The 50 represents the voltage, lower voltages for lower mhz settings. /proc/overclock/mpu_opps is the command line that will show you your current setscale.

 

[Piiman]

The 50 represents the voltage, lower voltages for lower mhz settings. /proc/overclock/mpu_opps is the command line that will show you your current setscale.

Ohhhh Thanks air!

I just tried running it and I get setscaling.sh not found. (yes it's there)

Once get that to work do I then reboot or does it take effect instantly.

and once I've found a good setting I have to do that other recovery command to make it stick right?

 

[Airmaxx23]

Ohhhh Thanks air!

I just tried running it and I get setscaling.sh not found. (yes it's there)

Once get that to work do I then reboot or does it take effect instantly.

and once I've found a good setting I have to do that other recovery command to make it stick right?

Rebooting the phone will reset the setscale back to stock, until you run the recovery command. You do not want the setting to stick until you've found good, stable settings. I'd give it a day or two of good heavy use before you run the recovery command. Once you change the settings in the set scale (you can do it through root explorer) the setscale needs to be "executed", which you can do through root explorer also.

 

[dvation]

So I've been trying some other people's settings to see if they work for my phone. I was able to get the 1.1 boost working fine, but when I tried settings people posted for 1.2, 1.3 and 1.4, my phone just slows down to a crawl after running the setscaling.sh command. No reboots or lock ups - just slows down to a crawl. What's happening to my phone?

 

[pandapaul]

It's been running for 24 hours now with no reboots. Here is the scale that I've using.

echo 65 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 65 > /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

What made you decide to increase the 27v @ 300 Mhz to 30?

 

[Airmaxx23]

What made you decide to increase the 27v @ 300 Mhz to 30?

I'm using setCPU to keep it down to 300MHz when the screen is off and it seems like the slight increase in voltage helps with the slight lag when waking the phone and unlocking it.

 

[ECFfighter7232]

Question, when running the stress test in setCPU is there a certain amount of time im supposed to let it run for? it just says "device may be unresponsive, press back to exit" and has the circle going round and round.
right now im just running all stock voltage at 1175 mhz with a 100 bump on the rest.

 

[pandapaul]

Question, when running the stress test in setCPU is there a certain amount of time im supposed to let it run for? it just says "device may be unresponsive, press back to exit" and has the circle going round and round.
right now im just running all stock voltage at 1175 mhz with a 100 bump on the rest.

Just hit back when you feel it has proven its stability to you. To ensure the stability of my 66v @ 1350Mhz I let the stress go for an hour. In general, I think that if you're testing some risky settings then just run it until it crashes. If it doesn't crash within a reasonable time frame (15 min? 1 hour? up to you), then perhaps you're good to go. Keep in mind, though, that the stress test doesn't guarantee stability. That's what I found out when I had a seemingly stable 1.4 Ghz going, but somehow the phone still crashed when using Twitter. lulz.

 

[Piiman]

Rebooting the phone will reset the setscale back to stock, until you run the recovery command. You do not want the setting to stick until you've found good, stable settings. I'd give it a day or two of good heavy use before you run the recovery command. Once you change the settings in the set scale (you can do it through root explorer) the setscale needs to be "executed", which you can do through root explorer also.

Ok After looking around I don't have the setscaling.sh files but I have the setscaling100.sh. Should I have both or do I just execute the 100.sh file? The OP only seems to cp the setscaling.sh....

What is the setscaling100.sh vs the setscaling.sh? Just an example?

 

[tom108]

Ok After looking around I don't have the setscaling.sh files but I have the setscaling100.sh. Should I have both or do I just execute the 100.sh file? The OP only seems to cp the setscaling.sh....

What is the setscaling100.sh vs the setscaling.sh? Just an example?

its just a copy. you can use that file and edit it. just modify your script to execute that file.

 

[Airmaxx23]

Ok After looking around I don't have the setscaling.sh files but I have the setscaling100.sh. Should I have both or do I just execute the 100.sh file? The OP only seems to cp the setscaling.sh....

What is the setscaling100.sh vs the setscaling.sh? Just an example?

The setscale100.sh is overclocked by .1 GHz and setscale.sh is the stock setscale. You can use either scale, just edit the values to your liking and try it out. I'd start with one of the 1300 setscales and slowly try to go up from there.

 

[Piiman]

its just a copy. you can use that file and edit it. just modify your script to execute that file.

I feel so noobish
What script? LOL
Well I executed the 100.sh file and I get massive 694
well second run gets 1308
Now what? How do I start jacking it up or down?