Originally Posted by pio_masaki (Post 604139)

I know this is a little bit late, but of my two apaches, my older qwest only managed 520 stable, 624 would fail on benchmarking, or after an hour of normal use. My newer sprint apache runs 624 all day long and can run 633 with some moderate benchmarking time, 700 whatever instantly locks up.

Technically speaking, up to 624 is not overclocking the cpu in these, as these cpu classes are rated up to 624, however they take the "mid grade" cpu's that don't run at 624 but can run fine at say 520, and put them in machines meant to run at 412 or whatever. Because of this, your milage may vary from machine to machine, just as it does in any other instance of overclocking. This was done with x-cpu scalar and so it doesn't really belong here, but it does have some relevance.

I can't use the scaling feature of x-cpu as it locks me up, so I will be trying out this option and see what happens.

Oh and I'm pretty sure HTC ditched intel cpu's after the 6700, so anything meant to interfere with the cpu speeds for a 6700 or earlier intel won't work on a 6800 or higher, gonna have to find something new to play with when I finally upgrade.

Originally Posted by pio_masaki (Post 605058)

Ah well I figured you all prolly knew that already, but its all I know =P