Works on battery mode on Sprint Touch Pro 2. Max overclock of 768 without hangup. Exactly as when running Android!

Thank you for this wonderful app!

Originally Posted by demonlordoftheround

Works on battery mode on Sprint Touch Pro 2. Max overclock of 768 without hangup. Exactly as when running Android!

Thank you for this wonderful app!

How are you testing stability...do you run it then exit and send the phone to sleep or standby for a few minutes?
Mine can go to standby (manually) but if I leave it there a few minutes then it wont come back.

Are you going to add "auto-apply at startup"?

Is it ok to cook this app into a rom?

Originally Posted by shaolin95

How are you testing stability...do you run it then exit and send the phone to sleep or standby for a few minutes?
Mine can go to standby (manually) but if I leave it there a few minutes then it wont come back.

Just happened to me as well. Going to set to 710 MHz and continue testing.

Sure you may cook it into your rom.

The reason "auto-apply at startup" is not enabled, is because it doesn't work on battery yet. Even for the guys where the phone doesn't hang, the overclock will be undone when on battery.

Or does the overclock stay active for some people on battery? I'd think it at least goes back to 528MHz.

Originally Posted by NetRipper

Sure you may cook it into your rom.

The reason "auto-apply at startup" is not enabled, is because it doesn't work on battery yet. Even for the guys where the phone doesn't hang, the overclock will be undone when on battery.

OK, great job anyway! That's a big step in overclocking Rhodium.

Originally Posted by shaolin95

How are you testing stability...do you run it then exit and send the phone to sleep or standby for a few minutes?
Mine can go to standby (manually) but if I leave it there a few minutes then it wont come back.

That might be the same issue as when on battery. When it comes out of standby, it will try to set the clock speed again, causing the device to lock up. If you go to standby and go out of it right away, the device doesn't actually go into full-standby yet (it takes at least a few seconds before it does).

You can test stability by using SPB benchmark or something similar that does lots of calculations. I.e. I can clock it at 750MHz, but when I run a benchmark tool, it will hang. At 710MHz I'm stable.

Originally Posted by NetRipper

That might be the same issue as when on battery. When it comes out of standby, it will try to set the clock speed again, causing the device to lock up. If you go to standby and go out of it right away, the device doesn't actually go into full-standby yet (it takes at least a few seconds before it does).

You can test stability by using SPB benchmark or something similar that does lots of calculations. I.e. I can clock it at 750MHz, but when I run a benchmark tool, it will hang. At 710MHz I'm stable.

I get the very same results on Rhodium (TP2) Verizon with MR2 rom in Battery mode.

If I do the quick standby (in and out) it works.

Letting the device go to sleep on its own locks the device and you have to do a battery pull to get it back.

Nice to see it come this far.

I set it to 710MHz and worked fine, unplugged the power cable and it stayed at 710MHz, but came back to check it about an hour later and it reverted to 528MHz as NetRipper said.

This is some great work NetRipper, hopefully you can figure out what in WinMo is reseting it on battery power.

Thanks again NetRipper.

Originally Posted by Epsilion

I set it to 710MHz and worked fine, unplugged the power cable and it stayed at 710MHz, but came back to check it about an hour later and it reverted to 528MHz as NetRipper said.

This is some great work NetRipper, hopefully you can figure out what in WinMo is reseting it on battery power.

Thanks again NetRipper.

Did the device go to standby at all?