• 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)

tomsfacts said:
Ya, but if you change your clock speed while set cpu is open in the background then it wont go to your new clock speed in the app. Just kill it with a task killer then restart
Click to expand...
Didn't see that he was on the leak, but there are several warning threads about this exact thing
 
Airmaxx23 said:
I just took over the number 8 spot with my 1931 qadrant...sweet!!
Click to expand...

weelllll actuuuallllllyyyyyy


attachment.php
 

Attachments

  • 1.4.jpg
    1.4.jpg
    133.5 KB · Views: 301
its 1.42 and can you please explain about the voltage?

like i see you had for ur 1.4 at 65 but i had to have mine at about 70. why is this difference? whats the highest recommended not to go over?
 
ok after i installed the file i edited setscaling.sh to the slots and voltages i wanted. so i ran the command:
insmod /system/lib/modules/overclock.ko
setscaling.sh

and my phone rebooted right from terminal. so i upped the voltage, got a reboot after running the command again. so i went to the stock slots and kept the barely lower voltage (55/45/35/25) and the phone rebooted after the setscaling.sh command. any ideas why?
 
Been running this for a few hours now: (1.3) really quick and stable.


Code: 
echo 64 > /proc/overclock/max_vsel
echo 1300000 > /proc/overclock/max_rate
echo 1 300000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 50 > /proc/overclock/mpu_opps
echo 4 1300000000 64 > /proc/overclock/mpu_opps
echo 0 1300000 > /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

1.6GHz worked was extremely stable for me, but extremely turtle. Ideas on voltage? Whats an average amount to increase? 3?
 
Question: Are the stock voltages scaled?

I think I remember in 2.1 somebody said that 300, 600, 800, and 1000 mHz all ran at 66vsel. Is that true for 2.2? Does the voltage stay constant at 56 or 58 or whatever it is regardless of the cpu speed?
 
tomsfacts said:
Airmaxx23, do you mind letting us see your values
Click to expand...


echo 69 > /proc/overclock/max_vsel
echo 1420000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 9500000000 45 > /proc/overclock/mpu_opps
echo 4 1420000000 69 > /proc/overclock/mpu_opps
echo 0 1420000 > /proc/overclock/freq_table
echo 1 9500000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
 
1.3gHz @ 60 vsel has been stable for 20 hrs. Battery life is better (I got 20-25 with 2.1, 18-20 with rubiX 0.5, and I'm averaging about 25 hrs with overclock. I think it's cause of the voltage scaling)

Testing:
1.4 gHz @ 68,
900 @ 44,
600 @ 30
300 @ 24

Hoping to squeeze out some more battery life, but also trying to find threshold or OC.

Quandrant 1815 and 1810. Only done 2 runs, so it's not bad.


Airmaxx23 said:
1.42 GHz, for now.

snap20101020_161042.png
Click to expand...

Nice!

Hey just for giggles you should run your benchmark with stagefright enabled.
 
OK so someone "splan this to me Lucie", this file ran awesome. I didn't realize my mpu and freq didn't match.

echo 68 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 400000000 30 > /proc/overclock/mpu_opps
echo 2 600000000 35 > /proc/overclock/mpu_opps
echo 3 800000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 68 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

I changed them so that everything is the same between mpu and freq_table.

Now that is all matches I get consistent reboots. Before it was as stable as all getout. :confused::confused::confused:
 
droid_freak said:
OK so someone "splan this to me Lucie", this file ran awesome. I didn't realize my mpu and freq didn't match.

echo 68 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 400000000 30 > /proc/overclock/mpu_opps
echo 2 600000000 35 > /proc/overclock/mpu_opps
echo 3 800000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 68 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 900000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

I changed them so that everything is the same between mpu and freq_table.

Now that is all matches I get consistent reboots. Before it was as stable as all getout. :confused::confused::confused:
Click to expand...

Please post the newly corrected code, but I'm guessing that it's because it has issues with trying to do 45v @ 900Mhz
 
pandapaul said:
Please post the newly corrected code, but I'm guessing that it's because it has issues with trying to do 45v @ 900Mhz
Click to expand...

Code: 
echo 68 > /proc/overclock/max_vsel 
echo 1400000 > /proc/overclock/max_rate
echo 1 400000000 30 > /proc/overclock/mpu_opps 
echo 2 700000000 35 > /proc/overclock/mpu_opps 
echo 3 900000000 45 > /proc/overclock/mpu_opps 
echo 4 1400000000 68 > /proc/overclock/mpu_opps 
echo 0 1400000 > /proc/overclock/freq_table 
echo 1 900000 > /proc/overclock/freq_table 
echo 2 700000 > /proc/overclock/freq_table 
echo 3 400000 > /proc/overclock/freq_table

so I know @800 45 works, I guess I will go with that or go to 1000 @ 45?
 
On an undervolting sidenote, 19 @ 300Mhz runs perfectly stable for me. That's exciting. I'm pretty happy with that in combination with the top end of 66 @ 1.35Ghz. Still working on the middle frequencies and hoping for best of both worlds in terms of performance and battery life. I can run at 1.45Ghz, but I think I'll probably stay with the rock solid 1.35Ghz.
 
Day 1 Launch Droid X. 1.3 ghz 63 vsel max

the best stability test for me is running PSX for Droid, ff9 rom....looping from bootup -> intro cgi's over n over hehe works like a charm
 
tom108 said:
That has been discussed. It is a built in safety feature so you don't get stuck in a bootloop after choosing a bad configuration. there is a command to make it permanent but i don't really suggest it. just use gscript to run the overclock commands after a reboot.
Click to expand...

Gscript doesn't work for me :-( it looks like it does but it isn't executing the sh file.

time to start moving up the speeds:p
 
So I'm running 1.45ghz now at 73 vsel's... anyone think that is too high voltage? I think its fine and the temp is running fine too. Just wondering if anyone has an opinion. Its stable too.
 
Would installing this part mess anything up if I have the clockword mod bootstrap recovery installed?

<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>

I would hate to have to flash my phone using the SBF for the third time if something goes wrong.
 
Do not do that optional step, because it will overwrite what clockworld mod boostrap does, which will in effect brick phone, but can still recover via System sbf. We have to find a new way to include that info inside the install-recovery.sh
I tried to include at end of file specified before, but it won't work. Can someone find out how to include in file to get it too work on bootup.
 
You must log in or register to reply here.
Back
Top Bottom