Related
I love Android, but very often I also hate it. Recently I was interested in getting this Bluetooth receiver for my car. The ideal scenario would be to be able to make calls, play songs, and navigate to an address by only pressing the button on this device on my dash and speaking, not touching the phone at all. Sounds great, right? And isn't this what Google Now and its voice actions are all about?
Well, seeing what a sorry state Bluetooth is in on my GNex, I think a device like this would be just about worthless. I have experienced no less than FIVE separate issues in attempting to get this scenario to work with the regular Bluetooth headset I currently own.
1) Bluetooth device disconnects every time I turn screen off. So when I turn screen back on, I have to re-pair the device.
2) The basic functionality of using Google voice actions over Bluetooth at all only works once. After that, it beeps, and then reverts to the handset mic and speaker. If you force stop Google Search, it will work again, but only once.
3) Pressing the button on the Bluetooth device activates old-school voice dialing instead of Google Now voice search. What's the point of this now that Google Now exists? I believe I have fixed this with the Bluetooth Launch app, but we'll have to see if it keeps working.
4) Music quality sucks, as we all know.
5) Google Now voice actions themselves are spotty. Sometimes advertised voice actions just result in regular searches instead. Sometimes it keeps listening for more input even though I've stopped talking, a force stop is required to fix this.
About the only thing that does work over Bluetooth is just regular calls that you initiate via the phone.
Which of the above issues do you experience, and can you share any workarounds? At this point, I honestly don't know what justification Google could give me to use this junk over an iPhone. I seriously believe they do not test anything, and do not care at all about their customers' experiences.
I have my Gnexus running 4.1.2 connected directly to my car's Bluetooth. I use it mostly for music and GPS, then calls sometimes, but rarely Google Now.
1) Doesn't happen to me ever. My phone stays connected until I turn the engine off and pull the key out of the ignition. I heard Bluetooth connection issues started with 4.2, hence why I haven't updated.
2) Not sure about this one. Google Now has always been spotty in my car (takes over 30 seconds to start up) and I'm not sure if it's because of Bluetooth or T-Mobile.
3) I think that's normal. Pushing the call button on my car's steering wheel activates my car's voice recognition system, not the phone's.
4) I use BT most often for music via Pandora and it sounds sounds fine to me. Occasionally there is a subtle skip, which I attribute to the wireless nature of Bluetooth. I would say the quality is 90% compared to wired.
5) Agreed. That seems unrelated to Bluetooth though.
I don't think there is a Bluetooth command for starting Google Now. Don't forget Bluetooth is a generic technology that is supposed to work with all phones, not just Android ones. I used to connect a Sony Ericsson phone for calls.
Except for accepting incoming calls and changing tracks/volume, I still have to initiate most actions by touching my phone. It sucks. Let me know if you find a good solution.
Sent from my Transformer TF101
Yeah, it seems at least some of these issues (the disconnecting, music quality) started in 4.2. #3 might be "normal", but is definitely not how it should be. You mention Bluetooth is a generic technology - this is true, but there doesn't need to be a special command for Google Now, the phone can just choose to respond however it wants to the standard "call" button/command. For example, with an iPhone, pressing the button on the Bluetooth device will activate Siri. Then you can speak any command or query you wish. There's no reason Android couldn't activate Google Now voice search in the same way, instead of the voice dialer.
I've been doing things same as you, doing everything via the phone except for answering calls or redialing the last number. I finally realized how useful voice commands could be when able to be summoned via Bluetooth. A couple simple updates to the Google Search app, and an improved Bluetooth situation in 4.3 could easily clear all this up. But after the many mistakes they've made, I'm not exactly holding out hope.
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah....all the issues I stated above are with that option checked.
xdp said:
Yeah, it seems at least some of these issues (the disconnecting, music quality) started in 4.2. #3 might be "normal", but is definitely not how it should be. You mention Bluetooth is a generic technology - this is true, but there doesn't need to be a special command for Google Now, the phone can just choose to respond however it wants to the standard "call" button/command. For example, with an iPhone, pressing the button on the Bluetooth device will activate Siri. Then you can speak any command or query you wish. There's no reason Android couldn't activate Google Now voice search in the same way, instead of the voice dialer.
Click to expand...
Click to collapse
Ah yeah, that's different then. None of the buttons on my car will activate any sort of voice recognition on my phone, because of the voice system in the car itself. Which sucks, because although it may have been advanced in 2009, smartphone voice tech has surpassed it by leaps and bounds, whereas my car software will never get updated.
So I think there's a better chance for an update to make this work for your setup than mine.
Sent from my Transformer TF101
tshelby73 said:
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Click to expand...
Click to collapse
Thanks for the tip!
I also added a Google now voice command short cut to my lock screen and launcher, so when I'm in the car I can quickly (hopefully) say a command.
Kind of sucks still that the call button doesn't do this, even my old school slider Nokia launched voice commands over Bluetooth.
LOL
I use mine and will do voice commands by pressing button. It will not search though just make calls. On CM based ROM'si have to freeze the voice dialer the ROM comes with or the cm dialer is default. I don't have the listen over Bluetooth checked. Maybe that checked would give me search feature using button.
Sent from my Galaxy Nexus using xda app-developers app
One of the more frustrating things for me with my Verizon HTC One has been the inconsistency of the following desired functionality:
1. Phone is connected to the car's bluetooth (2013 vehicle)
2. Phone is on Google Now screen
3. Car is on any audio input (let's say I'm listening to my local ESPN Radio station on AM radio)
4. I say "Okay Google"
5. The car begins "listening" -- when I speak my Google Now voice command, I'm doing it through the car's mic, and any responses are through the car's speakers
So that is what I want, and that is what has happened most of the time since I've had my HTC One. Just last week (and at other times), it stopped doing that. Here is what happens now:
1. Phone is connected to the car's bluetooth (2013 vehicle)
2. Phone is on Google Now screen
3. Car is on any audio input (let's say I'm listening to my local ESPN Radio station on AM radio)
4. I say "Okay Google"
5. The car's mic stays off and the speakers keep playing the AM station. My Google Now command will be listened to by the phone's mic.
Other phone/car interactions -- making calls, listening to Bluetooth Audio (using the Bluetooth/Aux car input) -- all of them to continue to work properly. This is the only thing that breaks.
I don't know what changed; I don't think anything changed, honestly. When it has happened previous times, I've also not figured it out, and then it would start working again. This time, it's been a week so now I'm trying to find a solution.
Thanks for any help that can be given. Hopefully I've detailed this out enough.
in google now, under settings > voice. Is bluetooth headset enabled?
synisterwolf said:
in google now, under settings > voice. Is bluetooth headset enabled?
Click to expand...
Click to collapse
synisterwolf, thank you so much -- it was not selected. I enabled it, tried it, and all is well again. I feel like a bonehead for not checking that, but I had forgotten about that setting.
So the one mystery still is how it got changed, but at least I have a good starting point next time this happens.
Thanks again, and have a great week.
bigperm71 said:
synisterwolf, thank you so much -- it was not selected. I enabled it, tried it, and all is well again. I feel like a bonehead for not checking that, but I had forgotten about that setting.
So the one mystery still is how it got changed, but at least I have a good starting point next time this happens.
Thanks again, and have a great week.
Click to expand...
Click to collapse
app updated, maybe it unchecked itself? glad you got it working. :victory:
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.
guys
pixel 3 xl is not playing well with my BMW 323i 2010 bluetooth call system.
When i get a call the ringtone comes through the car speakers. Then when i accept the call there is no more audio through the car audio system.
i tried unpair and reparing and same issue.
my original pixel xl works fine.
any idea? any1 having similar issue?
I have a 2013 328i, and this is the first phone I've had since the Nexus 6 that actually works well with it for music. I always had problems with the Bluetooth freezing.
Sent from my Pixel 3 XL using Tapatalk
sometimes telling the assistant to play music will get it to play nice if it is still paired just not sending audio. but for phone calls, thats weird
Did some troubleshooting today.
So after connecting the call if I manually select phone on the pixel3 and then switch to car audio Bluetooth then it starts working.
But it doesnt start automatically when the call connects.
I will log it with Google and hope for a fix.
Thanks guys.
Try resetting the cache for the Bluetooth app in the app manager in settings (You have to tun on system apps to see it)
2013 BMW 328i, never had an issue with any other phone, seems at random call audio will stop working over Bluetooth in the car and the only remedy is to reboot the phone. Have tried everything with no solution.
jrock60 said:
2013 BMW 328i, never had an issue with any other phone, seems at random call audio will stop working over Bluetooth in the car and the only remedy is to reboot the phone. Have tried everything with no solution.
Click to expand...
Click to collapse
yep, my issue still not fixed and making me crazy.
1 thing i am gonna try today is that disconnecting p3xl from my samsung gear s3 and see how it works while only connected to bmw's audio. if that does not work then i will send this phone back.
it is insane how many software issue this phone has.
Argh, same thing with my 2011 128i. NEVER had a single problem with my Pixel 1 XL, got the 3 XL a few days ago. Today I need to make a call in the car, pair the phone and... no audio. In fact I think it was still playing music, even though it showed "Connected". I have the "Professional" audio system; ie: the simple one. Not with the big display etc, iDrive I think it is.
Could you let me know the bug ID you logged and I'll star it and participate in it with logs etc as they request them? I don't make a lot of calls in the car but I often drive into work listening to conference calls so this is seriously annoying.
My two bluetooth headsets work fine, so it doesn't appear to be a overall issue with bluetooth headset audio etc. I might try it in my wifes car just to see if it works there, for more datapoints too.
Very, very odd... I read a suggestion to boot into safe mode and connect the phone to the car and that worked, everything is fine now. What's stranger, to me anyway, is that it continues to work fine! But as odd as it sounds, this is something to try.
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
I may not have the answer that you want to hear but I did find a temporary solution. There's an app in the play store nRF Connect that works. Slide over to bonded, put devices in pairing mode and hit scan and wah lah. Any questions I'll do the best I can to help.
I've noticed the same on my galaxy buds, but when I connect another pair of wireless earbuds that i sometimes use they connect as soon as i turn them on when Bluetooth is activated, without me manually having to go into the settings and do it. Not sure the reason for this. Would've thought the earbuds that's actually made by Samsung would be the ones connecting right away.
hotshot646 said:
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
Click to expand...
Click to collapse
Hej...
I don't if this would help You...
When I got the Note 10+ there's Was, out of the box on initial settings, active few Bixby Routines... and that, till i figure out this, was driving me crazy... When I turn Bixby Routines off everything back to normal...
Well I've had a similar problem. For me the issue is that it always autostart even tho I have BT autoplay unchecked in the car. If I have listen to any music, audio books, podcasts and turn them of when I exit the car, not leave them in the background, they will start playing even if the cars media system is offline.
Works perfectly with my wifes OnePlus 6, but not for me. Extreamly annoying to noticed that the audio book is playing after a 60min drive and I haven't heard anything..
I tried the app Tasker, it was a compleat waste of $4 for me anyway, didn't work, will try nRF Connect now.
I don't want to have BT of due to that I aways have my Jabra buds with me so that I can talk while driving if needed.