OK Google woes

[petvas72]

I love my Nexus 6P but one thing that happens a lot and gets on my nerves.

Many times I want to use my 6P as a timer. I am in the kitchen and I say OK Google, and then I tell it to set the timer. This worked 100% of the time with my iPhone 6S (now sold) and Siri.
My 6P will sometimes not respond at all. Other times it will wake up and say that this is not allowed while my device is locked! The thing is, my device should not be locked. I am using Smart Lock and have enabled my location and my voice as trusted..Some times it does work..
The only way I have found that works 80% of the time is by unlocking the phone using fingerprints, and then saying OK Google to set the timer.
Does anyone have a solution or suggestion? Thanks.

 

[Cant Miss]

Does anyone have a solution or suggestion?

Send feedback to Google. Seems pretty silly the way it works now.

 

[Droid Nigel]

I believe for smart lock to work you have to;

Be connected to the internet
Have your location settings on
Unlock manually first-after that it will remain unlock


I believe you may have to check you google now settings to make sure trusted voice is one of the ways of unlocking

 

[petvas72]

Everything is configured correctly..The whole thing is just extremely buggy.

 

[Droid Nigel]

I've been having issues with it lately that I hadn't had before. Maybe it was a bad update. Is it extremely slow for you as well?

 

[Cant Miss]

The difference I am seeing with MM is that OK Google is not waking the screen, both on my 6P and 7. Now the 7 has no locking enabled, and while it does do what I ask it, the screen does not turn on if it's off. Under L, the screen would wake on OK Google.

My 6P works the same way, IF it is unlocked. If it's locked, it will answer questions, but it will not set a timer, launch an app, create an event, send text, etc., complaining that it is locked.

My "feeling" is that, whatever smartlocks you have set up, they don't initiate until the screen wakes, and since OK Google in MM no longer wakes the screen, the device appears as though it is locked, and commands that require an unlocked device fail.