InfamousDX
Lurker
My release day X is up to 1.175 but that's about it. Trying my damnedest to get to any higher and it just won't take. I get instant turtle mode
-
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
JetCrosset
Lurker
Got my release day X to 1.38, had to bump the voltage up to 72 on the high end though.
Yes, I've tried killing tasks, clearing cashe, rebooting first....you name it. 1.15 is the most it'll give me.
I did download the new Droid x/2 overclock app and tried running all the different configs (Low voltage, medium voltage, high voltage) but same results. A bit disapointing, I guess they got better at making the processors the later it got.
InfamousDX
Lurker
Can both of you guys paste your setscaling.sh? I want to try your values; maybe they'll work. Right now i'm rock solid at 1.175 62vsel
whats that read? cant really see. and what overclock speed was used?
Mine didn't change either until I discovered there are two setscaling.sh files. The one you must change is located at /system/xbin/setscaling.sh
Be sure to set root explorer or whatever you use to edit with to r/w. When you have completed your changes, your system will probably save the original as setscaling.sh.bak. Once you save your changes, then you can type insmod /system/lib/modules/overclock.ko to install the newly changed file, then in the next line type setscaling.sh to activate it. Hope this helps. Be sure your spacing is exactly like I typed it,(space between insmod and the / ) and don't use the italics.
No joy.
Even upon reboot, which should erase the effects of the overclocking, I can no longer see the CPU speed change via SetCPU.
It's locked at 1000 no matter what I try.
Try hitting the setting button or whatever it is, the one next to the home button on the physical keys, then hit device selection and auto detect. That's worked for me before.
About JRummy's app. I got a chance to use it now and it seems, if I'm reading it right, that even at the lowest voltage the voltage is pretty high. This is what the read out gave me.
Code:
#cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1200000000 opp_id=4 vseld=62 vsel=62
mpu_opps[3] rate=1000000000 opp_id=3 vseld=58 vsel=57
mpu_opps[2] rate=850000000 opp_id=2 vseld=48 vsel= 54
mpu_opps[1] rate=400000000 opp_id=1 vseld=33 vsel=52
Outlaw71
Android Expert
im tryin out that over clock app and i still cant get above 1.1. my values that work that i have without the app
echo 62 > /proc/overclock/max_vsel
echo 1120000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 4 1120000000 62 > /proc/overclock/mpu_opps
echo 0 1120000 > /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
echo 62 > /proc/overclock/max_vsel
echo 1120000 > /proc/overclock/max_rate
echo 1 400000000 25 > /proc/overclock/mpu_opps
echo 2 700000000 34 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 4 1120000000 62 > /proc/overclock/mpu_opps
echo 0 1120000 > /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
tomsfacts
Newbie
If it were me, I would have made the changes in Bold and see if it boots, if it keeps looping then try adjusting one voltage level at a time until you see something stable
tomsfacts
Newbie
I don't use the app, I use the method at the beginning of this thread, and use root explorer to edit the values
I applied the settings from the app then went into my terminal and put in the code
cat /proc/overclock/mpu_opps
which returns a read out of your current frequency and voltage settings like I had in my post.
tomsfacts
Newbie
There really isn't a "correct" value, your either giving too much or too little voltage for the specific echo value. I would change them all at once, execute the file, see if it reboots on me, if it does, I would raise the voltage values on the low end by 2 each and maybe 1 or 2 on the top end.
Rinse, and repeat
tomsfacts
Newbie
If it is running smooth it could have enough voltage for what you are running on, but maybe it won't have enough voltage when you are running a cpu intensive app, or maybe it has too much, its hard to say, but just pay attention to when it crashes, and then adjust it based on if it was during high performance or low performance.
I assume you mean SetCPU, and I just did that.
Still locked at 1000.
It sees that the max value is 1100, but even if I slide both sliders up to 'force' it, it still stays at 1000.
tomsfacts
Newbie
Throw up your script, maybe there are some errors
I'm also limited to 1.15 using JRummy's app. Using low voltage now and it's stable. Have yet to try manually editing and applying setscaling file. I was able to quad a 1600 on this 
DX 2.2 OTA deodexed and themed. I'd love this thing to be stable at 2 but as much as I use it the battery would probably only last an hour!
DX 2.2 OTA deodexed and themed. I'd love this thing to be stable at 2 but as much as I use it the battery would probably only last an hour!
im running 1.45ghz pretty stable. even through idle at night. kinda of tinkering with voltage tho to try to get as low a voltage as i can and remain stable
i clocked at 2ghz but was a turtle none the less
JrzDroid
Android Expert
I messages you about your setup to see if I can run either