Hey guys, pretty sure a lot of people out there are using a smartwatch along with their Pixel so maybe someone can help me with this: when my Galaxy Active 2 smartwatch is connected most of the time I can not use voice input with Google Assistant / search. When I wake up the Assistant by long-pressing power the device starts listening but apparently can't hear me. When I disable Bluetooth or power off the watch everything's working just fine.
The weird part is this though: most of the time the watch is connected, a Bluetooth icon with two dots on the left and right can be seen in the status bar, but not always! And only when the icon is NOT there, while the watch is STILL connected and fully usable, voice commands DO work! What on earth is going on there?
Same thing with the camera app: when the watch is connected and the icon is there, the cam app tells me a Bluetooth microphone is connected. When the watch is connected and the icon is NOT there, the app doesn't tell me. With the cam it is not a problem either way though because here I can choose what audio source I wanna use, while in the Google app I can't.
Any ideas?
It seems that your Galaxy Active 2 gets recognized by the P6 as a Bluetooth microphone capable device, ergo it won't use the in-build phone microphones.
Does it have microphones, by the way?
You can always change the system "primary" source of a microphone/sound source by going into the Sound menu (press volume rocker, press on three dots, change there or go into See more).
Morgrain said:
You can always change the system "primary" source of a microphone/sound source by going into the Sound menu (press volume rocker, press on three dots, change there or go into See more).
Click to expand...
Click to collapse
Yeah I'm looking for a way to do that, change primary audio source, but I don't see any options for that in the sound or any other menu...
I'll add another bug to the list.
When a watch capable of making and receiving calls (Huawei Watch GT2 Pro) is connected, initiating a phone call from a BT headset/earbuds starts a phone call through the headset, but as soon as the phone call connects, the audio switches from BT headset to phone internal speaker.
You have to disable the "phone" function of the BT settings for the smartwatch to get this to work properly.
This didn't use to be the case, so it's clearly a new bug either in P6P or Android 12.
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
Hi.
I can't get OK Google to work via my bluetooth microphone.
I have the Google app open and it says "say OK Google".
It works 10/10 when I say it directly into my phone.
When I press the microphone button manually, it picks up 10/10 commands via my bluetooth headset.
Ok Google detection is ON for the Google App. (and it works via phone)
Hands-free -> For bluetooth devices = allowed
"Record audio through bluetooth headset if available" = ON
When I do the "OK google voice model" guide, where it asks you to say OK Google 3x, it doesn't listen to my headset at all. It picks up nothing.
As I said when I press the mic button manually it works 10/10, there's nothing wrong with the bluetooth set or connection.
Any ideas?
DoubleYouPee said:
Hi.
I can't get OK Google to work via my bluetooth microphone.
I have the Google app open and it says "say OK Google".
It works 10/10 when I say it directly into my phone.
When I press the microphone button manually, it picks up 10/10 commands via my bluetooth headset.
Ok Google detection is ON for the Google App. (and it works via phone)
Hands-free -> For bluetooth devices = allowed
"Record audio through bluetooth headset if available" = ON
When I do the "OK google voice model" guide, where it asks you to say OK Google 3x, it doesn't listen to my headset at all. It picks up nothing.
As I said when I press the mic button manually it works 10/10, there's nothing wrong with the bluetooth set or connection.
Any ideas?
Click to expand...
Click to collapse
I don't think "OK Google" is intended to work from the microphone itself. A long press of my headset button brings up Google Now without saying "OK Google". I trained it for my voice on the phone, just in case I ever want to use it without the headset.
JimSmith94 said:
I don't think "OK Google" is intended to work from the microphone itself. A long press of my headset button brings up Google Now without saying "OK Google". I trained it for my voice on the phone, just in case I ever want to use it without the headset.
Click to expand...
Click to collapse
Yes the "OK google" is intended for the microphone... how else are you going to say it? The only thing is that android chooses to listen to the internal microphone, and then when you say OK google into your phone it starts checking for bluetooth devices and it switches listening to that for the actual command. At least, that's what's happening on my device.
Why wouldn't they make it so it listens to your bluetooth device in the first place? It's connected so you can assume you are using it (they apply the same principle for audio output).
I use a bluetooth headset on my helmet, and the buttons are already used for play/stop, and forward/back.
But that's not the problem, I can easily launch Google app with a tasker whenever I connect my bluetooth device.
I found a workaround though after trying about 10 apps, most don't work.
Smart Bluetooth Headset allows me to remap functions (not buttons, which never works for me) of my bluetooth device.
I've now set it to replace "redial function" with "Voice assistant" which basically opens Google app and starts listening. Great because I didn't like the redial function anyway.
DoubleYouPee said:
Yes the "OK google" is intended for the microphone... how else are you going to say it? The only thing is that android chooses to listen to the internal microphone, and then when you say OK google into your phone it starts checking for bluetooth devices and it switches listening to that for the actual command. At least, that's what's happening on my device.
Why wouldn't they make it so it listens to your bluetooth device in the first place? It's connected so you can assume you are using it (they apply the same principle for audio output).
I use a bluetooth headset on my helmet, and the buttons are already used for play/stop, and forward/back.
But that's not the problem, I can easily launch Google app with a tasker whenever I connect my bluetooth device.
I found a workaround though after trying about 10 apps, most don't work.
Smart Bluetooth Headset allows me to remap functions (not buttons, which never works for me) of my bluetooth device.
I've now set it to replace "redial function" with "Voice assistant" which basically opens Google app and starts listening. Great because I didn't like the redial function anyway.
Click to expand...
Click to collapse
I guess we have very different headsets. My Plantronics Voyager Legend uses one tap to answer or end a call, double tap to redial the last number, and long press to activate Google Now or whatever else you choose to program it to. It sounds like you have programmed a button to open Voice Assistant, which accomplishes the same thing as my long press.
JimSmith94 said:
I guess we have very different headsets. My Plantronics Voyager Legend uses one tap to answer or end a call, double tap to redial the last number, and long press to activate Google Now or whatever else you choose to program it to. It sounds like you have programmed a button to open Voice Assistant, which accomplishes the same thing as my long press.
Click to expand...
Click to collapse
Yeah, that's because it's not a bluetooth headset used primarily for talking, but more for playing music.
Still I don't see why android is using ONLY the internal mic even when you have a bluetooth A2DP device connected.
DoubleYouPee said:
Yeah, that's because it's not a bluetooth headset used primarily for talking, but more for playing music.
Still I don't see why android is using ONLY the internal mic even when you have a bluetooth A2DP device connected.
Click to expand...
Click to collapse
I'm guessing that having the microphone on all of the time would kill the headset battery pretty quick. When Chrome enabled Google Now on the desktop, I could never get my headset to trigger it either. The only way I could get it to work was to click on the microphone icon on the screen.
JimSmith94 said:
I'm guessing that having the microphone on all of the time would kill the headset battery pretty quick. When Chrome enabled Google Now on the desktop, I could never get my headset to trigger it either. The only way I could get it to work was to click on the microphone icon on the screen.
Click to expand...
Click to collapse
Well I guess it's a valid point, but in my case (I use it on my helmet) it's always playing music anyway, so it already has a constant connection to my phone.
For other people, it wouldn't be a problem either because it would only have the microphone on when the Google App is in the foreground. So if you don't need it it's not used at all.
JimSmith94 said:
I guess we have very different headsets. My Plantronics Voyager Legend uses one tap to answer or end a call, double tap to redial the last number, and long press to activate Google Now or whatever else you choose to program it to. It sounds like you have programmed a button to open Voice Assistant, which accomplishes the same thing as my long press.
Click to expand...
Click to collapse
I use the same headset and I experience issues with the long press-action. When I do so, the phone replies "wait", the screen says "Initialising", there's a slight static in my headset and then - nothing...
Latest firmware is installed and I have ticked the bluetooth recording-box in GoogleNow.
Any ideas?
Hi, for this bug you can use thé application BT gnow.
My problem is an other, Google now audio is routed through the a2dp channel and not the hsp headset channel
my OK GOOGLE stop working from time to time. I rarely use it now.
I have the same issue, i cant get the activation of the "ok google" hotword via a wired headset nor a bluetooth headset on a Pixel... any advice?
DoubleYouPee said:
Hi.
I can't get OK Google to work via my bluetooth microphone.
I have the Google app open and it says "say OK Google".
It works 10/10 when I say it directly into my phone.
When I press the microphone button manually, it picks up 10/10 commands via my bluetooth headset.
Ok Google detection is ON for the Google App. (and it works via phone)
Hands-free -> For bluetooth devices = allowed
"Record audio through bluetooth headset if available" = ON
When I do the "OK google voice model" guide, where it asks you to say OK Google 3x, it doesn't listen to my headset at all. It picks up nothing.
As I said when I press the mic button manually it works 10/10, there's nothing wrong with the bluetooth set or connection.
Any ideas?
Click to expand...
Click to collapse
I'm clueless :silly: but I have a Moto G5 Plus that had this issue I fixed today and another android phone a few years back that had the same issue.
I'm posting this around in a few forums since there doesn't seem to be much info on this anywhere. Maybe it will help.
To fix the broken setting that causes Google search / voice to text apps to not work with Bluetooth Microphones in my phones, I did the following:
Note: This will erase your google data on the phone maybe including your linked credit card authorization from your bank in android pay (tap payment only, not Wallet.) which I seem to recall having to re-set it up with my bank since they are very secure with that, so make sure you are prepared for that possiblity. It won't delete your linked accounts or authenticator two factor auth. Just the core googly stuff and settings related to the local settings on the phone.
Go into settings > apps > "Google". Disable it to reset it back to the original version, then enable it again, it should auto update back to current version later. Still in the Google app, click on storage, then manage space > clear all data.
Go back to settings > apps > show system apps. Find Google Services Framework. Click storage, click clear data.
Your Bluetooth microphone should now start working again. You may just get away with deleting the data on the framework app, I usually do both since I don't want to mess around any longer than I have to.
That didn't worked for me, although in my headphones manual says to press bluetooth sync button once for Google Now/Siri. I have PHILIPS SHB3060BK/00 headset.
DoubleYouPee said:
Hi.
I can't get OK Google to work via my bluetooth microphone.
I have the Google app open and it says "say OK Google".
It works 10/10 when I say it directly into my phone.
When I press the microphone button manually, it picks up 10/10 commands via my bluetooth headset.
Ok Google detection is ON for the Google App. (and it works via phone)
Hands-free -> For bluetooth devices = allowed
"Record audio through bluetooth headset if available" = ON
When I do the "OK google voice model" guide, where it asks you to say OK Google 3x, it doesn't listen to my headset at all. It picks up nothing.
As I said when I press the mic button manually it works 10/10, there's nothing wrong with the bluetooth set or connection.
Any ideas?
Click to expand...
Click to collapse
Just turn off the "Record audio through Bluetooth headset if available". It will just work fine.
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....
Running a bone stock OP3, non-rooted, no mods, on the Community Build. Since the latest update, my BT audio is weird.
I pair my phone to my motorcycle helmet. Its a Shoei GT Air with a Sena 20S Comm system installed. It's a very nice unit.
So what happens is that when I push the button on the comm to activate Google Now, so that I can speak to my phone and tell it to dial, get directions, play music, etc... No matter what volume level I set my phone to, or the headset, the "beep" and "Ok" that Google Now speaks when you activate it, blows out my eardrums. It is like WAY high volume, 5x as loud as the music or anything else. I have gone through the comm system settings and there is nothing in there to mess with. I also notice that the volume of Google Now only goes that high when the screen of the phone is off. If the screen is on, then the tone is the same level as whatever music is playing, etc...
If I turn the screen off and the music is at a normal listening level and I hit the button to make a call or fast forward to the next some, that damned Google Now tone is back to ear shattering levels...
I am convinced that it isn't the comm system, because a google search shows similar issues with Android phones and BT over the past few years...
Another weird thing, is that when I turn on and pair the comm system and I hit the button to activate Google Now, if I do it 5 or 6 times in a row, it will eventually revert to normal audio levels, the same as the music or navigation... But when I turn off the comm, then the next time I turn it on I have to do it all over again...
Very annoying but I an convinced that it isn't the comm system. It seems to have started last week when the new Open Beta came out and I installed it.
Now, I have unpaired, deleted and repaired the connection, I have wiped cache and stuff, but I can't seem to get this to work right.
Any ideas?
It has to do with how Bluetooth handles its datastream.
Bluetooth has very limited bandwidth, so it has to allocate based on the situation. When streaming music from your phone to the BT device, it can dedicate the entire bandwidth to the unidirectional stream. However, if you need to use the helmet's mic, then BT has to use the same limited bandwidth to stream data in both directions. This is why BT devices have notable audio quality degredation when used to make calls.
When your screen is on, Google Assistant/Now will acutally use your phone's mic to listen for commands rather than your BT's mic, which means that it does not have to change protocols and reduce audio output bandwidth.
To address your issue with Google Assistant/Now's increased volume, try to place a call while your helmet is connected to your phone and reduce the volume while in call with your phone's volume buttons. Hopefully, the volume change will stick when your helmet uses the same two-way protocol when using the voice assistant.
Try:
Developer options -> disable absolute volume
Tried that Developer Option, made no difference. It's clearly something else going on under the hood. Other Android phones have had it over the years when connecting to BT devices... I guess I will have to just live with it.
Hi, every one! I bought brand new JBL Bluetooth Headset, model name is JBL Reflect mini BT2, and when i turn bluetooth and headset on, there is nothing in the pairing menu. I had older BT-Headphones and everything worked fine. However, the JBL headphones connect to my Galaxy Tab A perfect. On my Mi5S runs LineageOS 16.0, latest update.
Greetings
You might have already tried this since you managed to pair the headphones to another phone, but maybe they don't want to pair to a new device unless the following is done:
To connect to a different Bluetooth device, first switch the headphones off.
Now press and hold the center button on the headphone remote control for about 3-5 seconds.
You should see the light blinking red/blue to indicate pairing mode, and the voice prompt should state “looking for device”.
You should see "Reflect Mini 2" appear on the source's BT list. Choose that option, and wait for the voice prompt to state “connected”
unicastbg said:
You might have already tried this since you managed to pair the headphones to another phone, but maybe they don't want to pair to a new device unless the following is done:
To connect to a different Bluetooth device, first switch the headphones off.
Now press and hold the center button on the headphone remote control for about 3-5 seconds.
You should see the light blinking red/blue to indicate pairing mode, and the voice prompt should state “looking for device”.
You should see "Reflect Mini 2" appear on the source's BT list. Choose that option, and wait for the voice prompt to state “connected”
Click to expand...
Click to collapse
I do this everytime and also did a hard reset on the headset and still not found.
I'm on LOS 16 too and don't have problems connecting to a headset or BT speaker. Here's one crazy idea Go to Developer settings (might need to enable them first - go to About phone, and click on build number at the very bottom until you get a note that you're a developer). Now go to System, Advanced, Developer options and under Networking hit Show Bluetooth devices without names. This will give you a list of BT MAC addresses. I'm curious if you see the JBL listed now. You can get its MAC address from the other phone.