Overclock TP2 in WM?

[cls_]

Hmm, I wonder if the rom was running low on memory and auto closed a few apps including SetCpuSpeed...

[aguenter322]

Or that. Doesn't WM normally kill off applications before background processes though?

[robinsondm]

Originally Posted by aguenter322

When I first uploaded 1.0d I had forgotten to add the shortcut to the CAB again, but I fixed it immediately after (file still had 0 views) and I tested the new version. I'll have to check again, thanks.

Edit: Just looked in the CAB and I see the shortcut there. Can anyone confirm that the current 1.0d makes the StartUp shortcut? Thanks.

Ah, then I think I know what happened. I grabbed your 1.0d cab from xda-developers shortly after it appeared yesterday, and obviously got the pre-shortcut version. I saw one other person on xda had this issue, but you got him fixed up.

As the person who raised the question, I'm happy to confirm that the current 1.0d cab does indeed create the startup shortcut. Thanks for all your work on this!

[puff601]

Originally Posted by aguenter322

Good to know, that's what I assumed was happening to him.

Device goes into suspend, SetCpuSpeed catches it and throttles CPU, and then at some point before the device resumes and SetCpuSpeed bumps the clock speed back up the process crashes. If that happens, running SetCpuSpeed.exe from \Storage Card\Program Files\SetCpuSpeed is fine.

I really hope Netripper releases v3 soon or Oruam comes back with a new build of SetCpuSpeed...I really don't want to debug it myself.

thats exactly what seems to happen.. its not that big of a deal right now. restarting the process manually is fine for the time being... i can definitely tell the difference when it goes from 768 to 528 though lol.

[aguenter322]

Originally Posted by robinsondm

Ah, then I think I know what happened. I grabbed your 1.0d cab from xda-developers shortly after it appeared yesterday, and obviously got the pre-shortcut version. I saw one other person on xda had this issue, but you got him fixed up.

As the person who raised the question, I'm happy to confirm that the current 1.0d cab does indeed create the startup shortcut. Thanks for all your work on this!

Glad you've got it working.

Originally Posted by puff601

thats exactly what seems to happen.. its not that big of a deal right now. restarting the process manually is fine for the time being... i can definitely tell the difference when it goes from 768 to 528 though lol.

Yeah, it's a world of difference isn't it! I'm updating some stuff in the CAB as we speak, I might write a script that runs every 10-30 seconds to check on SetCpuSpeed and restart it if it has crashed for the time being.

[n2wishin]

OC'ed to 710.4MHz with 528MHz on standby. Everything opens up faster and smoother than ever before. Morphgear and Nester works great. When tapping on Menu to open up the cookietab menu options there is no lag and the sliding animation is quick/smooth.

[puff601]

that sounds like it probably work. will any of this extra polling cause drain on the battery?

[aguenter322]

Originally Posted by puff601

that sounds like it probably work. will any of this extra polling cause drain on the battery?

Nah, once every 30-60 seconds will be negligible.

[puff601]

Originally Posted by aguenter322

Nah, once every 30-60 seconds will be negligible.

cool

[twebb32]

I was going to buy sprints epic that comes out in aug....but now that we have this program, I'm much happier, and will keep this phone much longer. Thanks for everyone's hard work, it's really appreciated.