Help bluetooth problems

[jlatour88]

is it just me or does the droid not like my bluetooth headset? its paired and everything and the phone is connected but the headset is not being used. i tried accessing the voice dial on my headset and nothing happens i try calling someone on my droid and the sound comes out of the speakers not the headset. anyone have any suggestions?

 

[Carl C]

Android is very itchy when it comes to bluetooth anything

Maybe if you post the specific headset your using someone using the same model could possibly help?

 

[koticphreak]

I'm having a similar problem. the bluetooth headset connects just fine, and calls go through it both ways, but the button on the bluetooth headset does NOTHING... so I still have to make/accept the call on the phone itself - defeating the purpose of handsfree.

I'm using the Jabra BT 250v

 

[koticphreak]

I'm having a similar problem. the bluetooth headset connects just fine, and calls go through it both ways, but the button on the bluetooth headset does NOTHING... so I still have to make/accept the call on the phone itself - defeating the purpose of handsfree.

I'm using the Jabra BT 250v

BUMP - anyone else having similar problems?

 

[DroidPower]

i was a bluetooth person, but they have so many issues i now use the 3.5 ear phones, its clear and not frustrating. I have tried so many bluetooth pieces and everyone could never get the voice activation right.

Use the 3.5 and live happy ever after

 

[koticphreak]

i was a bluetooth person, but they have so many issues i now use the 3.5 ear phones, its clear and not frustrating. I have tried so many bluetooth pieces and everyone could never get the voice activation right.

Use the 3.5 and live happy ever after

My Jabra BT 250v has been working beautifully with the last 4 phones I've had... it took a while to find one that worked (went through 2 motorola bluetooths prior to this), but this one works great - now just need it to work on my droid!

 

[un8elievable]

Android is very itchy when it comes to bluetooth anything

Maybe if you post the specific headset your using someone using the same model could possibly help?

after pairing, try un-checking the bt altogether then turn it back on. this fixed my bt issues with my car and headset. good luck

 

[Freebyrd]

My bluetooth headset has problems also. It will play music but on a phone call I can hear the other person but it will not transmit my voice so I have to dig the phone out. Oh, is there a way to turn on auto answer while connected a the bluetooth headset?

 

[scorrpio]

It has been confirmed that at this point, there is no voice dialing support via Bluetooth. Google up 'Google code android issues', top result, and star issues 1181 and 1412 - both have to do with this issue.
That said, my BlueAnt Z9i pairs with the Droid perfectly, headset rings when phone does, I can take a call by tapping a button on the headset, and end call by tapping that button again. I can redial last number via headset, too. Did not test out the remaining functionality (i.e.rejecting a call, transferring to/from headset, call waiting/conference). But voice dialing over BT is a derfinite no.
A bummer for sure. Hope it'll get fixed soon.

 

[koticphreak]

But voice dialing over BT is a derfinite no.
A bummer for sure. Hope it'll get fixed soon.

Maybe its just me, but that seems like a HUGE minus. I really hope they fix this ASAP, it's like the iPhone all over again.

 

[scottjays]

very annoying that somehow bluetooth voice dialing is disabled. clearly not a
hands free phone. can't use this in my car while driving
see ongoing thread at the motorola support website.
https://supportforums.motorola.com/thread/15939?start=0&tstart=0

 

[Freebyrd]

Thanks for the info Scorrpio. What a shame, first on Motorola and second on ME for assuming it would have bluetooth functionality.

 

[Soda Popinski]

I can't get any sound to come out of my bluetooth. It looks like everything has connected but then no sound.

 

[stantheman]

Hello Droid users, I have the Samsung Moment which is also an Android phone. I have the same type of problems with bluetooth and it appears to be widespread among all Android phones. This would appear to point to software as the culprit. Google must be aware of this by now and is hopefully working on a fix. This is a major glitch and it would be nice if someone would step forward form one of these companies and say,"Yes, we're aware of the problem and we're working on it."

 

[Clementine_3]

I had no problems hooking up my Plantronics head set or Blue Ant car BT, both work nicely (besides the no hands-free of course).
What I found out today though is that if I have BT activated and switch to speaker-phone it will revert back to BT when the screen times out. I was on a call, BT battery was dying so I hit speaker on the droid. It switched over no problem but then as soon as the screen 'blacked' it went right back to the BT earpiece. What's up with that??

 

[kharman777]

I'm a new Droid user, and I can't seem to be able to pair the Jabra bluetooth headset to the Droid. I've tried turning bluetooth on & off, I've set the phone to discoverable, and hit 'scan for devices'. I've tried turning the headset off and on, and all permutations of the above. No luck. The Jabra (brand new) is supposed to automatically pair.
Any suggestions?
ps - I've yet to find a bluetooth headset that works consistently and well with any of my phones - I'll be pleasantly surprised if I can get this to work.

 

