Overclock TP2 in WM?

[aguenter322]

Originally Posted by nayr1482

Ok...since I have seen many of these posts....
(I really suggest reading the thread - or at least part of it - over on xda)


1) Get Netripper's OC v2 program over at xda http://forum.xda-developers.com/show....php?p=7181179
2) Install MortScript if you dont have it already
3) Download the attached file onto your computer and unzip it
4) Open it with Notepad, Change the speed settings in the file to what your OC should be
*Be careful not to set it to high!
5) Save the file, make sure to set notepad to "all files" and make sure the file extension is .mscr (by default notepad will try to save it as a .txt)
6) Place this file onto your SD Card
7) Create a shortcut to this file in your Windows/Startup folder
*This is for safety - if you set your OC too high and place the actual file in your start folder you are screwed. If you have the file on your SD Card and you go to high, you can take your SD card out and you will be able to boot
8 ) Reboot


*Note - if you are using this script do NOT change the OC speed using NetRippers program. Change the speed in the script file only! If you want to change speeds, change the values in the file, save it, overwrite the file on your SD Card (as long as you do not rename it, the shortcut in your Startup folder will still work).


This script prevents SOD and allows you to run 24/7 OC'ed on battery power.
*The script does NOT work for everyone (you will get an error message if it doesnt) but works for 95% + so far.



Big thanks to Netripper for the App. Script was a group effort (jpc, RoboWang, cmd512, myself, etc...).

Thanks for this! Could you please explain why there are two variables for the overclocked speed though (and set to different values in your script as default)?

There is a start_speed and a boost_speed, and if I'm reading the script correctly the CPU is initially overclocked to the start_speed value if there is not a shortcut to the Msm7KAutoCpuSpeed program in \Windows\StartUp, and then the boost_speed variable is used when the device isn't in a state that needs to be throttled.

Why can't those two variables be merged into boost_speed and just make the initial call to Msm7KAutoCpuSpeed.exe use the value of boost_speed?

For example:

If (NOT (FileExists("\Windows\StartUp\Msm7kAutoCpuSpeed.ln k")))
RunWait("\Program Files\Msm7kCpuSpeed\Msm7KAutoCpuSpeed.exe", boost_speed)
EndIf

PS - Just tried the script and it's working great, I can see it throttled and then unthrottle within a few hundred milliseconds when I come back from sleep. Thanks to you and everyone else who put the effort in to making this usable!

[nayr1482]

Originally Posted by aguenter322

Thanks for this! Could you please explain why there are two variables for the overclocked speed though (and set to different values in your script as default)?

There is a start_speed and a boost_speed, and if I'm reading the script correctly the CPU is initially overclocked to the start_speed value if there is not a shortcut to the Msm7KAutoCpuSpeed program in \Windows\StartUp, and then the boost_speed variable is used when the device isn't in a state that needs to be throttled.

Why can't those two variables be merged into boost_speed and just make the initial call to Msm7KAutoCpuSpeed.exe use the value of boost_speed?

For example:

If (NOT (FileExists("\Windows\StartUp\Msm7kAutoCpuSpeed.ln k")))
RunWait("\Program Files\Msm7kCpuSpeed\Msm7KAutoCpuSpeed.exe", boost_speed)
EndIf

PS - Just tried the script and it's working great, I can see it throttled and then unthrottle within a few hundred milliseconds when I come back from sleep. Thanks to you and everyone else who put the effort in to making this usable!

Hi, the two speed logic was in place before i started working on the script. you are sorta right...
what it does, is the start_speed kicks in basically as soon as windows loads. then after 30 seconds (roughly when sense, etc...is loaded) it moves onto the loop where it is checking for backlight, phone calls, lock screen, etc...

Basically the start speed is just to give it a little extra through the boot process.

If you dont want this - just set the start_speed to the same as your boost_speed.

[aguenter322]

Ah ok, I hadn't considered pushing the clock rate a bit higher just for getting through the startup procedure of Sense and everything. I misread the last sleep before the endless loop, I thought it was for 3,000 milliseconds but it is actually 30,000...makes sense now. Thanks for the info.