Ok google not responsive - Huawei Watch

I'm on latest firmware. But I have problem with "ok google". The google always recognize different word from what I speak. Moreover, I need to say "ok google " for few times in order for the microphone to appear. What has gone wrong?

Related

[Q] No "ok google" at top of search bar?

For some reason "ok Google" has disappeared from my search bar. I feel like it might've come with the 4.4 kit Kat update because I only recently realized it was gone, and I downloaded KitKat less than a week ago. I'm not 100% sure though. I've tried uninstalling and reinstalling all Google search updates to no avail. Does anyone have any idea how to get it back? I can't voice activate Google now anymore, and I really liked that feature. I'm currently running the latest android kit Kat version. Thanks!
I'm getting the same problem here. It's weird because the checkbox under settings in voice for me shows that hotword detection is on...
Same here. Glad to know I'm not alone.
The "OK google" text goes away after a few uses but the OK Google hot word should keep right on working
Nope doesn't work
bump

recent-apps list disappears

Starting yesterday, I find that my AT&T Note 5's recent-apps list occasionally disappears--pressing the recent-apps button just shows "No recently used apps" and continues to do so no matter what apps I subsequently start. The only way I've found to restore the recent-apps function is to reboot the phone. When I do that, I can immediately once again see all the previously-listed apps that had disappeared from the list.
A web search shows this to be a widespread problem, especially in the past two weeks, across a variety of phones and carriers. Some users report that using the "OK Google" feature of Google Now seems to trigger the bug. My own occurrences of the bug have always been preceded by a recent "OK Google", but I can still use "OK Google" without difficulty most of the time, so I'm not certain that's the trigger.
It appears that today's beta update of the Google App (6.3.29.21.arm64) may have fixed the problem. So far so good, anyway.

[HELP] "Ok Google" self-activating voice search

Hi everyone,
I'm using OnePlus 3 for 4 months and through every update (3.2.1 --> 3.2.2 --> 3.2.4 --> 3.2.6 --> 3.2.7) I've experienced this strange issue.
Sometimes (like once in 2 days) the voice search, the one that normally activates with "Ok Google", self-activates and waits for a command, eventually saying "I didn't understand".
It happens when the screen is on or when the phone is charging, usually when there are other noises (people talking at work, television, etc).
Did it happen to anyone, too? I never experienced this behaviour in none of my previous phones, I even tried restoring voice recognition but the problem is still there.
Thanks in advice!
repsol89 said:
Hi everyone,
I'm using OnePlus 3 for 4 months and through every update (3.2.1 --> 3.2.2 --> 3.2.4 --> 3.2.6 --> 3.2.7) I've experienced this strange issue.
Sometimes (like once in 2 days) the voice search, the one that normally activates with "Ok Google", self-activates and waits for a command, eventually saying "I didn't understand".
It happens when the screen is on or when the phone is charging, usually when there are other noises (people talking at work, television, etc).
Did it happen to anyone, too? I never experienced this behaviour in none of my previous phones, I even tried restoring voice recognition but the problem is still there.
Thanks in advice!
Click to expand...
Click to collapse
I never had the issue on my LG G2 but it happens now. Also happens often on my Galaxy Tab S2 really often. I think its a Google thing and they have made things too sensitive.
Go into Google Now, Settings, Voice, "Ok Google" detection. Turn off From Any Screen.
natboy said:
Go into Google Now, Settings, Voice, "Ok Google" detection. Turn off From Any Screen.
Click to expand...
Click to collapse
Well, actually that's not a solution, more like a "workaround"... I like the "Ok Google" From Any Screen feature, I use it once in a while.
It's like asking "I have bad call quality, what can I do?" and receive "stop doing voice calls" as an answer...
Update: I flashed 3.5.4 yesterday, same issue experienced today.
I tried to install google assistant, but it showing "This account is not eligible for the feed"

Can't train "Hey Google" on the assistant

Hello there guys,
i've recently been looking for a way to use something else rather than "Ok" to summon the assistant, and i found out that Google actually released the "Hey Google" hotword for it.
Before it, i've been able to use the assistant using my voice just fine, but when i've been prompted to retrain the assistant, it asked me to record 4 things (Ok, Hey, Ok, Hey, as far as i know, cause i've never gotten to the "hey" part) instead of 3 (Ok 3 times).
Problem is, when i say "Ok Google", nothing happens. It just stays there, waiting for me to say it, even though i did. And the only solution is to revert the Google app to the factory version, retrain the assistant with the 3 "Ok Google", and then re-update the Google app. Point is, if i even try to retrain the assistant while the Google app latest version is installed, i get stuck, and have to re-do all the process.
Is there any way i can solve this?
I have a OnePlus 5T running Android 8.0.0.
Thank you so much.
I've also been prompted by Google via notification to train the assistant using "Hey Google" as well... but the same bug occurs.

OK Google with screen off

I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.
This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.

Categories

Resources