OK. I understand what you mean. I have been using version 2 for a week without incident. I find that kind of surprising, seeing as I have put phone to sleep prolly 150 times and haven't had 1 SOD. It's my understanding that the script doesn't prevent SOD, but it is in a "loop" that merely reduces the chances of SOD because it happens so rapidly. I would think that in over 100 some odd sleeps that I would have hit the sweet spot and had 1 SOD, but it really does work perfectly.
I believe that there is a several second delay between the time the screen goes off and the device actually goes to a suspend state, so as long as the script checks the screen state during that transition period, you will never get a SOD. Because Windows Mobile has a habit of arbitrarily terminating processes when resources get low, I suspect that people who are getting the SOD are getting it because Windows Mobile is closing the mortscript process that runs the script.
Hi, for those of you using the script (getting SOD on phone calls, etc...) I have updated the script to include a basic GUI modeled off of aguenter's GUI.
Just put both files in the root of your storage card and create a link to OC_Auto4 in your windows/startup folder as always. When you want to change speeds just go and click on the OC_Auto4_GUI. GUI lets you change your OC speed and/or Poll Interval. Enjoy!
*Keep in mind the faster the polling rate the more CPU used up!
*Note if you are using OC_Auto3 - there are no "real" differences from 3 to 4 other than adding the GUI so if you are all done tweaking your speeds etc...dont bother updating!
|htc, msm7k, overclock, rhodium, touch pro2|
|Thread Tools||Search this Thread|