Google Voice commands sometimes don't turn the phone on, is anyone else experiencing this?

[West Coast Wolverine]

Google Voice commands sometimes don't turn the phone on

This issue is utterly maddening for a phone in 2016 . Many times when my phone is off, I will ask Google a question and it won't unlock the phone. Sometimes I'll ask again and it will work and other times I end up having to unlock it with either the fingerprint sensor or the passcode. This is annoying at any time, but really bad when I'm driving. Is anyone else running into this? Any suggestions?

 

[eaccentsac]

Re: Google Voice commands sometimes don't turn the phone on

This issue is utterly maddening for a phone in 2016 . Many times when my phone is off, I will ask Google a question and it won't unlock the phone. Sometimes I'll ask again and it will work and other times I end up having to unlock it with either the fingerprint sensor or the passcode. This is annoying at any time, but really bad when I'm driving. Is anyone else running into this? Any suggestions?

I think I might be seeing this sporadically in the car. I will have to pay closer attention.

One thing to try is to wipe the OK Google setup (wipe app data) and re-record and re-enable the feature that allows us to unlock by voice command. To me, I think things get messed up a bit whenever there is a Google App update....

 

[mclaser]

Re: Google Voice commands sometimes don't turn the phone on

I've experienced similar behavior for years with Android. I have Wi-Fi at my house and a shop that's 300' away. When I go out my driveway my BT becomes intermittent. Until I get out of Wi-Fi range and it gives up (I think). I think there's a long standing bug in that Wi-Fi switching which causes BT to stutter. It seems a lot better on the 5x than it ea on my Moto X.

 

[nycdaddio1]

Re: Google Voice commands sometimes don't turn the phone on

Same... Works about 50%of the time. My 2013 moto x worked 100%of the time. Frustrating

Posted via the Android Central App