Database Info

google now always listening stopped work?

My google now hot work detection stopped work for some reason, even tho I have hot work enabled thru google now and the language is English (US). You can see my google voice mic in the google search bar is hollow. Anyone know a fix for it? I tried rebooting the phone and it didn't help.
https://www.dropbox.com/s/u4bgk8j8ni186u0/Screenshot_2013-11-13-23-41-01.png

bluesfear said:
My google now hot work detection stopped work for some reason, even tho I have hot work enabled thru google now and the language is English (US). You can see my google voice mic in the google search bar is hollow. Anyone know a fix for it? I tried rebooting the phone and it didn't help.
https://www.dropbox.com/s/u4bgk8j8ni186u0/Screenshot_2013-11-13-23-41-01.png
Click to expand...
Click to collapse
Scroll over to Google Now and head to settings and look inside the Voice category.
See if Hotword Detection is on or not. If not, turn it on and that should do the trick!
If it IS on though, try giving it a toggle.

it is checked. I gave it a toggle it still doesn't work...

It likes to stop working for me too.
I found that putting in headphones tends to disable the hotword.
Try plugging in headphones, unplugging them, then screen off, and screen on.

I found the problem. It was pushbullet. Whenever I have that installed it disabled my always listening hot word detection. Not sure why.
Sent from my Nexus 5 using Tapatalk

[Q] Google Now Hotword Detection Everywhere?

So now that we have root, is there any way to get Google Now to detect our hotword everywhere? I really miss this feature from my Moto X. I know the X has a slightly different implementation, but Lollipop has some of this functionality built in, so I'm hoping its something we can get to with root.

cmdoptesc47 said:
So now that we have root, is there any way to get Google Now to detect our hotword everywhere? I really miss this feature from my Moto X. I know the X has a slightly different implementation, but Lollipop has some of this functionality built in, so I'm hoping its something we can get to with root.
Click to expand...
Click to collapse
Not sure, but with Nova Launcher, you can at least enable Google Now from the home screen by saying OK Google. Another trick I learned is that you can hold down the home button, that will take you to Google and then you say OK Google. It's okay but still not the ideal solution.

cmdoptesc47 said:
So now that we have root, is there any way to get Google Now to detect our hotword everywhere? I really miss this feature from my Moto X. I know the X has a slightly different implementation, but Lollipop has some of this functionality built in, so I'm hoping its something we can get to with root.
Click to expand...
Click to collapse
My Galaxy S5 does this even without root, in fact it's built in to every Lollipop build now AFAIK. It's in the Google Settings App > Voice > "Ok Google" detection > Turn on both From the Google app and From any screen option. Voila!
Hope this works on the S6 as well.

sirmookie said:
My Galaxy S5 does this even without root, in fact it's built in to every Lollipop build now AFAIK. It's in the Google Settings App > Voice > "Ok Google" detection > Turn on both From the Google app and From any screen option. Voila!
Hope this works on the S6 as well.
Click to expand...
Click to collapse
THAT's the problem.....it DOESN'T!!!!!

Samsung decided in it's infinite wisdom that the Lollipop functionality should disabled because it interfered with S Voice. Thus, no hotword everywhere for S6 users.

I guess this was not intentional and Google and samsung both are trying to figure out what went wrong. There was just an article about it.

OK Google from anywhere is working again. Google fixed it.

"OK Google" command not always waking the phone up

Anyone else having inconsistent results with saying "OK Google" while the screen is off?
It seems to work fine when actively using the phone, but if I hit the power button to turn off the screen then it may (or may not) turn the screen on with the Assistant after saying "OK Google" (nothing happens).
I tried turning on fingerprint/pin security, but this will still sometimes not respond to the command. Additionally, it will also still sometimes ask me for a pin even though I have "Trusted Voice" enabled.
Not sure if it's a hardware issue or software related (again, everything works perfectly if the phone screen is already on and in use).

Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.

Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.

I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?

kinetic758 said:
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
Click to expand...
Click to collapse
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs

ryken229 said:
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Click to expand...
Click to collapse
xShadoWxDrifTx said:
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
Click to expand...
Click to collapse
I was not connected to wifi but the signal seemed fine. I'll keep an eye on it next time.

nednednerb said:
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.

kinetic758 said:
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
Click to expand...
Click to collapse
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs

nednednerb said:
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).

kinetic758 said:
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
Click to expand...
Click to collapse
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs

nednednerb said:
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.

What is scary for me, is any time there is a Pixel commercial on TV and the guy says "OK Google", my phone wakes up. So quite the opposite from the OP experience. Actually scary from a security standpoint. The old Motos used to allow limited functionality via voice but not full unlock (smart idea). There should be a way to remotely disable voice detection if you lose your phone.

kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.

dispatch said:
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
Click to expand...
Click to collapse
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.

I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Sent from my LG-D801 using Tapatalk

kinetic758 said:
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
Click to expand...
Click to collapse
I really don't think it's the hardware, but you never know. I don't yet have a large enough sample size to say if 1 in 10 is accurate in the long run or if it is truly closer to 1 in 100 that it fails to wake. I always assume we're beta testers for Google anyway so I have come to expect things like this.
aquatarkus said:
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Click to expand...
Click to collapse
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.

