Thursday, 22 October 2015

[Q] Google's "Okay, Google" detection not working consistently.



I'm having an interesting problem, and I've had this same issue with the n920C running OHx firmware, the N920I running OHx and OIx variants, and the N920I running a stock tmobile firmware.

I've enabled google's "okay google" detection, trained the voice, turned on "from the google app", turned on "from any screen" and turned on "trusted voice." At that point, I can be on any screen in the phone and if I speak "okay, google", it wakes up as expected.

As soon as my screen powers down, the voice detection stops working even when the phone is charging (both wireless and plugged in charging.) If I power back on the screen, "okay google" still won't work. If I unlock the phone manually (fingerprint), it still won't work. In fact, the google voice detection won't work again until I manually start the google app again (either via the app icon or press/hold the home button.)

The strange thing about this is that the google app is still running while the voice detection isn't working (as seen with various application managers and even the "smart manager" RAM tool.

It's as if something is turning off google's voice detect as soon as the screen turns off and not turning it back on.

I've had this same experience regardless of which version of the google app is installed, with all samsung apps running and enabled, immediately after a factory reset and only basic reconfiguration (so wiping data/cache isn't going to help), and also after disabling all "s voice" related samsung apps.

Can others please report if "okay google" detection works for them (or not) under the circumstances I've described? Even better, if someone had this problem and found a work-around, please let me know.

Thanks
Gary



No comments:

Post a Comment