I can't use the "OK Google" command within the launcher. It's not responding when I say OK Google. When I tap on the microphone icon next to the search bar, it says "Can't Open Microphone".
I've tried re-starting, installing a new build, and even tried clearing the cache for Google Apps, Maps.
This problem occurred earlier when I was trying to use the voice command to do a GPS search with Google Maps. Google Maps was acting all weird and couldn't locate my position then the Can't Open Microphone error began popping up. I don't know what to do.
I'm using the latest CM Nightly build from 09/29.
Same problem here. My Google now can't detect and says "can't open microphone" .
On CM11 KK
Meo15 said:
Same problem here. My Google now can't detect and says "can't open microphone" .
On CM11 KK
Click to expand...
Click to collapse
My problem is fixed now. I'm not sure what happened, but after a reboot. It's working. Wish I could be more of a help. Hope you find a solution. Though I am certain is an app conflicting with the Voice function.
i had an update and now mine works too
Replaced audio_policf.conf and now its working. OK Google ???
Related
Hi all,
the recent update to Maps (7.6.0) has broken Google Now, for me.
When I swipe to the Now screen and refresh it, I always get a message saying "Unfortunately maps has stopped."
Have uninstalled the update through Play Store, it's on 7.4.0 now, the error in Now has disappeared.
Any one else seeing this ???
Update :
Play Store is now offering Maps 7.6.1 which has solved the issue for me.
Tommmii said:
Hi all,
the recent update to Maps (7.6.0) has broken Google Now, for me.
When I swipe to the Now screen and refresh it, I always get a message saying "Unfortunately maps has stopped."
Have uninstalled the update through Play Store, it's on 7.4.0 now, the error in Now has disappeared.
Any one else seeing this ???
Click to expand...
Click to collapse
I have the exact same issue and I get the error on both my Nexus 4 and Nexus 10. However, there's no error on my wife's Nexus 4 and also when I switch to her account on N10.
Unfortunately Maps has stopped
I am also experiencing the same thing on my Nexus 5. I think the problem started after updating to the latest Google search app.
Yep, same except problem for me. Was on Purity decided to go back to Stock and confirmed the problem still exists.
As my experiencing, Maps (7.6.0) has broken in each minutes on both Galaxy Nexus and Samsung Note3. No error after uninstalled the map(7.6.0).
I've updated to maps 7.6.1, issue is resolved.
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?
Hi, everyone
I'm using fake nexus 7.1 rom, and enabled google assistant, the problem is , even though I've already saved my voice model, when I say ok google, it shows the "teach the assistant to recognize your voice" menu every time-_-
and when I choose "do it later", google assistant will come out normally.
Does anyone have the same issue?
hyoui0407 said:
Hi, everyone
I'm using fake nexus 7.1 rom, and enabled google assistant, the problem is , even though I've already saved my voice model, when I say ok google, it shows the "teach the assistant to recognize your voice" menu every time-_-
and when I choose "do it later", google assistant will come out normally.
Does anyone have the same issue?
Click to expand...
Click to collapse
It's a known issue on nougat ROM. The developers cannot patch it, it's a Google bug, or possibly feature. Lol.
Is anyone looking into this. Its really annoying.
Same here on Marshmallow with Assistant Enabler Xposed Module. This is so annoying that I might actually go back to Google Now.
Download app "ChopAssistant" from google play. It fixes the problem, trust me
aciupapa said:
Download app "ChopAssistant" from google play. It fixes the problem, trust me
Click to expand...
Click to collapse
It still shows up in the background behind the Google Assistant Dialog box anyway around that?
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
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