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
Is there a way to get ok google to work on the edge?
Sent from my Samsung Note Edge using Tapatalk
It works just fine on my t-mobile edge. Just scroll to whatever home screen your Google search bar is on and say, Okay Google.
I was playing with the settings the other day to try to save battery power. I must have shut something off, because it doesn't work on mine.
Sent from my Samsung Note Edge using Tapatalk
Ok ran google setup and now it works. But it just made the search bar useless. Didn't like the looks of it anyway.
Sent from my Samsung Note Edge using Tapatalk
Have you tried this?
Settings -->language and input --> turn on voice search --> turn on, "ok Google" detection --> record your own, "ok Google "
When done, try it and works even when screens off....
That is a different way of getting there, but that is how I got it to work again. (You can also get there by using google setup in the app drawer) of course the OK Google is gone from the widget, but I guess it's better this way.
Sent from my Samsung Note Edge using Tapatalk
Oditius said:
That is a different way of getting there, but that is how I got it to work again. (You can also get there by using google setup in the app drawer) of course the OK Google is gone from the widget, but I guess it's better this way.
Sent from my Samsung Note Edge using Tapatalk
Click to expand...
Click to collapse
If you are using Nova launcher, it has the capability to work from any screen of the launcher. (homescreen/alt screens/dashboard)
Been using Nova for a few years and they've done a great job integrating things like this, while adding a little extra capabilities.
If you follow the directions in google setup, you can access OK Google from any screen and also if the lock screen is on if you choose to do so.
Sent from my Samsung Note Edge using Tapatalk
Oditius said:
If you follow the directions in google setup, you can access OK Google from any screen and also if the lock screen is on if you choose to do so.
Sent from my Samsung Note Edge using Tapatalk
Click to expand...
Click to collapse
I know this but tons of other dont.
No one ever cares to read the manual.
Plus alot of stuff is disable by the carrier if they let them setup the phone.
That's why I always setup my own phone and then later go through all the settings.
I had my Note 3 able to send text messages by voice while the screen was off. And it's nice to be able to tell it to play a song while it's in your pocket.
Voice controls are cool to me. Just suck that's it's always listening so if you say something similar it will wake up.
Someone please help me out here. S voice is giving me some serious pain in the ass right now.
I want to disable S voice completely and only use Google Now but that seems to be impossible.
The Issue:
I can only OK Google from my home page where the Google search widget is. On my G3 I could OK Google from any app any screen and even lockscreen without a hiccup.
S Voice is causing issues pretty much everywhere I want OK Google
What I've tried:
Tried freezing S Voice in which case I lost the ability to OK Google from Anywhere and the lockscreen.
So tried using the S switcher app which was very buggy and had to simply uninstall it...
What I want:
Just plain OK Google and nothing else. All I want to be able to do is OK google from any screen and any app like I did so many times before on all other devices I've owned.
Ideally I would want to be able to activate it from lock screen too but that's not a priority.
Can anyone help me out here.
My friends S4 can do this all seamlessly too but the Edge seems to bug out everywhere because of S Voice
If you go to your Google settings in the app drawer, you'll find the options for ok Google to activate from any screen. I have a t-mobile Edge.
Google Settings->Search and Now
If you're rooted you can install xposed and install the ok Google module which works for any launcher
Oditius said:
That is a different way of getting there, but that is how I got it to work again. (You can also get there by using google setup in the app drawer) of course the OK Google is gone from the widget, but I guess it's better this way.
Sent from my Samsung Note Edge using Tapatalk
Click to expand...
Click to collapse
I can use OK Google from any screen and it's still available from the widget. I am using the stock launcher & have an AT&T Edge. My friend has a T-Mobile Edge and he couldn't get OK Google to work from any screen other than the home screen, even though his OK Google detection settings are the same as mine. He gave up and started using Nova launcher lol.. could be that some devices have an issue with this.
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
knlgSeeker said:
I can use OK Google from any screen and it's still available from the widget. I am using the stock launcher & have an AT&T Edge. My friend has a T-Mobile Edge and he couldn't get OK Google to work from any screen other than the home screen, even though his OK Google detection settings are the same as mine. He gave up and started using Nova launcher lol.. could be that some devices have an issue with this.
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
Click to expand...
Click to collapse
This pretty much sums it up. Like I have said I'm no noob when it comes to using Google Now and know every detail of it's settings. Yes, all my settings are set to activate from any screen yet it fails to activate.
The issue is if I freeze or uninstall S Voice I am no longer able to check mark the Activate from any screen box and if I have S Voice activated it just seems to cause issues with ok google and just a clumsy software overall.
I was just wondering if anyone had a workaround.
You have to freeze S-Voice, then clear data for the Google Search app and then set Google up again. Trust me.
tospace2006 said:
The issue is if I freeze or uninstall S Voice I am no longer able to check mark the Activate from any screen box and if I have S Voice activated it just seems to cause issues with ok google and just a clumsy software overall.
I was just wondering if anyone had a workaround.
Click to expand...
Click to collapse
You do have to freeze S voice. Then while in application manager go to Google search and clear data. Then get out of settings because you are correct the option to activate from any screen is gone. Now go to your app drawer and choose Google settings. Click on Search & Now. Click on Voice and set it up from there. The option is available in these settings.
audri5 said:
You do have to freeze S voice. Then while in application manager go to Google search and clear data. Then get out of settings because you are correct the option to activate from any screen is gone. Now go to your app drawer and choose Google settings. Click on Search & Now. Click on Voice and set it up from there. The option is available in these settings.
Click to expand...
Click to collapse
YES! you da best. Now for the sake of it could I do the exact reverse to only use S Voice if I ever feel like using it exclusively?
tospace2006 said:
YES! you da best. Now for the sake of it could I do the exact reverse to only use S Voice if I ever feel like using it exclusively?
Click to expand...
Click to collapse
Well I'm no expert but I don't see why it wouldn't work the same for S voice.
The issue I'm having is Google now won't work when connected to bluetooth. I have mine connected to my Gear S and when I say ok Google the bar stays frozen instead of jumping around showing you it's listening. Soon as I disconnect my watch it works fine. It's annoying!
Sent from my SPH-L900 using XDA Free mobile app
Been looking around for the past few weeks for a solution to this. I thoroughly enjoy Cortana being able to sync reminders with my Windows PCs, and decided I wanted to officially switch over to using it instead of Google Now. There are some guides out there, but only show switching a soft button on the screen to utilize this feature. However, with the Galaxy S7, it opens Google Now by holding the Home button. I went through and dug through apps attempting to change that, but couldn't get anywhere (Nothing in Cortana allowed me to make that change, and even disabling Google Now in an attempt to have Cortana be the only option available just made holding the home button not work). Anyone know where I can find a setting to change this?
QuentinX5 said:
Been looking around for the past few weeks for a solution to this. I thoroughly enjoy Cortana being able to sync reminders with my Windows PCs, and decided I wanted to officially switch over to using it instead of Google Now. There are some guides out there, but only show switching a soft button on the screen to utilize this feature. However, with the Galaxy S7, it opens Google Now by holding the Home button. I went through and dug through apps attempting to change that, but couldn't get anywhere (Nothing in Cortana allowed me to make that change, and even disabling Google Now in an attempt to have Cortana be the only option available just made holding the home button not work). Anyone know where I can find a setting to change this?
Click to expand...
Click to collapse
All in one gestures app from the play store will let you set various keys to do different things. You could set it up to launch cortana instead of google now.
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures
copenhagen said:
All in one gestures app from the play store will let you set various keys to do different things. You could set it up to launch cortana instead of google now.
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures
Click to expand...
Click to collapse
Exactly what I was looking for, and exactly did the job. Thanks!
To switch without using a third party app in the Galaxy S7:
Go to Settings
Search for "Device assistance app" and click it.
click "Device assistance app" and change it to Cortana