"Ok Google" detection no longer working on lock screen (AT&T) - Galaxy S 5 Q&A, Help & Troubleshooting

Hi,
I just noticed today that "Ok Google" detection does not work from the lock screen (screen is on, but phone is still locked by fingerprint). I checked the Google Now settings, and the "From any screen" setting under Voice -> "Ok Google" detection is enabled. "Ok Google" detection works fine when the phone is unlocked.
This previously worked, though I don't remember the last time I used it (probably a few weeks ago). On Oct 26th, I applied the 5.1.1 update from AT&T on the third attempt after the first two were unsuccessful due to available space issues. Could this update have anything to with why my phone no longer responds to "Ok Google" when the screen is on, but locked?
Thanks,
Brian

I'm running KitKat (just my preference lol) with fingerprint lockscreen, and 'ok google' doesn't work for me either.....
I guess it's a security feature of the fingerprint lockscreen.......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
I'm running KitKat (just my preference lol) with fingerprint lockscreen, and 'ok google' doesn't work for me either.....
I guess it's a security feature of the fingerprint lockscreen.......
Click to expand...
Click to collapse
Interesting. What launcher are you using? "Ok Google" had always worked fine for me using the Google Now Launcher. I'm stumped why it's not working today.

Nova.....but I have the xposed framework installed too.....With the 'ok google for 3rd party launchers' module enabled too.
http://i.imgur.com/rVnFwJM.jpg

This is no longer working for me either. I just noticed today, after installing Android M. It was working the other day with android 5. I went to the "Ok Google" detection settings screen and the option for lock screen is completely gone. Now all I see is "From the Google app", "From any screen" and "Personal results". Did they remove this feature? This was really important to me when I was in the car.
---------- Post added at 08:56 PM ---------- Previous post was at 08:36 PM ----------
jjorloff1 said:
This is no longer working for me either. I just noticed today, after installing Android M. It was working the other day with android 5. I went to the "Ok Google" detection settings screen and the option for lock screen is completely gone. Now all I see is "From the Google app", "From any screen" and "Personal results". Did they remove this feature? This was really important to me when I was in the car.
Click to expand...
Click to collapse
I think I just figured it out. I don't know when this was changed, but apparently the "From any Screen" option is what the Nexus 5 has now, and it is only listening when the screen is off when the device is charging. That is what was wrong for me. The "Always on" feature is apparently only available on Nexus 6 and Nexus 9 (and a few other specific models).

jjorloff1 said:
This is no longer working for me either. I just noticed today, after installing Android M. It was working the other day with android 5. I went to the "Ok Google" detection settings screen and the option for lock screen is completely gone. Now all I see is "From the Google app", "From any screen" and "Personal results". Did they remove this feature? This was really important to me when I was in the car.
---------- Post added at 08:56 PM ---------- Previous post was at 08:36 PM ----------
I think I just figured it out. I don't know when this was changed, but apparently the "From any Screen" option is what the Nexus 5 has now, and it is only listening when the screen is off when the device is charging. That is what was wrong for me. The "Always on" feature is apparently only available on Nexus 6 and Nexus 9 (and a few other specific models).
Click to expand...
Click to collapse
Very interesting. I just testing this by plugging in the phone and trying "Ok Google" with the screen both on and off, and it worked intermittently. So I think this is probably a buggy update. (I'm running the factory OS for the device. I'm not rooted either.)

Related

OK Google from screen off requires PIN. How to turn that off?

