Hi everyone,
I got a new Moto X (2014) recently (through the Motorola Cyber Monday deal). It's really a great phone.
I have one small question: The "OK Google" voice command doesn't seem to work from the lock screen (yes, the option is enabled in settings and yes, I've 'trained' it to recognize my voice). It works fine when the screen is unlocked. Initially I thought it was because Moto Voice was activated and I tried deactivating/turning off Moto Voice (both in accessibility as well as in the 'Moto' app settings). Still I can't get the phone to respond to the "OK Google" command when screen is locked. Am I missing something somewhere?
PS., I have tried using Moto Voice and it works too (I tried with one of the suggested phrase, "OK Moto X"). But for some reason, it doesn't recognize properly and if I say, for example, "Call Mom", it opens up a contact whose name has "Mohan" in it (Google opens my mom' contact details perfectly every time).
Thanks.
I can't test it right now, but if I remember correctly, the default command is "OK Google Now," not "OK Google."
Thanks,
It works with "OK Google" once the screen is unlocked and I'm on the home screen (or any of the home screens). and not when the screen is locked.
Edit: Funny (and weird). I tried with "OK Google Now" few times and then went back to repeating "OK Google" and it's now recognizing the command from the lock screen. As mentioned in the initial post, Moto Voice is inactivated (both under settings > accessibility and the Moto app).
Well, it's stopped working again this morning (after working for a while last night). The voice command "OK Google" doesn't do anything when the screen is locked (yes, the option "when locked" in 'voice settings' is turned on).
Though, the Moto Voice command that I set up works when the screen is locked. It's just the "OK Google" command which isn't working properly.
Any ideas on how to fix this? Thanks.
PS., I can use Moto Voice instead but as I said, for some reason it's not recognizing my voice / accent as well as Google does. Google voice gives an almost 100% perfect voice recognition.
I believe the "locked" is in reference to the "lock screen", not screen off "locked". Definitely diminishes its functionality, though...
Yeah, they mean the screen is on but locked, not that the phone is locked.
"Locked" meaning when the screen is locked or screen is turned off. There is an option in Google Now voice settings to enable the device respond to the "OK Google" command even when the screen is turned off or locked (precise wording - "Allow OK google to start a voice search or action from a secure lock screen").
Does that mean when the screen is 'locked' with either a PIN or pattern (and not just swipe)? I have tried "OK Google" both with just a 'swipe' setting or a 'PIN' lock setting. Doesn't work in either case (it did work for a short while though, last night, when I had the screen lock set to just 'swipe').
Edit: Thanks, @chrisrozon . So it doesn't work when the phone is 'locked'? Does the screen have to be turned on? Meaning, even if it's locked, does the lock screen have to show up before having it respond to the "OK Google" command?
When I tried (and when it worked intermittently) last night, I was able to see the device respond to "OK Google" from when the screen was locked and when the screen was turned off.
Alright. I checked again and it works when the screen is locked but the lock screen is on. Does it make sense? I mean, when the screen is locked and then I activate the display so that the lock screen shows up, then the "OK Google" command works.
This kind of defeats the purpose of 'works even when the screen is locked', isn't it? Or is this a known issue?
But I swear I could have the device respond to the "OK Google" command even when the screen/display was locked AND turned off. Or may be I was just trying too soon once the display turned off because I have the display to turn off after 15 sec of inactivity and the screen lock set to 15 sec after display turns off.
Well, I am just confused.
That's how it is supposed to work, the screen needs to be on.
fonduekid said:
But I swear I could have the device respond to the "OK Google" command even when the screen/display was locked AND turned off. Or may be I was just trying too soon once the display turned off because I have the display to turn off after 15 sec of inactivity and the screen lock set to 15 sec after display turns off.
Well, I am just confused.
Click to expand...
Click to collapse
You are not the only way cause I was able to get this to work yesterday with the screen turned off. I waited a good 5 mins with the screen off and said "OK Google" and it wake up the phone. it worked great for about 2 hours and then it just stop. Even since I cant get it to work again. I went ahead and did a factory reset last night and this moring trying to get it to work and and its still not working.
Were you plugged in? Because it always works when you are plugged in.
Well, looks like that's how it works - screen needs to be turned on. For sure I am not doing a factory reset for this!
bongostl said:
Were you plugged in? Because it always works when you are plugged in.
Click to expand...
Click to collapse
I haven't checked when it's plugged in. I'll do that later this evening and get back. Thanks.
dazz87 said:
You are not the only way cause I was able to get this to work yesterday with the screen turned off. I waited a good 5 mins with the screen off and said "OK Google" and it wake up the phone. it worked great for about 2 hours and then it just stop. Even since I cant get it to work again. I went ahead and did a factory reset last night and this moring trying to get it to work and and its still not working.
Click to expand...
Click to collapse
I see the ability to use the launch phrase when the screen is off, locked (use swipe) when connected to a trusted bluetooth device. Otherwise, the screen need to be on, but can still be locked. When no trusted bluetooth is connected, I'll wave, wake the screen, then say the launch phrase.
bongostl said:
Were you plugged in? Because it always works when you are plugged in.
Click to expand...
Click to collapse
Amazing. Yes, it works when plugged in. It also works when connected to a trusted bluetooth device as sailindawg mentioned.
Otherwise I have to wave to turn the screen on (still locked) and then use the "OK Google" command.
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
stevetsimmons.com said:
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Tried this. Doesn't work for me.
stevetsimmons.com said:
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
I think you're talking about the MOTO Implementation, NOT the pure Android "OK Google" that we are talking about in this thread.
Hi there,
it's a few days that something is happening on my g watch R
even if "tilt to wake up" is disabled it wakes up continuosly showing "Ok Google".
I'd like to have the watch display turned off and i'd like to turn it on only manually.
got enabled "Turn off display" - got disabled "gestures".
any way to fix it?
am i missing something or doing something wrong?
I'm having the same issue. No idea how to fix it.
Any solution ever come up for this?
Did you reset it recently? If so, say "Ok Google" a few times to activate the voice recognition and have it stop 'advertising' the voice prompt to you. (Not sure if that 'voice prompt ad' wakes up the display, but it's worth a try.)
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
I noticed the same issue a few times. However, even if it works, the screen won't fully unlock when you complete a voice command, which makes it basically useless.
Hey everyone. I previously used hotword detection all the time. On my old LG G2, I used the Nexus 5 mod to enable hotword detection from any screen. It only worked when the screen was on, which eliminates false-positives.
However, with the Nexus 6, I can only enable hotword detection on ALL THE TIME, even when the screen is off. It's extremely inconvenient due to the sheer number of false-positives I've encountered. I'll be listening to a podcast or music with the screen off. Even if the audio doesn't even resemble "OK Google," my audio will pause and I'll hear that trademark ping as my screen turns on, awaiting a command. How can I disable hotword detection when the screen is off?
It's trivial to turn the screen on before using it. It's annoying to have to dismiss the Google Now and then turn my screen off. Even if I could dismiss Google Now by saying "cancel" or "never mind", it still doesn't turn the screen off. I have to go and turn it off myself. Right now, my only option is to allow hotword detection from my homescreen but that's suboptimal. If I'm in an app and want to use it, I have to first tap-and-hold on the home button to bring up Google Now, then I say "OK Google."
I've been having this problem since 6.0. The thing is, I can say OK Google and sometimes hear the chirp but the screen doesn't kick on, but it's useless in most cases because I need the screen on to see directions or a phone number for a place I'm looking up. It's frustrating.
Hung0702 said:
Hey everyone. I previously used hotword detection all the time. On my old LG G2, I used the Nexus 5 mod to enable hotword detection from any screen. It only worked when the screen was on, which eliminates false-positives.
However, with the Nexus 6, I can only enable hotword detection on ALL THE TIME, even when the screen is off. It's extremely inconvenient due to the sheer number of false-positives I've encountered. I'll be listening to a podcast or music with the screen off. Even if the audio doesn't even resemble "OK Google," my audio will pause and I'll hear that trademark ping as my screen turns on, awaiting a command. How can I disable hotword detection when the screen is off?
It's trivial to turn the screen on before using it. It's annoying to have to dismiss the Google Now and then turn my screen off. Even if I could dismiss Google Now by saying "cancel" or "never mind", it still doesn't turn the screen off. I have to go and turn it off myself. Right now, my only option is to allow hotword detection from my homescreen but that's suboptimal. If I'm in an app and want to use it, I have to first tap-and-hold on the home button to bring up Google Now, then I say "OK Google."
Click to expand...
Click to collapse
Those false positives were positively driving me batty as well. I managed to cut them down by going into a closet and performing three REALLY good recordings in Google Now hotword voice training.
There is something else to try: Benzo ROM is a custom Marshmallow ROM that has hotword detection from any screen (NOT always on). I can't link it in XDA, but if you were to Google "Benzo ROM" you'd find the Google+ community that has download links for the ROM. Good luck!
Hi all.
Google Assistant responds to "Ok Google" every other time...
1 - 3 days responds to the command stably, then no reaction to the phrase "Okey Google". What with the screen off, what with the on ...
Should you turn off / on the device, and how long does this function work again!
What in the OS can jam the operation of this application through some time?
The version of android and this application is up-to-date.