How are Voice Commands Working? - Wear OS Q&A, Help & Troubleshooting

With 3rd party support for Lyft and IFTTT that obviously use voice commands to function - what is happening in the background to make this possible? There are no public APIs for devs to add their own voice commands to Google Now. So what kind of witchcraft is happening here?
Thanks!

just taking a wild guess here... google teaming up with devs to get stuff supported on android wear before releasing to public?

IFTTT doesn't really have voice command support. The only trigger available for Android Wear it to tap a button. Basically you go in the app and there's buttons for the recipes you want to run.
Sent from my Nexus 5 using Tapatalk

Related

Google Voice Search

Does anyone know how to replace the Motorola voice search with the Froyo 2.2 Google default voice search. I used the Google one on my nexus one and it is much, much better than the Motorola version.
Thanks for any help.
Do you mean the double tap home button action?
If so, go to Settings > Application Settings > Double tap home launch
Then scroll down to Voice Search
No, I mean when you have a bluetooth headset on and press the button it launches the Moto voice app. I'd like it to launch the google voice command program.
Sent from my DROIDX using XDA App
gchglobal said:
No, I mean when you have a bluetooth headset on and press the button it launches the Moto voice app. I'd like it to launch the google voice command program.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I dont' think voice search works over bluetooth anyway.
Zaphod-Beeblebrox said:
I dont' think voice search works over bluetooth anyway.
Click to expand...
Click to collapse
Hmmm, I gotta test that now
Zaphod-Beeblebrox said:
I dont' think voice search works over bluetooth anyway.
Click to expand...
Click to collapse
It works fine with 2.2. Actually I believe the Moto version worked with 2.1. It's just slow and not as accurate as the 2.2 built in google version.
There seems to be no way to change the default voice choice. I've thought about deleting the moto voice to see if I could then use the google but haven't yet.
I believe the Nexus One/Droid has an additional APK that allows this. VoiceDial or something like that.
I'd rather use the google one instead of the slow, limited Nuance Motorola version.
drhill said:
I believe the Nexus One/Droid has an additional APK that allows this. VoiceDial or something like that.
I'd rather use the google one instead of the slow, limited Nuance Motorola version.
Click to expand...
Click to collapse
No, the Nexus One brings up the same voice search application that you can get from the market and launch manually. It's just set up so that it also launches when you hit your bluetooth button. Seems like there should be some way of changing which program is default for voice search.
OK... I think there is mucho confusion about programs here.
Voice Command = program from Nuance. This currently launches when you long press the dial button on the bluetooth headset. It DOES support input from the Bluetooth headset. This program has a limited/specific command set.
Voice Search - the default Android program. Can be activated by Long pressing the search button (hardware key). It was updated in the 2.2 release (I think you can also download the latest version via market). It DOES NOT support input from bluetooth. This too has a limited command set, but anything outside of it's commands will be launched as a web search.
I think what we are after here is for 'Voice Search' to be the default app launched when Long-Press Bluetooth is issued.
My point was that Voice Search doesn't support BT input. But I wish it did.
Zaphod-Beeblebrox said:
OK... I think there is mucho confusion about programs here.
Voice Command = program from Nuance. This currently launches when you long press the dial button on the bluetooth headset. It DOES support input from the Bluetooth headset. This program has a limited/specific command set.
Voice Search - the default Android program. Can be activated by Long pressing the search button (hardware key). It was updated in the 2.2 release (I think you can also download the latest version via market). It DOES NOT support input from bluetooth. This too has a limited command set, but anything outside of it's commands will be launched as a web search.
I think what we are after here is for 'Voice Search' to be the default app launched when Long-Press Bluetooth is issued.
My point was that Voice Search doesn't support BT input. But I wish it did.
Click to expand...
Click to collapse
Once again, In 2.2 the "Voice Search" app by Google works with bluetooth. I have it currently working on my nexus one. Please see http://developer.android.com/sdk/android-2.2-highlights.html#PlatformTechnologies
All I'm trying to figure out is when I long press the bluetooth button on my headset that it launch Google's "Voice Search" application versus Motorola's built in Voice Search application.
gchglobal said:
Once again, In 2.2 the "Voice Search" app by Google works with bluetooth. I have it currently working on my nexus one. Please see:
[new user had to remove url]
All I'm trying to figure out is when I long press the bluetooth button on my headset that it launch Google's "Voice Search" application versus Motorola's built in Voice Search application.
Click to expand...
Click to collapse
@gchglobal How does Voice Search work w/ Bluetooth? You mean you can push the the Voice Search on the phone and then speak into your Bluetooth?
If so, are you sure your phone isn't just picking up your voice?

How can we get Google to develop a Honeycomb Google Voice app?

