Droid X 2.2 Overclock (Kernel Module w/Instructions)

FreeWELL · October 18th, 2010, 08:08 PM

Milestone Overclock as of version 1.4.3 now officially supports Droid X/2 running 2.2/Froyo. Go download it for FREE from the Market. Here is a a post from Tiago from the DroidXForums thread.

Quote:

Hi all, I'm the Milestone Overclock guy. I'd like to let you know that the latest version of Milestone Overclock supports Droid X 2.2 and is now in the Market. It is based on the fix by nadlabak/kabaldan but done "correctly" now that we have the kernel source.

Note also that this fix should correct the vsel problem that many had in android 2.1. The previous module/app simply wasn't setting vsel at all, as many of you suspected. Let's hope this version takes care of it, for anyone that didn't upgrade to 2.2.

For those of you not familiar with Milestone Overclock, it's the original overclock app for the Motorola Milestone (which has a locked firmware just like the Droid X) but nowadays strives to support all OMAP3 phones, and that includes Droid, Droid X, Droid 2 (working on it), many XT7xx/XT8xx and even a Samsung (Galaxy Beam; others are Hummingbird, not OMAP). And yes, it's free!

If you're interested, you can check out the issue which led to this release in the project site:
Issue 36 - milestone-overclock - Modify Source to Support Droid X. - Project Hosting on Google Code
(many thanks to tekahuna)

Thanks
Tiago Sousa aka mirage

Side Note:
The Milestone Overclock kernel module is at the core of all other Droid X/2 overclocking "apps". I'd prefer to call them "Alternate User Interfaces" or "Skins" to the Milestone Overclock kernel module. If you appreciate the ability to overclock your Droid X/2, please Donate to Tiago!

Instructions:
Download Milestone Overclock from the Market, and give it a whirl.

The app is geared towards providing the basics, in a safe manner. It has brick protection, where if you happen to input a custom setting that is out of spec, and causes you to bootloop, you can pull your sdcard and get into your phone to clear the settings...

