[APP] LeoCpuSpeed v4, control cpu speed & overclock

As some folks had already discovered by finding some test versions, I've been making an app to control the speed of the CPU. Started out as a test to determine if the "1ghz hack" was genuine or not, and ended up to be able to control cpu speed and to overclock to some degree.

First of all. This app is NO LONGER BEING DEVELOPED. You can use it as-is and at your own risk. And no, I won't make a WP7 version.

Features
- Updates CPU speed every half second (calculated from the processor registered directly! not from some driver)
- Can stress the CPU to show you that it goes up to 998mhz under load (when idle speed is less than 998mhz)
- Disable autoscaling so that you can control the speed yourself
- Select the speed you want by moving the slider or pressing 768/998 presets
- Automatically disable autoscaling and set speed at boot (via menu)
- Overclocking

Notes on auto-apply speed at startup
1) Disable autoscaling
2) Select the cpu speed you want
3) Menu > Apply speed at boot

Notes on overclocking
1) Obviously overclocking is completely at your own risk, as you could harm your device. Luckily, in most cases, your device will just lock up and you'll need to restart your device (remove battery, re-insert and turn on again).
2) The green buttons were the overclock settings that have been succesful 9 out of 10 times. The orange speeds have been succesful like 5 out of 10 times. The red speeds have never worked for me yet.
3) The higher the speed, the more unstable. This is mainly because I don't have a way to increase voltage of the core.
4) Overclocking only works on AC power! When on battery power, the overclock will work but will be undone within 500 milliseconds by the OS. Something within the OS, or a driver, or the radio rom, enforces the proper CPU speed every 500ms.

Notes on battery
I have seen only very very miniscule differences on battery usage when using 998MHz all the time. You really wouldn't notice the difference if it were at 998MHz all the time, or at 768MHz (default). The only thing you _do_ notice, is that it feels snappier.

Try playing a decent movie in TCPMP or coreplayer with autoscaling on, and try again with autoscaling off and at 998mhz. Huge difference. (Note that some ROMs already have autoscaling disabled and will run at 998MHz all the time, like CleanEX. You won't notice a difference there obviously.)

Screenshots


Versions
v4
- For advanced users only: call LeoAutoCpuSpeed.exe with a custom performance level to set that speed (and disable autoscaling if enabled). So, calling "LeoAutoCpuSpeed 12" will set it to 768MHz. And FYI, 18 = 998MHz.

v3
- Add overclock
- Add auto-apply at startup

v2
- Add speed control by slider
- Enable/disable autoscaling

v1
- Initial version (only read cpu speed & stress cpu)

Known issues
Q: Current CPU speed reads 4294967 MHz, that's amazing!
A: Read here why that happens. It's at 128MHz or 256MHz when it shows this.

Q: CPU speed is at 921MHz and pressing 998MHz doesn't change it to 998MHz.
A: Click the 768 button, then the 998 button. It'll be at 998MHz now (has to do with the internals of the driver).

Download
HERE

lemonspeakers said:

Fixed: I copied the .dll file from V2 into the startmenu folder under windows and then re-installed V3's cab. it works now. werid.

Click to expand...

Click to collapse

Glad it works now, but it sounds really weird. You shouldn't need a dll in \windows\startup, only a shortcut (if auto-apply is enabled) to the leoautocpuspeed.exe. The app creates this shortcut when you enable auto-apply. Maybe it conflicted with someleft-overs you had from v2? Dunno otherwise.

radiohead7778580 said:

do you think there will be a way to leave the overclock on in battery mode and not ac only ?

Click to expand...

Click to collapse

I've been trying to figure it out for a while. Also tried patching coredll but I can't find the correct function to patch.

miko3d said:

I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.

Click to expand...

Click to collapse

Thanks for that observation. That's a nice find. First of all it's weird you cannot overclock on AC the normal way, but it sounds related to the same problem on battery. It's weird that the device stays overclocked when under load. But it might help me localize where to look to fix this.

chalid said:

When running at 998 MHZ the taskbar is updating noticably slower. Just tested a few times to make sure. When pressing the startbutton, showing the start menu, and closing it with the X-button in the corner, the taskbar icons update. With 998mhz, this takes a few moments longer, resulting in a small stutter (pretty much the same as with the weather update). With scaling off and running at 768mhz, the update is definitely faster and stuttering is pretty much gone (as used to).

anyone can check with their device?

Click to expand...

Click to collapse

Are you sure you just disabled autoscaling, and did not press "start test"? To be absolutely sure, start the app, disable autoscaling, set it to 998mz, and press "exit" (the app does not need to keep running). If you still notice the performance hog, it's really weird.