Trusted Voice: Say 'OK Google' to unlock phone - not working with AOD enabled

[DLCPhototography]

I have been playing around with this, as I would like to send texts hands-free using my phone, even if it is locked. For example, if I'm in the car, and don't have Android Auto running.

I've found that if "Always On Display" is enabled, when I say 'OK Google' there is a little vibration, showing that the phone has recognized my voice, but it doesn't unlock the phone. If I manually unlock it, the Google screen is shown, indicating that my saying 'OK Google' did in fact start the process.

If I turn off "Always On Display" then my saying 'OK Google' will in fact unlock the phone, and bring up the Google App. I do have to say 'OK Google' again, to have it ready to receive my request, but it does work as I would want it to in that context.

This is a Verizon phone, in case this behavior differs from one provider to another.

Can anyone confirm or disconfirm this behavior? The way it seems is that I have to choice to either have the Always On Display enabled, and not be able to wake the phone with OK Google, or turn AOD off, and be able to use OK Google to unlock the phone.

Loving this phone, after 3 days of ownership, and trying to learn to get everything I can out of it!

 

[Old g]

not sure why your not using Bixby trust she come a long way

 

[TheLegoJoker]

I made a similar post earlier this evening and I’m finding the same to be true. With AOD it doesn’t work at all, even in a trusted location, but without it I can make it work. Sometimes on one try, sometimes two, other times not at all. Very inconsistent. Also on Verizon. Fantastic device aside from this and a couple other little nits.

 

[TheLegoJoker]

not sure why your not using Bixby trust she come a long way

Bixby is very inconsistent as well, and you have to take the long way around to get Bixby to perform. For instance, to get directions on google assistant or Siri, you say the proper voice command and ask for directions and either will get you what you need. Bixby needs you to tell it to open google maps and get directions to wherever, and then (for me) about half the time it says it can’t do that right now.
I want to use Bixby, but it’s extremely buggy at the moment.

 

[DLCPhototography]

I've played around a little with Bixby, and it's ok, but to specifically get it to send a text, hands-free, simulating what I can do with Android Auto, it falls short.
@TheLegoJoker - yeah, I just saw your other post after I had posted mine - sorry!

In reading about this, some reported on other phones that having it plugged into a charger made a difference, but I just tested this, and it didn't seem to make a difference. AOD seems to prevent OK Google from unlocking the phone.

I also made sure I disabled "Hi Bixby" to avoid any conflict there, but the problem remains.

 

[Strawdawg2013]

mine works with no problem. I had the trouble periodically with my 7E. Usually rebooting the phone would work.

 

[DLCPhototography]

mine works with no problem. I had the trouble periodically with my 7E. Usually rebooting the phone would work.

Verizon or other?

You're saying that even with AOD enabled, you can consistently unlock your phone when it is off, with AOD on, by saying OK Google?

What security settings are you using: fingerprint, iris, pin, or do you not have any turned on?

Curious...

I just turned my phone back on for the day (I turn it completely off at night), and found that saying OK Google the first time caused the little vibration, but then I said it again, and it did unlock the phone. I thought I had tried that yesterday, but perhaps I was mistaken.

Do you have to repeat it like this, or will one command unlock your phone?

 

[Strawdawg2013]

Verizon or other?

You're saying that even with AOD enabled, you can consistently unlock your phone when it is off, with AOD on, by saying OK Google?

What security settings are you using: fingerprint, iris, pin, or do you not have any turned on?

Curious...

I just turned my phone back on for the day (I turn it completely off at night), and found that saying OK Google the first time caused the little vibration, but then I said it again, and it did unlock the phone. I thought I had tried that yesterday, but perhaps I was mistaken.

Do you have to repeat it like this, or will one command unlock your phone?

ATT, finger print, face recog, pin.

I played with it a bit last night trying to make it fail. I found that if I activated it but said nothing other than Ok Google and let it time out, then I could not reactivate it unless I used the phone for something else or used a long press to bring it back to life. After, it came back to life, then it would repeatedly work as long as I said OK Google and asked a question, etc.

 

