[Windows Mobile Apps and Games] 5318008:
Results of speed and software combination testing

I've finished quite a bit of testing at different speeds and with different software combinations running, primarily to see what would cause a freeze or SoD on my phone.

I have a T-Mobile Touch Pro 2 set up with OliNex HardSPL 0.85, flashed to a stock, non-branded (and not T-Mobile-approved) HTC 2.07.401.1 (80303) WWE ROM that includes Sense 2.5.20121225.0, OS version 5.2.21887 (21887.5.0.86), and Radio version 4.49.25.91. It has the recent HTC SMS hotfix applied, and also uses the T-Mobile keyboard fix, both from official cabs.

I had ESET Mobile, cleanRAM, and S2Shutdown processes running on the system for all tests. I also had WiFi-On-Demand enabled, BlueTooth off, Phone Radio on, and Cellular Data disabled.

Things I found not to make any difference:

Battery vs. AC vs. USB power.

Sense vs. Windows Mobile vs. no UI.

S2U2 vs. WM lock vs. no lock.

Leaving the OC program running vs. Set OC and close. (Somebody said they were able to escape SoD by doing this, so I tried it too.)

Camera in background vs. other programs in background vs. no programs in background. (Somebody said they escaped SoD by running camera in background, so I tried it too.)

For stock vs. 604 vs. 710 vs. 768MHz, no noticeable changes in heat output or battery drain.

Given all the above, here's what I found:

At 604MHz, I was able to OC, sleep, OC, sleep, OC, sleep, and so on indefinitely. No SoD issues at all on 604MHz.

At 710MHz and 768MHz, I ran stable, but experienced the SoD after OC, sleep, OC, sleep. The other times I'd tried this and gotten away with it, I don't believe I let it sleep long enough.

At 787MHz, I was able to keep operating for several seconds after OC, but always got a freeze after a few seconds.

I didn't try any underclocking at all, or any OC speeds other than 604, 710, 768, and 787MHz, and anyways I'm much more interested in OC than UC.

I also tried running S2U2 after using the S2U2 Settings tool to change Advanced>Don't Suspend Power>"ON" to try and keep my Rhodium from sleeping, but it didn't seem to work, as the clock would still reset after a time spent blank.

I used Slide2Shutdown to force sleep in all instances other than testing the S2U2 Settings for Don't Suspend Power. For that one I let it blank out on its own.

I didn't run any benchmarking tools as I was mostly searching for stability, rather than metrics.

I haven't tried that registry-setting thing yet, but if it works, or there's any other way to avoid SoD, and also if there's a silent-run version of the OC program developed, then S2U2 Settings tool has an option to run a specific program when the phone gets unlocked. It would be simple to point that at a run-silent version of the OC program to re-overclock each time the phone is unlocked. There are probably better options, like using wake events and such, but I thought I'd throw that out anyways.

Other than all that, nothing for me to add other than what everyone else is saying about how nice it is to run at 768MHz, and also thanks, and keep it up, it's great work so far.

EDIT: Somebody a few pages back was asking me about my avoidance of SoD after multiple OC/sleep/OC/sleep cycles, and I think it was that I hadn't let my phone sit long enough the previous times, as it reliably locks up after two OC/sleep cycles with anything higher than 604MHz.