Overclock TP2 in WM?

[one80oneday]

Running great with v2 and cab. Would be nice if we could toggle on and off so I could run android. Would love if this turned into SetCPU! Save battery life and overclock!

[jerryyyyy]

I posted this over at the Developers site, but think it merits a warning:

Well, I was so happy that I had no problems with the scripts solution for several days until Sunday night when I was supposed to do my Sprite Backup, well it crashed and noiw Sense will not load even after removing the scripts. Looks like serious damage was done along the line.... does not seem to like the backup at high speed....

Interestingly, it was the home screen setting for Sense that was hosed. Not the system.

I'll try to trouble shoot this, but look like if you backup with Sprite, better do it at low speeds...

[NIKOKAPS]

Got my Sprint TP2 OCed to 749mhz stable and running FpseCE games much more playable then before. Here is Grand Turismo running while OCed on battery power with the G-Sensor and sound.

http://www.youtube.com/watch?v=R-GwLzzXO5I

[quickdraw62]

Installed this the other day and it locked up the phone. Couldn't run it at 710 so I tried 537 and wanted to work up from there. Still locked up the phone when it went into sleep mode. I've since uninstalled it and have had no problems.

[loader187]

quickdraw. Mine was doing the same thing and i overclocked mine to 710 and under clocked the sleep time while changing the polling to 150. My phone has been good. I also turned off the phone going into lock on standby and just lock it manually and so far so good.

I also noticed that using the S2U2 application locks up my phone (this was before the overclocking). I was wondering if anyone knew if their is a setting change that I need to do to prevent S2U2 locking up my phone when it goes into sleep. It didnt start doing this until mid June releases of NRG. I still like the old school ROMS so I am using the 21911 cookie versions and it locks up. Any help would be great thank you.

[Maxx134]

Originally Posted by jerryyyyy

I posted this over at the Developers site, but think it merits a warning:

Well, I was so happy that I had no problems with the scripts solution for several days until Sunday night when I was supposed to do my Sprite Backup, well it crashed and noiw Sense will not load even after removing the scripts. Looks like serious damage was done along the line.... does not seem to like the backup at high speed....

Interestingly, it was the home screen setting for Sense that was hosed. Not the system.

I'll try to trouble shoot this, but look like if you backup with Sprite, better do it at low speeds...

Did you slide out the keyboard before that happened?
Naw I have crashed Sense homescreen so many times I stopped counting.
If you install extra tabs, or a cabbed HTCmessaging version, or flip to landscape on the newer Sense versions ...
It likes to crash...
Check and delete worthless "application data" folder on mem card if it is there.
Sense likes to make that folder and throw temp data in thr that may conflict with homescreen.
If not, a soft reset always brings me back.
overclock speed did not matter.
I may try it without cookie home screen to see if it helps, But its just a guess.

[4wheelfurry]

Originally Posted by aguenter322

Are you using the OC_Auto script or my cab?

The registry value tells you nothing about the actual processor speed at any given time, only Netripper's app will.

If you're using my cab check your task manager (view processes, not applications) and let me know if SetCpuSpeed.exe is still listed when your CPU no longer runs at the higher speed as reported by Msm7kCpuSpeed. If you're using the script check for MortScript.exe (assuming you don't have more than one persistent MortScript running all the time).

If you suspect that there is a memory leak in SetCpuSpeed.exe you can check for this in the same place. Look at it in the task manager and note the amount of memory it is using when your device boots, then check it later when you notice a decrease in memory and compare the two numbers.

I sent you a PM on this, I updated to your 1.0d cab and it runs in overclock but will SOD everytime on the first sleep. I have changed the settings in running and sleep and polling every way possible, no setting will prevent it from SOD.
I am running a stripped Titanium ROM so no Sense or S2U2 or anything that could cause issues with the app...
If I can provide more info let me know, until its better I can't use.

[Maxx134]

Originally Posted by 4wheelfurry

I sent you a PM on this, I updated to your 1.0d cab and it runs in overclock but will SOD everytime on the first sleep. I have changed the settings in running and sleep and polling every way possible, no setting will prevent it from SOD..

Do not set sleep (in Power/Backlight settings) for anything less than 2MINUTES!
Set to dim the screen 30sec.
try now.
It is not the cab. It is the overclock app.
EDIT:
If you still have problems for sleep, try this cab:

[4wheelfurry]

I originally had dim set to 1min and sleep at 2min. SOD every time

So I changed to dim at 30sec and sleep at 3min. SOD again

Changed again to dim at 30 and sleep at 5min. SOD each time

I understand the cab is script to run the app. The app needs more work. I'm gratefull to be able to test! and hope to be able to use as stable some day!!

EDIT: I wil try the cab you posted.

[Maxx134]

Originally Posted by 4wheelfurry

EDIT: I wil try the cab you posted.

Ok feel free to try that cab as it is just a few reg edits changing a few settings in the powersave mode area of the network settings that my testing showed gave me conflict.
No major folder or name changes, just some power settings