Each phone is different. Its random too. I can run 1.45 easily and probably higher, but I don't. Others are at 1.1. But when we were on 2.1 I couldn't get nearly as high as everyone else. Just odd. But to answer your question its the difference in the OMAP processor during manufacturing that causes the difference in overclocking speeds.

 

WhWhat he said. I cann only get up to 1.15 until it Turtles on me.

 

You can probably get up higher, you just have to run higher voltage. As said, it's highly variable depending on the particular processor/production batch.

That said, I fooled with overclocking for a while... and finally realized that my day-to-day operations were really no faster, so I clocked it back down to stock and I have the O/C application on the phone for times when I might find it useful. With a custom ROM, this is a freakin' fast phone, so I don't really see the need to shorten the phone's life by running additional voltage through it.

 

I can run stable at 1400mhz only at the highvoltage setting. If you want to run high, you need to run the high voltage frequency and say bye bye to your battery life. Its a trade off for performance.

 

That's why I run the default frequencies with the voltage turned down. It's still instantly fast and my battery life is +++

 

I recall that you were going to experiment with lower voltage settings to see how much battery life improved. What was the lowest stable setting that you found and how much did your battery life improve?

 

It's gonna vary for each phone because they'll be more/less tolerate of the lower voltage.

300/600/800/1000 @ 24/30/44/50 for me is running stable. I don't have quantitative results but so far the battery life has been great. I'm on 6+ hours off the charger and moderate use, still at 70%. Not too shabby.

 

In all likelihood, you'd see a similar battery improvement from the maximum frequencies that a given voltage will support.

There are two schools to minimum power consumption: do the task using the minimum power draw necessary, or do the task as fast as possible despite a higher power draw. The reason the latter is often optimal is because the power consumption increase isn't linear with the frequency increase. I don't know specifically about the phone voltages since I haven't played with them much but most of the time you can get a 20-30% increase in frequency without a 20-30% increase in power consumption.

More info:

LessWatts.org - Saving Power on Intel systems with Linux

 

I think that there is a difference in the droid x's that were bought with 2.1 installed as soon as the phone was available and the droid x's that came preloaded with 2.2. I know my phone has mediocre battery life with average usage when some people get like 2 days, and I don't have anything running (just weather updated every 3 hours) and I was an early adopter. But the most I could oc mine was 1.1. I tried to sbf back to 2.2 in hopes to oc higher, but now I can't seem to root my phone. Freaking annoying.

 

Have you tried any of the 1.35GHz settings? I can copy my scale if you'd like, it's good and stable.

 

The max voltage is the same as it was for 2.1, the rest of the voltages are stock 2.2. You could use setCPU and set 400 min/ 1000 max to save on battery use but still have stock (or slightly better) performance and then bump it up when you want. Quadrant with a max of 1GHz is still around 1400, 1.35GHz is 1800+. If you use 400 min/max when the screen is off it will turn back on just as the phone starts to ring. Let me know how it works for you.


echo 66 > /proc/overclock/max_vsel
echo 1350000 > /proc/overclock/max_rate
echo 1 400000000 27 > /proc/overclock/mpu_opps (stock - 300000000 27)
echo 2 700000000 38 > /proc/overclock/mpu_opps (stock - 600000000 38)
echo 3 1000000000 50 > /proc/overclock/mpu_opps (stock - 800000000 50)
echo 4 1350000000 66 > /proc/overclock/mpu_opps (stock - 1000000000 56)
echo 0 1350000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 700000 > /proc/overclock/freq_table
echo 3 400000 > /proc/overclock/freq_table

 

1.15 is the most I can get at any voltage. After that = turtle. I actually forgot to bootstrap recovery and was stuck in turtle mode. It took 2 hours to log into google and download bootstrapper again. Annoying as hell.

 

I'm using jrummys overclock app. I'm at 1.35 low voltage. So far no issues. Its been 36hrs. Not bragging. No special rom just leaked 2.2.

 

Having the exact same issue. It's hard to believe these OMAPS were manufactured so differently. Battery life is go so far (24hrs) and it's pretty fast, but I don't see how it runs the same 1.15 at ULV and HV and them turtle modes at any value above 1.15????

Running rubiX 1.0, leaked 2.2, No theme, Jrummy OC app, SetCPU

 

Let me know if it works out for you.

 

Mine locks up at 1.45 at high voltage. I run stable at 1.3 on HV, although I've had a couple lockup/reboots at the slide unlock screen lately. I set boot to 1.2 at HV and have had no issues. Battery life seems no better or worse so far. BTW, with the new quadrant update I am getting scores over 2500 now. Just ran quadrant at 1.4 HV with a score of 2560.

 

im running medium voltage at the lowest default setting and got like 1610 on quadrant ive never had the phone this fast when i was running 1.1 or 1.2 it was actually slower does that make any sense