ѠѳѺ Ultimate Overclocking, Tweaks and Tools Guide For TP2 ѺѳѠ Updated 10/21/2010

[neudof]

I would love to see this stickied, so here are some tips:

1. You have packaged other peoples work into a zip.
   1. Link to the origional creators thread so the people that made the app can get credit,
   2. Users can have the most up to date app.
   3. Discussion on how to use or problems with each part can be directed to the correct thread rather than trying to discuss multipe different methods in one thread.
2. There are at least 2 other OC methods. Add information on how to use those as well.
3. Add the information on how to dual boot to android using the different OC methods.

All the information is out there, if you could pull it all together that would be awesome!
Great start, keep up the good work!

[gono666]

Originally Posted by neudof

I would love to see this stickied, so here are some tips:

1. You have packaged other peoples work into a zip.
   1. Link to the origional creators thread so the people that made the app can get credit,
   2. Users can have the most up to date app.
   3. Discussion on how to use or problems with each part can be directed to the correct thread rather than trying to discuss multipe different methods in one thread.
2. There are at least 2 other OC methods. Add information on how to use those as well.
3. Add the information on how to dual boot to android using the different OC methods.

All the information is out there, if you could pull it all together that would be awesome!
Great start, keep up the good work!

Thanks for your comments and suggestions, i just downloaded the android Os again i will install it as soon as Mr.X releases the update\fix for his titanium rom,once i flash it i will test the other overclocking methods except for the one using motorscript i thought it could be to hard to do for less experienced users,i also plan on making the full guide with pictures and maybe videos to make it alot easier for everyone,so far the method i described on my guide has been the most stable overclock i have achieved.
Thanks again!

[neudof]

Everyone should be aware that your device is different than mine. Two devices with the exact same ROM, settings, SD Card, apps could max OC at two completely different speeds.

I am able to get to 786 without any issues both on stock and the latest NRG ROM, there are a lucky few that are able to achieve 806

The best advice I can give you is start low, and work your way up

If you think you have found your max speed, here is the best test I have found to verify stability...

1. Open a text message
2. Flip open your keyboard and start typing,
3. If you lock up you need to drop the speed a level and try again!

[gono666]

Originally Posted by neudof

Everyone should be aware that your device is different than mine. Two devices with the exact same ROM, settings, SD Card, apps could max OC at two completely different speeds.

I am able to get to 786 without any issues both on stock and the latest NRG ROM, there are a lucky few that are able to achieve 806

The best advice I can give you is start low, and work your way up

If you think you have found your max speed, here is the best test I have found to verify stability...

1. Open a text message
2. Flip open your keyboard and start typing,
3. If you lock up you need to drop the speed a level and try again!

I will make sure that on next update of my guide i post your method of testing the stability of the overclock,do you know any other ways to trigger instability that i can use during my testing?

[gspitman]

Originally Posted by gono666

Instructions

