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

eqbbyo.jpg
 
Ok, here's what I don't get. It is set on performance mode which maxes out both max and min. The scales show that but the figures don't. They say 2000 max and 1000 min. Anyway, yeah, I want to see some test results.
 
cjdecarl said:
Or he could post whats in his setscaling.sh :p
Click to expand...

echo 70 > /proc/overclock/max_vsel
echo 2000000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 48 > /proc/overclock/mpu_opps
echo 4 2000000000 OVER9000!!!!!!!!! > /proc/overclock/mpu_opps
echo 0 2000000 > /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




note: plz don't try actually running that...
 
It says 1000 minimum because of the way that the setscaling is set up. Its the same as if you use off values. Its proof of concept that 2ghz works and runs without a force reboot. Battery gets hot enough to fry an egg though
 
xxxdroidxxx said:
im new here. can someone tell me step by step on how to do this. My phone is rooted.
Click to expand...

Well, first, I would recommend downloading setCPU, root explorer, and a terminal (I have terminal emulator) from the market place.
1) download the file from the first post onto your computer then extract the file onto the sd card of your phone.
2) on your phone, type it the code from the first post in your terminal. DO NOT input the the optional part.
3) open up root explorer and open system then open xbin. Find the file there and long press on it and select edit.
4) go in and change the numbers. I would recommend you go with one of the ones that have been posted in this thread until you understand it more.
5) go back to the file and short press it and select execute.

Now, it is just trial and error.
6)Open up setCPU and go to the fourth tap over on the top, info, and run a stress test. I do 15 min tests. If your phone reboots or freezes up then you need to lower the frequency or increase the voltage. If the test works though, then you can increase the frequency or lower the voltage. Oh, the frequency is the long number and the voltage is the 2-digit number. On voltage, do not go above ~92 though most people don't even go above 70.
 
joe772 said:
It says 1000 minimum because of the way that the setscaling is set up. Its the same as if you use off values. Its proof of concept that 2ghz works and runs without a force reboot. Battery gets hot enough to fry an egg though
Click to expand...

I would still like to see a quadrant test on it. Is it stable enough to last that long?
 
He hasn't said whether or not it's running turtle or not though. Most running 1.6 also mentioned they ran turtle at that speed.
 
Any reason why i would be seeing turtle with anything over 1.1? Even bumping to 1.2 (with a small voltage bump) causes it. I've tried numerous settings that people have claimed to work in this thread and come up with nothing. Is it really possible that my chip just cant be pushed that far? i'm not new to OCing but this does seem odd.

EDIT: Seems like it might be related to SetCPU. I disabled all profiles and set it to "performance". It doesnt seem to be turtling at the moment.

EDIT2: It might actually be turtling....what exactly does that mean for everyone else? I used to see immensely slow performance (it would take 10 sec for the notification bar to pull down and it would do it in about 2 frames). Now, it just appears to be a little slower than normal, but def not the 1.3 setCPU says its at...
 
Ah, that sucks.

Quick question, is there any evidence or do you think it would make a difference in amount you can overclock if a ROM was flashed? The one I'm thinking about flashing has most of the MotoBlur removed.
 
Carpatus said:
Well, first, I would recommend downloading setCPU, root explorer, and a terminal (I have terminal emulator) from the market place.
1) download the file from the first post onto your computer then extract the file onto the sd card of your phone.
2) on your phone, type it the code from the first post in your terminal. DO NOT input the the optional part.
3) open up root explorer and open system then open xbin. Find the file there and long press on it and select edit.
4) go in and change the numbers. I would recommend you go with one of the ones that have been posted in this thread until you understand it more.
5) go back to the file and short press it and select execute.

Now, it is just trial and error.
6)Open up setCPU and go to the fourth tap over on the top, info, and run a stress test. I do 15 min tests. If your phone reboots or freezes up then you need to lower the frequency or increase the voltage. If the test works though, then you can increase the frequency or lower the voltage. Oh, the frequency is the long number and the voltage is the 2-digit number. On voltage, do not go above ~92 though most people don't even go above 70.
Click to expand...

I'm a newbie! When I run SetCPU, my max shows 1000000 and my min shows 300000. My Quadrant scores range from mid 1200's to high 1400's before overclocking. I followed your instructions to the letter. I overclocked my max to 1250000/60, saved the settings and clicked "execute". After overclocking, I'm getting the same type of results. I noticed in your instructions you didn't mention anything about the "Run Instructions". When I tried to follow those instructions on Better Terminal Emulator, I get an error that says "No such file or directory/#".

Am I doing something wrong? if so, what? BTW, I am on Droid X with 2.2 OTA, Rooted and Deodexed (I think Deodexed).

Please Help!!!
 
FreeWELL said:
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
Click to expand...

Once I copied "setscaling100.sh" to /system/xbin/setscaling.sh, everything worked great. Thanx!
 
yes in case any1 wants to know 2ghz is turtle. i even ran it myself (thank goodness for gscript..1 click OC off!)

so far 1.45 ish is as stable as i can get. been testing others but as you go up it seems harder to run a quadrant cuz itll cut out in the middle or even last few seconds and return to quadrants home screen. and incase some dont know you actually have to run quad a few times just to get a somewhat accurate reading.

i.e: oc at 1.45 first readin, 1820.....1999....1878...2019.....1700...2029..etc. <-example
 
eacosta4207 said:
I'm a newbie! When I run SetCPU, my max shows 1000000 and my min shows 300000. My Quadrant scores range from mid 1200's to high 1400's before overclocking. I followed your instructions to the letter. I overclocked my max to 1250000/60, saved the settings and clicked "execute". After overclocking, I'm getting the same type of results. I noticed in your instructions you didn't mention anything about the "Run Instructions". When I tried to follow those instructions on Better Terminal Emulator, I get an error that says "No such file or directory/#".

Am I doing something wrong? if so, what? BTW, I am on Droid X with 2.2 OTA, Rooted and Deodexed (I think Deodexed).

Please Help!!!
Click to expand...
You said you saved your settings and clicked "execute", what program did you use to click "execute"?
 
You must log in or register to reply here.
Back
Top Bottom