Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,806,815 Members 40,272 Now Online
XDA Developers Android and Mobile Development Forum

Google Now Not Listening: US

Tip us?
 
danlo
Old
#1  
Senior Member - OP
Thanks Meter 15
Posts: 132
Join Date: Feb 2006
Location: New York, NY
Default 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.
Attached Thumbnails
Click image for larger version

Name:	uploadfromtaptalk1384025338103.jpg
Views:	1403
Size:	35.8 KB
ID:	2381904  
 
rokius
Old
#2  
rokius's Avatar
Member
Thanks Meter 54
Posts: 96
Join Date: Jul 2009
Quote:
Originally Posted by danlo View Post
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.
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
 
danlo
Old
#3  
Senior Member - OP
Thanks Meter 15
Posts: 132
Join Date: Feb 2006
Location: New York, NY
I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.
 
TJCacher
Old
#4  
TJCacher's Avatar
Member
Thanks Meter 43
Posts: 64
Join Date: Jul 2006
Location: Springfield, MO
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
The Following User Says Thank You to TJCacher For This Useful Post: [ Click to Expand ]
 
danlo
Old
#5  
Senior Member - OP
Thanks Meter 15
Posts: 132
Join Date: Feb 2006
Location: New York, NY
Quote:
Originally Posted by TJCacher View Post
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
Thanks for the tip!
 
bengrulz
Old
#6  
Senior Member
Thanks Meter 3
Posts: 195
Join Date: Jun 2008
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.
 
shaklee3
Old
#7  
Member
Thanks Meter 2
Posts: 68
Join Date: Oct 2011
Quote:
Originally Posted by bengrulz View Post
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.
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.
The Following User Says Thank You to shaklee3 For This Useful Post: [ Click to Expand ]
 
TJCacher
Old
#8  
TJCacher's Avatar
Member
Thanks Meter 43
Posts: 64
Join Date: Jul 2006
Location: Springfield, MO
Quote:
Originally Posted by bengrulz View Post
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.
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.
The Following User Says Thank You to TJCacher For This Useful Post: [ Click to Expand ]
 
anis2913
Old
(Last edited by anis2913; 12th November 2013 at 02:54 AM.)
#9  
Junior Member
Thanks Meter 3
Posts: 8
Join Date: Jul 2009
Location: Atlanta
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...
Phones:
Nexus 5, Stock
Nexus 4, CM10 Nightlies
G1, Rooted, CM6
Nexus One, Rooted, CM7 Nightlies

Tablets:
Asus EEE Pad Transformer, Stock 3.2
Galaxy Tab 10.1, Stock (TW) 3.2
 
gaetawoo
Old
#10  
gaetawoo's Avatar
Senior Member
Thanks Meter 35
Posts: 178
Join Date: Jul 2010
Quote:
Originally Posted by shaklee3 View Post
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.
Quote:
Originally Posted by bengrulz View Post
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.
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.


Quote:
Originally Posted by TJCacher View Post
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.
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.

The Following User Says Thank You to gaetawoo For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes