[Touch Pro, Fuze General] b0z0k:
As we know, overclocking MSM is possible now. Just check :

But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)

I use GSM unbranded TP100 & TAEL v.5 ROM.

I'll start with my experience :

1. grab the v.2 file from the thread above. (1st page)

2. Install it to phone Memory.

3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.

4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.

5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.

6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup

7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)

8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.

From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.

In this

http://xdaforums.com/showthread.php?t=725290&page=120

thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)

I'll write my experince using above method :

The method is : (Credit goes to Qzytor)

Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://xdaforums.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
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 = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10

Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.

To restore back to phone default speed:

Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.

1. Performance Level 35 is overclocking @ 672 Mhz

2. Add 1 level means add 19.2 Mhz in clock speed

3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40

4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.

5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Rhodium (Touch Pro 2)

6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.

7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.

I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^