I have been having a problem with Google Voice Search for the past while.
What is happening is when I activate the Voice Search and speak something like "Navigate to [random store name]" or "Map of [random place]" it just ignores the command part (Navigate/Map). It just searches the non-command part on google in the browser.
Also does not work with "Text", "Call", Dial" or any other command.
I have tried Clearing data/cache, uninstall/reinstall and neither have helped at all.
I have a HTC HeroC with the same setup and version and it works flawlessly.
It is not a timing thing as I can give it a few seconds before talking and it still does this.
While it is processing the command has a spike in the audio, so it is detecting that I said it.
Has anyone else experienced this? and how can I fix it?
Thanks.
Google Assistant recently showed up on my phone, however she will not actually complete the action. If I ask for directions to somewhere, she will say "ok, here we go", but she never open the maps app and start navigation. I cannot even click the map or the navigation arrow to start maps manually. If I ask for the closest restaurant, she will show me a list, but I cannot click on any of the locations. Anyone else having similar issues with Google Assistant?
I recently got my phone back from warranty service, so the OS is basically factory new.
Running:
- 7.1.1
- March Update
- Unrooted
What phrase did you use? I said, "Navigate me to...", it opened a result, then Map opened, saw the following screen:
And then navigation started.
Sent from my Nexus 5X using Tapatalk
I use the same phrase "Navigate to..." then the address or place.
I have an issue, Ok Google keyword is activated in the options of wear 2.0 but the keyword does nothing. if i long press the button the assistant come in but the keyword don't work. Is there a workaround? Am i the only one with this issue?
On my watch it works well.
Settings-presonalization-ok google.
Mike
sp5it said:
Settings-presonalization-ok google.
Mike
Click to expand...
Click to collapse
Already activated but no effect, trying factory reset
Ok, just pinpointed the issue, "ok google" works only if the language is set to english, don't work in french...
Problem was here too. I do reset/wipe my watch and now all work. And now battery is better. Yesterday in 12 hours 80%, today after reset in 6 hours 10%
Working now after 3 factory reset and changing language to english and to french thereafter.
Same problem after the OTA : Ok google doesn't work ! long press the button works fine !
After factory reset all works perfectly !
I have the same problem. I also noticed that instead of using assistant on push held it defaults to google search. That's why the keywords aren't working. I have factory reset my watch at least four times and the problem comes back after a couple of days. I am in English US and have switched it back and forth just for kicks. Has anyone had any luck?
edit: I also noticed my Talkback services are buggy and don't provide and example when I tap on the icon under the settings
joeanca said:
I have the same problem. I also noticed that instead of using assistant on push held it defaults to google search. That's why the keywords aren't working. I have factory reset my watch at least four times and the problem comes back after a couple of days. I am in English US and have switched it back and forth just for kicks. Has anyone had any luck?
edit: I also noticed my Talkback services are buggy and don't provide and example when I tap on the icon under the settings
Click to expand...
Click to collapse
Hello everybody,
As i've said it in my post above, a factory reset has resolved the problem and now Ok Google works perfectly !
BillalS3 said:
Hello everybody,
As i've said it in my post above, a factory reset has resolved the problem and now Ok Google works perfectly !
Click to expand...
Click to collapse
Did you actually take the time to read my post? I mentioned I have done that several times and the problem keeps coming back.
Hello joeanca
Yes I've taken time to read your post, and I don't understand why a factory reset don't resolve your problem. Because, for myself it resolves it.
Perhaps somebody else could have a new idea to help you
I have the same issue. Factory reset only fixes the issue for a few hours then it happens again (I think once they lose the connection between them (for example because of distance) and reconnect again. Factory reset also enables wi-fi again. The issue is that if the watch is connected only through Bluetooth with wi-fi closed, google assistant and play don't work , if you go in watch settings it says disconnected in Bluetooth but no "cloud" icon pops up at the screen and on phone Bluetooth settings it says connected furthermore the watch works perfectly like receiving notifications changes song track etc. Oh also the silence phone setting from android wear app doesn't work
I just had this problem and resolved it by dumb luck.
I originally synced two Google Accounts to my watch. After updating apps on the watch, OK Google detection hasn't worked.
I found that my default account in Google Assistant on my phone had changed from my primary account. I removed all but my primary account from the watch, and selected my primary account in Google Assistant. OK Google now works again on the watch.
Darkmage40 said:
[..]if you go in watch settings it says disconnected in Bluetooth but no "cloud" icon pops up at the screen and on phone Bluetooth settings it says connected furthermore the watch works perfectly like receiving notifications changes song track etc.[..]
Click to expand...
Click to collapse
This exactly my problem. The phone says it is connected and the watch works, but the Assistant only says it is offline and cannot understand me. That drives me crazy. I have only one account synced. This Thread is the only thread so far that has my exact problem in it. I know it is a little older, but is there anyone with an idea?
thx and regards
My issue is the Ok Google gets locked into a loop. Whatever the first command I speak to it after Ok Google.. it just loops. Be it What is the time, what day is, send a message, etc. it keeps looping on that command. only seems to affect my Huawei watch 2 classic. phone doesn't have the same issue. have rebooted watch. If i swipe the google assistant away and execute another command, it loops on that one. I have both Facer and Watchmaker watchface apps installed. an issue like this should not have been present in a beta stage so I have to wonder.. what could I have on my watch causing this?
--edit--
Well... it seems Wear 2.0 does NOT like more than one account on a watch. I had three accounts hooked to the watch. My phone's private account. My professional email account, and a purchases account. 3 accounts. Seems that just wasn't how it wanted to work things. As soon as I cut out the pro and purch accounts it starts acting right. I have one account that my android devices get to access for uniformity of data but nothing else gets to use it. I have several emails for various purposes.
So if you have more than one account, as others have found.. remove them down to a single account. Things will probably start working right.
And its back to looping. basically.. if I say Ok Google, then wait for the ready prompt and give it a command "Set an alarm" it will process that command, ask when I want the alarm for, but feed itself the "Set an Alarm" command, ask when, feed command back to itself, ask when... on and on.
Had the same problem. Deleting cache and data of Google app on the watch worked for me. OK google finally works, but I cannot send WhatsApp messages via ok Google, what worked a few days ago with manually starting google by press and hold the upper button.
With Google even talking back works now
i solved the ok googlo hotword problem by deleting chache and data of google app on my huawei watch 2 and it started working again
Ok so I'm trying to get my pixel 2 xl to unlock straight to the assistant with the "ok google" voice command, bypassing the lockscreen but it keeps asking for my passcode, even though I have set the "Unlock with Voice Match" switch on in the assistant settings. I also retrained my voice and still no luck.
Any suggestions? it seems to be a bug or something.
Grafdude said:
Ok so I'm trying to get my pixel 2 xl to unlock straight to the assistant with the "ok google" voice command, bypassing the lockscreen but it keeps asking for my passcode, even though I have set the "Unlock with Voice Match" switch on in the assistant settings. I also retrained my voice and still no luck.
Any suggestions? it seems to be a bug or something.
Click to expand...
Click to collapse
Don't know if this will help or not. Have you tried clearing the Google app data and cache. Reboot, then try again. Just spitballing.
I'm now having the same problem. Seems like it happened right after I signed up for the Google play services beta though. Did you sign up for that as well?
Badger50 said:
Don't know if this will help or not. Have you tried clearing the Google app data and cache. Reboot, then try again. Just spitballing.
Click to expand...
Click to collapse
I tried that, had to retrained the voice command and all that, still asking for passcode.
mptrh336 said:
I'm now having the same problem. Seems like it happened right after I signed up for the Google play services beta though. Did you sign up for that as well?
Click to expand...
Click to collapse
No I did not sign up for that.
Just turn ooff and back on the ok google from any screen and voice unlock on the assistant settings, then retrain a couple of times, try using various tones when doing so
Mine has been doing that as well. Never had this issue before
I've always had this issue. Works after delete voice training, then redo it. But, it reverts back to asking for passcode.
dinkoh said:
I've always had this issue. Works after delete voice training, then redo it. But, it reverts back to asking for passcode.
Click to expand...
Click to collapse
Ditto. It drives me crazy! It never seems to recognise my voice. On the plus side, I got the Google Home Mini free, and despite being an Alexa girl I decided to keep it to play around (and compare with). So if I'm trying to set phone reminders and the like while I'm my living room, it gets picked up by the Mini and a stubborn phone doesn't matter.
...though it's still a pain anywhere else of course. Especially if you're out and about and just want to talk to the phone instead of typing. Frankly it always seems to pick the most inconvenient times possible to decide it doesn't know who I am. Grrrr....
A thread to discuss various google assistant issues and resolutions. If in wrong section please move
I have had issues on global rom with Google Assistant and now when I have used Lineage and RR I still have issues. On RR Ok google works from lock screen and in OS. But I get google voice search instead of assistant. I got the option as a notification to test the new assistant but when I press the notification it disappears and nothing happens. This is what it looks like to me. Any solution to this so you have assistant instead of voice search? For example, you cannot use routines with voice search.
I had the same problem with flash of XASP. Problem with my home lights .
You must to link your Google account, even if it is linked and do the voice match assistant even if you have already done it.