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.
Related
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.
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.
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.
Not sure if this is a fault, but think it is, since I got my phone in December, "OK Google" works most of the time, but when it doesn't I have to manually activate it, by squeezing or swiping up from the bottom corner, once that's done it works again for a while.
The phone has been restored multiple times and upgrade when the newest updates are available.
Anyone had this before
Thanks Steve
Greetings everyone, I just got the rog phone 3 last week and noticed that I cannot get Google assistant to work with any of the standard phrases such as "Hey Google" or "Ok Google". I've tried deleting and retraining the assistant many times, and clearing cache. The assistant seems to only work if I activate it manually. Does anyone else have this issue or know what I should do ?
have the same problem, but havent really found it a big issue, so havent dived into "why" yet
edit: after removing and setting the "tick" in the assistant wake-up phrase it works again ,,, ,,,