Netripper overclock working on touch pro 1

[jrebo]

Originally Posted by solcam

Will this cverclock still be there if i flash to another rom or will i have to reapply this?

You will need to reapply.

[frizzlefry]

I am glad to hear that others are enjoying this.
Remember to vote so that others may have an easier time deciding whether or not to try it, I think they are missing out.

[hillsmi]

Firstly, thank you to all who worked hard to accomplish this.

Secondly, I've applied the settings and ensured that the registry values emulate what is listed in the OP, but...

my displayed speed is shown as 672, even after soft resets.

I've opened the SetCPUSpeed program in the program list, and picked 710, and then 692, soft reset, and when it reboots, it still displays 672 after a couple of minutes when I open the Msm7KCPU program.

Any thoughts?

Oh, duh! Is it because I have the performance level set at 35? Was reading someone's post re: GoogleMaps (I use that a lot, and want to make sure it works, so I set the PL at 35).

[thejaredhuang]

Can you guys post your speeds? My Fuze is freezing ~600mhz. I have lowered my screen off level to 16 (~307Mhz) in an effort to increase battery life. Could that be the problem?

[hillsmi]

Originally Posted by frizzlefry

Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:

BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 37 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 20
SettlingTime = 10

each performance step is equivilant to 19.2 mhz

Can someone explain for those of us that are tech challenged what the above registry values actually mean?

Also, with the SetClockSpeed prgm, what is the difference between the 'clock speed' and the 'throttled clock speed'?

Thnx

[frizzlefry]

Originally Posted by hillsmi

Can someone explain for those of us that are tech challenged what the above registry values actually mean?

Also, with the SetClockSpeed prgm, what is the difference between the 'clock speed' and the 'throttled clock speed'?

Thnx

This is directly copied from oruam's readme contained in the zip xda-developers - View Single Post - [APP] Msm7kCpuSpeed - Overclock Raphael/Diamond/Topaz/Rhodium/Blackstone/Whitestone.

SetCpuSpeed V1.0
SetCpuSpeed uses Msm7kClockLib.dll (from Msm7kCpuSpeed application developed by NetRipper, [APP] Msm7kCpuSpeed - Overclock Raphael/Diamond/Topaz/Rhodium/Blackstone/Whitestone - xda-developers) to over and underclock the CPU.

Requirements and compatibility
SetCpuSpeed was developed for HTC Topaz (Diamond 2) with WM6.1 and it critically depends on Msm7kClockLib.dll that should be present in \Windows directory. It may be working on other HTC phones that use the same CPU (Rhodium, Raphael, Blackstone, Whitestone) but the test is up to you.

Install
Install Msm7kCpuSpeed application. If Msm7kClockLib.dll is not installed in \Windows directory copy it there.
Copy SetCpuSpeed.exe somewhere in your phone, run it and check its working (see Usage below).
When satisfied in \Windows\Startup directory create a link to SetCpuSpeed.exe with parameter "/boot". Set BootTime value (see Parameters below) to a value large enough to allow you to kill SetCpuSpeed.exe with a task manager after soft reset.
Soft reset your phone and wait. If the phone freeze soft reset again, kill SetCpuSpeed.exe before it changes the clock, lower PerformanceLevel value and try again.

Uninstall
If present remove the link to SetCpuSpeed.exe from the \Windows\Startup directory, then soft reset. After that you can safely delete SetCpuSpeed.exe.

Parameters
SetCpuSpeed working depends on some parameters it gets from registry under the keys HKEY_LOCAL_MACHINE\Software\Msm7kCpuSpeed. All the values are DWORDs.
File SetCpuSpeed.reg can be used to set the default values using a regeditor that can import it (examples are Dotfred's Task Manager, Dotfred's TaskMgr, and SKTools, SKTools features).
Command - (default value: 0) - If set to 1 SetCpuSpeed reloads the parameters and restores Command to 0. If set to 2 SetCpuSpeed restores Command to 0 and terminates itself.
BootTime - (default value: 20000) - If run with parameter "/boot" SetCpuSpeed waits BootTime milliseconds before acting on the clock.
CheckTime - (default value: 200) - SetCpuSpeed checks the CPU clock every CheckTime milliseconds.
SettlingTime - (default value: 10) - Time to wait after restoring CPU clock to safe value (604 MHz).
PerformanceLevel - (default value: 33) - This is the overclock factor, the CPU clock is approximately PerformanceLevel * 19.2 MHz (e.g. 33 * 19.2 = 633.6 MHz).
ScreenOffPerformanceLevel - (default value: 9) - This is the underclock factor, the CPU clock is approximately ScreenOffPerformanceLevel * 19.2 MHz.

Usage
SetCpuSpeed works this way.
1 - When the phone is about to suspend (for the user pressing the Power button or due to power timeout) SetCpuSpeed sets the CPU clock to the safe value (604 MHz) to prevent SOD.
2 - If SetCpuSpeed is called with parameter /screenoff it undercloks the CPU according to ScreenOffPerformanceLevel. The CPU remains underclocked until the screen is switched off and then on again or until the phone is suspended and then resumed. If you have TouchLockPro installed ([APP][Updated 1-4-2010] TouchLockPro 2.12.8 *NEW* with Proximity sensor support - xda-developers) SetCpuSpeed will also make the screen go off.
3 - When the phone resume from suspend or the screen return on SetCpuSpeed overclocks the CPU according to PerformanceLevel value.

USUAL LEGAL DISCLAIMER
Use SetCpuSpeed at your own risk! NO WARRANTY! Although running this application does not seem to produce any damage on my phone, I take no responsibility for any kind of damage or major or minor inconvenience caused to devices or data or person or whatever else due to this application and its usage.

[hillsmi]

I don't know about anyone else, but I have actually seen an improvement in by battery life with this OC mod.=D>

I had a stock battery, was crap, as everyone else's; having to place on charger 1-2x/day.

Decided to get the 3000mAh Mugen. Even that started to show a quick drain throughout the day from full charge.

But over the past 24hrs since I installed this OC mod, my % reading on the battery has decreased very little since taking it off the charger this morning. It is now 13hrs later, and it reads 93%. Last week, it would have read <60% by now.

Don't know why, but in my book, that's a BIG +.

[hillsmi]

Okay, so it was working fine for about a day or two.

Now I can use it for one application / pgm, and then it freezes.

I've only got it set on 672. I'm using Calkulin's Alltel 30 ROM.

I've reflashed the ROM, and haven't tried the OC yet again. If I do, I think I'll start one step above 528, and go up from there.

Anyone else with freezing after a couple of days?

It's a shame too, as I stated earlier, it was massively extended my readable battery %.

[ajskhan]

So, should I just install those two cabs on the first post?

[hillsmi]

Originally Posted by ajskhan

So, should I just install those two cabs on the first post?

Yes, I think that's how it works. Install the one file to the SD card as stated, and the other most-likely to the device.

That's how I did it.