Well... which ones do you have that work.. Please share!!
PG
Sony Ericsson Akono Headset HBH-662 (I do not like the way this one fits my ear, but it works), Plantronics Voyager 855 (my current favorite), and the Plantronics Voyager 510 (love this one, too).
__________________
Samsung Omnia- WM6.1 - VZW
HTC TyTN II - WM6.1 - on the new at&t - and loving it! "Fact veracity is not based on the validity of the source, but on the last thing posted."
I thought you would like to know that all my BT headsets work as you desire except for the H700. I stopped using that one since it does not work roperly with my TyTN II either. Sorry.
I have the H700 and it works just fine. I am able to initiate a call using VC by pressing the button. I can answer or terminate a call either with the button or by flipping open the boom mic.
In fact, aside from the headset switching problem and a slight delay when pressing the send/end button, I am very satisfied with the BT stack on this phone.
I have the H700 and it works just fine. I am able to initiate a call using VC by pressing the button. I can answer or terminate a call either with the button or by flipping open the boom mic.
In fact, aside from the headset switching problem and a slight delay when pressing the send/end button, I am very satisfied with the BT stack on this phone.
I will try mine again, but it did not work the time I tried it and since I had the others that I like a lot more, I did not keep trying.
__________________
Samsung Omnia- WM6.1 - VZW
HTC TyTN II - WM6.1 - on the new at&t - and loving it! "Fact veracity is not based on the validity of the source, but on the last thing posted."
I'm having the same problem moving between my Prius, Scala 500 and Anycom headset - in fact, I can't seem to use my Prius connection at all anymore, though I haven't tried to erase and re-pair it.
I got my new i760 as a replacement for the i730 I accidentally drowned last week, and the thing that baffles me about this is that my i730 never had this problem - the bluetooth always worked like a charm, even as other "features" may have frustrated me.
I will call Verizon to add my voice to the growing chorus of complaints, but am I crazy to think there should be some way to just reuse the code from the i730 BT implementation?
But it looks like sligthly different then I'm reading in this thread.
As I mentioned before I had Motorola E815 and XV6600 working fine (XV6600 after updating bluetooth stack few times), but i760 does not work.
What's happening is this:
1. Turn on engine i760 and car pair fine
2. I can talk and receive calls
3. After while (most of the time within 10 miutes or even a minute) phone and car are not connected any more.
4. I can't reconnect/pair them in any way
5. When I have opportunity (stop lights), I turn off and turn back on engine, phone and car pairs and stays on now.
Go figure!
I'm trying different compination playing with handsfree check box off or on of f and on. The same problem.
I am using Microsoft's own SYNC platform, and I can make or receive exactly one call. When either I or the other party ends the call the SYNC will think the phone is on hold. I am unable to clear the hold until I completely turn off the car or turn off bluetooth on my phone. I can't even listen to the radio until one of these is done.
It it very frustrating that a Microsoft OS connecting to Microsoft Windows Automotive can't even work correctly.
Don't blame Microsoft on this, this works on other WM6 phones, just not ours or the Blackjack apparently. I have the SAME exact issue you are talkling about with my UConnect system in my Dodge Caliber. This appears to be an issue with Samsung's Bluetooth drivers...
Current way..
1. Select the right menu.
2. Press the up navigation once.
3. Hit the Center OK button.
4. Select the BT device you won't.
5. Use down navigation button to select handsfree
Has anyone looked at a script or some other way to get to the Bluetooth handset menu in one or two button clicks?
There has to be a shorter way to get to that menu.
It may not work for you guys, but this is what I did for my car to kluge together a workaround. Helps if you still have your contacts on your prior device (and working BT on that device):
Verizon isn't going to fix this especially when it's happening to other devices Samsung makes for OTHER carriers... Calling Verizon won't do anything except waste your time IMHO...
For anyone having connection issues I found a way to make it work on my Pioneer Bluetooth adapter in my car with a registry change. Aside from pairing problems I was getting communication errors.
Verizon isn't going to fix this especially when it's happening to other devices Samsung makes for OTHER carriers... Calling Verizon won't do anything except waste your time IMHO...
Can you tell us what exactly phones they would be and the carrier?
__________________
VZW, It's 2009! Time to embrace technology, not suppress it. - oops too late I've moved on over to the iPhone w/ AT$T!
Any one having issues with BT please call VZW and log your issue.
Complaing here will do nothing to fix the problem.
Call VZW, then call Samsung.
The squeaky wheel gets the ........BT fixed back to how it is supposed to work!
I called both Verizon and Samsung. Both CSRs singing the same party line: "We have had absolutely NO ONE call us about this." Samsung graciously offered to take my phone away from me for 10 to 14 days and "repair" it, I said no thanks. My month trial is up next week. Verizon of course said I couldn't extend the return period.
Thinking about bailing....
They both suck...
Last edited by LawyerInNC : 11-16-2007 at 02:20 AM.
I have called both VZW and Samsung and at this time even Level 2 at Samsung is aware of the problem and (along with level 3) compiling a list of people calling. I was told that the issue is being looked at and IF it can be resolved by an OTA fix it MAY be taken care of in a future update. Keep calling because if enough people call there will be a fix!
I have called both VZW and Samsung and at this time even Level 2 at Samsung is aware of the problem and (along with level 3) compiling a list of people calling. I was told that the issue is being looked at and IF it can be resolved by an OTA fix it MAY be taken care of in a future update. Keep calling because if enough people call there will be a fix!
This man speaks the truth!! Call in and let them know!
1. They are aware of BT issues with the device, and are studying them. I just asked them to add me to their count of complaints, both for the "multiple" issue, as well as loss of car kit functionality vs the 730.
2. Second, I asked for, and received an extension of my 30 day return window from 11/22 to 12/6, which I was told would give me a chance to try out the 6800, as it is being released by then.
For all of the complaints, at lease VZW is being flexible here.
I have called both VZW and Samsung and at this time even Level 2 at Samsung is aware of the problem and (along with level 3) compiling a list of people calling. I was told that the issue is being looked at and IF it can be resolved by an OTA fix it MAY be taken care of in a future update. Keep calling because if enough people call there will be a fix!
Can you please post the number to cal at Samsung?
__________________
VZW, It's 2009! Time to embrace technology, not suppress it. - oops too late I've moved on over to the iPhone w/ AT$T!
Woe Woe Woe upon them all
987-4357.
Login
Panel
