I have set up "OK Google" to recognize my voice from screen off.
This works great, however, when I use it, it requires me to enter my PIN/fingerprint to show the results.
Is there any way to turn this off? I find it kind of silly that I have to do that every time.
And as far as security reasons, the phone won't respond to anyone else, so it's not like someone would be able to "OK Google" and unlock my phone, unless they sound exactly like me.
mgorman said:
I have set up "OK Google" to recognize my voice from screen off.
This works great, however, when I use it, it requires me to enter my PIN/fingerprint to show the results.
Is there any way to turn this off? I find it kind of silly that I have to do that every time.
And as far as security reasons, the phone won't respond to anyone else, so it's not like someone would be able to "OK Google" and unlock my phone, unless they sound exactly like me.
Click to expand...
Click to collapse
I've been having this issue as well, I've been meaning to start a thread about it. It seems that trusted voice isn't working correctly - this is meant to unlock the device when it responds to your voice. Well that's my understanding anyway.
Ah I see what is missing. You have to enabled "Trusted Voice" in the security settings for smart lock. Once I did this, it now unlocks with OK Google.
mgorman said:
Ah I see what is missing. You have to enabled "Trusted Voice" in the security settings for smart lock. Once I did this, it now unlocks with OK Google.
Click to expand...
Click to collapse
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
I too was confused by this. I was like.. well google now from screen off is totally useless if I have to unlock the phone after making my request. lol
All is good now. Thanks for the tip.
Tung_meister said:
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
Click to expand...
Click to collapse
Unfortunately, trusted voice matching is still hit and miss. It can depend on the environment when you talk to it, or even on you if you have a cold or something else that effects you. The best option is to try retraining the voice recognition in the ok google settings; I had to do that once when I had a particularly poor match up.
cbowens said:
Unfortunately, trusted voice matching is still hit and miss. It can depend on the environment when you talk to it, or even on you if you have a cold or something else that effects you. The best option is to try retraining the voice recognition in the ok google settings; I had to do that once when I had a particularly poor match up.
Click to expand...
Click to collapse
Surely though if the phone responds to my "OK Google" and wakes it up it has recognised it as me though so should work?
Tung_meister said:
Surely though if the phone responds to my "OK Google" and wakes it up it has recognised it as me though so should work?
Click to expand...
Click to collapse
While I don't have documentation to support my understanding, the best I've been able to put together is that "trusted voice" and "hotword detection" operate on different levels of accuracy. When you train it to recognize "Ok Google" in order to launch voice commands, it's attempting to better recognize you based on your enunciation and potential accent, where as the trusted voice is actually trying to match further, perhaps with things such as tone and pitch, in order to authenticate that its really you. For example, after training my phone, I can use "Ok google" to launch into voice commands when the phone is unlocked, or to bypass the unlock requirement when the phone is locked and execute a voice command. My wife, if she tries to immitate the way I say the phrase, can get my phone to launch into voice commands when the phone is unlocked, but if she tries while the phone is locked, it will require a PIN entry. It seems to be the same situation as what you're describing.
To me, this is exactly how it should work.
Tung_meister said:
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
Click to expand...
Click to collapse
You should retrain your voice model then. Be sure to speak naturally and at a distance that you'd be speaking at the phone normally. I always practice a few times before hand to make sure I don't sound robotic like I am talking to an automated operator. "Speak to a representative..... Speak to a representative.... SPEAK TO A REPRESENTATIVE!"
You can use this app to pass that policy: https://play.google.com/store/apps/details?id=com.luutinhit.doubletapscreenoff
Related
Hey guys, just got my S4. Excited about the features and the new S Voice. It tells me it can wake up the phone by voice command which is like totally awesome. You know like in Star Trek they always call the computer to do some stuff for them haha. So I wanted to do the same but it seems you first have to click the home button and then unlock by voice. So it's more like Unlock by voice rather than Wake-up by voice.
Is it possible to make the phone actually waking up by voice without having to touch the home button first?
elpin said:
Hey guys, just got my S4. Excited about the features and the new S Voice. It tells me it can wake up the phone by voice command which is like totally awesome. You know like in Star Trek they always call the computer to do some stuff for them haha. So I wanted to do the same but it seems you first have to click the home button and then unlock by voice. So it's more like Unlock by voice rather than Wake-up by voice.
Is it possible to make the phone actually waking up by voice without having to touch the home button first?
Click to expand...
Click to collapse
Well as of now its not available we myte get in the future but would be battery killer as for that we need to have som modification in kernal which can wake device from sleep with voice if i m not wrong
I see, thanks.
I just recently bought my Note 4, and have to say it is the single best phone I have ever owned lol. I am still trying to learn about it. I mean it is Rooted and I do not even know what that means LOL
Anyways the reason I joined is because I need help. This has been happen off and on, my phone keeps beeping every time I shake my phone. I did not know you can shake the phone and even have it do anything (I need to really learn more about my phone haha). When I am out walking the beep drives me bonkers! It will even bleep during the start of a phone call. I recorded the sound and really hope that I can upload it.
Thank you in advance for any help you may be able to provide. I am sure it is just something simple, but I am not seeing it
Hi there,
A simple Google search brings me here:
http://forums.androidcentral.com/samsung-galaxy-s4/282858-2-tone-beep-sound-constantly-playing.html
Did you try turning off NFC to see if this causes the problem?
(This doesn't seem to happen on my handset when turned on btw.)
Else turn off Orientation Lock maybe?
(Seeing the fact you say it occurs more when you move or shake your handset.)
Question: Does the sound also play if the profile is on silent mode?
Kind regards, Stefan.
Thank you for taking the time to respond to my question
I came across that same thread when I was searching for answers before coming here. It did not find it relevant because my NFC is not on.
I was able to kind of see a screen before silly me accidentally hit the back button. I did not see the name of the app, but it was a white background with a picture of an orange mic and switch on the bottom in orange that says sonar. There was probably other things on the page but that is all I saw for the split second I saw the screen. Then it is after it started doing the beeping. When I look at my apps the only ones I have that have anything to do with my mic is S Voice, Voice Recorder and Voice Search, and not one of them are what I saw. The beeping I am hearing same kind of sound I would hear if I tap Voice Search, but that is not what is causing the beeps.
Hi again,
It does sound like the Voice Search beep, but it seems different.
You could try to disable double tap home for Svoice but I doubt if it would work:
Double tap the home button to*open S Voice.
Press the menu button in the top right of the app.
Tap “Settings.”Uncheck “Open via the home key.”
Did you check the screen orientation lock yet?
I assume you have rebooted your handset right?
Kind regards, Stefan.
We are becoming fast friends! LOL
Yes it does sound the voice search, and it does go away after I reboot my phone, I would just really like to know what this is though so I can try to prevent it from happening or turn it off when it does happen.
Again, thank you so much for caring enough to try and help me.
An other thing that ia worth mentioning is under:
Accessibility these is: direct acces.
When enabled it enables certain user set options by 3x pressing the home button.
But I could not find any option that enabled this beeping.
It could very well be a third party app causing it.
Anyways good luck, maybe anyone else has some input.
Kind regards, Stefan.
You might try safe mode to see if an app is causing it. It will temporarily disable all non-system apps. See if that fixes it. If so, it is an app you installed. m.androidcentral (I can't post links yet so change this to a '.') com/galaxy-note-4-safe-mode
Sent from my SM-N910T using XDA Free mobile app
Hi everyone,
I want to use Tasker to wake up the phone by saying a some pharse, but not "Okay Google". Since Tasker can't turn on the display on the Nexus 4, I'm using the Secure Settings plugin. I know for a fact this plugin works because I managed to wake up the device by shaking it, just to try. Issuing the voice command is something else entirely.
For this I downloaded Autovoice, and set it to continuous listening. For some reason, it doesn't respond (even when the screen is on), unless I use Google now. By watching one of Armando Ferreira tutorials on Tasker (https://www.youtube.com/watch?v=J259WzkO3-Y) I learned that by setting continuous on in Autovoice, you can issue voice commands without saying "Ok Google" but it doesn't work for me.
Any ideas why and what I can do?
Thanks.
Today I updated Google and noticed that saying "okay Google" from the home button screen (whatever it's called, the screen shown when you hold the home button for a bit) doesn't work anymore. It works from any other screen from the home screen to the lock screen.
I searched around but found no solution. Anyone have any ideas, or is experiencing the same thing? Could this be just an issue with the update and require another update to fix?
Edit: And now it's mysteriously working again, with absolutely nothing changed or done on my end.
Did you ever get this fixed? Ok google has been very buggy for me. I have a Google Home and wondered if it was messing it up.
So I noticed after the update I couldn't unlock the Axon 7 when it had its screen off and it was plugged in (the feature obviously doesn't work at all if the device isn't plugged in). The way I solved this was to go to the voice activity on Google and I paused (or deactivated) it. By doing this, you essentially reset all Google Voice settings (not the history). Then, just long press the home button which brings up the assistance which will ask you to give it permission to listen to you. It will then ask you to say "Ok Google" three times (as if it's the first time you're using it). When the trusted voice option is toggled (which is automatically will do it for you), the issue is fixed and the phone can be unlocked with you voice with its display off and while plugged in.
I have an AT&T H910 patched to latest (I think Nov 2018). I noticed that the phone is listening all the time. If I speak "OK Google", when I unlock the screen, it is the Google Assistance waiting for me. Also, it will respond to someone else yelling "OK Google" from a distance. Often when I am using the phone. So I found out how to disable it, which is via the "Google App, Settings, Voice".
This works for a while. However, after a few days. The "OK Google" is once again turned back on. I went to the settings, it is off. I have to turn it back on and off again to have it disabled again. Does anyone know what is going on?
nookin said:
I have an AT&T H910 patched to latest (I think Nov 2018). I noticed that the phone is listening all the time. If I speak "OK Google", when I unlock the screen, it is the Google Assistance waiting for me. Also, it will respond to someone else yelling "OK Google" from a distance. Often when I am using the phone. So I found out how to disable it, which is via the "Google App, Settings, Voice".
This works for a while. However, after a few days. The "OK Google" is once again turned back on. I went to the settings, it is off. I have to turn it back on and off again to have it disabled again. Does anyone know what is going on?
Click to expand...
Click to collapse
just download the LG app disabler and then select ok Google and the Google search, helps for no voice commands, for me anyway but it will also break voice text ect. It's called package disabler for LG apps
Thanks for the tips. But if it breaks voice-to-text (the mic icon on keyboard), it is a non-starter...