Still holding strong at 1.4 GHz, I broke the 1900 mark with a Quadrant test this morning.
I'm so jealous but good for you man. I love seeing higher and higher quad scores since it continues to highlight the potential of the droid x (even if it's not mine
).
Unfortunately, I'm in the camp with folks that can't oc past 1.2. I can do 1.25 at 68 vsel but it will eventually freeze and reboot. 1.3 won't even work for one second before it freezes.
Here is my current (seemingly stable) setup running at 1.2ghz:
echo 68 > /proc/overclock/max_vsel
echo 1200000 > /proc/overclock/max_rate
echo 1 300000000 27 > /proc/overclock/mpu_opps
echo 2 700000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 50 > /proc/overclock/mpu_opps
echo 4 1200000000 68 > /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
However, I also ran essentially the same setup but with the max set at 1.175ghz at 64 vsel with no issue.
While I'm all about speed, I think I might go back to the 1.175ghz setup. It's only a little slower (1591 quad score versus 1643 at 1.2ghz) but uses less voltage, which will probably better on my battery.
Besides, I did this primarily for better mp4 playback using rockplayer, which plays most of my files fine but does get choppy with certain rips I've made. I played one of the chopper rips a 1.175ghz and it was choppy for just the first few seconds and then played fine the rest of the way (versus intermittent choppiness at stock 1ghz). I'm okay with that for now.