One of the main reasons I went with an Android Honeycomb tablet versus the iPad 2 is the deep level of Google account integration with Honeycomb. I was willing to overlook the lack of Honeycomb-based apps, knowing that Google would push it as they did O.G. Android (and that certainly paid off).
Oddly enough -- one of the few apps that you cannot even download for Honeycomb even though there is a pre-3.0 counterpart, is Google Voice. GV users on HC have to download an old, hacked version of the APK (to give you an idea of how out-dated, it is from before the GV app had push notifications).
How do we go about pushing Google to get HC users a working GV app, one that we can download from the Market??
I hate starting things like this, but the situation is dire (okay, not really, but still!). My plan is to tweet "Please @googlevoice push out a #Honeycomb compatible #googlevoice TODAY!" or "What does #Honeycomb and #iOS have in common? No native @googlevoice app!"
I installed groove IP from the market and installed the GV apk from this forum and it all works perfectly. I know its not native but works. Just did a few test calls to the wife and a friend
Sent from my GT-P7510 using Tapatalk

[Q] Which mod has best voice control?

I moved from Iphone this spring. I am using MDOB now. Samsung Svoice never seems to get my voice commands right; can't find the right contact and totally gets my music voice commands wrong. For example, always thinks I'm asking for "back" when I say "beck"-- the only thing in my library.
Siri was an order of magnitude better at all this. Google is better at general voice recognition, but doesn't work with AT&T/Samsung. I tried and get a google dialer popup and it won't control the Samsung music app.
Should I go to Google Edition? Will Google correctly work over bluetooth headset for music and calls? Is it more accurate than Svoice?
Help!
starmanj said:
I moved from Iphone this spring. I am using MDOB now. Samsung Svoice never seems to get my voice commands right; can't find the right contact and totally gets my music voice commands wrong. For example, always thinks I'm asking for "back" when I say "beck"-- the only thing in my library.
Siri was an order of magnitude better at all this. Google is better at general voice recognition, but doesn't work with AT&T/Samsung. I tried and get a google dialer popup and it won't control the Samsung music app.
Should I go to Google Edition? Will Google correctly work over bluetooth headset for music and calls? Is it more accurate than Svoice?
Help!
Click to expand...
Click to collapse
When you refer to "Google is better at general voice recognition, but doesn't work with AT&T/Samsung.", what specifically are you referring to? I use Google Now and it's voice recognition and it works perfectly fine for me? Google Now is integrated in the new Google app. You can also access it from holding the menu haptic button.
Google Now does not control anything. Does not control music, texting, etc. on a Samsung/ATT device.
So my question, and I guess this is the wrong place to ask it since nobody seems to know here, is will AOSP or plain vanilla google ROMs do as good a job as Siri at controlling music via bluetooth headphones, texting, etc. etc.?

[Q] Disable Android Wear Voice Recognition

I newly have a Moto 360 and I don't like that a) anybody shouting 'Ok, Google' next to my watch will enable voice listening, and b) that music playback stops once voice listening starts, e.g. when accidentally tapping the watchface.
Is there a way to just disable voice commands and let the watch just use tapping, swiping, and all this?
Yes this is a annoying behavior. If you put the wear device in flight mode nothing else will work. Even the time display will be wrong after some time. Because I didn't found a solution I've coded myself a little app which mutes the microphone, and disables the speech recognition:
Ups, Im not allowd to post a link. Simply search the play store for "mute wear mic"
have fun
flex48
Sorry, disregard post...
flex48 said:
Because I didn't found a solution I've coded myself a little app which mutes the microphone, and disables the speech recognition: [...] "mute wear mic"
Click to expand...
Click to collapse
Sorry that I answer late.
I would see it the same way as the person in the single review on Google Play — I would not trust this app, I would not even install it.
In the last time I'm more and more looking for Open Source software.
I really want to know what an app does.
So, as your app is not even a paid app, and a very small one, grab some non-copy license and post your source code, then I'll happily try your app.

Autovoice and Google Now - It looks like your AutoVoice account is not yet linked

