Plantronics 655 and the Q

[TampaChris]

I recently purchased a Q and a Plantronics 655 headset. Often when I answer calls from the headset, it will not connect.
For both incoming and outgoing calls, it often takes several seconds for the audio to transfer from the handset to the headset.

Is anyone else having similar problems with the 655 and the Q?



TampaChris

[jim9112]

If you search around the forum you will find that a bunch of people have had bluetooth issues. I have been a long time platronics user but i have found that they dont work very well with my Q. the connection gets droped a bunch. I switched to a motorola h700 and have had zero problems. If you buy a new headset though make sure you can return it though in case thats not the answer for you

[rudeboy]

i have the 510 Voyager and there is a slight delay before it answers.. i hear like a double beep and then i know i can start yapping :}

[Stealth]

Its the way to go. I works good for general use.

[TampaChris]

Thanks for the feedback. I called the Verizon store where I purchased the Plantronics 655 and the rep said they have had other customers who are not happy with the headset. He suggested the Motorola 700. On Friday I'm going to swap this 655 out for a Motorola 700; I'll post the results.

[traceywaldron]

Before the Q's firmware update, my Discovery 655 worked absolutely fabulously with the Q. No real noticeable delay, no problem receiving or making calls with the headset, no sound problems. Then, once we got the firmware update I began having problems receiving calls. I get the beep & vibrate notifying me the call is coming in, but the Q displays Answer and Reject (or whatever that other option is) softkeys; and in order to take the call, I must press the Answer softkey. If I press the headset button, the call is automatically Rejected and goes to voicemail. Merely removing the headset from the sleeve does not answer the call either, as it should.

Plantronics replaced my headset once, thinking it was their hardware. As soon as I received the new one, it worked for the first call. Thereafter, behavior was as I described in the first paragraph.

I believe there has to be a registry hack we can make that'll turn off those softkeys and auto-direct the call to the headset. I'm pretty sure there was no such softkey display before the firmware update, but I really don't remember for certain, since I didn't have to futz with the phone to take a call! Perhaps merely turning off the softkey might be enough to properly direct the call to the BT device.

Anyone familiar enough with the registry to try to find it??


-Tracey