In Settings > Apps > Choose default apps I have replaced Bixby with Assistant as my default digital assistant app but this obviously does not concern earphone shortcuts (triple taps or long presses) which still invoke Bixby. I have also changed the setting for "press and hold Home key" from Bixby to Assistant but this doesn't help either. What other settings needs to be changed in order to activate Assistant via earphone taps?
retry it....go to bixby, clear default, then go to wearable app....touch controls>touch and hold>make either left or right ear "voice command"
Livin Vibz said:
retry it....go to bixby, clear default, then go to wearable app....touch controls>touch and hold>make either left or right ear "voice command"
Click to expand...
Click to collapse
I dont have Galaxy buds but ordinary buds. No software to configure them (I guess)
SEEK | Bluetooth headsets | Voice & Sport | CellularLine Site WW
SEEK are the Bluetooth® earphones with a lightweight, portable design, equipped with an LED display on the case which shows the remaining charge, so that you know exactly when it is necessary to recharge the case (via the included USB-C cable). Thanks to their ergonomics and well-balanced audio...
www.cellularline.com
Yea if you have no way to configure your earphone settings you probably won't be able to get it done. (Not sure though)
Here is your answer. Confirmed works. ~2mins in.
Livin Vibz said:
retry it....go to bixby, clear default, then go to wearable app....touch controls>touch and hold>make either left or right ear "voice command" penalty kick online
Click to expand...
Click to collapse
It's worked for me.
Related
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
self bumb
How did you do it with tasker? If I can get that working I could help you out an see if I experience the same thing.
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
How did you do it with tasker? If I can get that working I could help you out an see if I experience the same thing.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I use tasker and Autovoice (a plugin for tasker). I have autovoice assigned to my bluetooth button. So when I press it, Autovoice comes up waiting for a command.
Then I have this tasker profile:
Profile: Google
State: AutoVoice Recognized [Configuration:Command: "hey google" ]
Task: Load App: Voice Search Data
A tip for AutoVoice when you set up the command make sure to check 'Event Behavior' or it'll keep the tasker profile active.
So when I say "hey google", Google now (or voice search) launches. But as I stated, with the headset the mic never turns red. It works great without the headset though (I have a shortcut to launch autovoice recognize). The other interesting thing is Autovoice uses the same voice engine that GN uses, and it works fine with the headset.
Just downloaded Tasker. I added a profile an selected voice search as my app. I now have to select a task. What should I choose?
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
Just downloaded Tasker. I added a profile an selected voice search as my app. I now have to select a task. What should I choose?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm assuming you've never used Tasker before.
You'll need both Tasker and AutoVoice from the market. I'll post a step-by-step really fast, even though it's a bit off topic.
Go into tasker --> Click '+' --> Name it whatever --> State --> Plugin --> AutoVoice Recognized --> Edit --> Check 'Event behavior', click Command Filter and enter 'hey google' (make sure no space after google) --> click check on top --> click icon on top left --> new task --> name it whatever --> click '+' --> App --> Load App --> Voice Search --> click icon on top left --> click icon on top left.
Now the bluetooh button should launch AutoVoice to wait for your command.
Well I got it running. Great instructions. I got this though now when I press the button. I select autovoice but nothing happens an I just go back to my home screen.
I understand you had another question so no worries. You can pm if you want. Hopefully someone can chime in for your question.
Sent from my SCH-I535 using xda app-developers app
havetolovemusic said:
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
Click to expand...
Click to collapse
Try this.........
http://www.youtube.com/watch?v=c9lElGDIOGM
Bump.
Any new news here? I have the same problem as the OP. It seems that some devices don't play well with Google now bluetooth still. I have a Motorola H700 headset that the mic will not work with Google now. S-voice hears my commands thru the bt mic fine (but has its own problems). It's just GN. I have the box checked, and I hear the beep in my headset but it can't hear any instructions. HELP!
havetolovemusic said:
I'm assuming you've never used Tasker before.
You'll need both Tasker and AutoVoice from the market. I'll post a step-by-step really fast, even though it's a bit off topic.
Go into tasker --> Click '+' --> Name it whatever --> State --> Plugin --> AutoVoice Recognized --> Edit --> Check 'Event behavior', click Command Filter and enter 'hey google' (make sure no space after google) --> click check on top --> click icon on top left --> new task --> name it whatever --> click '+' --> App --> Load App --> Voice Search --> click icon on top left --> click icon on top left.
Now the bluetooh button should launch AutoVoice to wait for your command.
Click to expand...
Click to collapse
Thank you, these instructions were very helpful.
Headset difference
Hi All,
I am facing a peculiar problem. I have 2 BT headsets. A Samsung WEP one and a Nokia 110 one. When I press the BT button on my Samsung headset, I am able to invoke the google now option. However, the same thing does not work with the Nokia. I do not get any option/default command when I press the button for Nokia BT headset. It works properly otherwise(recieve/reject call)
I have tried clearing the BT data in all apps and few other suggestions as well but the Nokia one just doesn't invoke Google now.
What might be missing in my Nokia headset?
Please suggest.
Thanks
Vishal
havetolovemusic said:
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
Click to expand...
Click to collapse
At least for me, the only thing I had to do to get audio from the BT headset was:
Open Google Now
Press Menu --> Settings
Select "Voice"
Check "Bluetooth Headset - Records audio through Bluetooth headset if available" box
EDIT:
Be warned that Google Now's audio prompt and voice playback appears to use the system volume (opposed to media or notifications), uses the Bluetooth media volume settings, so make sure it's not turned all the way down.
Hope this helps!
Has anyone had any success with this recently? I heard that usb audio is finally working on CM 10.2. Last I tried I still couldn't get usb audio + bluetooth mic for voice commands/Google Now.
havetolovemusic said:
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
Click to expand...
Click to collapse
I finally figured it out. You can use SoundAbout to force the mic through bluetooth.
VoiceCommand 1.1.1
Delete
Has any one come across a way to change the default voice dial selection when you press the activate button on the headset the stock voice dial is junk when compared to google now.
Robert Hodgson said:
Has any one come across a way to change the default voice dial selection when you press the activate button on the headset the stock voice dial is junk when compared to google now.
Click to expand...
Click to collapse
I just noticed this myself as well. I very rarely use the phone button on my bluetooth headset (as my headset is actually just a thing that I plug my own headphones into) but it would be nice to be able to text while I'm outside without pulling my phone out of the pocket.
I'll look into this a bit and see if I find a way to do it. It's likely going to involve an app. With my last phone it was able to be done, but it was using one of the apps that were bundled in by Samsung.
Robert Hodgson said:
Has any one come across a way to change the default voice dial selection when you press the activate button on the headset the stock voice dial is junk when compared to google now.
Click to expand...
Click to collapse
This is what I found. Works perfectly with my samsung HS3000. It does not work with my sony MW1, but that's because the sony MW1 does not seem to let the action button be used for anything other than answering or hanging up a phone call.
https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch
Thanks Cirkustanz it worked out great
Sent from my Nexus 5 using Tapatalk
Just wrote a very simple app called BT GNow, which activates Google Now rather than the default Android Voice Dialer when you hit the hands-free button on your Bluetooth headset. Surprisingly, I can't seem to find another app that accomplishes this simple function. Bluetooth Launch does this to an extent, but the UI is difficult, it requires some configuration, it seems to me to cause wakelock problems, and the instance of Google Now that it starts takes off where Google Now left off (so you are often brought to an old search rather than an opportunity to speak a new voice command).
BT GNow keeps only a limited wakelock, requires no configuration (other than configuring Google Now to accept input from your Bluetooth device and possibly disabling the native Voice Dialer), and starts a fresh instance of Google Now each time.
Here's the Play Store link: https://play.google.com/store/apps/details?id=com.vibaroo.btnow
And the (minimal) website that describes the setup: https://sites.google.com/site/btgoognow/home
Great will try tomorrow
I will try now, great APP man:good:
Fail, my bluetooth now is not working, i tried, factory reset, re-flash system but not working more
Wow, great app. Makes my bluetooth headset and Google Now work as I always expected it would have to begin with.
I noticed that there was a problem with the screen locking and not responding to touches if lockscreen security is enabled and Google Now is interrupted. Solved this problem with the latest version and also improved wakelock control by sticking an icon in the corner of the screen. The icon disappears when the screen is turned off, and the phone is kept awake only as long as the icon is present.
Got rid of the icon that people seemed to dislike (made it invisible).
Donations?
New Feature
Some have reported problems with BT GNow not effectively bypassing the lockscreen. To address this, I've added an option that requires you to say "OK Google" after pressing your handsfree button; this in effect lets Google Now handle the lockscreen itself. You can activate this option by clicking on the app in the launcher and choosing the "OK Google" option.
Note that if you choose this option, you have to make sure that "OK Google" detection is set to work "From any screen": Google Now > Settings > Voice > 'OK Google' Detection > From any screen (checked or set to "on").
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Dzinic said:
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Click to expand...
Click to collapse
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
NYZack said:
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
Click to expand...
Click to collapse
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Dzinic said:
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Click to expand...
Click to collapse
Did you try disabling the voice dialer (as in the instructions)?
NYZack said:
Did you try disabling the voice dialer (as in the instructions)?
Click to expand...
Click to collapse
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Dzinic said:
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Click to expand...
Click to collapse
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
NYZack said:
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
Click to expand...
Click to collapse
Don't go out and get one just to fix my problem! I just don't use my phone for music enough to justify investing in a bluetooth, haha. Thanks for looking into it.
:thumbup:
Thanks!
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
patientzero said:
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
Click to expand...
Click to collapse
I've noticed that problem if you have more than one bluetooth device connected at once - for instance, if your phone is connected to your car's bluetooth or a stereo headset while connected to your Moto Hint. I'm considering options to try to fix this. In the meantime, perhaps it's better not to use the "OK Google" option and just launch directly from the bluetooth button?
My friend has same thing on his iPhone. I can now use google now with handsfree, when i driving my car. Thanks! The Coolest app on my week!
Wishlist ....
Given the code you have already written here is a little wish from me ... could you implement that the HFP bluetooth headsets just do not launch any application - just volume up and down.
xperia Z, TWIINS bluetooth headset for motorcylce, mono Bluetooth to route Navi output to headset - whenever I press volume down I get the stupid voicedialer or -if disabled- a black screen. I do not want to make any phoncalls on a fast bike!
Thanks in advance.
DrT_Music
So I got a new car (2016 "facelift" Kia Ceed 4 Tech)... and whilst OK Google Hotword detection over bluetooth sort of works, the
state of the dialler appears quite broken... and I was hoping if anyone could help.
Nexus 5 running Marshmallow paired to the car with Phone & Media Audio selected.. Google Voice Typing settings set to record audio through headset if available.
1) With screen on, say "Ok Google" wait for phone to respond with the first and then second beeps (I guess the second beep is to
signify the phone is then listening over bluetooth)
2) Say "Call xxxxxx mobile/home" etc.
3) Phone responds and starts dialling. Call is answered and the car Infotainment screen gives a prompt to change to "hands free mode", requiring a manual button press..
Not exactly "hands free behaviour".. Not compared to when I pair my wife's Galaxy Note 4, do exactly the same steps and everything goes through seamlessly with
the car automatically going to bluetooth handsfree without requiring me to press the button on the infotainment screen.
Now if you look at the dialler screen on the Nexus 5 whilst the call is going through, you can see the dropdown to manually choose between "Headset" "Speakerphone" "Bluetooth"
and the "Bluetooth" one is indeed selected but clearly the phone and car aren't handshaking to tell the car to automatically default to handsfree. At this point, you can re-select the bluetooth
option but it doesn't do anything, and the car is still waiting for manual confirmation.
More weirdness is, if you start a voice call with OK Google but actually press the phone button to action the call, then it all works fine...
Both Marshmallow and the car are new, so I'm not hopeful that anyone has an answer but given the Note 4 works perfectly, I'm keeping my fingers crossed..
Looks like a known problem since lollipop for nexus and some other phones.. not fixed in marshmallow either.. not sure what to do..LLC.. wait and see I guess
here
Hi,
I want to use the Google Assistant on my new earbuds but not the usual way.
I know how I can set it to a button (left or right earbud) for calling up the assistant, but the thing is, I wanna use the buttons with the defaulted settings. So left is now ambient noise cancellation and ambient sound. And the right earbud is for music control, what I really like. So these are my favourite settings and I want to stick with it.
But I am not making it easier.
Now, I found out that when I long press the right earbud, Bixby pops up on my phone. And that is exactly what I don't want to happen. I want to kill Bixby and use the Google Assistant. I already know that there is no way (for a common guy like me) to delete Bixby from my Galaxy A50.
So here comes the question:
How can I call up the Google Assistant by long pressing the right earbud?