[swvajanyatek]

I've got a similar problem. I can pair my headset fine, but it can't stay connected. Usually, when I restart my phone, it will connect upon the first call, but after that its 50/50, and whenever the connection does eventually drop, it almost always requires another restart of the phone. It sounds like an os update is the only likely resolution.

 

[kharman777]

As it turns out, there's a problem with the Jabra bluetooth. I connected my old blueant bluetooth headpiece, and that one works perfectly! I don't have to re-pair it every morning. I just turn on the blueant, and it works. Also, whenever I get a phone call, I answer it through the blueant, and it works EVERY TIME! I'm so happy with my Droid for this reason. It's the first phone I've had where bluetooth actually works.

So, my solution was to get rid of the Jabra headpiece and use the BlueAnt headpiece. I've had no problems since then.

 

[mswhite60]

I have a Plantronics Voyager 510 and it pairs just fine. I can answer a call and end a call, but cannot initiate or voice dial. I do love this headset and use it for hours daily to do software demos and keep my hands free. It worked flawlessly on my old WinMo phone with every feature.

I also can't seem to figure out how to get music or movie audio to transmit to the headset - is there a setting I'm missing or is that just a 510-Droid problem?

-Matt

 

[kharman777]

Well, with the BlueAnt I can voice dial with no problem - it has worked every time! I haven't done anything special - simply paired it the first time, and it's worked ever since.

 

[evestal]

I have a Voyager 510 and it works fine for everything except voice dialing. I understand that Android does not support voice dialing with the press of the BT headset button YET. Can you tell me exactly how you would voice dial someone like John Doe - mobile that's listed in your contacts?

 

[kharman777]

You're right - I can't do it with the press of the BT headset button. I do have to select the microphone on the Droid first. Bummer!

 

[bamaredwingsfan]

I have a slightly different problem with my bluetooth. The volume is very low, even when i have it set to max. I have the plantronics 220 which has a bud that goes inside the ear to an extent. I need a bluetooth that has volume level to an almost eardrum splitting capability. Well not quite that loud, but it needs to be pretty high, as i don't have the best of hearing anyway. Anyone have any suggestions for me to try? I like the current one i have, its just the volume level that bothers me.

 

[jlatour88]

ya iv read most of the replys and i agree..... the droid doesn't have a very good hands free option. that sucks big time. i cant even find my BT headset anymore lol. think i got pissed at it and threw it somewhere. anyway im more of a txter anyway.

 

[AzJazz]

Yep. The Android Bluetooth issues are pretty huge. I've written quite a few posts about my BT HFL problems on multiple forums.

One BIG issue may never get solved (or, may be quite a while if it can be solved): Voice dialing via the Bluetooth connection.

From what I've read, Google's architecture is different from all other phones out there: Google does real-time Universal Search voice recognition very frequently (and, even moreso with 2.1). Whenever you issue a voice command to your Droid ("Call Yoda at Work", "Navigate to Nearest Starbucks"), the analysis of that command does not occur directly on your phone. Instead, the audio is digitized/processed and sent up to Google's Voice Recognition servers. Then, Google sends the results back down to your phone.

When you have used the Voice Universal Search in the past, there has probably been a lot of times that Google will come up with wrong answers - especially when you are trying to do something dealing with the Contacts stored on your phone/GMail. I personally have had tons of problems.

An underlying problem with Universal Search is this: It's "universal" - many times with no basis for context of the voice request. Your Droid knows that you're asking for something, but it doesn't know why you are asking (or what you are really asking for).

So, if I try to issue a voice command to "Navigate to Joan Sellner" (who is stored as a Contact), Google seems to frequently search businesses before it investigates Contacts. As a result, I get directions to the nearest Long John Silver's. Google found lots of "hits" with similar sounding restaurants, and so it assumes it found the match for what I was looking for.

No other phone that I know of does voice searches in this manner. When you issue a "Call Joe Schmoe at Home" request on other phones, the audio is processed on the phone itself when trying to find a match.

Since Google searches everything, they had to come up with a priority scheme of what they would search for first when someone initiates a Voice Universal Search. It seems to me that Google selected businesses for the top of the pile.

If Google selected Contact Names to be first in the search order, then tons of people would be complaining about how their Android phones would be falsely matching to entries in their Contacts list instead of listing a restaurant they were trying to find.

I'm not saying that this particular issue is insurmountable (it's not), but I wanted to give y'all a heads-up on one of the reasons why this issue isn't being solved as quickly as we would like. This may only be fully solved when Google's Voice Recognition servers get much, much better at voice analysis.