LexusBrian400
Android Enthusiast
Its actually not a big jump at all. If you check back to when we had OC on 2.1, I believe stock was 68 Or close to it. Check the thread
-
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)
- Thread starter FreeWELL
- Start date
-
- Tags
- motorola droid x
Its actually not a big jump at all. If you check back to when we had OC on 2.1, I believe stock was 68 Or close to it. Check the thread
Phantom_DroidX
Newbie
So far I am still going with the 25,35,45,50 and no reboots or lock ups yet I am about to try lower voltage so we will have to see how it goes.
Napalm
Android Expert
Yes, its surprising what a few hundred Mhz will do. CPU intensive apps are running much faster. Like Titanium Backup for example, it flies through backing up/restoring batch apps.
I <3 OC and the people who say its not needed must not know how to do it
I'm kidding of course, but I just dont understand why some ppl are so against overclocking. Its always made computers in general faster and perform better.
Fixed it for you.
Sorry, had to. I always try to overclock any computer I have at least slightly except for my laptop. its about getting that extra amount out of it. Like tuning a car.Curious, any major detriment to battery life. This is my only holdup not that I can't burn some, but I don't want to OC and then end up with a 7 hour phone.
Currently running stable at a max of 1.4 Ghz with 68 vsel.
Details:
1400 / 68
1000 / 49
700 / 34
300 / 25
Still testing each voltage for stability through long SetCPU stress tests, but is looks as though my results are quite good. For whatever it's worth, I'm scoring quadrants in the 1700's and Linpacks around 19. Actual performance is, of course, quite snappy. I attempted 1.5 Ghz, but couldn't seem to get there with any reasonable voltage increase.
EDIT: 300 / 15 is a weak point of stability. Testing further.
--> kicked it up to 25v and blasted it with successive quadrants and stress tests. Running stable and solid.
--> please see my next post: http://androidforums.com/droid-x-al...rnel-module-w-instructions-2.html#post1767139
Details:
1400 / 68
1000 / 49
700 / 34
300 / 25
Still testing each voltage for stability through long SetCPU stress tests, but is looks as though my results are quite good. For whatever it's worth, I'm scoring quadrants in the 1700's and Linpacks around 19. Actual performance is, of course, quite snappy. I attempted 1.5 Ghz, but couldn't seem to get there with any reasonable voltage increase.
EDIT: 300 / 15 is a weak point of stability. Testing further.
--> kicked it up to 25v and blasted it with successive quadrants and stress tests. Running stable and solid.
--> please see my next post: http://androidforums.com/droid-x-al...rnel-module-w-instructions-2.html#post1767139
someotherguy
Well-Known Member
Run Instructions
adb/terminal:
$ su
# insmod /system/lib/modules/overclock.ko
# setscaling.sh
Does the "insmod /system/lib/modules/overclock.ko" need to be run after reboot/changes or just the setscaling.sh
adb/terminal:
$ su
# insmod /system/lib/modules/overclock.ko
# setscaling.sh
Does the "insmod /system/lib/modules/overclock.ko" need to be run after reboot/changes or just the setscaling.sh
Airmaxx23
Android Expert
Just after a reboot. You can change the setscale values with root explorer and then just execute setscale when you're done.
someotherguy
Well-Known Member
How are you changing with root explorer?
I can view the script or execute, but it doesn't seem to want to let me edit it. I made sure to mount rw.
I can view the script or execute, but it doesn't seem to want to let me edit it. I made sure to mount rw.
Airmaxx23
Android Expert
Long press on it and then scroll to the bottom, once you edit it save it and then "execute".
someotherguy
Well-Known Member
Thanks! Scroll further. I'm an idiot.
OMJ
Bazinga
I'm so jealous. Anything highet than 1.15 for me and my phone goes into turtle mode. I used 68 vsel and couldn't even get to 1.2. My D1 was such a champ, looks like my DX is a dud
man its crazy how inconsistent TI chips are. I think 1.45 might be my ceiling or close to it. I tried 1.5 and I didnt last very long before I got a reboot.
Yes, they do the same thing.
setscaling.sh is all stock settings
setscaling100 is stock voltage w/100mhz increase at all frequency slots
Neither is a "stock" file to the phone. They are just simple scripts that tell the overclock.ko kernel module what frequency/voltage to run.
tom108
Android Expert
I'm so jealous. Anything highet than 1.15 for me and my phone goes into turtle mode. I used 68 vsel and couldn't even get to 1.2. My D1 was such a champ, looks like my DX is a dud
up to 1.45 but suffering reboots. have not found a good setup yet. my D1 was awesome and could take any LV or ULV kernel and i had no problem with any OC level but my DX seems to be a little more picky.
So once we run the first set of commands edit the setscaling.sh that was loaded?
Thanks!
Airmaxx23
Android Expert
Yes you can, I use root explorer to edit the setscale and then just execute it afterward.
It might work as-is. If not, someone will need to do the Milestone Overclock Disassembly Process and find out what the three memory addresses are.
A start would be running the following in terminal/adb:
Code:
# busybox grep omap2_clk_init_cpufreq_table /proc/kallsyms
c00489e0 T omap2_clk_init_cpufreq_tableDo you get c00489e0 as well? If so, the module should work as-is. If not, someone will need to do the disassambly process completely.
If someone with a D2 is serious about getting this running, PM me and I'll help out.
1000@56 under 2.2
1000@66 under 2.1
I think we can safely say that is why Froyo has had better battery life than 2.1 did. Could also by why a lot of people are having problems. 1000@56 might not be stable for all.