Root Droid 2 Overclock(Kernel Module+Instructions)

[n0yd]

I can't get 1.4 @ 64 to work. As soon as I set it, the phone slows to an unusable crawl.

 

[Cilraaz]

I can't get 1.4 @ 64 to work. As soon as I set it, the phone slows to an unusable crawl.

1.4GHz @ 64 is asking a lot. I'm tweaking my 1.3GHz setup now and 64 reboots immediately in a stress test. I'm guessing 1.4GHz would require a good bit more.

 

[bizzshow]

Then bump the voltage up some of you do that and it still sucks your phone may not like 1.4
edit 64 is my voltages at 1.3

 

[Redflea]

I believe Walcs was running 1.4 at 73 or so...64 is a BIG ask for that speed.

 

[Thornfullessrose]

is anyone working on a easier process for us non-advanced root users?

 

[Super_Six_Two]

is anyone working on a easier process for us non-advanced root users?

Well I haven't actually had time to do this yet, but I will see if I can come up with some step by step instructions when I do.

 

[Thornfullessrose]

Well I haven't actually had time to do this yet, but I will see if I can come up with some step by step instructions when I do.

ok

 

[Cilraaz]

Finally stable at 1.3 @ 66. Ugh.

Carrying my data forward:

1.2 @ 59: 470 sec stress test hit 38*C; Quadrant scores - 1708, 1632, 1622
1.3 @ 66: 317 sec stress test hit 42*C; Quadrant scores - 1669, 1714, 1699

That's a heck of a voltage and temp increase for fairly little return. I guess I got a rather 'meh' CPU. I'll probably try 1.4GHz, but I doubt I'll get a reasonable return.

[edit: For those running 1.3 and 1.4, what temps are you seeing?]

 

[Redflea]

For those of you who are moderately technical but don't want to use ADB or Terminal on the D2 to type commands (tedious after a while), you can use Gscript from the market to do some simple overclocking automation all directly on your D2.

Put a text file w/the install commands on your SD card (or copy them from a web page, whatever method you prefer). Copy/paste the install commands into a new script in gscript, and place the two files (overclock.ko and setscaling.sh) on your SD card in the appropriate directory, and run the script in gscript.