Full control of freq/vsel still requires a setscaling.sh script(that's how the cool folks like to do it anyways). Pull that from the original zip file. I'll update that when I get a chance.

Original Post:

Quote:

Milestone Overclock Module 1.2t (nadlabak's patch) w/ Memory Locations for DroidX 2.2 Added by FreeWELL

Credits:
Tiago Sousa aka Mirage: for The Milestone Overclock Project
nadlabak: for patching in Froyo/2.2 Support
FreeWELL: for finding DroidX 2.2 memory locations/module compilation

Notes:

I'm trying to keep this as close as possible to the way it was done on 2.1. For me, 2.2 seems to need a little more voltage to be stable than it was under 2.1. I've included two versions of setscaling.sh to start from.

setscaling.sh is set to stock voltages/clock speed

setscaling100.sh is set to stock voltages w/100mhz bump accross the board to 400/700/900/1100 (This appears to be stable for me, and is the baseline for my testing/tuning)

Install Instructions

adb/terminal:
$ 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

<optional(only do after thoroughly testing what works for your DroidX in setscaling.sh)>
# cp install-recovery.sh /system/etc/install-recovery.sh
# chmod 755 /system/etc/install-recovery.sh
</optional>

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

Run Instructions

adb/terminal:

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

Airmaxx23 · October 18th, 2010, 08:21 PM

Now I just need to remember how to do everything....

Fabolous · October 18th, 2010, 08:40 PM

Damn, I was just being envious of the G2 for hitting 1.36GHz today and look what's waiting for us

GTvert90 · October 18th, 2010, 08:44 PM

Very interesting.

Once this is changed it stays that way every boot up right? Do I have to make a backup of anything first? If I mess something up with SBF fix me up?

Thanks.

dilks44 · October 18th, 2010, 08:50 PM

Oh hell yes! cant wait to try this out!

JrzDroid · October 18th, 2010, 08:54 PM

We got oc?!
Yay!

jr1125 · October 18th, 2010, 09:01 PM

Any1 test this yet?

scarsonator · October 18th, 2010, 09:01 PM

In setscaling.sh which numbers are the voltage values and are they the stock values?

I would like to stay at stock speeds but lower the voltage a bit. What all values would I have to change to make this work?

Have you tried this, and if so what have you found to be stable values?

FreeWELL · October 18th, 2010, 09:02 PM

Quote:

Originally Posted by GTvert90

Very interesting.

Once this is changed it stays that way every boot up right? Do I have to make a backup of anything first? If I mess something up with SBF fix me up?

Thanks.

It will not start up every time, unless you install the optional install-recovery.sh file. Do not do this until you have thoroughly tested out what setting will work for you in the setscaling.sh file.

If you never overclocked under 2.1, reading the following threads should help get you up to speed.

[How-To] Overclock your Droid X

[How-to] Overclock that survives a reboot

LexusBrian400 · October 18th, 2010, 09:02 PM

Nvm - just needed to use setscaling100

Works great. Thank you!

Fabolous · October 18th, 2010, 09:06 PM

I'm stuck at 1.15GHz. If your phone gets all slow after you raise the speed, it goes into a "turtle mode", rather cooldown mode and becomes completely unresponsive.

A battery pull will fix this (as long as you did NOT do the install-recovery.sh script)

Beesley, you need to edit the setscaling.sh file to change the slots and voltages they will use. Then, insmod the overclock module and run the setscaling.sh script to change your slots. Then, use SetCPU to change the frequency.

Phantom_DroidX · October 18th, 2010, 09:06 PM

Awesome, thx to all for their work on getting OC capability to the DX froyo users.

LexusBrian400 · October 18th, 2010, 09:08 PM

Quote:

Originally Posted by Fabolous

Beesley, you need to edit the setscaling.sh file to change the slots and voltages they will use. Then, insmod the overclock module and run the setscaling.sh script to change your slots. Then, use SetCPU to change the frequency.

Yes thank you very much.. Just realized I was using the wrong setscaling!

Fabolous · October 18th, 2010, 09:10 PM

Using the 'Stress Test' feature of SetCPU is a good idea for your custom slots and voltages.

Currently doing 1.1GHz at 50 vsel and it's looking good

FreeWELL · October 18th, 2010, 09:11 PM

Quote:

Originally Posted by scarsonator

In setscaling.sh which numbers are the voltage values and are they the stock values?

I would like to stay at stock speeds but lower the voltage a bit. What all values would I have to change to make this work?

Have you tried this, and if so what have you found to be stable values?

I have not really tried undervolting yet. But if that's what you want, you need to edit setscaling.sh to look something like this...

Code:

echo 51 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 600000000 33 > /proc/overclock/mpu_opps
echo 3 800000000 45 > /proc/overclock/mpu_opps
echo 4 1000000000 51 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

This is -5 across to board from stock for the voltage. I have not tested this. It's just an example of how undervolting could be achieved. You'll need to test to find out what actually works for your particular Droid X.

tom108 · October 18th, 2010, 09:16 PM

Damn you all! my DX felt just fast enough. Never thought it really needed OC but now that it is this easy looks like i have some testing to do.

scarsonator · October 18th, 2010, 09:16 PM

Quote:

Originally Posted by FreeWELL

I have not really tried undervolting yet. But if that's what you want, you need to edit setscaling.sh to look something like this...

Code:

echo 51 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 600000000 33 > /proc/overclock/mpu_opps
echo 3 800000000 45 > /proc/overclock/mpu_opps
echo 4 1000000000 51 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

This is -5 across to board from stock for the voltage. I have not tested this. It's just an example of how undervolting could be achieved. You'll need to test to find out what actually works for your particular Droid X.

I'll try it out.

Thanks

Fabolous · October 18th, 2010, 09:25 PM

I am finding these settings to work very well for me, though not all Droid X's are created equal. I actually think mine is kind of a dud

Code:

echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 32 > /proc/overclock/mpu_opps
echo 3 900000000 44 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

JrzDroid · October 18th, 2010, 09:26 PM

alright so after the install how do we set the overclock?
i never messed with the setscaling and just wanna try some different OC speeds
i remember the overclock.sh ####### ## thing but that didn't work

so how do i do it now?!

OMJ · October 18th, 2010, 09:27 PM

thanks freewell. so far it seems to be working well.

Phantom_DroidX · October 18th, 2010, 09:28 PM

Here is my setscaling.sh contents. This is the same that I used in 2.1 OC and its been 10 minutes running setcpu stress test and all seems ok. In 2.1 I was actually able to drop the voltages to like 20,30, 35, and 42. However I am not sure this will work not however i will give it a shot.

Code:

echo 56 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

Phantom_DroidX · October 18th, 2010, 09:32 PM

Quote:

Originally Posted by JrzDroid

alright so after the install how do we set the overclock?
i never messed with the setscaling and just wanna try some different OC speeds
i remember the overclock.sh ####### ## thing but that didn't work

so how do i do it now?!

After the OC install just do this.

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

If you are using the downloaded setscaling with no changes however it will just be stock. You will have to manually change the settings like in my previous post. I recommend using notepad++ in Windows to change params.

Fabolous · October 18th, 2010, 09:34 PM

Quote:

Originally Posted by Phantom_DroidX

I recommend using notepad++ in Windows to change params.

+1

FreeWELL · October 18th, 2010, 09:58 PM

Quote:

Originally Posted by Phantom_DroidX

Here is my setscaling.sh contents. This is the same that I used in 2.1 OC and its been 10 minutes running setcpu stress test and all seems ok. In 2.1 I was actually able to drop the voltages to like 20,30, 35, and 42. However I am not sure this will work not however i will give it a shot.

Code:

echo 56 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

Typo line 2... should be:
echo 1100000 > /proc/overclock/max_rate

bgill55 · October 18th, 2010, 10:00 PM

Ahh very Cool Thank you for this!!!!

humungus · October 18th, 2010, 10:09 PM

Awesome man. Thanks for including stock voltages so we can get some clue about how far we should vary.

s0n- · October 18th, 2010, 10:17 PM

Anyone looking to undervolt, doesnt look like you can get as low as 2.1 I have had automatic restarts on a couple tries right after running setscaling.sh.

EDIT: Dropped it down 5 for now to test. When I cat mpu_opps after running everything I get

vseld=62 vsel=51 for 10000000
vseld=58 vsel=45 for 8000000
vseld=48 vsel=33 for 6000000
vseld=33 vsel=22 for 3000000
I dont remember it appearing like that, should the vseld be the same or is that the original?

chrlswltrs · October 18th, 2010, 10:18 PM

I am getting ready to install this.

I edited setscalling.sh to 1.1GHz and undervolt, do I need to edit anything else to do undervoltage?

chrlswltrs · October 18th, 2010, 10:20 PM

Quote:

Originally Posted by s0n-

Anyone looking to undervolt, doesnt look like you can get as low as 2.1 I have had automatic restarts on a couple tries right after running setscaling.sh.

What volts are you trying, I'm about to try

22,33,43,47

Phantom_DroidX · October 18th, 2010, 10:22 PM

Quote:

Originally Posted by chrlswltrs

What volts are you trying, I'm about to try

22,33,43,47

I'm at 25,35,45,50 atm let me know if that works out for you. I am playing around to see if this is stable enough before I drop again.

s0n- · October 18th, 2010, 10:25 PM

Just tried the one above with -5

echo 51 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 600000000 33 > /proc/overclock/mpu_opps
echo 3 800000000 45 > /proc/overclock/mpu_opps
echo 4 1000000000 51 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 600000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

I initially for my 2.1 had

echo 34 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo 1 300000000 22 > /proc/overclock/mpu_opps
echo 2 500000000 26 > /proc/overclock/mpu_opps
echo 3 800000000 30 > /proc/overclock/mpu_opps
echo 4 1000000000 34 > /proc/overclock/mpu_opps
echo 0 1000000 > /proc/overclock/freq_table
echo 1 800000 > /proc/overclock/freq_table
echo 2 500000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table

Which ran fine

avlfive · October 18th, 2010, 10:28 PM

Quote:

Originally Posted by chrlswltrs

What volts are you trying, I'm about to try

22,33,43,47

Quote:

Originally Posted by Phantom_DroidX

I'm at 25,35,45,50 atm let me know if that works out for you. I am playing around to see if this is stable enough before I drop again.

I'm running 28, 32, 44, 50 at 1.1 right meow and it all seems OK so far.

msburr87 · October 18th, 2010, 10:33 PM

Going to give some speeds a shot when im done with hockey, looking forward to getting a solid over/under running. Best of both worlds

mhornfeck72205 · October 18th, 2010, 10:56 PM

Code:

echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

tried using this, no luck.. locks and reboots on me.. too extreme on the voltages?

Outlaw71 · October 18th, 2010, 11:10 PM

Quote:

Originally Posted by avlfive

I'm running 28, 32, 44, 50 at 1.1 right meow and it all seems OK so far.

You've fooled us up until now, but alas you have outed yourself... but don't worry, we don't mind the occasional p*ssycat in this forum!

JrzDroid · October 18th, 2010, 11:15 PM

Quote:

Originally Posted by mhornfeck72205

Code:

echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

tried using this, no luck.. locks and reboots on me.. too extreme on the voltages?

i've had one lock up so far on this setup
anyone else got something stable?

chrlswltrs · October 18th, 2010, 11:17 PM

Quote:

Originally Posted by chrlswltrs

What volts are you trying, I'm about to try

22,33,43,47

Quote:

Originally Posted by Phantom_DroidX

I'm at 25,35,45,50 atm let me know if that works out for you. I am playing around to see if this is stable enough before I drop again.

First one didn't work = instant reboot

Tried 25, 32, 43, 48 = instant reboot

I'm going to play around with it a little more tomorrow, I'm done for tonight.

Maybe I am doing something wrong, I am trying to go to 1.1GHz with the lower voltages. Someone mind posting what my setscaling.sh should look like

Outlaw71 · October 18th, 2010, 11:18 PM

I'm looking forward to hearing how effective undervolting will effect battery life. I just hope people don't undervolt, then lay their X on their night stand asleep for a week and then report back that they're getting CrAzY battery life!?!?!

chrlswltrs · October 18th, 2010, 11:21 PM

Quote:

Originally Posted by Outlaw71

I'm looking forward to hearing how effective undervolting will effect battery life. I just hope people don't undervolt, then lay their X on their night stand asleep for a week and then report back that they're getting CrAzY battery life!?!?!

Don't worry once I get mine stable I will give real world results, I can't leave my phone alone for a day even if I tried, LOL

charlesbeebe · October 18th, 2010, 11:29 PM

When I:
insmod /system/lib/modules/overclock.ko
I get:
insmod: init_module '/system/lib/modules/overclock.ko' failed (File exists)

What does this mean and how do fix it?

FreeWELL · October 18th, 2010, 11:31 PM

Quote:

Originally Posted by mhornfeck72205

Code:

echo 50 > /proc/overclock/max_vsel
echo 1100000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1100000000 50 > /proc/overclock/mpu_opps
echo 0 1100000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

tried using this, no luck.. locks and reboots on me.. too extreme on the voltages?

You have to play around with things a bit. Settings are not always going to transfer from one DX to the next. It was discussed extensively under 2.1, that there is a good degree of variation from chip2chip/phone2phone as to what these things can handle. You must become one with your X! LOL

Seriously, though... Your freeze/crash/reboots could be from any of the 4 frequency slots having too low a voltage for the frequency it is set to. It is good to use the first page in SetCPU to lock your processor at a certain speed by setting both sliders to the same frequency or by using the performance governor, and test out each of your frequencies with stress test.

I'd also suggest starting from setscaling100.sh and working your way down in voltage, in increments of 2... get a crash... do the previous stress test tip, and find out which slot crashed you.. just keep honing in on what works.. might take some time getting it all the way there...

FreeWELL · October 18th, 2010, 11:33 PM

Quote:

Originally Posted by charlesbeebe

When I:
insmod /system/lib/modules/overclock.ko
I get:
insmod: init_module '/system/lib/modules/overclock.ko' failed (File exists)

What does this mean and how do fix it?

Means it is already loaded... Did you have a crash/short reboot?

in adb or terminal:
# rmmod overclock.ko

charlesbeebe · October 18th, 2010, 11:39 PM

Quote:

Originally Posted by FreeWELL

Means it is already loaded... Did you have a crash/short reboot?

in adb or terminal:
# rmmod overclock.ko

I didnt have a crash or reboot since applying the patch. I went ahead and removed the mod overclock.ko and re-ran through everything though... seems to be working now. Thank you!

SimsDelt · October 19th, 2010, 12:03 AM

so if I run the stock voltages with higher frequencies I should expect better performance with about the same battery life right?

FreeWELL · October 19th, 2010, 12:36 AM

Quote:

Originally Posted by jonathanmsims

so if I run the stock voltages with higher frequencies I should expect better performance with about the same battery life right?

Should be about the same. You just might save battery because you spend less time running your highest voltage... Who knows...

Kirch21 · October 19th, 2010, 12:59 AM

anybody notice any big changes with the OC?

LexusBrian400 · October 19th, 2010, 01:05 AM

Quote:

Originally Posted by Kirch21

anybody notice any big changes with the OC?

Yes, its surprising what a few hundred Mhz will do. CPU intensive apps are running much faster. Like Titanium Backup for example, it flies through backing up/restoring batch apps.

I <3 OC and the people who say its not needed must not know how to do it

I'm kidding of course, but I just dont understand why some ppl are so against overclocking. Its always made my phones faster and perform better.

msburr87 · October 19th, 2010, 02:13 AM

Anything stable yet? Tried fab's but keeps locking up.

LexusBrian400 · October 19th, 2010, 02:18 AM

Quote:

Originally Posted by msburr87

Anything stable yet? Tried fab's but keeps locking up.

I'm running @ 1.2Ghz with 68 vsel. didnt change anything else.

msburr87 · October 19th, 2010, 02:25 AM

Quote:

Originally Posted by LexusBrian400

I'm running @ 1.2Ghz with 68 vsel. didnt change anything else.

Thats a pretty big jump on the vsel, sounds like it will drain your battery pretty quick if you use your phone a lot.

Edit: Gonna giver her a whirl, I have the extendo so I'm not too worried. Just be nice if we could find something super stable, so far I haven't even came close.

Edit: -- Nevermind no dice going to try more at 1.1 @62 everything else the same seems good for tonight. (boo)