I am on a Galaxy S8 and Android 7.0.
Following this guidance, http://lifehacker.com/how-to-create-custom-voice-commands-with-tasker-and-aut-1282209195, I installed Tasker and AutoVoice. Google app already installed. I enabled Autovoice accessibility service and AutoVoice Google Now integration.
OK Google is enabled on all screens.
However, when I say "OK Google, use Autovoice" Google consistantly comes back with "It looks like your AutoVoice account is not linked yet." How do I do this?
When I run AutoVoice Testing with my trigger words, they work. I have another 6.0 Android device where all this (Tasker, Autovoice, Google Now) works seamlessly.
Is there some other step required for S8 / Android 7.0 go get AutoVoice integrated with Google Now?
SomebodySysop said:
I am on a Galaxy S8 and Android 7.0.
Following this guidance, http://lifehacker.com/how-to-create-custom-voice-commands-with-tasker-and-aut-1282209195, I installed Tasker and AutoVoice. Google app already installed. I enabled Autovoice accessibility service and AutoVoice Google Now integration.
OK Google is enabled on all screens.
However, when I say "OK Google, use Autovoice" Google consistantly comes back with "It looks like your AutoVoice account is not linked yet." How do I do this?
When I run AutoVoice Testing with my trigger words, they work. I have another 6.0 Android device where all this (Tasker, Autovoice, Google Now) works seamlessly.
Is there some other step required for S8 / Android 7.0 go get AutoVoice integrated with Google Now?
Click to expand...
Click to collapse
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
Thank you very much! This is the first clue I've been handed to the source of my problem. You are right. On my px5 head unit, there are no settings for Google Assistant. On my S8, there are. However, I don't know why they are there, or how to disable Google Assistant without disabling OK Google. When I disable GA and speak "OK Google", it immediately asks me to turn GA back on to respond. Do you know how I can resolve this? Again, thanks!
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
SomebodySysop said:
Thank you very much! This is the first clue I've been handed to the source of my problem. You are right. On my px5 head unit, there are no settings for Google Assistant. On my S8, there are. However, I don't know why they are there, or how to disable Google Assistant without disabling OK Google. When I disable GA and speak "OK Google", it immediately asks me to turn GA back on to respond. Do you know how I can resolve this? Again, thanks!
Click to expand...
Click to collapse
Never mind. I found it: https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Problem is, don't have root on Galaxy S8. Google REALLY needs to give us the option for something like this instead of forcing it down our throats whether we like it or not!!!
SomebodySysop said:
Never mind. I found it: https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Problem is, don't have root on Galaxy S8. Google REALLY needs to give us the option for something like this instead of forcing it down our throats whether we like it or not!!!
Click to expand...
Click to collapse
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Acoustichayes said:
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Click to expand...
Click to collapse
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
SomebodySysop said:
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
Click to expand...
Click to collapse
No problem man. I use tasker, autovoice, and autoremote religiously haha. Too much home automation and laziness not to utilize them. You should look into the natural language it can now use. Takes a while to understand and set up, but after that, it's much better than regular recognize
Acoustichayes said:
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Click to expand...
Click to collapse
SomebodySysop said:
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
Click to expand...
Click to collapse
Acoustichayes said:
No problem man. I use tasker, autovoice, and autoremote religiously haha. Too much home automation and laziness not to utilize them. You should look into the natural language it can now use. Takes a while to understand and set up, but after that, it's much better than regular recognize
Click to expand...
Click to collapse
I'm having fun, and pulling my hair out, just trying to get this going right now. At least twice this week I was in my car (head unit not installed yet) and really wanted to send time sensitive messages on my s8 using Google Voice. I don't text and drive, religiously. But being able to say "google voice text so-and-so" would have been quite useful.
One last, final question: I've been learning tasker/autovoice on a rooted px5. Just got this galaxy s8 and, of course, it's not rooted. Looks like I shell commands a lot in my profiles, particularly "input keyword" and "input text".
So, if I want to send %avcommnofilter as response to app, do you recommend autoinput for that?
SomebodySysop said:
I'm having fun, and pulling my hair out, just trying to get this going right now. At least twice this week I was in my car (head unit not installed yet) and really wanted to send time sensitive messages on my s8 using Google Voice. I don't text and drive, religiously. But being able to say "google voice text so-and-so" would have been quite useful.
One last, final question: I've been learning tasker/autovoice on a rooted px5. Just got this galaxy s8 and, of course, it's not rooted. Looks like I shell commands a lot in my profiles, particularly "input keyword" and "input text".
So, if I want to send %avcommnofilter as response to app, do you recommend autoinput for that?
Click to expand...
Click to collapse
Figured out this issue here: https://forum.xda-developers.com/u/...to-screen-rooted-device-t3620540#post72644822
SomebodySysop said:
Figured out this issue here: https://forum.xda-developers.com/u/...to-screen-rooted-device-t3620540#post72644822
Click to expand...
Click to collapse
My apologies for not responding! Got caught up with root searching and things of the sort. But im glad you figured it out!
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
FINALLY! This is how you link AutoVoice (or any 3rd party app) to Google Assistant: https://productforums.google.com/d/msg/websearch/HwJUpkrHPr4/xIJACIlEAwAJ
So, you have to say "OK, Google, ask Autovoice to...." followed by your AutoVoice command. Still wish I could just say "OK, Google" then command, but this will do for now.

Categories

Resources