• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Droid 2 Overclock(Kernel Module+Instructions)

FreeWELL

Member
Aug 9, 2010
99
69
* Props to Super_Six_Two and WalCs for helping me get the memory address' and testing the module out for the D2*

Before continuing on please check out the following links, and learn from what the DX guys have discovered:

http://http://androidforums.com/droid-x-all-things-root/201920-droid-x-2-2-overclock-kernel-module-w-instructions.html

http://androidforums.com/droid-x-all-things-root/145209-how-overclock-your-droid-x.html

http://androidforums.com/droid-x-all-things-root/146969-how-overclock-survives-reboot.html




Here it is:

Milestone Overclock Module 1.2t (nadlabak's patch) w/ Memory Locations for Droid2 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 the Droid X. 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/droid2_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
 

Attachments

  • droid2_22_oc.zip
    11.5 KB · Views: 571
I failed, therefore i am... a noob...

i ran the commands and it didnt change a thing on my droid 2. it still says 1000mhz.

???????

ok... in adb/terminal execute:

Code:
cat /proc/overclock/*

Does it throw an output or error?

The setscaling.sh file is actually set to stock values... It must be edited to overclock... Please read through the first link I posted in the OP, it explains a lot of this stuff.
 
Upvote 0
Hi everyone,

I wrote a simple Linux shell script called dooverclock.sh. Give it a try. Standalone.

1. Extract
2. Chmod
3. Run dooverclock.sh
4. Follow directions (1.2, 1.3, 1.4 are meant for D2) in UI

-Kevin

Information and downloads here:
DOOverclock - Easier Way to OC Your Droid 2 - xda-developers
Will port to Windows as soon as I have time.

Do you have an eta on windows version? I have been fighting with adb to read my phone and it was a no go last night
 
Upvote 0
Thanks for this. I got it working in all of 2 minutes just using better terminal on my phone instead of using adb.

I'm trying to get 1.2 stable and not having much luck. Quadrant is stable, I get low 1600's on 1.2. And setcpu stress test passes, but I still get random reboots. Could you please explain to me the voltage number in the script for the vsel variable setting? I'm going by another users settings for 1.2 and he has it set at 56. I would like to adjust this value, but I would like some explanation of this number first as to how it correlates to voltage. I am a heavy overclocker on desktops using watercooling, phase change and peltiers in the past, and understand vcore etc. But just the number "56" makes no sense to me. So if someone could please provide a good explanation, that would be great.

Also it has always seemed in the past, that putting the voltage up high won't really make it get to the point of overheating the chip and frying it. Whenever I had the voltage too high on my Original Droid, Eris and G1 they would just reboot before it ruined anything.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones