Database Info

Google Now Not Listening: US

Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.

danlo said:
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
Click to expand...
Click to collapse
Were you using headphones that day? I've seen this issue, and I think it's an audio issue (software). When I had this issue, the speakers didn't work either.
Sent from my Nexus 5 using Tapatalk

I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.

Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk

TJCacher said:
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip!

man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.

bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.

bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.

I've had the same issue, but I can add that this is happening with games as well. Specifically, asphalt 8 causes this problem. Obviously, when I'm switching between apps, I wouldn't want to kill an ongoing game or song just to make the hotword work. The HC issue is annoying and I hope there's a fix to always keep it live no matter which apps are in the background...

shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
My hotword detection also suddenly doesn't work. I've toggled the option in google now settings, rebooted, cleared cache, turned off google music... nothing turns it back on.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
didn't help me. can't figure out what is going on. so frustrating.
---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.

gaetawoo said:
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
Click to expand...
Click to collapse
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk

TJCacher said:
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've talked to them, they know about it and are working on it, but that say it could be an OS issue.. that are trying to figure it out.

This happens to me at least couple times a day. Either Wi-Fi disconnect or a OK Google three I n a row consecutive search. Solution: kill the g search app it will automatically restart and you'll be gtg

Pebble whatsapp notifier causes this same problem. Unchecked it in accessibility and viola! Always listening again..

Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.

TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
I have the same issue and none of that work for me, it gets stuck with real racing, i force the stop once and it started to work again but minutes later it was hallow again, please help

shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
Are you on stock? I thought this was a result of the new launcher in today's version of cm.
Sent from my Nexus 5 using XDA Premium 4 mobile app

xdapro said:
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
Click to expand...
Click to collapse
I love you dude or dudette I was going balled trying to figure this out, thanks a lot!

I found out that the hot word detection only works on the default launcher. If I add the google search widget on apex launcher, I get the search bar with a hollow mic, and hot word detection does not work.
If I use default launcher I got the full mic and hot word detection works.
Sent from my Nexus 5 using xda app-developers app

OK Google - Doesn't work

I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?

brandypuff said:
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
Click to expand...
Click to collapse
Nop, works for me even on BT. Maybe you have it disabled?

so what should I do? under the screen "OK Google" detection, it shows, From the Google App=on, but the other options are greyed out. When I turn on From Any Screen, it asks me to Just say OK Google three times, and it's listening, but it never recognizes my voice even if I say it 100 times. But, I can do a voice search OK in I manually click the google microphone button.

I have the same problem. Recently bought an Idol 3 5.5, and cannot get 'OK Google' to work. Any amount of 'OK Google' commands in different accents (and by different people) are useless. I can do voice search by clicking the microphone button on Google search app. Not sure what is the problem here. How do I make sure this feature is not disabled on my phone?

Same issue here as well. It "will" work if you open the Google App first. It then recognizes commands without having to select the microphone. But yes, without first opening the google app, it does not work.

you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.

There is something wrong with it on the Idol 3. If you boot into safe mode, you can enable it but only from safe mode. I did this and it workd for awhile but then something disabled it again. Very Frustrating. Unfortunately, I doubt we will get any fixes from Alcatel. BTW, to boot into safe mode, press the power button and then long press on either restart or power off. I can't remember which.

like i said it works well on my and many other devices, so you have to set it right.

DallasCZ said:
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
Click to expand...
Click to collapse
Yes, it works from any screen as long as you have "previously" opened the "Google App", and, it's still running in the background.
For instance, if I cycle my phones power, and come to the home screen, "Ok Google" will not work, it simply doesn't work. But, if I open the "Google App" after a reboot, and then go back to my home screen, or any screen, it will work. You have to open that "Google App" first, or it doesn't recognize any command, because it's not "listening" / running in the background. If I "close" all running apps, which you should be doing quite often, "Ok Google" will not work, until I again open that "Google App".
The phone should "Always" be listening (provided you want to use this feature), without the need to run the "Google App" first, but that's simply not the case. To me it's just poor implementation, because it forces you to always make sure the "Google App" is running, or hit the microphone. This shouldn't be necessary. It should just work from the moment the phone has booted up (again, if you want this feature), but it doesn't.
Better implementation would have been a "service" you either turn on, or off, under settings, so it's always running (from the moment the phones powered up), or it's not running.
I hope that's clear, and makes sense?

Makes sense that that's what happening to me as well. I recall it worked just fine previously. I wonder if the recent updates did something to that interface.

I'm having the same problem after doing a factory reset and reloading everything.
It was working fine before the reset and since it will only work if I've recently opened the Google app. I've checked all of the settings multiple times, uninstalled/reinstalled the Google app, and it's still occurring.
Has anyone found any possible solutions?
(Not sure if this is anyhow related, but before the reset the flip to mute and snooze gestures didn't work at all. Since the reset, they work perfectly.)

googlequicksearchbox:interactor error

Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?

xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I have the same issue, the only solution I have is to disable the ok Google option as you said.

xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I think problem should be addressed to Google first cause of Google now, or Huawei, second, cause the service is continuosly listening for "Ok google" activation, but it should stop or, better, stand-by, so the
microphone can be used by the concurrent app, when finished, service automatically restarted. This behaviour doesn't require any error or warning pop-up when happens.
Even I like to know, if anyone knows how to submit issues directly to Huawei/Honor.

Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper

@Xichael: Tap on "Delete Voice Model" and you can turn it off permanently. This is, as far as I know, the only way other than deleting / deactivating the Google App or possibly tweaking certain permissions. Once you delete the voice model, the "Ok Google" should still work within the app or when long pressing the home button.
@xghost1 Yes, deactivating "Ok Google" on any screen by deleting the voice model is so far the only solution that works permanently. There is currently no way to have "Ok Google" everywhere while also not getting that error message. We'll just have to wait for a fix. I think this only applies to the current "Google Assistant" though. It might be possible to go back to an older version of "Google Now" where "Ok Google" on any screen still works while not getting that error.

Thanks, that solves it for me. I can live without "Ok Google", but that popup was intolerable.

xichael said:
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
Click to expand...
Click to collapse
Remove your trained voice and then "Ok Google" detection on any screen will then turn off. That is the only way I found to disable it.
Sent from my FRD-L04 using Tapatalk

xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I was having similar problem and it's gone after i denied permission for microphone...before it was turning itself and made me crazy...I hope it will help You with this issue

famanfwppc said:
I think problem should be addressed to Google first cause of Google now, or Huawei, second,
Click to expand...
Click to collapse
Other Nougat phones with OK Google active don't have this issue. So I'd say Huawei would be the first to be addressed.

It's hard to know who to blame on this one. When Googling, it looks like it's only a problem on Huawei devices. That said, when I try to disable all-screen OK Google detection, the setting won't stick and always reverts. That sounds like a Google issue. I had to delete the voice model.
Likely it's some combination of both.

I called the service hotline last week and they said it was the update to Google app that was screwing things up. For me it was creating a toast message in my camera app when I would record video or use voice activated shutter control for still pictures. He told me to revoke permissions in the Google app for the microphone, or revert to an older version of the app. I'm assuming pre Google Assistant. I haven't tried that option yet.

Turning off all-screen 'OK Google' detection is likely the best option, especially because you can map your Smart Key to Voice Search and get nearly the same functionality. The only impaired function is if you hands-free dock in your car, but even then I rarely use Assistant anyway in that setting.

Thank you all for your comments and replies.
For your information I was receiving this error even without Google Assistant, since I was using my phone with Portuguese language. I tried to reset and changed it to English, now I have Google Assistante working but the error still remains. So like it was already mentioned my best gues is to associate the problem with Google App and Huawei Software.
To be sure it would be good if anyone could test the issue on a Custom Rom.
Thanks

Go into Playstore and chose to uninstal Google app. It will roll back to a version before Google Assistant and your phone will act as normal, you just don't have assistant. I even noticed an issue prior to this while using Shazam to identify a song I was listening to.

Background processes
"com.google.android.googlequicksearchbox:interactor" is a common Android process.
Huawei is at fault for this bug.
I can confirm only Huawei handsets are experiencing this annoying bug.
Huawei also has their own voice assisted application/processes I.e. Quick calling. If you disable all Huawei voice assisted features, this most likely will solve the problem as well.
It seems Huawei voice assisted processes and Google voice assisted processes cannot be active at the same time without the user seeing this message. If you prefer "Ok Google" and other Google voice assisted processes then try disabling Huawei voice software first.
Go to settings and search "voice" then select "voice control" turn off all Huawei voice assisted processes.
Hopefully this helps.

I guess if I want to disable OK Google and use Huawei's voice assistant instead, I can be away from the evil Google. But what does Huawei voice assistant do? I only found "find my phone" and very few other functions. While from what I heard, in China where Google services are totally disabled, Huawei's voice assistant can do a lot more things. Where are they?

Turning off the Huiwei voice facilities does not work. Still get same error.

To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.

SolarisSixth said:
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
Click to expand...
Click to collapse
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Sent from my FRD-L09 using Tapatalk

ckckckckck said:
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Click to expand...
Click to collapse
I totally agree, but that's what we get for giving Huawei money, clearly they don't care.

Google is recording your voice all the time! There is also an annoying box.

Any time I use an app that uses audio, Google freaks out and gives me a little box saying that Google is recording audio. You can't interact with any portion of the screen while this is happening.
I used to be able to wade through going into the setting menus and turn off "OK google from anywhere" detection, which I also don't want to do, but now I can't even do that. It just turns itself back on after the recent Google app update. In my case, I don't even have "Ok Google" enabled, but still when I say "Ok Google", the phone responds with a vibration. So, it seems Google is listening and recording my voice all the time... Scary! How to remove the little box at the first place? And any way to disable Google's recording behavior?

i2000s said:
Any time I use an app that uses audio, Google freaks out and gives me a little box saying that Google is recording audio. You can't interact with any portion of the screen while this is happening.
I used to be able to wade through going into the setting menus and turn off "OK google from anywhere" detection, which I also don't want to do, but now I can't even do that. It just turns itself back on after the recent Google app update. In my case, I don't even have "Ok Google" enabled, but still when I say "Ok Google", the phone responds with a vibration. So, it seems Google is listening and recording my voice all the time... Scary! How to remove the little box at the first place? And any way to disable Google's recording behavior?
Click to expand...
Click to collapse
If you want to get rid of google listening, just go to apps in settings, google app, uncheck mic.

faizalotai said:
If you want to get rid of google listening, just go to apps in settings, google app, uncheck mic.
Click to expand...
Click to collapse
Ok, I am disabling that. Hopefully there is no side effect for other things. Thanks.
PS: I disabled body sensor permission to Google App as it used a lot of battery, then Android Pay cannot work. Mic might be different.

Related issue
https://forum.xda-developers.com/honor-8/help/googlequicksearchboxinteractor-error-t3576362

Google Assistant--User/setting errors?

Edit: So on my drive this morning after the 2nd command through Assistant things worked as they do through Google Now (speaking options, playing music). Took a week, which is quite odd (and not sure if it will continue working later). Might be a bluetooth issue which I am aware that there are many right now.
Started using my Pixel 2 last week and have noticed some 'issues' with Assistant commands over Google Now commands and am not sure if these are settings/user related as I would expect Assistant to be the same if not more feature packed than Google Now.
All the things I am listing work without issue through Google Now and on both my Pixel 2 and my previous Moto Z Play.
1. No voice prompt 'beep' when Assistant is activated. Google Now has a tone to let you know when it starts and stops 'listening.'
2. No talking back (responses) when sending SMS, setting reminders, setting calendar events, asking where the nearest 7/11 is, etc., when connected to vehicle system (2015 Grand Cherokee UConnect)
3. No starting music back up once the above #2 is complete. Have to hit the 'play' button after each command.
The one issue I have solved is that if you are experiencing a blank screen when using Google Assistant (not Google Now) to send/set things, turn back on animation scaling to anything other than 'off' and it should properly display the text.
So Google Now works much better for my uses. Unfortunately, the phone is built with Google Assistant so I have not found a way to default Google Now over Assistant with at least the 'ok Google' hotword (doesn't seem there is any control over Active Edge). Moto Z let you create your own voice activation phrase for Google Now--I really miss that.
But because Google Now works without issue I do not know If I am just missing some settings or more control options for Google Assistant. Any recommendations?