Ever since upgrade to AW 2.0, "OK Google" doesn't work 90% of the time. Today, I figured out why. Here's the experiment:
1) Make sure the watch and the phone are connected.
2) Toggle "Personalization -> OK Google detection" off and back on ... "OK Google" now works
3) Toggle phone's Bluetooth off
4) Try "OK Google" on the watch now. It still works, but tells us it can't connect to the phone -- as expected.
5) Toggle Bluetooth on the phone back on. Make sure watch and the phone are now connected again.
6) "OK Google" now never works
I've tried and re-created this scenario multiple times. Does it match everyone else's experience?
Which brings me to the following question -- is there a way to flash the watch with AW 1.5? The watch was infinitely more useful with a reliable voice input; now it's just a notification device.
Just hold down the crown button for a few seconds and Google Assistant will start listening. I think it's more convenient than saying "OK Google" anyway
jbmatson said:
Just hold down the crown button for a few seconds and Google Assistant will start listening. I think it's more convenient than saying "OK Google" anyway
Click to expand...
Click to collapse
That doesn't work all that great when, say, driving or cooking. Having hands free voice commands work close to flawlessly is what made me return Apple Watch and switch to Android; Wear 2.0 was as much of a CF for that functionality as a major upgrade could be, and Google doesn't seem to be in a hurry to fix that.
Related
EDIT: I have modified this post to focus more on getting google now/touchless control to stop making calls. I think this should be doable, but I'm banging my head against the wall trying to figure out how?!?
Please read my second post. However, feel free to comment on the other questions below as they are still bugging me too.
I know I talk louder than most folks. When I ran the touchless control training on my Moto X Dev Ed, I have to really talk lower than I normally do. Is there some way to adjust the mic level so I can talk normal?
Also, sometimes I have to say "ok google now" a few times to get the phone to respond, maybe once out of every 10 times this happens. Any suggestions on this?
Additionally, sometimes it will try to call a contact when the phone is locked after I say "ok google now", even though I have this option unchecked under settings->touchless controls. What gives?
I'm running a stock 4.4.2 rom that is unlocked and rooted . Touchless Controls version 4.3.11.1 and Google Search version 3.3.11.1069658.arm.
I really love the phone and bought it to control my home with my voice (which works great for the most part). Hopefully someone has suggestions on fixing these small issues.
Update: disabling all Touchless Control commands for the phone lock screen does nothing.
I went to Touchless Controls -> Comamnds while locked -> unchecked everything, but my phone still makes calls when I say "call [contact name]" and the phone is locked, along with the other commands. What a joke!?! Does Google test software before publishing it?!? I guess simple if/then logic is beyond a company to get right before releasing an app.
For Google Search I also ensured Google Search->Settings->Phone search->Contacts is unchecked. I also unchecked everything else. Google Search->Settings->Accounts & privacy->Contact recognition is also unchecked and Perosnal results is turned off. Google Search/Touchless Control still uses my contact information to make calls (without my consent) regardless of these settings too.
Allowing it to make calls would be fine if it didn't randomly misunderstand a command and try to make a call.
etc6849 said:
Update: disabling all Touchless Control commands for the phone lock screen does nothing.
I went to Touchless Controls -> Comamnds while locked -> unchecked everything, but my phone still makes calls when I say "call [contact name]" and the phone is locked, along with the other commands. What a joke!?! Does Google test software before publishing it?!? I guess simple if/then logic is beyond a company to get right before releasing an app.
For Google Search I also ensured Google Search->Settings->Phone search->Contacts is unchecked. I also unchecked everything else. Google Search->Settings->Accounts & privacy->Contact recognition is also unchecked and Perosnal results is turned off. Google Search/Touchless Control still uses my contact information to make calls (without my consent) regardless of these settings too.
Allowing it to make calls would be fine if it didn't randomly misunderstand a command and try to make a call.
Click to expand...
Click to collapse
I cannot get control of Google search volume during a Bluetooth connection with my Jawbone.
http://forum.xda-developers.com/moto-x/general/workaround-fix-loud-prompt-google-voice-t2725610
Your bluetooth volume issue sounds crazy. You'd think Motorola's engineer's could spot such simple issues assuming they actually use their products, but I guess not. The phone is really well engineered otherwise. These types of errors might be ok for beta software, but not after many revisions.
Is there any way to stop "OK Google" showing up on the watch face? I don't use the "Speak" function and would really like to have a clean watch face.
Cheers.
Si
http://forum.xda-developers.com/showthread.php?t=2972318
Tonio78370 said:
http://forum.xda-developers.com/showthread.php?t=2972318
Click to expand...
Click to collapse
Don't know how I missed that. I tried doing what it said but it reappears when I bring the watch out of dimmed mode.
Many thanks.
Managed to get rid of it by saying "OK Google" a few times. I guess it hangs around initially as a reminder just until you get used to it.
Once every few days I get this notification from Google asking me to say "OK Google" three times to train the device. I always say it, although the recognition of me saying "OK Google" has actually gotten worse and worse. Before Google started asking me this it nearly always worked. Now it works only about 10% of the time I say "OK Google". Now having to say "OK Google" into my phone over and over again in front of others is embarassing. What is going on?
I have the same issue. The only way I was able to fix it was by reverting to the stock Google App (uninstall updates for this app through App Manager) and retraining my voice. Now it's back to normal. To note, the current Google App beta also didn't help things. Same problem.
KruseLudsMobile said:
Once every few days I get this notification from Google asking me to say "OK Google" three times to train the device. I always say it, although the recognition of me saying "OK Google" has actually gotten worse and worse. Before Google started asking me this it nearly always worked. Now it works only about 10% of the time I say "OK Google". Now having to say "OK Google" into my phone over and over again in front of others is embarassing. What is going on?
Click to expand...
Click to collapse
Can you post a screenshot? I am curious what is this
No because it only appears when it wants to. Also, I resolved the issue. I went into Google settings and deleted all the voice data they had about me. Then I noticed the voice recognition of "OK Google" works much better once again.
I'm not sure when this changed. I used to be able to say "OK Google" and the assistant would interact with certain apps, like texting or calendar, when the phone was still locked. Now, as soon as I say the hot-phrase it goes straight to the pattern lock screen and won't go further until I unlock. Is this a function lost on devices without "Trusted Voice"?
I'm running the latest PN with the stock PN kernel. I'm not in beta for the Google app either.
I've tried retraining voice recognition, turning always listening off/on, updated Google app a couple times, tried different launchers (Action and Pixel)...
Any thoughts or recommendations on this?
The way I handle this is using tasker to set the screen lock delay to some thing silly like 10 days when the phone is in a "safe" location. Then the ok google works as expected with the screen off. The rest of the time I live with the fact that I have to unlock the phone to use ok google.
On reflection, smart lock should give the same effect of there is a trusted device connected.
I've considered something like what you've said. I do want the security to work though. I used to be able to do very basic things by voice without unlocking. I don't want to effectively turn off security.
Curious to see if anyone else is having success with using their voice to start commands on this watch. I have the "OK Google" recognition turned on. However, it never responds. If I restart the device, then it will recognize the command and proceed as normal.
All other voice prompts work as normal (after touching the screen of course). Not sure if I need to enable another setting.
thanks!
I just got this watch and had a similar issue. It seemed to work ok with one account on the watch. If I put my work account on it stopped working. It was set to the correct account etc. I reset 4 times, and each time the second account would mess it up. Eventually I discovered that there was an app update to androidwear on the watch that happened in the back ground that may actually be the culprit (discovered by some trials). I've only had the watch 3 days ago I'm still working on it. Last night when I went to bed, it was working. We'll see this morning. Also found out that needed to say "OK Google" slower. This is my 4th search watch and most finicky for sure!
i think I just found the answer: http://www.androidpolice.com/2017/1...-android-wear-fix-smartwatchs-stuttering-lag/
to summarize, disable the ok google detection, and the watch speeds up dramatically. i can confirm this. but I really did not want to lose the ok google feature. but I read (and tested) that my long-pressing on the big button, google assistant pops up. this is an acceptable alternative for me.
hope this helps others.
When I was on Ver 2.0, "Ok Google" seldom worked. I gave up on it working.
I have reverted back to Ver 1.5 about a month ago and now, "Ok Google" works every time and very quickly.