Overclock TP2 in WM?

[aguenter322]

I've cabbed up oruam's utility for those that would like it.

The CAB (as of 1.0d) should install everything you need to get going, including copying the Msm7kClockLib DLL to the Windows path.

The installer will ask whether you want to install to the Device or Storage Card; it does not matter which you choose as only support files are installed to that location. "Storage Card" is recommended, just to keep everything together and tidy.

* This CAB forces installation of certain files to \Storage Card\Program Files\SetCpuSpeed for safety purposes. If your locale doesn't use \Storage Card for the SD path or you don't have an SD card this CAB won't work for you.

* Use the SetCpuSpeed shortcut in your start menu to set clock speeds and modify the polling interval. (requires MortScript)

* Modify the polling interval (CheckTime) with caution. If you're experiencing SODs you can attempt to lower it from the default (200), but beware that this comes with a price of increased CPU usage of the SetCpuSpeed process. So far those with SOD issues have had some luck with a value of 150.

If your device fails to boot due to an unstable clock speed, pull the SD card and soft-reset. After WM boots completely (and you get the error message about SetClockSpeed not being found) reinsert the SD card, run the SetCpuSpeed shortcut from the start menu and choose a lower speed.

Huge thanks to oruam and everyone else working to make this stable, the script was great but now that we have a native process it's even better! Without the MortScript overhead we no longer have the 1-2% constant CPU utilization and can squeeze even a few more MHz out of our Msm7k's.

Uninstallation/Upgrade procedure:

Killing oruam's process causes the device to hang, and because the uninstaller kills the process to remove the executable...well, you see the problem I'm sure.
To easily uninstall (or upgrade) the CAB without problems perform these steps in order:

1) Pull SD card
2) Soft-reset
3) After WM/Sense/etc has loaded completely (and you get the error message about the shortcut target SetCpuSpeed.exe not being found), insert the SD again
4) Uninstall or install new version of CAB

-----------------------------

* SetCpuSpeed-1.0d.cab
- Installs the required DLL (from Netripper's Msm7kCpuSpeed v2) to \Windows
- Queries user for initial settings and starts oruam's utility after installation, no soft-reset needed

* SetCpuSpeed-1.0c.cab
- Added polling interval (CheckTime) setting to GUI

Post on XDA: http://forum.xda-developers.com/show...postcount=1000

[meechieervin]

thanks for the cab its working great on my tp2 thanks again

[jerryyyyy]

Looking at all the threads seems to me the new program is associated with some instability and SODs. I tried to push the now old script above 729 and could not do it... hangs on the Sense initiation, so it is 729 for me. Now stable 2-3 days.

[aguenter322]

For what it's worth, oruam's app has been running superbly on my Verizon TP2 for the last 12 hours, even after an 8 hour suspend. I guess time will tell.

[erockvr6]

ok ive set everything up w/ the cab from aguenter, i think its working but how can you tell what speed the cpu is running at?

[nayr1482]

Originally Posted by erockvr6

ok ive set everything up w/ the cab from aguenter, i think its working but how can you tell what speed the cpu is running at?

open up Netrippers App (dont change anything and exit after you check your mhz)

[puff601]

oruam's app has been working smoothly for me as well... ive been using it since yesterday afternoon. i havent had any issues running at 768.

[aguenter322]

The CAB that bundles oruam's utility has been updated with a GUI for changing clock speeds

http://forum.ppcgeeks.com/showpost.p...&postcount=121

[cls_]

Been running oruam's app since it posted... @ 806.4 without problems. No SoDs yet... knock on wood.

[erockvr6]

Originally Posted by aguenter322

The CAB that bundles oruam's utility has been updated with a GUI for changing clock speeds

http://forum.ppcgeeks.com/showpost.p...&postcount=121

guessing old one needs uninstalled