[APP] Msm7kCpuSpeed - Overclock Raphael/Diamond/Topaz/Rhodium/Blackstone/Whitestone
to overclock the HD2, I've been working on overclocking the MSM7k SoC on the Raphael, with success. The same processor is present on the Diamond, Rhodium and the Topaz, so it should work on all of these devices. I've been able to underclock to 57MHz and overclock up to 710MHz, using small 19.2MHz steps. It can clock even further, but it depends on the quality of the processor in your device where the limit for you lies.
- Rhodium (check out this post for a nice guide
and this app by oruam57
to prevent SOD)
- The CPU speed is calculated from the actual clock registers, not via some dll or shady method.
- CPU speed is updated every 250ms (I haven't seen it auto-scale to other frequencies yet, but kept this feature from LeoCpuSpeed).
- A small dot blinks on each update so that you can see if your device hangs or not.
- Under- or overclock by moving the slider
- Automatically apply setting at boot
- While waiting for version 3 of this app, oruam57 made a little app that automatically scales down when the screen is off and overclocks again when exiting standby, effectively preventing SOD
Notes on overclocking
1) AT YOUR OWN RISK
2) Only works while connected to AC power (depending on device)
3) The "604MHz" OC frequency is a special one. Only with this frequency set, you can remove AC power without having a lockup. So: after you overclock and want to remove your USB cable, set it to 604MHz first!
You'll see it go back to the default 528MHz a second after you remove the cable. That's something the device does, not my app.
4) Overclocking while on battery gives insta-hang (for me). It seems this depends on the device.
5) Use "Apply at boot" wisely! If you use a setting that is unstable, your device may not boot up anymore! You'd need a hard-reset (factory settings).
When using TCPMP to benchmark the overclock, be aware that this tool overclocks the CPU, not the GPU.
I have not done any tests regarding battery life. The voltage to the processor is the same as when it is on 528MHz. It seems it cannot be increased. However, more speed will result in more heat, which means energy from your battery.
(And before you ask, I haven't performed any temperature tests either).
- Enabled apply at boot option (Choose wisely, if your device hangs on boot, you'll need a hard reset
- Fix app crash (trackbar exception) when going into standby
- Increased max freq to 902.4MHz for those fortunate enough
- SoD/hang on battery/etc not fixed yet
- Initial release
Q: My device hangs when unplugging from AC power
A: Read the overclock notes.
Q: When on battery and I press the "604MHz" button, it shows 604MHz for a brief second, and then goes back to "528MHz".
A: Some driver, module, or whatever in Windows Mobile enforces CPU speed every second, overriding the overclock. This is a known issue.
Q: My device hangs after standby (Sleep Of Death)
A: This is a known problem. Until fixed, only solution is to clock to "604" (the special frequency) before putting your phone away.
Q: Msm7kCpuSpeed crashes. When it does, and I click "details", it says something about System.Windows.Forms.Trackbar.set_Value.
A: This is a known problem. The app calculates frequency every 250ms. When the device goes into standby, there's a small window where the CPU is set to 19.2MHz, but my app isn't put to sleep by Windows Mobile yet. When in this small window, it calculates the frequency and updates the app, it crashes. This is because the lowest frequency in my app is 57.6MHz, and it can't find 19.2MHz (or 38MHz). Fixed in v2
Thanks to phhusson
for their overclock in the Linux kernel for MSM7k devices
, where I could lend some code from.
And thanks to BASSMANBOB
for letting me know such a tool is in demand