I have paired my Plantronics Marque Bluetooth headset with my Galaxy Nexus GSM model. The headset is paired and connected. I can say "answer" to answer an incoming call, but I can't hear anything through the BT headset. I think that the caller can hear me, but I'm not sure.
I also tried to use my Motorola H720 headset and had similar results. The Plantronics headset works fine with my HTC Sensation. Is there anything that I should do differently in order for the phone audio to work with the BT headset?
I think there is a problem with the bluetooth stack in the Galaxy Nexus, I've been encountering sync issues with my car which works fine with Nexus S and Nexus One.
Should I contact Google about this? Using BT is important while I drive. I have gotten used to not holding a phone up to my ear while I talk, so this could be a deal-breaker for me. I really like this phone and don't want to give it up, though.
Hi,
I have an issue with voice search and voice dialer app. I recently came from a SGS with cm9 and these features worked well. I replaced it with a gnex and it does not work well. I am on stock ICS (rooted).
When I use my Bluetooth earpiece I am able to hear commands and it seems to work reasonably well. When I use it over the speaker or connected to my car Bluetooth I do not hear commands and I get off the wall searches.
Any assistance or thoughts on this?
Thanks
I have a Plantronics BT headset that I've been using for years.
It has a "main button" that, when long-pressed, starts a voice dialing dialog with the phone, even when the phone is locked.
Or it did, from the original Captivate running Froyo all the way to my Kit-Kat GS3.
This no longer works on the G4. I get the beep indicating that the long press was registered by the headset, but nothing happens on the phone.
I know I can use "OK Google" to call Google's Voice Search and then tell it to dial, but that only works when the phone is unlocked and the screen is on, which defeats the whole point of hands-free operation.
LG's Voice Mate simply sucks, at least through my Plantronics. It doesn't capture voice input, it interrupts it half a second after it starts listening... It is unusable.
Does anyone have an idea how to enable the good old voice dialing through a BT headset? OK, it was ugly and idiotic with its stupid "Select 1 for mobile..." prompts, but it worked.
It doesn't have to be that. As long as I can voice-initiate a call without fiddling with the phone, I'll be happy.
The G4 turned out to be a great phone, but this particular issue is irritating to me.
I have the same problem with my company-issued Rugby Pro running Jelly Bean. Samsung's S Voice is hit-and mainly miss. My old Rugby II flip was always ready to dial or answer if Bluetooth was on. I use it on a motorcycle, so no button pressing on the phone is possible. I have been trying utter! (still in Beta) the last few days, and it is the most promising that I've found, although it has way too many other things it tries to do. Otherwise, I'll have to try and swap this phone with someone for a i(don't even want to start using these)phone, or go back to the flip and just carry the Pro for use via wifi to get company email.
Voicemate is garbage.
Go into apps under settings and disable as many Voicemate related items as possible.
This will cripple Voicemate and Google voice search will launch on Bluetooth press. It works beautifully.
All the commands I've tried work. One of my favorites is "play <song name>" if you have Google music all access.
http://www.greenbot.com/article/2359684/a-list-of-all-the-ok-google-voice-commands.html
Sent from my LG-H810 using XDA Free mobile app
Hi everyone!
I'm searching a method to "call" Google Now when press the hands-free button on my car or voice command on my bluetooth headset.
Searching on internet I've found that it's a strange thing on Android, that call the old Voice Dialer insted the new Google Now :\
I've found an app, Bluetooth launch but on my Nexus 5X seems to not work...another app, GNow, in it's description talk about a changing in Android 6 and that their app isn't necessary enymore, but I haven't found nothing about on internet.
Note that this app's functionality has been incorporated into Android 6.0 (Marshmallow); so don't install if you're on 6.0 or later.
Click to expand...
Click to collapse
Any suggestion?
FullMetalGlicoz said:
Hi everyone!
I'm searching a method to "call" Google Now when press the hands-free button on my car or voice command on my bluetooth headset.
Searching on internet I've found that it's a strange thing on Android, that call the old Voice Dialer insted the new Google Now :\
I've found an app, Bluetooth launch but on my Nexus 5X seems to not work...another app, GNow, in it's description talk about a changing in Android 6 and that their app isn't necessary enymore, but I haven't found nothing about on internet.
Any suggestion?
Click to expand...
Click to collapse
Have you tried going in your Google now settings>voice>and enabling Bluetooth headset recording?
This works for my lg tone hbs810 Bluetooth headset giving me any ok Google option through the headset by tapping the call icon. Idk how it will work with the car though.
Let me know if it helps.
Sent from my annoying Nexus 5X
Nexus 5x stock unrooted here. I used to be able to both start Google Now by saying "ok google" or by long-pressing the BT button. (after the various necessary settings changes had been made of course).
I can't now. I've just followed the exact same path and discoveries the OP made.
I started on 6.0.1 and am on 7.0 OTA w/ Sep 2016 security updates. I *believe* it broke when my pricey but unreliable Philips BT headphones died. I switched back to an Anker Soundbuds Sport. I think that's when I lost that functionality. Can't start with "ok google" or with the BT headset button.
If I say "ok google" into phone's mic, I can then finish from my BT headset.
I know for certain I used to be able to launch with a button press as well as "ok google" so I think the problem is certain headsets. My BT button definitely works, it'll pause and start any music app I'm in. Answer calls, hang up. That's about it.
Would sure love a way to get this functionality back on my current Anker headphones.
And to reiterate yes my settings are correct, BT is enabled in both locations, ok google always listening is on etc etc etc.
I realize it's an old thread, but it's still an issue for some....
Has anyone tested the microphone on their bluetooth sets yet with the Pixel 2 XL?
I'm scared I might have a defective phone. My bluetooth headset connects to my phone just fine, and even plays audio just fine, however, the microphone is not picking anything up. This means I can't use hands free calling, or hands free Google assistant.
I know it's not my bluetooth device because it works fine when connected to my older phone (Nexus 6P)
Has anyone else had trouble with doing microphone over bluetooth? I'm not sure if I need a replacement or just a software patch.
For reference, I use the LG HBS-1100 bluetooth headset.
http://www.lg.com/us/bluetooth-headsets-headphones/lg-HBS-1100-Silver-tone-platinum
Later today, I will try a different bluetooth device.
EDIT: I tried with my older pair, the LG HBS-750, same issue.
I've got a soundbuds tag headset, the connection speed is faster and my phone calls seem ok. I've only made like 2 calls so far though.
@Traceguy I've had several lg headsets and they all sucked. No could hear me or I was breaking up all over the place. Switched to the jaybird x3 and it's been perfect ever since.
Disclaimer: I'm on a Nexus 6. Waiting patiently for the 2XL to arrive next week...
I've talked with Google support, they helped troubleshoot, but nothing could be found out of the ordinary, and it's now being elevated to the next level support team. They have my phone number and will call me back when they find anything.
My Bluetooth version is up-to-date, but there is a update pending for my Pixel 2 XL, which hasn't made it to my phone yet. That may or may not help. IDK
I will get a friend later today to connect his bluetooth to my Phone and test the mic. Maybe it's a total LG issue.
I'm gonna say it's an LG issue. I went through 4 pair of the infinium headsets. All had issues with ppl hearing me. Even when paired to different phones.
Larzzzz82 said:
I'm gonna say it's an LG issue. I went through 4 pair of the infinium headsets. All had issues with ppl hearing me. Even when paired to different phones.
Click to expand...
Click to collapse
I don't know much about how Bluetooth works, do Bluetooth devices use drivers similar to USB devices? Maybe the Pixel 2 XL is missing the necessary drivers for the LG HBS sets. That is something that can be fixed with a software update.
It's not an LG issue. It's happening with my car's head unit and others are reporting it in the Pixel User Community. This is one of a few strings that include it. https://productforums.google.com/fo...pPfDGvkNw;context-place=forum/phone-by-google
robsw said:
It's not an LG issue. It's happening with my car's head unit and others are reporting it in the Pixel User Community. This is one of a few strings that include it. https://productforums.google.com/fo...pPfDGvkNw;context-place=forum/phone-by-google
Click to expand...
Click to collapse
I'll just wait patiently to see what happens. I'm hopeful it's not a hardware defect with the bluetooth chip in my phone. I never use bluetooth car's head unit, for whatever reason it drops every few seconds or minutes. I'm driving a 2013 Charger, so I'd expect better results. I use aux, and thanks to the USB-C Dongle, I am not stuck without a way to play my music in the car, though without the microphone input from my headset, I can no longer tell Google which song to play.
I just came here to check.
I can place calls and be hear over bluetooth both on the car and my Sol Republic headphones.
Assistant can not hear over either. Assistant does work over a wired headset.
Support had me boot into safe mode, spoiler: Assistant won't even launch in safe mode, and factory reset which did not fix the issue.
They have no resolution at this time, but are looking into it and wanted me badly to leave feedback on the problem. I'd suggest anyone with the problem leave feedback as well.
At least I'm not the only one. They said I'm the first to call. ut then again they also said it coud be a hardware issue which I just can't see.
Mine, too. I have a Pioneer head unit. Playing is fine, Assistant is fine when not connected to Bluetooth, but Assistant just will not work over Bluetooth. I use this all the time so it's already driving me crazy and it's only been one day. (Same head unit worked fine with previous phones... Pixel 1, Nexus 6p, and OnePlus One.)
I'll add myself here as a +1... Same symptoms. Seems like microphone over BT doesn't work.
I have a Plantronics v5200 and it works for calls. But not for assistant. Sucks......it will activate assistant on a long press. But registers no sound. Works perfect on my original xl. So it's not the headset.
Also confirmed that it WILL work just fine if I launch it with "OK Google" instead of a squeeze or button. So it can work... Starting to seem like a bug in Assistant, which makes me hopeful for a decent fix.
@Anaelith Yes, but did you enable bluetooth Mic input from settings? If not, saying "Okay Google" will use the internal microphone in the phone instead of using bluetooth.
Go to Google Now settings > Voice > Enable "Bluetooth headset". This option "Records audio through Bluetooth headset if available"
That aside. I have tried bluetooth mic in a phone call and it works. I also tried Bluetooth audio with my Car's head unit and have not received a single drop. So the drop problem was related to my Nexus 6p.
Seeing as the mic works for phone calls, the problem seems to truly be software related.
Using a Jabra Eclipse, all settings correctly enabled. Not only does the Google Assistant not work, but neither does voice texting.
Worked fine on my original XL, so I know the earpiece is good.
Guess they better look into this...
Works fine on calls, won't work on assistant.
Man, I'm just gonna get my phones six months after release. It sucks to have to debug all this stuff for Google.
[UPDATE] I wrote here and I have a smaller pixel 2, but I have this issue too.
I'm another one. None of my Bluetooth microphones work on the pixel 2 XL, but do on my 6P
Hi everybody I think I may have found a possible fix/workaround
Settings\search\voice\Ok Google detection
Turn on ok Google anytime turn on trusted voice
(May have to do voice training)
Now when I press the call button and say "OK Google" then the command I hear it in my headset and it works. If I don't say ok google it doesn't work. It may be that it's actually my phone picking it up and not the Bluetooth mic but I hear the audio in my headset and can use it to search Google and play music. And it also picks up my audio in calls
I am on a regular pixel 2
Nealian said:
Hi everybody I think I may have found a possible fix/workaround
Settings\search\voice\Ok Google detection
Turn on ok Google anytime turn on trusted voice
(May have to do voice training)
Now when I press the call button and say "OK Google" then the command I hear it in my headset and it works. If I don't say ok google it doesn't work. It may be that it's actually my phone picking it up and not the Bluetooth mic but I hear the audio in my headset and can use it to search Google and play music. And it also picks up my audio in calls
I am on a regular pixel 2
Click to expand...
Click to collapse
I tried that.no go.. quite frustrated with this right now. Never realized how much I use this feature.
Sent from my Pixel 2 using Tapatalk
I am facing the same issue. When connected to my BT headset or car BT, it's like my mic mutes after the hot word. Also, some phone calls can't hear me at all. Have to hang up and call back, then no issues. I've also contacted support and sent in feedback with system info to create a ticket.
I was having different issues as well, so I wiped my device and manually put all of my stuff back on (vs doing a restore), just to see if this fixes anything. Haven't retried BT yet, but will this evening. Other issues appear to be gone and the phone feels a lot smoother since doing this though. I think my restore from my OG Pixel didn't go so well.