Database Info

"OK Google" not working anymore on LineageOS 15.1

Hi there,
for some months now I have a Honor View 10 with LineageOS 15.1 installed.
Recently I also got a Huawei smart watch which I coupled to the View 10.
On both devices, it was working perfectly fine to talk to the Google Assistant by just saying "OK Google" if the screen was turned on.
It automatically unlocked and followed my commands.
Since some weeks, though, the "OK Google" detection stopped working and I cannot find out, why.
When trying to activate Voice Match in the settings page of the Google app, there's a message that the service was not available in my current language...
(But I already tried many different languages - of course including "English (US)". And: it used to work until some weeks ago!)
I already changed many settings, tried several combinations of different settings unpaired my smart watch, deleted the cache and all updates of the Google apps, but I was not able to get OK Google back running...
I am not sure if this is a device-specific issue or a LineageOS-specific issue, but on my device with LineageOS it does not work anymore...
(Btw, when tapping the microphone icon in Google's search bar, the voice recognition is working fine!)
Any ideas?
Anyone having the same problem?
Anyone already fixed that?
Best,
Tom

I have the same problem with my stock phone.Ok google/Hey google not working.

BoxyK said:
Since some weeks, though, the "OK Google" detection stopped working and I cannot find out, why.
Click to expand...
Click to collapse
Try this:
https://forum.xda-developers.com/showpost.php?p=76652234&postcount=3

Unfortunately, this did not work.
Still all options for voice match are greyed out...

BoxyK said:
Unfortunately, this did not work.
Still all options for voice match are greyed out...
Click to expand...
Click to collapse
Try to delete google app data after you pushed those files. Here it works as expected.

I don't get that.
The Google app is part of the gapps. It's installed in the /system partition.
After deleting it, how should I re-install it?
From the Play Store (is it available there?)?
Or in the /system partition again (how?)

BoxyK said:
I don't get that.
The Google app is part of the gapps. It's installed in the /system partition.
After deleting it, how should I re-install it?
From the Play Store (is it available there?)?
Or in the /system partition again (how?)
Click to expand...
Click to collapse
Not the app eheh, only its data from Settings - Apps and notifications - Show all apps - Google - Storage space - Manage space - Delete all data.

I've done that several times already.
Now again, with the two apps installed in /system.
I deleted all the data of the Google app.
I've even tried to delete all data from Play services which meant re-configuring all the accounts and settings and so on again from scratch, but that didn't help, either.
This is really weird.

Check also if it's not a gapps issue, try this within Lineage: https://www.androidfilehost.com/?fid=674106145207491329
Otherwise i'm out of ideas, you could try my build (https://androidfilehost.com/?fid=962339331458996492) and see if you can enroll Ok Google again. Then, if it works, you could even try to flash Lineage again and see if it still works (you know, Google server side voodoo lol).

Completely stock here and having the same issue. I am starting to regret getting this phone.

I've tried now to
- re-install Lineageos 15.1
- install another build of Lineageos 15.1
- using different versions of GApps
but nothing brought my voice match back...
Now I'm a little bit frustrated

Google Assistant is messed up

Hey All, my google assistant on my pixel 2 stock rooted June patch on verizon is having odd behavior. It seems that localized commands will work such as, "hey google, what is the weather" or "okay google, turn off mobile data".
When i ask something that requires assistant to go out to thew web for results, it will recognize the command but then it will show the three dots as if it's searching but never return results. Another strange thing is that when i ask it to call my voicemail, it will do the same thing but if i turn off mobile data, it will make the call .
i've tried clearing google app data and cache. i've also taken the SIM out and put it back in but the issue persists.
anyone else ever experience this? any suggestions?

i re-downloaded and re-flashed the system image. issue persists.

Fixed it. Needed to uninstall the Google app updates. I updated again via the n play store and it continued to work

Play Store downloads stuck at 99 or 100% or SMS (stock app) stuck on sending?

If you are having these issues (see title), what worked for me was to disable, uninstall or freeze (if rooted) the google app. This means you'll lose "ok google", google lens, etc. everything related with the assistant, but, for me is worth it because sending sms messages to have them show "sending..." eternally while knowing they were received drove me nuts.
Try uninstalling or disabling the google app if you are having issues like this.
Good Day.

nichobrooks said:
If you are having these issues (see title), what worked for me was to disable, uninstall or freeze (if rooted) the google app. This means you'll lose "ok google", google lens, etc. everything related with the assistant, but, for me is worth it because sending sms messages to have them show "sending..." eternally while knowing they were received drove me nuts.
Try uninstalling or disabling the google app if you are having issues like this.
Good Day.
Click to expand...
Click to collapse
This worked exactly once for me. Has it solved your problem indefinitely? If so, do you know why?

channeledbymodem said:
This worked exactly once for me. Has it solved your problem indefinitely? If so, do you know why?
Click to expand...
Click to collapse
As long as I had the Google app disabled everything worked flawlessly (I tested for months)
Recently I had to restore my phone to factory (locked bootloader, wipe, etc)
Now Google and my phone can work together again.
Not sure what changed, but so far so good.

This oddly worked for me

have been having this problem since June 2019with a Honor V10. I too found disabling the Google app was a work around. Strangely yesterday I managed to enable Google update all apps and the sms sent fine for about 10 hours now I'm back to the same problem again. I have also restored the phone and reinstalled all apps from scratch rather than use a back up. With the same issue occuring I presume there must be a software conflict somewhere with the apps I download.
Did anyone find a long term solution that enable the Google app to run?
Cheers n Gone Nick

Whoever stumbles here from google, I had same problem today and instead of disabling Google app, just killing it worked for me.

"Ok Google" not working on new 7 Pro

I tried uninstalling and reinstalling the Google app, clearing cache in app and on phone. Retrained the voice in Google app a dozen times. Nothing is working. Side note: my SIM card is still installed in my old 5T. the 7 Pro doesn't have a SIM card. Not sure if that is a factor. Assistant works fine. *UPDATE: "OK Google" will launch when prompted when display is locked but it won't answer or respond to whatever I ask it. "OK Google" will not launch or respond when phone is unlocked at all.

I'm having similar issues but mine stops responding once I connect to my car stereo... And doesn't respond even after disconnecting until I reboot.

7 pro?

Same issue OK Google will NOT work on the One Plus 7 pro for some reason on my end
Did all that was suggested , Clear Cache , Clear Data, Disable Google, Reboot, then Endable google, retrain my voice
But still on the home screen when I say OK Google nothing happens
Anyone have a FIX for the Oneplus 7 pro? Thanks
BTW Stock 9.5.7 GMA21AA Firmware
Model GM1917
STOCK Not Rooted

I'm assuming you are rooted using Magisk? See my post here:
https://forum.xda-developers.com/oneplus-7-pro/help/google-match-lockscreen-t3936647

qwen3579 said:
I'm assuming you are rooted using Magisk? See my post here:
https://forum.xda-developers.com/oneplus-7-pro/help/google-match-lockscreen-t3936647
Click to expand...
Click to collapse
Not rooted. Using Nova and I restored from a Nova backup if that matters.

robdam1001 said:
Not rooted. Using Nova and I restored from a Nova backup if that matters.
Click to expand...
Click to collapse
Interesting. Sorry I can't help then. I had the exact same issue but was able to to resolve it by adding Google Framework to Magisk Hide. Since you're not rooted, this doesn't apply. Maybe try resetting to factory and see if it works before restoring any backups?

rooted, with custom kernel and custom launcher. OK Google works like a charm.

qwen3579 said:
Interesting. Sorry I can't help then. I had the exact same issue but was able to to resolve it by adding Google Framework to Magisk Hide. Since you're not rooted, this doesn't apply. Maybe try resetting to factory and see if it works before restoring any backups?
Click to expand...
Click to collapse
Just did factory reset and ok Google is now working. It hasn't finished restoring, however. I'll report back once it has. What a pita.

UPDATE: OK Google is working fine after Factory Reset, (PITA), and full restore.

That is what I was afraid of ,doing a full factory reset
If anyone has another solution that avoids that please let me know
Thanks all

Mine seems to work when the phone is awake however I have noticed that for some reason the Google pill widget does not show the 'ok google' text that normally shows up on my other phones.
Using stock launcher so not a 3rd party problem.
Anyone else notice this?

Not entirely helpful here other than to tell you that I'm not experiencing the same thing. ?

Full factory reset as a solution, lol. C'mon guys

No better solutions? Are we the only unlucky ones here.

The similar issue I have also come across on my phone and believe me, it was very irritating situation as I am not getting any way to fix it. Even I was not able to understand why it was happening but after searching a lot, I have got some solutions given in one blog. So if you are also coming across the same issue like "OK Google Not Working" then try the below solutions:
Solution 1: Restart Your Android Phone
Solution 2: Force Stop Google App
Solution 3: Clear Cache of Google App
Solution 4: Turn Off Bixby [For Samsung Users]
Solution 5: Make Sure That OK Google Command Is Enabled
Solution 6: Check Microphone On Your Device
Solution 7: Turn Off Adaptive Battery And Battery Saver Option

An old one here but have you installed any third party notification app like notifybuddy or plus beat? Ok Google won't work with these installed. The only notification app that doesn't interfere is AOE.

I have noticed a similar issue with voice-to-text being terrible and when this is happening OK Google does not work although it could be problem that happens even after OK Google is working but the voice to text is terrible at recognizing words. After android 10

Pixel 3a Stock ROM July Update Access with Voice Match keeps turning off!

Hi,
So today I tried to use the google assistant via voice commands and it didnt work. I ended up in the assistant settings and noticed Access with Voice Match was turned off. Every time I try to turn it on it turns itself back off.
I've looked extensively across the web for answers to this as others have had this issue in the past but nothing is working for me.
So far I have tried:
Rebooting Device
Re-installing the July factory image (via fastboot and removing -w)
Clearing the cache/app data for the Google app
Uninstalling and reinstalling the google app
Logging out of the google account and logging back in
Ensuring the google app has all permissions including microphone
Resetting application defaults
clearing cache/data of pixel launcher
clearing cache/data of play services
Nothing is working. This was definitely working before the latest update although I'm not sure if the update is at fault.
Any suggestions are welcome as this is driving me crazy. Thanks in advance!
EDIT: Just got off chat support with Google and nothing helped. They asked me to file a bug report.
Is anyone else having this issue on the July patch?
Thanks!
EDIT2: Seems to be related to a custom kernel (I think). I let the developer know and will post more when I find out about this. Removing the custom kernel fixes the issue.