1. Download and install "Total Commander" and "FDCSoft Task Manager" (LINKS ABOVE)
2. Download and Unzip "Overclocking Files" (I normally unzip them in My Documents)
3. Install "Msm7kCpuSpeed_v2" and run it, change the overclocking speed to 604MHz and click on the "MENU" soft key and select "APPLY SPEED AT BOOT"
4. Create a folder inside "\Program Files\" and name it whatever you want, i named mine "OC Tools" copy "SetCpuSpeed.exe" and "SetCpuSpeed.cpp" to the folder you have just created.(I normally create this folder on my device i have not tested this on my storage card)
5. Using "Total Commander" go to the folder created on step 4 highlight the "SetCpuSpeed.exe" by clicking it once,now click "MENU" on the bottom tool bar,click ">>>>>(A)" and now click "CREATE SHORTCUT" now you should get a pop-up click on "TREE" and select the following path "\Windows\Startup\" now click "OK" and "OK" again for the pop-up window.
6. Using "Total Commander" go to "\Windows\Startup\" find the shortcut created on step 5 (SetCpuSpeed.Ink) click and hold on the shortcut to get the right click menu click on "PROPERTIES" and click on the top tab "SHORTCUT" now on the target line you have to add "/boot" (No quotation " ") to the link location and it should look like this "\Program Files\**FOLDER NAME FROM STEP 4**\SetCpuSpeed.exe" /boot now you can click "OK"
7. Using "Total Commander" go to "\Program Files\Msm7kCpuSpeed\" and copy the file "Msm7kXClockLib.dll" and paste in the "\Windows\"
8. Using "FDCSoft Task Manager" click on "RegEdit" and go to "\HKEY_LOCAL_MACHINE\SOFTWARE\Msm7kCpuSpeed\" click on the "MENU BUTTON" which is next the the button that has arrows pointing up and down and click on "IMPORT" go to the folder where you unzipped "Overclocking Files" (In my case \My Documents\Overclocking Files\) and select the file "SetCpuSpeed.reg" and click the "CHECK-MARK" button you should get a message saying "Registry entries successfully imported" now click on the bottom right button to exit this screen.
9. Using "Total Commander" in the root menu go to "\\Plugins\registry\HKLM\SOFTWARE\Msm7kCpuSpee d\" and find the key "AutoPerformanceLevel" and double click it, now change the value to "40" and click "OK" (Highest stable overclock i have done with no crashes or problems, value 40=768MHz. Stability can SOMETIMES depend on rom build)
10. Using "Total Commander" in the root menu go to "\\Plugins\registry\HKCU\ControlPanel\Phone\" and find the key "Sleep" and double click it, now change the value to "0" and click "OK"

And... DONE! you can now soft reset your device and enjoy the new improved performance of your TP2!

So... most of this sounds like things that could be done with a well written cab file...

Unfortunately I'm not qualified to do so, but I'll see if I can dig up one of our resident rockstars to cab this all up so we can make it less complicated... hopefully reduce to copy and double click!

[neudof]

OC V1.5 is by far the easiest.
Install the cab, change the setings and commit them, turn it on and off when you want

[gono666]

Originally Posted by neudof

OC V1.5 is by far the easiest.
Install the cab, change the setings and commit them, turn it on and off when you want

thats the first method im gonna try as soon as i flash again, thanks

[ACHlLLES]

Originally Posted by neudof

OC V1.5 is by far the easiest.
Install the cab, change the setings and commit them, turn it on and off when you want

I'm liking it so far, but questions.

The OC doesn't stick after reboot correct? Is that a good or a bad thing?

I'm kinda hoping there's an option to turn it on/off on reboot.

Thanks.

[rhacy]

Originally Posted by ACHlLLES

I'm liking it so far, but questions.

The OC doesn't stick after reboot correct? Is that a good or a bad thing?

I'm kinda hoping there's an option to turn it on/off on reboot.

Thanks.

It's a good thing to start out with when testing OCT for stability.

If you want OCT to run at start up, you just need add a shortcut of it's run.exe to your Windows\Startup Folder. That said, I highly recommend you make sure you have the OCT cab installed to your micro SD card prior to adding the exe shortcut to the Startup Folder. Doing this allows you the option of pulling the mirco SD card and being able to boot back up with the stock clock speed. This precaution is just in case your overclock settings cause the system to get stuck in lockup loop during boot up.

Best to all,
R

[jerryyyyy]

Seems to me like many ways to the same end result. I used one of the earliest solutions and have not changed it for I guess a month now because it works. The one trick I used was to start at lower speed and then increase until I got a freeze, then I backed off two speeds (not just one) to give me a margin of error. I think people try to cut this too closely to eek out one tiny bit more performance. Then what happens is there is some unexpected system demand that pushes the processor over the top and it freezes. Anyway, I think the variability across solutions may be due to trying to cut it too close. 729 is just fine for me (compared to 528 ) and 768 is not that much of an increment to risk instability....