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
Last edited by FreeWELL; October 19th, 2010 at 11:48 PM.
The Following 8 Users Say Thank You to FreeWELL For This Useful Post:
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.
Sorry about the link... i fixed it. Please check that out... sounds like your module isn't loaded. try the run steps again... i can't go deep into troubleshooting right now.. got a screaming newborn I have to attend to..
Amazing!! Thanks so much for all your work, guys!!!
Running at 1.2Ghz atm, and everything seems to be running perfectly =) keeping an eye on the temps, but it looks as though it's going to remain stable!
what info could I post that would be of any help to anyone?
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.
Same comands. And I'm running at 1.3 it's been stable but I bumped the voltage up to 63 no heat issue lock ups of anything
What I am not understanding from the OP is how to get it from stock parameters to 1.3 and to edit the voltage. I just don't wanna run commands and not know.
What I am not understanding from the OP is how to get it from stock parameters to 1.3 and to edit the voltage. I just don't wanna run commands and not know.
You have to edit the setscaling.sh. Here's an example file, which would run the phone at 400/700/900/1100MHz (1.1GHz max):
Line 1 is the maximum voltage the phone will pass to the CPU.
Line 2 is the maximum CPU speed.
Line 3 through 6 are different CPU speed in Hz (from idle up to 100% usage) with voltages (the secondary two-digit number).
Line 7 through 10 are the same CPU speeds in kHz (minus the last three zeros from lines 3 through 6, to put it simply). Note that they are in reverse order. I would assume this is due to how the OS reads the mpu_opps table vs how it reads the freq_table.
What values will be stable for your phone will depend on your individual handset. Just like with a desktop CPU, each handset's CPU is slightly different and will handle overclocking better or worse at different speeds/voltages.
The Following 3 Users Say Thank You to Cilraaz For This Useful Post:
You have to edit the setscaling.sh. Here's an example file, which would run the phone at 400/700/900/1100MHz (1.1GHz max):
Line 1 is the maximum voltage the phone will pass to the CPU.
Line 2 is the maximum CPU speed.
Line 3 through 6 are different CPU speed in Hz (from idle up to 100% usage) with voltages (the secondary two-digit number).
Line 7 through 10 are the same CPU speeds in kHz (minus the last three zeros from lines 3 through 6, to put it simply). Note that they are in reverse order. I would assume this is due to how the OS reads the mpu_opps table vs how it reads the freq_table.
What values will be stable for your phone will depend on your individual handset. Just like with a desktop CPU, each handset's CPU is slightly different and will handle overclocking better or worse at different speeds/voltages.
PERFECT! That's the link up I needed. For some reason my brain wasn't thinking to edit the file itself, but to enter commands.
I haven't edited files since one of the earlier 2.1 bugless beasts on the D1, and that was one time to remove some included scaling parameters.
Thanks!
omg how are you guys doing that!!! mine just stays at 1000mhz after running the commands. i wanna know the same thing inssane wants to know.
NEVERMIND↑
Last edited by Thornfullessrose; October 20th, 2010 at 09:25 AM.
Yeah I had to run 1.2 at 59 but that's number basically is an amount of juice your phone sends to your cpu at that speed. That's why you don't want to go to high and if you drop it to low you can get reboots. Thus look for excess heat which could indicate your sending much power to it. Lockup and instability could mean not enough juice or your just running it to high
Yeah I had to run 1.2 at 59 but that's number basically is an amount of juice your phone sends to your cpu at that speed. That's why you don't want to go to high and if you drop it to low you can get reboots. Thus look for excess heat which could indicate your sending much power to it. Lockup and instability could mean not enough juice or your just running it to high
I know what the setting/number does, what I'm looking for is how it correlates into voltages. Obviously we aren't pumping 59 volts into our phones, lmao.
I know what the setting/number does, what I'm looking for is how it correlates into voltages. Obviously we aren't pumping 59 volts into our phones, lmao.
The CPUs most likely have a base voltage and the numbers we're using in the script are likely +mV values. At least that would be my guess.
The Following User Says Thank You to Cilraaz For This Useful Post:
You have to edit the setscaling.sh. Here's an example file, which would run the phone at 400/700/900/1100MHz (1.1GHz max):
Line 1 is the maximum voltage the phone will pass to the CPU.
Line 2 is the maximum CPU speed.
Line 3 through 6 are different CPU speed in Hz (from idle up to 100% usage) with voltages (the secondary two-digit number).
Line 7 through 10 are the same CPU speeds in kHz (minus the last three zeros from lines 3 through 6, to put it simply). Note that they are in reverse order. I would assume this is due to how the OS reads the mpu_opps table vs how it reads the freq_table.
What values will be stable for your phone will depend on your individual handset. Just like with a desktop CPU, each handset's CPU is slightly different and will handle overclocking better or worse at different speeds/voltages.
ah well.... even after this, i do not get it at all. guess i will have to wait for something simpler.
Wow wtf?! Hmm, you did up the other values as you went up, unlike me. Maybe if I changed mine too it would work. (ie. echo2, echo 3 etc)
Gonna test now.
If you're only increasing the maximum frequency (lines 2, 6, and 7), then you only need to increase the max voltage (line 1) and voltage for the maximum frequency (line 6). Increasing voltage to the intermediate speeds without increasing those speeds really doesn't do anything except stress the CPU harder when it's trying to relax.
If you're only increasing the maximum frequency (lines 2, 6, and 7), then you only need to increase the max voltage (line 1) and voltage for the maximum frequency (line 6). Increasing voltage to the intermediate speeds without increasing those speeds really doesn't do anything except stress the CPU harder when it's trying to relax.
Right, but I wasn't refering to changing the voltages. I was refering to the different speed steps. He changed his speed steps when he went to 1.3, where I did not, I left them at what they were for 1.2. But I think I found the problem, it was something else I missed.
EDIT: Ok I got 1.3 running nice and stable. Walcs, can you please tell me your voltage max for 1.4? Thanks ahead of time.
Also, why the hell did this forum disable tapatalk? What a pain in the ass.
Last edited by n0yd; October 20th, 2010 at 10:33 AM.
I'm also curious as to what voltages people are using for 1.3 and 1.4GHz. Right now I'm running 1.2GHz @ 59. A 470 second stress test hit 38*C max (while charging) with no errors. My Quadrant scores (my usual triple test) were 1708, 1632, and 1622. I'm not sure where that 1708 came from because I haven't been able to duplicate it.
Also, does anyone know what kind of maximum temps to avoid? I don't have much specific knowledge of the Droid hardware or ARM processors in general, and I really like to know my boundaries before I do too much.
Damn, even 1.25 at 60 and 61 hard locks instantly. I guess my phone just isn't that great. And to think this is my 5th D2, lmao.
Could it be because im not upping the other values as I go up, just the max values? Im leaving the other settings at what I had them at for 1.2Ghz.
I have had several D1 replacements and I have had ones that could run 1.25 std voltage - 1.2 ultra low voltage, with no issues.
Sometimes it was the ROM that failed on certain kernels and sometimes the phone. I had one phone that couldn't go past 1ghz and another that could only run standard voltage at 1.1ghz.
I am looking at the 1.4 quadrant and my pants just got tight, lol.
Can't wait to get home and do this - no time to do it at work, even though I could.
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
Last edited by bizzshow; October 20th, 2010 at 11:25 AM.
The Following User Says Thank You to bizzshow For This Useful Post:
Droid 2 Overclock(Kernel Module+Instructions)
