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.
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?]
Last edited by Cilraaz; October 20th, 2010 at 12:57 PM.
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.
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.
Last edited by Redflea; October 20th, 2010 at 02:43 PM.
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
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>
Last edited by Thornfullessrose; October 20th, 2010 at 02:05 PM.
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
Last edited by bizzshow; October 20th, 2010 at 01:43 PM.
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.
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...
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
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.
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.
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>
You might be better off using Darkonion's approach...
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.]
Last edited by Cilraaz; October 25th, 2010 at 12:26 PM.
The Following User Says Thank You to Cilraaz For This Useful Post:
Yes it a build properties edit. If you have root explorer navigate to system mount system rw then long press the build properties open it in a text editor. Scroll down and you will see options for stagefright they should read false change them to true save it. After a reboot you should have stage fright
Ughh, so I don't know if I just have a sad sad phone, or I'm doing something wrong. Every time I load the module, I edited the voltages and speeds to 1.2, as soon as I run the commands to run the module, the phone locks up for a second and immediately resets itself. Am I doing something wrong or is my phone just not good for overclocking? I read the original posts and I think I have the basic jist of it. I had an overclock D1 that I never had this much trouble overclocking. Any help would be greatly appreciated.
Ughh, so I don't know if I just have a sad sad phone, or I'm doing something wrong. Every time I load the module, I edited the voltages and speeds to 1.2, as soon as I run the commands to run the module, the phone locks up for a second and immediately resets itself. Am I doing something wrong or is my phone just not good for overclocking? I read the original posts and I think I have the basic jist of it. I had an overclock D1 that I never had this much trouble overclocking. Any help would be greatly appreciated.
So has anyone actually taken a look at any of the proc files, specifically /proc/overclock/mpu_opps? There's a setting in /proc/overclock/mpu_opps labeled as "vseld". It might make sense that these are the default voltage settings. If so, my mpu_opps file shows them as 62/58/48/33 for each profile top to bottom. It shows these values regardless of my current speed settings, so I'd imagine they're the default voltages for 1000/800/600/300, respectively.
If these are indeed the default stock voltages, they may be a reason why some people are having problems when trying to overclock. The scripts included with the package from the original post show lower default voltages.
Is there anyone a bit more knowledgeable on the matter that might be able to tell if I'm right or wrong?
Hi folks, I'm the Milestone Overclock guy. I just patched in support for Droid 2 in this beta version and I was hoping you could give it a try. I'm not sure the module will load and work because I don't have this phone. The module I'm using is exactly the same I use for the Droid X. The addresses are autodetected, so it should work nicely in D2 as long as the kernel accepts the module.
Already have it I'll see if I unload my module and reload your if it will work but I believe the modules are different so for the d2 you would have to use the module in this thread
Already have it I'll see if I unload my module and reload your if it will work but I believe the modules are different so for the d2 you would have to use the module in this thread
The module I posted in the OP is exactly the same as the DroidX module, except it has the memory addresses hard coded in for Droid 2, versus the one I posted for Droid X having the DX memory addresses hard coded. His new module autodetects everything and works on DX. It should therefore theoretically work for Droid2.
Please test this out...
This is so we can get official support for Droid2 in the Milestone Overclock kernel module. The modules I posted were patched/hacked and compiled against the OMAP kernel sources. Not the ideal situation, but it worked.
Tiago has cleaned up all the patches, and compiled the kernel against official Motorola kernel source. This is the right way!
All other Droid X/2 Overclock apps use Tiago's kernel module(the hacked version posted) to do the actual overclock. Lets get things working the right way!
And if you downloaded and paid for one of those other apps or just appreciate the ability to overclock, please donate to Tiago. He's the real reason you're overclocked right now. He doesn't really ask for donations like some do, so I am doing it for him. He is very deserving of the support of all who are overclocked on Droid X/2.
edit
just tried it works well getting 1850 in quadrant and 16.351 linpack scores any way to get it above 1.2
That's great! I'll publish it in the market soon.
To get higher frequencies you have to define custom rate/vsel in the settings (beware that rate is in khz), then move the slider to the far right.
Yes, I know, you can't define the entire frequency table in the app. The app was meant as a simple tool for beginners, but I see now that undervolting is something people really want, so I'll look into it.
So has anyone actually taken a look at any of the proc files, specifically /proc/overclock/mpu_opps? There's a setting in /proc/overclock/mpu_opps labeled as "vseld". It might make sense that these are the default voltage settings. If so, my mpu_opps file shows them as 62/58/48/33 for each profile top to bottom. It shows these values regardless of my current speed settings, so I'd imagine they're the default voltages for 1000/800/600/300, respectively.
If these are indeed the default stock voltages, they may be a reason why some people are having problems when trying to overclock. The scripts included with the package from the original post show lower default voltages.
Is there anyone a bit more knowledgeable on the matter that might be able to tell if I'm right or wrong?
Load Milestone Overclock from the market, and "cat /proc/overclock/mpu_opps"... You'll get the proper output.
The new kernel module writes to both... vseld was a byproduct of nadlabak/kaldaban having developed his patch on on the Milestone Froyo Leak... No source, just poking at it. Pretty sick if you ask me. So his patch did spit out a bunch of extra garbled stuff like all those 1111's and 000's... But it worked!!!
Should have updated the post but not 5 minutes after posting in tried to the custom rate and got 1.4 added some it works about to load the update and see if it works with it
I wanted to let everyone know that I've posted an app called QuickClock up on the market. It drastically reduces the amount of testing needed in order to find the best voltage settings. It's free for now, so snag it early.
Here's how it works: Find the absolute bare minimum vsel necessary at a given frequency that keeps the phone from crashing or turtling (but isn't necessarily "stable"). Slap that number and the frequency you used into the app, hit calculate, and BAM. You've got your battery-maximizing yet stable vsel recommendations.
Can't use this app to set them directly as I don't like the idea of packaging Tiago's work in my own app (at least not without talking to him first), but all those hours of testing and uncertainty will just fade away.
I'm using it like crazy now that I finally made it, and I hope you enjoy it too.