[sll1313]

I am also with Verizon ad I have AOD and Bixby enabled. I noticed when I haven’t used my phone for awhile it won’t unlock using trusted voice, “OK Google”. I hear it acknowledge it, but it won’t unlock it. However, I noticed that you said it won’t work in a trusted location. You need to check something because mine definitely works like a charm if I’m in a trusted location or with a trusted device. The ONLY issue I’m having is if I haven’t used the phone for awhile, like overnight, the initial time I say “OK Google” it won’t work. Once I use my fingerprint once. It now works with my trusted anything even with Bixby on as well as AOD enabled. I am working on trying to get it to work that initial time. I tried retraining my voice to see if that works. I will check it when I get up. It just dawned on me of another thought. I use Nova Launcher. I am pretty certain that I had a friend who was over my house who also has the Note, but doesn’t use Nova. She’s also with Verizon and has Bixby and AOD enabled. The only difference is not having Nova and I’m pretty certain I heard her sa6 “OK Google” and it worked. Part of the reason for the recollection is she said “unlock phone” after she gave it the “OK Google” command because I believe I questioned her. I had no idea mine wasn’t working or I would’ve paid closer attention. If I haven’t figured an answer by the next time I see her I will ask her to do a little experiment because now I’m wondering if it has anything to do with Nova. BTW, I do have the setting in Nova checked to make sure it’s working. I will keep everyone informed if I figure something out. I would greatly appreciate if everyone would let me know if they hear anything. Thanks in advance.

 

[lostart80]

Hello,

I have a Samsung Note 8 which I have been having issues with. My problem was that the "OK Google" voice command would not unlock the phone. I had tried many fixes for this issue. None of them helped to remedy this problem though. I found that after performing many configuration changes including but not limited to adding app permissions, delegating Device Administrators, etc, what ended up allowing the "OK Google" command to function and unlock the phone was turning off the "Edge Lighting" feature. Settings>Display>Edge Screen>Edge Lighting>Toggle Off.

I hope this helps someone!

 

[Baby_Doc]

Hello,

I have a Samsung Note 8 which I have been having issues with. My problem was that the "OK Google" voice command would not unlock the phone. I had tried many fixes for this issue. None of them helped to remedy this problem though. I found that after performing many configuration changes including but not limited to adding app permissions, delegating Device Administrators, etc, what ended up allowing the "OK Google" command to function and unlock the phone was turning off the "Edge Lighting" feature. Settings>Display>Edge Screen>Edge Lighting>Toggle Off.

I hope this helps someone!

I have Verizon and havr turned edge lighting off as well as trusted location off. My AOD is on and I am using Touch Wiz. It will take 2 tries for ok Google to work if my phone hasn't been used for a while. After that, if I keep locking my phone and reissuing OK Google, it unlocks the first time. I haven't seen the Edge lighting toggle influencing the outcome, as much as removing the trusted location.

I believe it a problem with Nugat 7.1. There is a Pixel 2 user with Nugat 7.1, who is complaining about the same problem on the Google forum. On the other hand, my wife who is running Google 7.0 on her LGg6, isn't having this issue at all. For what is worth, she is also Verizon and has trusted locations turned on.

 

[Curtmcgirt]

Att s9 plus with fingerprint and face detection unlocking. Edge lighting off, always on screen off, no trusted places or devices. "OK Google" wakes the screen up to the "use biometrics or enter pin" screen 100% of the time.

 

[Lexn]

Maybe it's Google play services which don't have enough permissions or are put to sleep via battery manager.

I had similar issues all due to Smart Lock from Google. When I went to settings of Smart Lock,I saw blank page. It's a bug and fix it you need to disable smart Lock in "trusted agents" under security. Then reboot and then enable smart Lock in trusted agents. When you open Smart Lock settings you will find Voice match.

Evert time phone does not unlock with the voice, check Smart Lock settings.