- Average user rating: 2.5 stars out of 22 reviews Back to product review
- My rating: 0 stars
Full user review
-
15 out of 15 people found this review helpful
2.5 stars
"Good try but flawed design"
Pros: Lightwieght
Cons: Slow to recognize, frequent problems
Summary: I have had the 650 wireless headset for 2 weeks now and have just sent it back for an exchange in hopes that my problems are related to a bum unit. I like the product with exception of the following:
1. When I have the phone on one side of my body and the headset on the other I get a "clicking" and severe static.
2. Similarly when I am using the phone/headset around my computer no matter how far or close the two are apart I get the same clicking/static.
3. Frequently I would turn the phone and the headset on and the phone and/or headset would not recognize the other was there. The only solution I could figure out was to go through the pairing process again and again.
4. There is a light on the power button of the headset that flashes indicating the headset is now on. The problem is the light is under your thumb while your pressing the button so you can?t see it.
5. When making or receiving a call the headset/phone will take 2-3 seconds to make the connection with the other forcing me to frequently apologize for why I am not there on in-bound calls.
I like the unit but to be quite honest the only feature that I find of any value that has to do with it being ?Treo 650 unit? is that it shares the same charger. Otherwise I wish I had bought one of the highly rated Motorola units (and may just do that if the one I get in return doesn?t solve the problems I was having).Updated
I got the exchanged and with exception of number 3 above all the same things are happening. I thought it was possibly my Treo 650 smartphone but I paired the new headset with a friends Treo 650 and got the exact same results. I am dissatisfied with this unit and would not recommend it.
- 1 reply to this review
-
I tried 3 different headsets and have the same issues. Hence it is not a headset problem but a TREO issue.
