Quote:
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.