problem with parrot 3200LS and ROM vanilla

[kkfuti]

hi guys,

I'm having some problems from time to time with the conecction between my p3300 Artemis Vanilla ROM 1.0. and the parrot 3200LS.

the problem is that when I turn on the car and the bt connection is set automatically the parrot appeas as if I was in a call.

if I finish the call still the p3300 and the parrot are linked becuase I cannot reproduce the radio or the CD's ("phone" appears in the display of the car).

if I turn off and on the car, when the bt connection is set again happend the same.

The problem is solved only if I make a soft-reset, so the problem is in the pda and I never had this before with WM5.

any idea?

thanks

[shawndh]

hi guys,

I'm having some problems from time to time with the conecction between my p3300 Artemis Vanilla ROM 1.0. and the parrot 3200LS.

the problem is that when I turn on the car and the bt connection is set automatically the parrot appeas as if I was in a call.

if I finish the call still the p3300 and the parrot are linked becuase I cannot reproduce the radio or the CD's ("phone" appears in the display of the car).

if I turn off and on the car, when the bt connection is set again happend the same.

The problem is solved only if I make a soft-reset, so the problem is in the pda and I never had this before with WM5.

any idea?

thanks

I had a similar problem earlier this week with my Parrot CK3000. But the problem only happened after I tried to download and use MS Voice Commander software. I tried to uninstall and go back to default Speed Dial but it wouldn't work correctly anymore with the Parrot kit or my headset. The software changed my registry settings - couldn't figure out how to fix it, so I had to hard reset.

But, right after a ROM upgrades and hard resets, I get the "phone" condition you described. It's like, the BT channel is just open, waiting for a command. The way to fix it is just to make a phone call and then hang up using the Parrots "end call" button. Then everything goes back to normal and this does not happen again. I only get this if I hard reset or ROM upgrade. Try it.

[dannyoneill]

I was fine with official asia 3.7
I was fine with Vanilla 1.0
Had the problem with Official Europe
Just installed Vanilla 2.0 and we will see how it goes.