Airmaxx23
Android Expert
You are correct, for the most part. If you change the values you need to execute the setscaling100.sh again. If you're using root explorer you can just press on the file (after you edit it) and press execute.
-
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
You are correct, for the most part. If you change the values you need to execute the setscaling100.sh again. If you're using root explorer you can just press on the file (after you edit it) and press execute.
Put it in the refrigerator and see if you can hit 2.ghz
If we keep this up we're going to see X's with CPU cooler attached. LOL
Flagdown87
Newbie
I'm not getting $ su when I try to do the install? Have I lost superuser access? What am I doing wrong?
I too am one of the unfortunate few that cannot overclock past 1.15 but considering that, you can run that 1.15 speed at stock volt while undervolting rest which is a huge battery saver. Also this coupled with fission (which leaves me with over 200mb free mem 90% of the time) I couldn't be happier with overall performance of my launch day DX.
JrzDroid
Android Expert
1.47! thats awesome!
i keep rebooting at 1.4, i need to play with some numbers
Push that 1.5!
cowboys4life22
Lurker
I have successfully installed the overclock files on my phone, and ran the insmod command. Here is the problem, when I open setcpu, the current speed of processor only goes up to 1000. I can adjust sliders for max and min to say 1400000, but never is reflected on current speed. Everything checks out as far as I can see, can someone help me figure out why the current speed doesnt go up to 1400000.
The old guide for 2.1 overclocking suggests not to go over 96.
(http://androidforums.com/droid-x-all-things-root/145209-how-overclock-your-droid-x.html)
I personally feel 80ish is going too high. I like to keep it in the realm of safe
someotherguy
Well-Known Member
What does your setscaling.sh look like.
I'm guessing you missed one of the lines.
When you edited setscaling.sh did you change the second line to 1400000 which denotes the maximum clock speed.
AndroiDsepTIX
Lurker
here are my settings....everything runs fine until I run Angry Birds. Any suggestions on what i should change.
echo 69 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 400000000 29 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1350000000 69 > /proc/overclock/mpu_opps
echo 0 1350000 > /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
also I have tried running some of the 1.4 settings others have tried and I get an instant crash. Should I try increasing the voltage?
echo 69 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 400000000 29 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1350000000 69 > /proc/overclock/mpu_opps
echo 0 1350000 > /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
also I have tried running some of the 1.4 settings others have tried and I get an instant crash. Should I try increasing the voltage?
I've got mine set as follows...
echo 68 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 300000000 24 > /proc/overclock/mpu_opps
echo 2 700000000 35 > /proc/overclock/mpu_opps
echo 3 900000000 45 > /proc/overclock/mpu_opps
echo 4 1350000000 68 > /proc/overclock/mpu_opps
echo 0 1350000 > /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
It runs fine when I lock each frequency in set cpu and do the stress test, but it will randomly reboot, sometimes hours later when several programs are running. Today it did it while I had google talk, text msg, and pandora running. I think it's one of the middle freq, not max. Any ideas where I might be off? Like I said, all four frequencies ran the stress test no probs. If it comes down to it, I'll take a random reboot if it means I can run it at 1.35g.
edit....Angry Birds runs no probs...
cowboys4life22
Lurker
I did recheck the info inside the setscaling.sh file, and yes on the second line its at 1400000. This is what is in my setscaling.sh file exactly.
echo 65 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 65 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
I have did the rmmod overclock.ko to remove the overclock and the retry, even rebooted the phone, but still same thing. Setcpu displays 1000 MHz at top in white. Below it says scaling performance in white. 1400 max and 700 min in green, based on my sliders. Hope someone can help me fix this.
echo 65 > /proc/overclock/max_vsel
echo 1400000 > /proc/overclock/max_rate
echo 1 300000000 30 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 1000000000 45 > /proc/overclock/mpu_opps
echo 4 1400000000 65 > /proc/overclock/mpu_opps
echo 0 1400000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 300000 > /proc/overclock/freq_table
I have did the rmmod overclock.ko to remove the overclock and the retry, even rebooted the phone, but still same thing. Setcpu displays 1000 MHz at top in white. Below it says scaling performance in white. 1400 max and 700 min in green, based on my sliders. Hope someone can help me fix this.
Airmaxx23
Android Expert
Make sure the tab on the main setCPU screen is set to "on demand". Try moving the sliders up and down, this is what gets the values to display correctly for me.
someotherguy
Well-Known Member
Did you redetect device/speeds in setcpu
cowboys4life22
Lurker
When I try moving sliders,especially the min one the phone locks up and crashes. I went and changed from performance to ondemand. This last time when I switched from performance to ondemand, it frozed up and rebooted.
OMJ
Bazinga
sounds like your phone cant handle 1.4. Or at least not those settings.
cowboys4life22
Lurker
I did redetect the speeds inside setcpu, but still nothing has changed except max min readings. Also something to note, if I try running insmod right after fresh reboot in terminal editor it locks up phone and reboots. When I go into setcpu and move the sliders for max to 1000 and min to same then it will allow me to insmod without locking up. When my setcpu opens up its set already at max 1000, min 300.
So, can anyone explain this Super Turtle syndrome, what it is or how to potentially bypass or trick it? I can get to 1.2ghz @ 68 stable without going into turtle mode, however, once I go higher than that, even by 10mhz to 1.21ghz it goes into a stable turtle mode. This is regardless of what I set the voltage. Any ideas? Is my phone just a dud with a cap of 1.2ghz?
I've got one of those notorious launch day X's (well, I got in the mail after that first weekend and my build date is 28/10) and Beesley's update.zip crashed my X after trying a second quadrant run. I'm playing it more conservative now and have the original first two tiers the same as stock and linearly interpolated the voltage for the third and fourth tiers, which are 900MHz and 1.2GHz. Running fine now, but I'll try pushing it to 1.3 after I get home from work.
cowboys4life22
Lurker
I figured it out, my phone wouldnt handle the 1400, I have it stable right now at 1195, wonder how much higher I can go.
OMJ
Bazinga
Sounds like 1.2 is your cap to me. My phone seems to turtle at anything over 1.5. 1.51 is instant turtle every time. Some are turtling as low as 1.16 I think. I wouldnt call your phone a dud since it was never intended to go past 1.0ghz but it doesnt sound like it takes to overclocking well.
