Overclock TP2 in WM?

[Maxx134]

I used my test cab because I didnt have mortscript installed or want to change rom.
That's a very smart method though.

My posted cab was a test epic-failure as further testing reveald it does not prevent SOD after 5min.

Further testing ....

[cls_]

Originally Posted by cls_

Just wanted to let everyone know that netripper over at xda has released an app to overclock our devices. There is some issues with SOD, but I have created a few mortscripts to prevent the SOD, and fully automate the overclocking. Here are the links:
http://ip208-100-42-21.static.xda-de...d.php?t=725290
http://ip208-100-42-21.static.xda-de...&postcount=430

You will need mortscript, and rhodium keyboard controller (included in Medium Hill Roms)

I have been testing this all day, and it works great. Gives the rhodium a slight speed increase, and makes CHT much smoother.

Just an FYI, but this solution seems to be rom dependent. So you may need to tweak the script to work correctly.
Original Script looked in:
HKLM\Drivers\Display\

Script w/ jpc073@gmail.com modifications looks in:
HKCU\ControlPanel\BackLight\

*EDIT* Updated scripts: http://ip208-100-42-21.static.xda-de...&postcount=570

[Maxx134]

Originally Posted by cls_

Just an FYI, but this solution seems to be rom dependent. So you may need to tweak the script to work correctly.
Original Script looked in:
HKLM\Drivers\Display\

Script w/ jpc073@gmail.com modifications looks in:
HKCU\ControlPanel\BackLight\

*EDIT* Updated scripts: http://ip208-100-42-21.static.xda-de...&postcount=570

Personally I don't like running scripts as a solution and so even though it is all we have now,
I am looking for a more direct solution.

My testing so far is showing that there are processes still incomplete on a soft-reset, that will also cause SOD .
You must not set the phone to turn off less than 2minutes on battery.
The area of trouble I have traced to the wireless networks section.

Also all registry settings on "Sleep", "PowerSaveMode", or "DisablePowerManagement" did nothing but speed up a few areas very negligible.

There was one setting taht did help besides the :
battery/suspend/timeout=at least 2min for the wireless networks to finish whatever the hell it is doing (in Sense, maybe weather updating?).

But my testing haven't been conclusive enough to narrow it down yet.
planning to cab any benefits on all settings above.

This is all pertaining to SOD only...

[cls_]

well, i believe the ideal solution is to write a service, register the service to get power state notifications, and have that service react to certain power state changes. This has been discussed in the xda thread, and references have been made to msdn articles about this.

I would code it myself, but have never wrote a service for win mobile and unfortunately do not the time to do this at the moment. Additonally, if netripper writes that into his code then we will not need to write this.... so if anyone decides to take up this task, I would pm netripper first just to see if you are not duplicating what he maybe doing.

[jerryyyyy]

Yes, still pretty unfinished. I was in a plane all day and had time to mess with this and the code if pretty rough. Registry keys vary by phone and so the various programmers cannot really collaborate.

I am about ready to drop the effort. When it does work, the phone is much snappier... but it does not last long before a SOD.

[rom116]

I realized after a lot of trial and error that if you let the phone go to sleep on it's own you'll get SOD, you'll need to use the top sleep button and have it appropriately mapped to the right mortscript. Very easy to do, been running 2 days at 728 no SOD using Rhodium Keyboard Controller app and the S2U2 app method. The S2U2 app launches the overclock app at the desired setting when you bring it out of lock mode and the sleep button script puts it at 604 to prevent SOD when you put it to sleep. Buru at XDA has a flawless tutorial with pics.

[jerryyyyy]

Well guys, I am now running at 691Mhz and no SOD for 14h... overnight, power on/off, going to sleep and phone calls... before I declare victory... what else should I test?

I am running the stock Sprint ROM, which may be a factor.

[demonlordoftheround]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

Well, you can try wifi, gps, etc but everything seems working for me at 749MHz.

[jerryyyyy]

Originally Posted by demonlordoftheround

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

Well, you can try wifi, gps, etc but everything seems working for me at 749MHz.

The only thing I noticed was it seemed slow to pick up a call when plugged in. Do you recall there is a registry setting to change the timing of how quickly it polls for an incoming call?

I think I am using the same script.

PS I guess I can creep up the overclocking speed given your results... Do you edit the script on the phone... I read there were problems unless you used the right editor.

[chronster]

I'm running 768mhz, and I've got it doing it automatically anytime I press my power button.

First I deleted this registry key:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Power/state/suspend
dword is :
"Default" = 3

Then I followed the steps in this post: http://forum.xda-developers.com/show...81#post7330081

BUT, instead of having it run his under.mscr file, I have it perform the default operation first, THEN run the auto overclock exe found in the startup folder.

There are some slight discrepancies with this method however. For instance, when the phone gets a text message, phone call, or when it's turned on by sliding the keyboard out, the overclock won't occur since the phone woke up without the use of the power button. To overcome this little annoyance, I set it so if I triple press my back button, the auto overclock exe is ran and the clocks are set to 768.

So far, I'm very happy, and I do notice a difference in performance. Not so much battery though. TCMP er whatever plays my futurama episodes just fine, which normally would pause and tear and not be playable at all.