MSVC 19209, BT and Sprint Leaked ROM Flaky

[mswlogo]

I've noticed VC (19209) is a little Flaky on the new Sprint Leaked ROM.

This is my longest experience with WM 6.1 and 19209 VC and that might be the issue.

Twice now when I've gone to hangup a BT Headset call, the phone transferred the call to the handset instead of hanging up. Well now that I think about it I guess VC command is out of the picture by then.

But I few times it's got the call and VC mixed up. It's dialing and proompting for a VC again etc.

Any suggestions?

Have you seen it?

I used the "Home Grown" CAB for 19209 and I wonder if all the timing parameters are set correctly or what I'm used to in the registry.

I was thinking of installing the Retail Version and Patch the DLL's and see if that makes a difference. I forget what version the patch DLL's bring it up to.

[boggsie]

So far, I have been having my best PPC results (touch & mogul) with PPCKitchen and MSVC 19209.

I had tried to run the Altell radio with a generic kitchenized version of the Altell ROM w/ MSVC 19209 and experienced all sorts of odd BT VC behavior. Some of what you describe sounds similar, but I didn't know what to make of it at the time.

I'd recommend trying PPCKitchen with MSVC 19209 (it is in the OEMs Kitchen) before throwing in the towel.

Best regards,
-boggsie

Originally Posted by mswlogo

I've noticed VC (19209) is a little Flaky on the new Sprint Leaked ROM.

This is my longest experience with WM 6.1 and 19209 VC and that might be the issue.

Twice now when I've gone to hangup a BT Headset call, the phone transferred the call to the handset instead of hanging up. Well now that I think about it I guess VC command is out of the picture by then.

But I few times it's got the call and VC mixed up. It's dialing and proompting for a VC again etc.

Any suggestions?

Have you seen it?

I used the "Home Grown" CAB for 19209 and I wonder if all the timing parameters are set correctly or what I'm used to in the registry.

I was thinking of installing the Retail Version and Patch the DLL's and see if that makes a difference. I forget what version the patch DLL's bring it up to.