Overclock TP2 in WM?

[jerryyyyy]

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 doing this. It is a pain for others to go through those pages. You got it right here.

[cmajewsk]

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)

Nice writeup, it's especially nice in that the XDA thread is constantly changing.

So if I am using this script fairly successfully and not running into any SOD's. My question is, what can you do to prevent Netripper's OC v2 application from erroring out when you move off AC power?

[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!

[puff601]

@jerryyyy, my sprint tp2 w/stock 6.5 runs fine on 768 and freezes after so long on 787. ive been running at 768 since OC v1.0

@nayr1482, what is the diff between Auto_OC2 and 3? im off to search for mortscript, install it and try Auto_OC3. if everything goes smoothly, i will then try to edit the script to run at 768... also installing to the sd card is a great idea.

Thanks for the help so far guys, i will be back to let you know the results.

[nayr1482]

Originally Posted by puff601

@jerryyyy, my sprint tp2 w/stock 6.5 runs fine on 768 and freezes after so long on 787. ive been running at 768 since OC v1.0

@nayr1482, what is the diff between Auto_OC2 and 3? im off to search for mortscript, install it and try Auto_OC3. if everything goes smoothly, i will then try to edit the script to run at 768... also installing to the sd card is a great idea.

Thanks for the help so far guys, i will be back to let you know the results.

OC3 does the same thing as OC2 - just trying to "trim some of the fat" out of it and make it more efficient / more understandable.

OC2 reads/writes the OC values to the registry, but it isnt needed so OC3 basically *should* all your phone to boot a TAD faster than OC2, and it should have a tiny bit more resource/time to check for the important things during normal operations (backlight on/off, in a phone call / not in a phone call, lock screen, etc...).

[puff601]

umm the script isnt working for me... its not doing a thing... im still @ 528 when windows starts... am i missing something?

[nayr1482]

Originally Posted by puff601

umm the script isnt working for me... its not doing a thing... im still @ 528 when windows starts... am i missing something?

did you install the cab for MortScript (the program)?
did you create a shortcut to the script file in windows/startup?

[puff601]

Originally Posted by nayr1482

did you install the cab for MortScript (the program)?
did you create a shortcut to the script file in windows/startup?

yep i installed Mortscript. can you post the same mortscript you are using? i created the lnk in startup too...

Edit: what are you using to check your cpu speed? when i open the overclock app, the slider still shows 528.

[aguenter322]

Originally Posted by puff601

yep i installed Mortscript. can you post the same mortscript you are using? i created the lnk in startup too...

The script he posted on the last page works fine for me. If you start the script from your file manager manually and then go to Msm7kCpuSpeed does it show a higher clock speed than 528? If it doesn't there's a problem with your script, if it does there's a problem with your shortcut to the script or something else in your startup sequence.

[puff601]

Originally Posted by aguenter322

The script he posted on the last page works fine for me. If you start the script from your file manager manually and then go to Msm7kCpuSpeed does it show a higher clock speed than 528? If it doesn't there's a problem with your script, if it does there's a problem with your shortcut to the script or something else in your startup sequence.

if i click on the script in file explorer it doesnt do anything and still shows 528 in the cpuspeed app