For example - I use the script below to set up a "clean" D2 for 1.2 OC (Gscript has a checkbox to confirm that su is required, so you don't need to include that in the script).

cd /sdcard/OC [NOTE: this is where I placed the OC files I'm using]
mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
cp overclock.ko /system/lib/modules/overclock.ko
cp setscaling200.sh /system/xbin/setscaling200.sh
chmod 644 /system/lib/modules/overclock.ko
chmod 755 /system/xbin/setscaling200.sh
mount -o ro,remount -t ext3 /dev/block/mcblk1p21 /system
insmod /system/lib/modules/overclock.ko
setscaling200.sh

This script only works if you have overclock.ko and setscaling200.sh in a folder in the root of your SD card called OC. Edit the script if you use a different directory or your setscaling file has a different name. You need to create the setscaling200.sh file by pasting the contents below into a text file and naming it setscaling200.sh. Each "echo" should start a new line in the file.

If I install a new ROM or new version of a ROM , I can simply run that script in GScript and my OC is set up in seconds.

The contents of the 1.2 setscaling file I use are below.

echo 62 > /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 62 > /proc/overclock/mpu_opps
echo 0 1200000 > /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 that helps some...

You can create scripts for various overclock settings to make it easy to switch between them, and you can export scripts from Gscript and execute them w/out gscript if you want.

 

[WalCs]

Voltages necessary will depend on your phone mine is running great at 1.3 and 64vsel hours yours may run at that voltage or more I haven't tried 1.4 but probably will tonight

lmao, stagefright?

 

[Thornfullessrose]

The 1.2 setscaling file I use is:

echo 62 > /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 62 > /proc/overclock/mpu_opps
echo 0 1200000 > /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

can some one tell me where this↑↑↑ comes in? is it a command? or...???





Hey Redflea: I get this in Gscript↓
<script src='http://img84.imageshack.us/shareable/?i=cap201010201357.jpg&p=tl' type='text/javascript'></script><noscript></noscript>

 

[bizzshow]

lmao, stagefright?

Yep 1.3 and stagefright just to see what it would net I've disabled it through no need for it. I average around 1700 without kinda sucks
and op use terminal or if you have root explorer navigate to hit and tap it should give you an option to execute. If using terminal just type sure enter then the name enter

 

[jayxpx]

where do i go to see the voltages or that bar scale that is shown above? Is it an app or is there a test you run?

 

[Cilraaz]

Well, I finished my 1.4GHz overclock. It took a voltage setting of 75. Anyway, here are my results from stock speed to 1.4GHz:

1.0 @ stock: no stress test; Quadrant scores - 1506, 1494, 1486; Average score 1495
1.2 @ 59: 470 sec stress test hit 38*C; Quadrant scores - 1708, 1632, 1622; Average score 1654 (10.6% increase from stock)
1.3 @ 66: 317 sec stress test hit 42*C; Quadrant scores - 1669, 1714, 1699; Average score 1694 (13.3% increase from stock, 2.4% increase from 1.2)
1.4 @ 75: 300 sec stress test hit 42*C; Quadrant scores - 1775, 1802, 1774; Average score 1783 (19.2% increase from stock, 7.8% increase from 1.2, 5.2% increase from 1.3)

Each test was done under pretty much worse case scenario. Each time there was pre-built up heat from previous failed OC attempts and/or reboots. Each time the test was done while charging the phone, which adds some extra heat. The 1.4GHz overclock was never 100% stable, either. On the last attempt, I managed the 5 minute stress test and multiple Quadrant tests, but then the phone rebooted while idle.

For day-to-day, I'll likely either go back to stock speeds (it's not like the device was slow to start with) or maybe run at 1.2GHz.

 

[WalCs]

Yep 1.3 and stagefright just to see what it would net I've disabled it through no need for it. I average around 1700 without kinda sucks
and op use terminal or if you have root explorer navigate to hit and tap it should give you an option to execute. If using terminal just type sure enter then the name enter

LOL, i got 1961 using no stagefright, i wonder what would i get if i used it...

 

[bizzshow]

Higher than mine. This was just to show that the g2 isn't the badest phone on the block especially since it has stagefright stock

 

[WalCs]

Higher than mine. This was just to show that the g2 isn't the badest phone on the block especially since it has stagefright stock

So you got 2400 with stagefright when only 1700 regular?
so that's 700 increase, so 1960+700 = 2660..WHOA

 

[bizzshow]

Should be be much higher than mine in did this just to show the g2 wasn't as much of a beast as though especially at 1.4 and it already has stagefright just enabled

 

[WalCs]

How high do you think it will go?

 

[darkonion]

For those of you who are moderately technical but don't want to use ADB or Terminal on the D2 to type commands (tedious after a while), you can use Gscript from the market to do some simple overclocking automation all directly on your D2.

Put a text file w/the install commands on your SD card (or copy them from a web page, whatever method you prefer). Copy/paste the install commands into a new script in gscript, and place the two files (overclock.ko and setscaling.sh) on your SD card in the appropriate directory, and run the script in gscript.

For example - I use the script below to set up a "clean" D2 for 1.2 OC (Gscript has a checkbox to confirm that su is required, so you don't need to include that in the script):

cd /sdcard/OC [NOTE: this is where I placed the OC files I'm using]
mount -o rw,remount -t ext3 /dev/block/mcblk1p21 /system
cp overclock.ko /system/lib/modules/overclock.ko
cp setscaling200.sh /system/xbin/setscaling200.sh
chmod 644 /system/lib/modules/overclock.ko
chmod 755 /system/xbin/setscaling200.sh
mount -o ro,remount -t ext3 /dev/block/mcblk1p21 /system
insmod /system/lib/modules/overclock.ko
setscaling200.sh

If I install a new ROM or new version of a ROM , I can simply run that script in GScript and my OC is set up in seconds.

The 1.2 setscaling file I use is:

echo 62 > /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 62 > /proc/overclock/mpu_opps
echo 0 1200000 > /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 that helps some...

You can create scripts for various overclock settings to make it easy to switch between them, and you can export scripts from Gscript and execute them w/out gscript if you want.

Kind of beat you to it in terms of scripts!

Got standalone over on XDA for D2 and DX. Code needs a lot of work though.

DOOverclock - Easier Way to OC Your Droid 2 - Page 2 - xda-developers

 

[Cilraaz]

How high do you think it will go?

My 1.4GHz with Stagefright jumped up to 2757.

It didn't seem to actually improve performance any, though. So what in the world does it actually do?

 

[Redflea]

can some one tell me where this&#8593;&#8593;&#8593; comes in? is it a command? or...???


Hey Redflea: I get this in Gscript&#8595;
<script src='http://img84.imageshack.us/shareable/?i=cap201010201357.jpg&p=tl' type='text/javascript'></script><noscript></noscript>

You might be better off using Darkonion's approach...

DOOverclock - Easier Way to OC Your Droid 2 - Page 2 - xda-developers

 

[WalCs]

My 1.4GHz with Stagefright jumped up to 2757.

It didn't seem to actually improve performance any, though. So what in the world does it actually do?

It does nothing, just makes score looks better

 

[inssane]

What is the standard voltage number - stock?
Congrats to those with HUGE gains!!!

 

[Cilraaz]

What is the standard voltage number - stock?
Congrats to those with HUGE gains!!!

Stock is 56 for 1GHz, and honestly, I saw very little gain outside of quadrant. The phone still felt like it had the same performance in normal usage, so I just set it back to stock.

[edit: I'm beginning to question 56 as stock. I'll make a new reply with my reasoning.]