[Windows Mobile Apps and Games] RoboWang:
Probably because you need to refresh the editor as it hasn't been refreshed since the system changed the value. Just refresh, it should match, then.

Holy Crap, just wrote a whole page and just lost it by doing something stupid. Well, I'll try again.

I just looked at your OverClock_Boost.mscr.

It will work 90% of the time, but there may be a situation when it will freeze. I'll explain.

I am trying to just update jpc's original script. His script (and his phone) uses the Cellular System Available (CSA) value, as yours appears to do.

That value will be be 2 or 4. Well, not really. What is the value when you miss a call? It's hard to catch, but it won't be 2 or 4.

What will this do? I know from experience that if the values aren't correct, the throttle will pulse up and down during the event (call in, missed call). Sometimes this pulse's timing goes off the track, and freezes the phone. It especially seems to happen when the phone is sleeping.

So, what to do?

Well, instead of using the values you use in your script, use jpc's values.

phn_value = 2 in call

phn_value <> 2 the rest of the time

This will prevent the system from being confused when you get a missed call.

For other folks, the purpose of this part of the script is to throttle the OC up or down during a call. It seems a lot of SOD's come while in call and the OC is maxed.

I, personally used it jpc's way for three days and never had a freeze, but others reported they did, so to be safe than sorry, I changed the script to reflect the Status values (which MY phone uses) and it works.

NOW we find out there ARE phones that use the CSA, like jpc original script called!

To see if your phone is throttling correctly, open the MSM7 app and note that your set OC is running. Arrange a call in and after answering the call, navigate BACK to MSM7 and see if the throttle worked. It should be 604. After hang up, it SHOULD throttle back to max OC, again.

As I said, if it doesn't, you may NEVER have a freeze up, but the real possibility is there if you don't use the right script. And as Murphy's law says, it will freeze/drop call at the worst time. And they use that scenario as a commercial!

With this new info, I can see that it's time to get serious writing a single script that checks the system for CSA or Status parameter usage, and where the parameter DispOn is located.

At this time, we are now going to need four scripts instead of two. And my gut feeling is we'll find out there are other parameters being used in other phones!

But 4 should get 90%.

If someone else wants to tackle this auto script thing, be my guest as I am very busy right now!

So for you guys looking at this and want to use this SINGLE script fix, once the right one is identified, I'll post the four with instructions. later on today.

And MAYBE have an auto check by Saturday if you would rather wait.

Using these scripts will involve MANUALLY checking parameter usage AND where your DispOn parameter location in a reg editor. So think about that if you are wanting to try it.

IF you are game, I can give you the places in your Reg Editor to look for these values so you will know what script to use when I post them, later.

To find out what calling system you device uses, in your reg editor, go to

HKLM\System\State\Phone then see what value is set in Cellular System Available. If it's a 9 value, you need the script for Status. If it's not a 9, then you need the script for CSA.

Then use the reg editor to search for DispOn. If it is in HKLM, then you need the M script. If it's in HKCU, then you need the U script.

Confusing, I know, but for right now, that's the only way. I will try to get time to make a single script in the next few days, so be patient.

Hopefully, nettrip will fix his app an save all the work for us all.