I have set up "OK Google" to recognize my voice from screen off.
This works great, however, when I use it, it requires me to enter my PIN/fingerprint to show the results.
Is there any way to turn this off? I find it kind of silly that I have to do that every time.
And as far as security reasons, the phone won't respond to anyone else, so it's not like someone would be able to "OK Google" and unlock my phone, unless they sound exactly like me.
mgorman said:
I have set up "OK Google" to recognize my voice from screen off.
This works great, however, when I use it, it requires me to enter my PIN/fingerprint to show the results.
Is there any way to turn this off? I find it kind of silly that I have to do that every time.
And as far as security reasons, the phone won't respond to anyone else, so it's not like someone would be able to "OK Google" and unlock my phone, unless they sound exactly like me.
Click to expand...
Click to collapse
I've been having this issue as well, I've been meaning to start a thread about it. It seems that trusted voice isn't working correctly - this is meant to unlock the device when it responds to your voice. Well that's my understanding anyway.
Ah I see what is missing. You have to enabled "Trusted Voice" in the security settings for smart lock. Once I did this, it now unlocks with OK Google.
mgorman said:
Ah I see what is missing. You have to enabled "Trusted Voice" in the security settings for smart lock. Once I did this, it now unlocks with OK Google.
Click to expand...
Click to collapse
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
I too was confused by this. I was like.. well google now from screen off is totally useless if I have to unlock the phone after making my request. lol
All is good now. Thanks for the tip.
Tung_meister said:
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
Click to expand...
Click to collapse
Unfortunately, trusted voice matching is still hit and miss. It can depend on the environment when you talk to it, or even on you if you have a cold or something else that effects you. The best option is to try retraining the voice recognition in the ok google settings; I had to do that once when I had a particularly poor match up.
cbowens said:
Unfortunately, trusted voice matching is still hit and miss. It can depend on the environment when you talk to it, or even on you if you have a cold or something else that effects you. The best option is to try retraining the voice recognition in the ok google settings; I had to do that once when I had a particularly poor match up.
Click to expand...
Click to collapse
Surely though if the phone responds to my "OK Google" and wakes it up it has recognised it as me though so should work?
Tung_meister said:
Surely though if the phone responds to my "OK Google" and wakes it up it has recognised it as me though so should work?
Click to expand...
Click to collapse
While I don't have documentation to support my understanding, the best I've been able to put together is that "trusted voice" and "hotword detection" operate on different levels of accuracy. When you train it to recognize "Ok Google" in order to launch voice commands, it's attempting to better recognize you based on your enunciation and potential accent, where as the trusted voice is actually trying to match further, perhaps with things such as tone and pitch, in order to authenticate that its really you. For example, after training my phone, I can use "Ok google" to launch into voice commands when the phone is unlocked, or to bypass the unlock requirement when the phone is locked and execute a voice command. My wife, if she tries to immitate the way I say the phrase, can get my phone to launch into voice commands when the phone is unlocked, but if she tries while the phone is locked, it will require a PIN entry. It seems to be the same situation as what you're describing.
To me, this is exactly how it should work.
Tung_meister said:
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
Click to expand...
Click to collapse
You should retrain your voice model then. Be sure to speak naturally and at a distance that you'd be speaking at the phone normally. I always practice a few times before hand to make sure I don't sound robotic like I am talking to an automated operator. "Speak to a representative..... Speak to a representative.... SPEAK TO A REPRESENTATIVE!"
You can use this app to pass that policy: https://play.google.com/store/apps/details?id=com.luutinhit.doubletapscreenoff

"OK Google" Detection?