dispatch said:
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
Click to expand...
Click to collapse
This. I've embraced (at least for now) the fact that Google is collecting information about me. I've bought into it (also purchased a Google Home) with the hope that this will make my life easier (if slightly). A double-edged sword, for sure.

dispatch said:
However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do.
Click to expand...
Click to collapse
I figure I'm smart enough not to need Google to run my life for me. I will first root the Pixel and remove the stuff I don't want. When a suitable version of CyanogenMod becomes available, I'll flash that into it, as it provides additional security/privacy controls.
Anyway, I hadn't meant to highjack this thread....
Sent from my LG-D801 using Tapatalk

kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
Also try training the voice by saying Ok Google at 3 slightly different volumes and with varied pace. Do say it clearly each time. I found voice recognition doesn't work as well if I train it with a forced or monotone rhythm. Cos real voice is more fluid and not always the same.
Good luck
Sent from my sailfish using XDA Labs

Mine works every time.
This was never the case on the Nexus 6P.
The only time the Pixel DIDN'T wake up is when it was on low battery and save mode got enabled. I believe this disables the always listening feature of this app.
Sent from my Pixel using XDA-Developers mobile app

Ok Google detection?

Maybe I am missing a setting somewhere or something, but the Google Assistant on my XZP only responds when the screen is on. I have it set to "any time" in the Assistant settings. Is this normal? I'm pretty sure it worked whenever (screen off/locked/charging/etc.) on my last couple of phones. I'd like it to at least work while the phone is charging.
Any ideas?

well yeah I had the same problem, apparently, Google changed the settings of the program, and it was only working while the phone is charging, so whenever u upgrade the application to its latest version you will lose this privilege. my advice and that's what I'm doing is to uninstall the updates from the google app and then give it all the permissions it needs and you will have it to work anytime the phone is charging no matter if the screen is on or off !!
btw my Google app version is 7.2.26.21.arm64

This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk

Jake_09 said:
This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk
Click to expand...
Click to collapse
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...

Heinous said:
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...
Click to expand...
Click to collapse
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for. I really wish they would also implement what Cortana does in terms of how she handles text messages when connected to Bluetooth devices. I love that she would ask if I want her to read it to me and then after reading it will ask me if I want to dictate a reply and send it.
Honestly, for some of the flak that I've seen Cortana getting lately, she's a much better and much more useful assistant than Google or Sri and she's probably the thing I miss the most from WM10.
Sent from my G8141 using Tapatalk

Jake_09 said:
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for.
Click to expand...
Click to collapse
It's not sure it's entirely Google's fault. It worked properly on previous android phones that I've owned.

I just noticed that it seems to work now with the Oreo update. My phone now wakes up and responds to "ok, Google" while the screen is off/locked. ?

This is by far the best part of the Oreo update. Google Assistant is at least 800x more useful now that it is actually hands-free.

Doesn't work wih mine. It blinks like I could say somehing, but stays closed. When I unlock it, nothing happens. My old phone then went into the assistant mode.
Which options do i have to set?

Hey Google Hotword Not Working

My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.

Yes I've had the same issue. Not sure what helped in the end. Maybe a phone restart? or reinstalling the google search app?

PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
georgs_town said:
Yes I've had the same issue. Not sure what helped in the end. Maybe a phone restart? or reinstalling the google search app?
Click to expand...
Click to collapse
Had the same issue 2 days ago on my P2XL. A cache and data wipe of the google app fixed it :good:

Badger50 said:
Had the same issue 2 days ago on my P2XL. A cache and data wipe of the google app fixed it :good:
Click to expand...
Click to collapse
Thanks, that worked for now....

PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
Personnaly I've noticed I have to yell the word in order for the phone to wake up. I first thought it was wrongly configurated and wiped the app data several time, until I figured the pixel was a bit deaf..

Aanze said:
Personnaly I've noticed I have to yell the word in order for the phone to wake up. I first thought it was wrongly configurated and wiped the app data several time, until I figured the pixel was a bit deaf..
Click to expand...
Click to collapse
I have noticed that Google Assistant been buggy during last few days. Clearing storage and cache does help but even when its back working sometimes it has issues making the registered action. For, example, setting alarm/timer gets registered (the text appears in google assistant but google assistant is sometimes slow to read the registered command + even after google assistant repeats the command and says its done the actual action does not following, meaning the alarm/timer is not set and only on second try it gets through. Never had similar issues before. Not sure if its google app or December update, but I did not have any issues before.
No issues with things like Weather reports and reminders though..

PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
This kept happening to me last week. My phone was on battery saver which did not turn off automatically after charging. Had to toggle the battery saver and do a restart to have OK Google work somewhat reliably.

jemeljsh said:
I have noticed that Google Assistant been buggy during last few days. Clearing storage and cache does help but even when its back working sometimes it has issues making the registered action. For, example, setting alarm/timer gets registered (the text appears in google assistant but google assistant is sometimes slow to read the registered command + even after google assistant repeats the command and says its done the actual action does not following, meaning the alarm/timer is not set and only on second try it gets through. Never had similar issues before. Not sure if its google app or December update, but I did not have any issues before.
No issues with things like Weather reports and reminders though..
Click to expand...
Click to collapse
I thought this was just a glitch, but my wife's old phone did this right before we upgraded to the Pixel 3. She burned the food in the oven because the timer didn't get set even though the assistant confirmed the command.
Maybe we should start saying please and thank you before the machines rise against us.