"OK Google" not working anymore on LineageOS 15.1 - Honor View 10 Questions & Answers

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

Related

[Q] Nexus 5 will not add calendar events via Google Now, any fix?

whenever I try to add a calendar event using a voice command in Google Now, it will get to the final confirmation screen and then error out.
This was an issue with 5.0.0, and remains an issue after I updated to 5.0.1 via OTA. Unfortunately I never tried to add calendar events with voice commands back in KitKat, so I don't know if it was a problem in 4.4.
I've tried many times and get the same result each time, regardless of whether I am on WiFi or LTE.
Google Now works fine in every other way. For example, if I use a voice command to start navigating to a specific address, there are no issues with that.
Here's what happens after I say the command. Everything looks fine at this point: http://imgur.com/8wpP5oc
However, as soon as I press the check mark in the bottom right corner, this happens: http://imgur.com/pOJkufp
Any ideas on a fix? Thanks!
Are you blocking/disabling anything regarding Google Play Services/Google Search?
Lethargy said:
Are you blocking/disabling anything regarding Google Play Services/Google Search?
Click to expand...
Click to collapse
Can you elaborate? I just recently upgraded to 5.0.1, so most of my settings are at defaults. I don't think I've gone in and specifically uninstalled/blocked anything related to Google search yet.
996gt2 said:
Can you elaborate? I just recently upgraded to 5.0.1, so most of my settings are at defaults. I don't think I've gone in and specifically uninstalled/blocked anything related to Google search yet.
Click to expand...
Click to collapse
Try clearing the data of Google Search/Google Play Services and maybe try removing and readding your Google Account.
If that doesn't work then make a backup then reflash factory images.
I finally got around to completely re-flashing my phone via fastboot. I am now on a completely clean install of Android 5.0.1. I've even gone back to stock keyboard and launcher in case Nova or Swiftkey was causing an issue.
However, still no luck. Getting the exact same error as before when trying to add a calendar event via Google Now voice command.
Any ideas?

[Android 5.1] Hangout constantly crashes on launch. + "Google Apps has stopped"

[Android 5.1] Hangout constantly crashes on launch. + "Google Apps has stopped"
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
Unfortunately, Hangouts has stopped.
Click to expand...
Click to collapse
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
Unfortunately, Google Apps has stopped.
Click to expand...
Click to collapse
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
===============================================
UPDATE -
POSSIBLE CAUSE AND SOLUTION​
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This is like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
What was your installation process for Play Services 7.0.93?
Aerowinder said:
What was your installation process for Play Services 7.0.93?
Click to expand...
Click to collapse
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
bagarwa said:
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
Click to expand...
Click to collapse
That is strange. I have the same version of Hangouts, but my updated version of Play Services is 6.7.76 (1745988-438).
bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
My issue is hangouts keeps getting killed by the Low memory killer even though I have 1gb free ram.
I did some monitoring, hangouts Noe has to run its own process that I've never seen before and after a minute it caches itself, and I guess the cache is dumped later since I haven't opened hangouts in 5 minutes, I have to restart the app every time I need to use it. I also don't receive any messages during that time because the app has been killed. Any ideas?
chabsie said:
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
Click to expand...
Click to collapse
POSSIBLE CAUSE AND SOLUTION​
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
bagarwa said:
POSSIBLE CAUSE AND SOLUTION​
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
Click to expand...
Click to collapse
Actually I'm using LBE as well and I suspected that it could have been the cause, and as you experienced, I removed all restrictions from the hangouts app and the problem still persisted.
My theory now is that a restriction that we've set on another app (or apps) is indirectly causing this issue with hangouts.
Does anyone know specifically which system apps could be connected to the functionality of Hangouts?
UPDATE: I've disabled restrictions on Youtube, Calendar, and Drive. This appears to have solved the problem.
Hangouts is working normally thus far and I haven't seen any error messages. Will update if things change.
I have a feeling that it's Drive.
What s
Is LBE? I'm stock phone sideloafed 5.1 and I have actually disabled hangout prior to upgrade now getting this error
Lee
Google play services "keep awake" disabled could cause it
I let all my apps keep awake in app ops and so on, but still have an issue with hangouts. It gets killed by system 5-10 minutes of not using it even if I leave it in background
2nd Update:
The problem is persisting again... my hypothesis has been disproved.
Any other suggestions or discoveries would be appreciated. I'm trying to find a way to fix Hangouts while keeping privacy settings in place as much as possible...
If XPrivacy was working for Android 5.0+ this issue would disappear.
I re enabled hangouts and updated it and not had the issue since
Play Service 7.0.96 from http://www.apkmirror.com/apk/google-inc/
Hangouts (+LBE) works fine by 5.1
Nexus 5 32GB, Android 5.01
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
I had a similar issue, so I rolled back hangouts to 2.5x and it's working fine now, YMMV. of course this may not be a viable solution to you but a working older version is better than a non-usable latest version.
Cheers!
Well, the only thing I can think of, in my circumstances, is that I had hangouts disabled when I updated to 5.1 (I don't use it). So yesterday I enabled it, cleared data, and disabled it again, and so far no crash. Maybe something got changed in the update and it didn't like the fact hangouts was disabled. Again, your issue may vary.
spark001uk said:
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
Click to expand...
Click to collapse
The new play services pretty much renders your phone useless due to nonstop update wake lock, (read more on the cataclysm ROM thread, like last 30 pages). The only way to fix the wake lock so far is to flash the cataclysm ROM patch (idk if it will work with stock ROM but it should) and it blocks the wake lock.
See attached picture below, that's how bad the new google play services is.
As for hangouts I got UKM and lowered the low memory killer to a minimum and disabled laptop mode (I'm using elementalX) and hangouts works just fine for me now.
russian392 said:
The new play services pretty much renders your phone useless due to nonstop update wake lock.
Click to expand...
Click to collapse
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
spark001uk said:
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
Click to expand...
Click to collapse
Yes, it would.

Speech to Text (Voice Typing) on Nexus7 (CM12 and Marshmallow)

I have a Nexus7 (flo). I have never been able to get Speech-to-text functional. I think the device came with KitKat, but I've upgraded it all the way through to Marshmallow without getting the damn "Voice Typing" function to work. I'm using the google keyboard, and everything has been stock up until now. A couple weeks ago I flashed to TWRP and CM12, and it still doesn't work. Here's the lowdown-
Google Keyboard is properly set up with my native language.
The microphone icon on the keyboard is shown, but there is no result when it's pressed, long-pressed, or tapped repeatedly in anger.
I've tried several suggestions involving deleting any cache or app data via TitaniumBackup and TWRP.
There is no voice typing option in any of the menus.
I have the following Google-related apps installed:
Google Play Store
Google Keyboard
Google Contacts Sync
And the following Google services:
google backup transport
google account manager
google one time init
google partner setup
google play services
google services framework
Unfortunately I don't know what services or components are required for google voice typing. It didn't work when I had absolutely *everything* from google installed (as it came on this device), so any advice is greatly appreciated!
hello everyone,
got the same problem as artician on my i9100 under CM12. I installed the gapps pico.
Is another gapps version needed? If yes which one?
thanks a lot for anyone's help
Yeah I still haven't heard anything. Not even from Google.
Bricolux said:
hello everyone,
got the same problem as artician on my i9100 under CM12. I installed the gapps pico.
Is another gapps version needed? If yes which one?
thanks a lot for anyone's help
Click to expand...
Click to collapse
By the way, I am also experiencing some loss of wifi connection. I need to switch off, and then back on the wifi of the phone to reconnect to my router.
Do you also have this problem? (I'm running the CM12 20151116 SNAPSHOT version)
cheers

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

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.

Categories

Resources