[Kirk Burkhead]

My Ok Google command does not work when screen is locked like it did before Oreo update.

Anyone else have this issue?

[can3gxw]

I had to delete and retrain mine. Also try toggling the ok Google lock screen setting

[maxburn]

I had to delete and retrain mine. Also try toggling the ok Google lock screen setting

I think I had to do this too.

[matty032]

My OK Google has been hit and miss since day one. I have retrained voice several dozen times. It always seems to fail when I am showing off the feature to someone.

[Kirk Burkhead]

I had to delete and retrain mine. Also try toggling the ok Google lock screen setting

That's what I had to do. Working well now.

[ptkelly]

I'm using the Pixel. When I upgraded to the final Android 8.0 I did a factory restore. I don't really know if there would have been a problem but I often use OK Google to give voice instructions for a reminder and it works fine on a lock screen.

[ASFraley]

I had the same experience as can3gxw. After update to Oreo 8.0, "OK Google" was no longer recognized when phone was locked or unlocked. What can3gxw suggested worked for me.

I opened the Google App and went to Settings in main menu. Then "'OK Google' detection". Then I disabled all 3 OK Google settings ("Say 'OK Google' any time", "Trusted voice", and "While driving"). Then I re-enabled all 3 and it asked me to retrain by saying "OK Google" 3 times (which is weird because I never explicitly deleted the training data). Then "OK Google" seemed to work fine again after Oreo upgrade.

For fun, I disabled and re-enabled all 3 another time and it did NOT make me retrain "OK Google" phrase again. So I'm guessing somehow the Oreo upgrade corrupted the "OK Google" training data.

[dcseain]

Okay Google does not work.on my Pixel since Oreo. have no settings for Okay Google, Voice, nor Google Assistant in the settings on my Pixel. Should I reset and try again?

[mmcclure0453]

I had the same experience as can3gxw. After update to Oreo 8.0, "OK Google" was no longer recognized when phone was locked or unlocked. What can3gxw suggested worked for me.

I opened the Google App and went to Settings in main menu. Then "'OK Google' detection". Then I disabled all 3 OK Google settings ("Say 'OK Google' any time", "Trusted voice", and "While driving"). Then I re-enabled all 3 and it asked me to retrain by saying "OK Google" 3 times (which is weird because I never explicitly deleted the training data). Then "OK Google" seemed to work fine again after Oreo upgrade.

For fun, I disabled and re-enabled all 3 another time and it did NOT make me retrain "OK Google" phrase again. So I'm guessing somehow the Oreo upgrade corrupted the "OK Google" training data.

Just did the same thing. Fixed mine. Thanks.

[ptkelly]

I don't understand the terms but my Pixel with Android 8.0 responds to nothing when it's powered off for the night. It just sits there. When I power up in the morning and the screen goes black either because I tap the power buttons or it's screen-on time expires, it responds to Ok, Google. I say, "OK, Google," and the black screen turns on, shows the home page, and goes to the OK Google screen in about a half-second.

It seems to work fine. I don't know if it matters but I don't have Google Now active.

[hub1]

I don't understand the terms but my Pixel with Android 8.0 responds to nothing when it's powered off for the night. It just sits there. When I power up in the morning and the screen goes black either because I tap the power buttons or it's screen-on time expires, it responds to Ok, Google. I say, "OK, Google," and the black screen turns on, shows the home page, and goes to the OK Google screen in about a half-second.

It seems to work fine. I don't know if it matters but I don't have Google Now active.

Do you mean that you turn the phone off or do you mean just the screen is off. The phone won't respond if it's not powered on.

[ptkelly]

Do you mean that you turn the phone off or do you mean just the screen is off. The phone won't respond if it's not powered on.

If you're asking me, I turn my phone off at night when I go to bed. I spent 40 years on call and I'm not doing that any longer. When I power up I get my number pad to enter my PIN. OK, Google does not work before I enter the pin. Neither does my fingerprint scanner. But, once I've entered my PIN, I can use OK, Google when the screen is turned off by the power switch or when it has timed out and gone dark and it works perfectly.

[mmcclure0453]

If you're asking me, I turn my phone off at night when I go to bed. I spent 40 years on call and I'm not doing that any longer. When I power up I get my number pad to enter my PIN. OK, Google does not work before I enter the pin. Neither does my fingerprint scanner. But, once I've entered my PIN, I can use OK, Google when the screen is turned off by the power switch or when it has timed out and gone dark and it works perfectly.

Mine does exactly the same thing. In my opinion, you have a perfectly functional Pixel. Unless I missed something else that yours is doing. Sounds perfect to me.

[sjjpo2002]

I had the same experience as can3gxw. After update to Oreo 8.0, "OK Google" was no longer recognized when phone was locked or unlocked. What can3gxw suggested worked for me.

I opened the Google App and went to Settings in main menu. Then "'OK Google' detection". Then I disabled all 3 OK Google settings ("Say 'OK Google' any time", "Trusted voice", and "While driving"). Then I re-enabled all 3 and it asked me to retrain by saying "OK Google" 3 times (which is weird because I never explicitly deleted the training data). Then "OK Google" seemed to work fine again after Oreo upgrade.

For fun, I disabled and re-enabled all 3 another time and it did NOT make me retrain "OK Google" phrase again. So I'm guessing somehow the Oreo upgrade corrupted the "OK Google" training data.

I did disable the OK Google detection and it's still picking up OK Google but after that I doesn't reply. I updated to Oreo running on my Pixel

[Bill Boxall]

I did disable the OK Google detection and it's still picking up OK Google but after that I doesn't reply. I updated to Oreo running on my Pixel

I think this is happening to me. I used to have the Nexus 6P. With the screen locked, I could say "OK Google", ask it something, and it would respond. I just got the Pixel 2. Yes, I've trained the voice and everything. With the screen locked, I say "OK Google" and I get the beep that it heard and is waiting for my question. I ask the question, and it just ignores me. No response, nothing. So it beeps, waiting for input, then ignores the input. I unlock the device, and it answers fine.

The only other setting I saw was to allow OK Google to unlock my device. If I set that, it works. It will respond. But that is inherently less secure, if it will unlock when I say OK Google, and I don't want that behaviour. I didn't use it on the Nexus 6P (using Oreo), I shouldn't need to use it here on the Pixel 2.

Is there another setting squirreled away somewhere that I'm just not finding? I've looked everywhere for an option. Can't find one.

[bond007x]

THANK YOU so much for this answer - updated to Oreo on day#3 after release (rooted Nexus 6p!) and have missed "OK Google" since that time!!! Of course the setting to turn it back on is buried / not in the default Android settings After finding this solution, I am back up and running again in 10 seconds. This saves physically unlocking the phone while driving!!! Much safer!