Hi,
Anyone having issues with getting their MXPE to detect "OK Google"? I've disabled Moto Voice because I prefer the stock Google Now experience, but my phone won't detect "OK Google" with anywhere near the same consistency with which it detected the Moto Voice launch phrase. The only time "OK Google" works is after I've manually activated the mic by pressing the mic icon in the Google search bar widget. After I run a search that way, the phone will detect "OK Google" for a little while, but then it stops detecting again. It's as if doing it manually launches a process that should always be running but is eventually killed by the kernel after a few minutes.
I am having the same problem. I can't figure it out for the life of me. I hope someone has some kind of solution
Frank_Murphy said:
Hi,
Anyone having issues with getting their MXPE to detect "OK Google"? I've disabled Moto Voice because I prefer the stock Google Now experience, but my phone won't detect "OK Google" with anywhere near the same consistency with which it detected the Moto Voice launch phrase. The only time "OK Google" works is after I've manually activated the mic by pressing the mic icon in the Google search bar widget. After I run a search that way, the phone will detect "OK Google" for a little while, but then it stops detecting again. It's as if doing it manually launches a process that should always be running but is eventually killed by the kernel after a few minutes.
Click to expand...
Click to collapse
Exact same issue here. Works for while after mic icon pressed then nothing.
Asus Zenfone 2
Lollipop 5.0
OK Google detection can't access mic after turning off Moto Voice in Accessibility
Having same issue OK Google detection can't access mic after turning off Moto Voice in Accessibility, won't let me turn on from any screen anymore in Settings->Languages input->Voice input->enhanced Google services gear settings->tap "Ok Google" detection when I try to turn on From any screen there's an error prompt "Can't use the microphone. Restart your device" which doesn't help.. ideas?

"Okay Google" Not Working Since Update?

Today I updated Google and noticed that saying "okay Google" from the home button screen (whatever it's called, the screen shown when you hold the home button for a bit) doesn't work anymore. It works from any other screen from the home screen to the lock screen.
I searched around but found no solution. Anyone have any ideas, or is experiencing the same thing? Could this be just an issue with the update and require another update to fix?
Edit: And now it's mysteriously working again, with absolutely nothing changed or done on my end.
Did you ever get this fixed? Ok google has been very buggy for me. I have a Google Home and wondered if it was messing it up.
So I noticed after the update I couldn't unlock the Axon 7 when it had its screen off and it was plugged in (the feature obviously doesn't work at all if the device isn't plugged in). The way I solved this was to go to the voice activity on Google and I paused (or deactivated) it. By doing this, you essentially reset all Google Voice settings (not the history). Then, just long press the home button which brings up the assistance which will ask you to give it permission to listen to you. It will then ask you to say "Ok Google" three times (as if it's the first time you're using it). When the trusted voice option is toggled (which is automatically will do it for you), the issue is fixed and the phone can be unlocked with you voice with its display off and while plugged in.

"ok google" detection when screen off...?

Hi
I searched everywhere but did not find solution how to unlock and start google assistant application using "ok google" command when screen is off? When I tried "Hi galaxy" on S Voice it works perfectly when screen is off and also not charging phone. I also disabled S Voice but "ok google" still do not work. I tried every tutorial in google. Does anyone know solution for this? my phone is original and not rooted. with official latest update.
Doesn't q work q with Samsung
U tried to do it but no way

Cannot disable "OK Google" permanently

I have an AT&T H910 patched to latest (I think Nov 2018). I noticed that the phone is listening all the time. If I speak "OK Google", when I unlock the screen, it is the Google Assistance waiting for me. Also, it will respond to someone else yelling "OK Google" from a distance. Often when I am using the phone. So I found out how to disable it, which is via the "Google App, Settings, Voice".
This works for a while. However, after a few days. The "OK Google" is once again turned back on. I went to the settings, it is off. I have to turn it back on and off again to have it disabled again. Does anyone know what is going on?
nookin said:
I have an AT&T H910 patched to latest (I think Nov 2018). I noticed that the phone is listening all the time. If I speak "OK Google", when I unlock the screen, it is the Google Assistance waiting for me. Also, it will respond to someone else yelling "OK Google" from a distance. Often when I am using the phone. So I found out how to disable it, which is via the "Google App, Settings, Voice".
This works for a while. However, after a few days. The "OK Google" is once again turned back on. I went to the settings, it is off. I have to turn it back on and off again to have it disabled again. Does anyone know what is going on?
Click to expand...
Click to collapse
just download the LG app disabler and then select ok Google and the Google search, helps for no voice commands, for me anyway but it will also break voice text ect. It's called package disabler for LG apps
Thanks for the tips. But if it breaks voice-to-text (the mic icon on keyboard), it is a non-starter...

Categories

Resources