ok so... with the phone on the table and the screen is off (standby). if i say "ok google" and do a search for anything. once im done i can hit the home button and it takes me right into home screen without inputting my finger print or password. So that means anyone can now say "ok google" and bypass any of the securities. come you guys confirm this as this is a major problem for me. I have the verizon edition pixel.
Audigy187 said:
ok so... with the phone on the table and the screen is off (standby). if i say "ok google" and do a search for anything. once im done i can hit the home button and it takes me right into home screen without inputting my finger print or password. So that means anyone can now say "ok google" and bypass any of the securities. come you guys confirm this as this is a major problem for me. I have the verizon edition pixel.
Click to expand...
Click to collapse
Settings>>Google>>Search & Now>>Voice>>OK Google Detection - In here you can set options to secure this feature to your liking. Notice the 'Trusted Voice' Option which detects its YOU before unlocking. There of course is room for error where someone sounding similar to you in might be able to get it. That's why these features are there to disable if it matters to you.
I personally don't care much..
Cheers!
(There might be a faster way to get to those settings. That's just how I always remember to do it)
And it also makes you acknowledge everything you just said before enabling trusted voice.... you must've missed that part.
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
How long has your friend been using their V20? I know they become much more accurate the longer you use it, similar to the fingerprint scanner. Google has you train it to understand you with 3 sets of 'ok google' but that doesn't mean it's done learning. Give it some more time maybe? Just thinking...
hes been using it for 4 about a week now. the v20 is a nice. i feel it is noticeably faster than the note 7 i had. only issues are the screen it average. Its sharp but color is average. the hole phone vibrates from the speakers which is a downside for me.
Ill give the pixel some time to learn my voice and report back. hopefully i cant fool it lol
Try this
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
Press power button while Pixel is in sleep mode. That will bring up the lock screen. At the bottom of the screen you will notice a fingerprint icon. Tap that and you will get the message "Device will remain locked until you manually unlock."
No amount of saying "OK, Google" will allow access now until you either use the fingerprint scanner or enter your pass code.
Yea I pointed this out here: http://forum.xda-developers.com/showpost.php?p=69303648&postcount=12
It is a big issue. It should allow limited assistant functionality, but not entire phone.
as always, if you are so concerned about security on your phone, dont keep anything on it that you are afraid of someone else accessing..
very simple solution
wase4711 said:
as always, if you are so concerned about security on your phone, dont keep anything on it that you are afraid of someone else accessing..
very simple solution
Click to expand...
Click to collapse
Thats horrible.
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
km8j said:
Yea I pointed this out here: http://forum.xda-developers.com/showpost.php?p=69303648&postcount=12
It is a big issue. It should allow limited assistant functionality, but not entire phone.
Click to expand...
Click to collapse
Both of you! Turn "trusted voice" off
It is a setting in Google -> Search and Now -> voice -> and OK Google detection.
Turn off "trusted voice"
No more "GLARING SECURITY HOLES" in... Your knowledge of your phone.
Because, asking for limited functionality of Assistant when trusted voice is off doesn't sound right to me.... Like asking for AI to know which questions are answerable while screen is locked seems too tricky at this time.
The design is to use a lock or leave it off, currently.
Sent from my sailfish using XDA Labs
nednednerb said:
Both of you! Turn "trusted voice" off
It is a setting in Google -> Search and Now -> voice -> and OK Google detection.
Turn off "trusted voice"
No more "GLARING SECURITY HOLES" in... Your knowledge of your phone.
Because, asking for limited functionality of Assistant when trusted voice is off doesn't sound right to me.... Like asking for AI to know which questions are answerable while screen is locked seems too tricky at this time.
The design is to use a lock or leave it off, currently.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Well 1) the voice recognition isn't good 2) we want the functionality 3) the assistant could act on limited functionality: weather, reminders, send texts, make a phone call. If someone gets my phone and wants to manipulate a voice to send texts, whatever. This is how moto handled their voice assistant and it was perfect.
Oh this thread is now a feature request? It was about a security issue. Things can change.
Give Google feedback through "about phone" in settings! Maybe they will add the feature.
Sent from my sailfish using XDA Labs
Turn off trusted voice in Smart Unlock.
HeCareth said:
Turn off trusted voice in Smart Unlock.
Click to expand...
Click to collapse
Finally somebody with a smart answer...this controversy could all be avoided by a simple google search telling you how to disable the the trusted voice in smart lock, as the person states above. Im all about helping newbs out but research before you post...especially security stuff...... the title of you post makes it sounds as if there has been a security breach or major security flaw in the firmware.
Sounds about like the guy I sold a Gear 2 Neo too. I was showing him how to use some things and he freaked out when the Trusted Device feature left his phone without a passcode. So we disabled it, then he wanted to add a passcode to the watch to get get into it which really only works if it's disconnected from the phone. He was pretty honest about his reason. He's cheating on his wife and didn't want her to find out.
Sent from my Pixel using Tapatalk
Janker5050 said:
Finally somebody with a smart answer...this controversy could all be avoided by a simple google search telling you how to disable the the trusted voice in smart lock, as the person states above. Im all about helping newbs out but research before you post...especially security stuff...... the title of you post makes it sounds as if there has been a security breach or major security flaw in the firmware.
Click to expand...
Click to collapse
It is a security flaw if you can get through it with someone else's voice easily.
km8j said:
It is a security flaw if you can get through it with someone else's voice easily.
Click to expand...
Click to collapse
When I click on it in settings it tells me directly that it can be "less secure."
Yep. So it is not a flaw. It is a feature.
You should feel informed by the warning in settings, not like "it doesn't work.."
It is a fact more voices are similar and voices are easier to mimic than... Fingerprints. Rhythm and pitch are easy to steal. Ever hear of a cover band? Or confuse yourself which band you're listening to because of singer? If never... Wow dude.
Sent from my sailfish using XDA Labs
Related
Hello,
I just want to share a confusion. The phone unlocking mechanisms nowadays are plenty. Apple patented "Swipe to unlock", while Google created "Pattern Unlock" and "Face unlock".
I find it very weird that no one thought about "Voice Unlock", specially that both Apple and Google worked hard on voice recognition for the past time and released spectacular applications.
Voice Unlock should have been done years ago and should have been so popular because, if done properly, it would be used much more than Face Unlock. If the phone can recognize its owner's voice when saying "Hello Nexus" or "Wake-up Nexus" and simply unlocks itself, that would something amazing.
I don't know what are the reasons for the delay in such technology but I do hope that it will be available soon on Android.
I just wanted to share this concern in case anyone has any idea why this unlocking mechanism has been avoided by Apple and Google.
Thanks
PeritoX said:
Hello,
I just want to share a confusion. The phone unlocking mechanisms nowadays are plenty. Apple patented "Swipe to unlock", while Google created "Pattern Unlock" and "Face unlock".
I find it very weird that no one thought about "Voice Unlock", specially that both Apple and Google worked hard on voice recognition for the past time and released spectacular applications.
Voice Unlock should have been done years ago and should have been so popular because, if done properly, it would be used much more than Face Unlock. If the phone can recognize its owner's voice when saying "Hello Nexus" or "Wake-up Nexus" and simply unlocks itself, that would something amazing.
I don't know what are the reasons for the delay in such technology but I do hope that it will be available soon on Android.
I just wanted to share this concern in case anyone has any idea why this unlocking mechanism has been avoided by Apple and Google.
Thanks
Click to expand...
Click to collapse
That would kill the battery like crazy. Not to mention leaving the mic always on could be a very big security issue as then something could be used to record everything while the screen is off. Just because you can doesnt mean you should.
zelendel said:
That would kill the battery like crazy. Not to mention leaving the mic always on could be a very big security issue as then something could be used to record everything while the screen is off. Just because you can doesnt mean you should.
Click to expand...
Click to collapse
The cam is not always on when using "Face unlock". The mic should definitely not be always on when we use "Voice unlock". Only when the user wants to actually unlock.
PeritoX said:
The cam is not always on when using "Face unlock". The mic should definitely not be always on when we use "Voice unlock". Only when the user wants to actually unlock.
Click to expand...
Click to collapse
Actually the mic would always be on, an inactive mic wouldn't be able to track said user's voice. The phone's camera is active(screen on) while the device is on, Android phones enter sleep/deep sleep after X amount of seconds. Unless you are suggesting that Voice unlock be used once a user turns on the screen...Which would be pointless since you would just use your hands or camera Via Face Unlock.
Now if you mean "hands-free" Voice Unlock, that would clearly require an active mic 24/7 so that it can always check for user input. Both seem useless though IMO. It takes like 4 secs to unlock in jelly Bean so why bother with the phone detecting your voice? That's precious time be wasted on a gimmick.
If I'm not mistaken, S Voice is capable of doing that.
i don't think so...
I think it is need a special kernel. S3 have it. maybe big guys can port it but it is must special for every device
I hear over and over how the Ok Snapdragon is more responsive and the phone seems to pick it up better from the lock screen. What I was hoping for when the CM12 5.0.2 came out with the Ok OnePlus that my voice would be able to unlock the phone. I still have to put my lock pattern in after I wake it with Ok OnePlus. That kind of defeats the purpose IMO.
Will Ok Snapdragon do this?
Probably not, as anyone could say "OK oneplus" or "OK Snapdragon" and unlock your phone. If you set a pattern, you'll always have to enter it whatsoever. The only way here is to remove the pattern on the lockscreen and any other security method. "OK Oneplus" will then unlock your phone
OneTruth said:
Probably not, as anyone could say "OK oneplus" or "OK Snapdragon" and unlock your phone. If you set a pattern, you'll always have to enter it whatsoever. The only way here is to remove the pattern on the lockscreen and any other security method. "OK Oneplus" will then unlock your phone
Click to expand...
Click to collapse
I guess I was under the impression that the technology allowed it to use my voice to unlock the device.
At least I can say 'Ok OnePlus' to activate the screen then say 'Ok Goggle' to do hands free searches or start a timer (which I use a lot)
tjlmbklr said:
I guess I was under the impression that the technology allowed it to use my voice to unlock the device.
At least I can say 'Ok OnePlus' to activate the screen then say 'Ok Goggle' to do hands free searches or start a timer (which I use a lot)
Click to expand...
Click to collapse
NO, you are right, just disable ok, oneplus and then enable google now.
Connect your phone to power and say ok google, it will unlock itself.:highfive:
oneplus just simply sucks!! i purchased this phone for that feature only, never been able to use it.
never buy anything from them again.
masterchop said:
NO, you are right, just disable ok, oneplus and then enable google now.
Connect your phone to power and say ok google, it will unlock itself.:highfive:
oneplus just simply sucks!! i purchased this phone for that feature only, never been able to use it.
never buy anything from them again.
Click to expand...
Click to collapse
so you are saying when connected to a power source it will unlock but when not connected it wont do it with the same voice command.
Not for nothing but why have a lock and then have it be disabled by a voice command. Its kind of counterproductive and see this as a feature and not a bug per se.
playya said:
so you are saying when connected to a power source it will unlock but when not connected it wont do it with the same voice command.
Not for nothing but why have a lock and then have it be disabled by a voice command. Its kind of counterproductive and see this as a feature and not a bug per se.
Click to expand...
Click to collapse
This is how google protects the moto phones with always listening feature.
There is a lof of phone out there with the same CPU meaning they are able to use this feature (like theOPO and many others) but google hardcoded so we cant use it when you unplug the device.
I know it sucks but its marketing...
masterchop said:
This is how google protects the moto phones with always listening feature.
There is a lof of phone out there with the same CPU meaning they are able to use this feature (like theOPO and many others) but google hardcoded so we cant use it when you unplug the device.
I know it sucks but its marketing...
Click to expand...
Click to collapse
I kinda agree with them and not have my phone unlock by voice. I getnit though if you wanna take that risk it should be on you
Anyone else having inconsistent results with saying "OK Google" while the screen is off?
It seems to work fine when actively using the phone, but if I hit the power button to turn off the screen then it may (or may not) turn the screen on with the Assistant after saying "OK Google" (nothing happens).
I tried turning on fingerprint/pin security, but this will still sometimes not respond to the command. Additionally, it will also still sometimes ask me for a pin even though I have "Trusted Voice" enabled.
Not sure if it's a hardware issue or software related (again, everything works perfectly if the phone screen is already on and in use).
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
kinetic758 said:
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
Click to expand...
Click to collapse
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
ryken229 said:
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Click to expand...
Click to collapse
xShadoWxDrifTx said:
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
Click to expand...
Click to collapse
I was not connected to wifi but the signal seemed fine. I'll keep an eye on it next time.
nednednerb said:
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
kinetic758 said:
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
Click to expand...
Click to collapse
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
nednednerb said:
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
kinetic758 said:
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
Click to expand...
Click to collapse
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
nednednerb said:
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
What is scary for me, is any time there is a Pixel commercial on TV and the guy says "OK Google", my phone wakes up. So quite the opposite from the OP experience. Actually scary from a security standpoint. The old Motos used to allow limited functionality via voice but not full unlock (smart idea). There should be a way to remotely disable voice detection if you lose your phone.
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
dispatch said:
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
Click to expand...
Click to collapse
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
Click to expand...
Click to collapse
I really don't think it's the hardware, but you never know. I don't yet have a large enough sample size to say if 1 in 10 is accurate in the long run or if it is truly closer to 1 in 100 that it fails to wake. I always assume we're beta testers for Google anyway so I have come to expect things like this.
aquatarkus said:
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Click to expand...
Click to collapse
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
dispatch said:
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
Click to expand...
Click to collapse
This. I've embraced (at least for now) the fact that Google is collecting information about me. I've bought into it (also purchased a Google Home) with the hope that this will make my life easier (if slightly). A double-edged sword, for sure.
dispatch said:
However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do.
Click to expand...
Click to collapse
I figure I'm smart enough not to need Google to run my life for me. I will first root the Pixel and remove the stuff I don't want. When a suitable version of CyanogenMod becomes available, I'll flash that into it, as it provides additional security/privacy controls.
Anyway, I hadn't meant to highjack this thread....
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
Also try training the voice by saying Ok Google at 3 slightly different volumes and with varied pace. Do say it clearly each time. I found voice recognition doesn't work as well if I train it with a forced or monotone rhythm. Cos real voice is more fluid and not always the same.
Good luck
Sent from my sailfish using XDA Labs
Mine works every time.
This was never the case on the Nexus 6P.
The only time the Pixel DIDN'T wake up is when it was on low battery and save mode got enabled. I believe this disables the always listening feature of this app.
Sent from my Pixel using XDA-Developers mobile app
Maybe I am missing a setting somewhere or something, but the Google Assistant on my XZP only responds when the screen is on. I have it set to "any time" in the Assistant settings. Is this normal? I'm pretty sure it worked whenever (screen off/locked/charging/etc.) on my last couple of phones. I'd like it to at least work while the phone is charging.
Any ideas?
well yeah I had the same problem, apparently, Google changed the settings of the program, and it was only working while the phone is charging, so whenever u upgrade the application to its latest version you will lose this privilege. my advice and that's what I'm doing is to uninstall the updates from the google app and then give it all the permissions it needs and you will have it to work anytime the phone is charging no matter if the screen is on or off !!
btw my Google app version is 7.2.26.21.arm64
This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk
Jake_09 said:
This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk
Click to expand...
Click to collapse
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...
Heinous said:
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...
Click to expand...
Click to collapse
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for. I really wish they would also implement what Cortana does in terms of how she handles text messages when connected to Bluetooth devices. I love that she would ask if I want her to read it to me and then after reading it will ask me if I want to dictate a reply and send it.
Honestly, for some of the flak that I've seen Cortana getting lately, she's a much better and much more useful assistant than Google or Sri and she's probably the thing I miss the most from WM10.
Sent from my G8141 using Tapatalk
Jake_09 said:
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for.
Click to expand...
Click to collapse
It's not sure it's entirely Google's fault. It worked properly on previous android phones that I've owned.
I just noticed that it seems to work now with the Oreo update. My phone now wakes up and responds to "ok, Google" while the screen is off/locked. ?
This is by far the best part of the Oreo update. Google Assistant is at least 800x more useful now that it is actually hands-free.
Doesn't work wih mine. It blinks like I could say somehing, but stays closed. When I unlock it, nothing happens. My old phone then went into the assistant mode.
Which options do i have to set?
As in Title I can't use Google Assistant when phone is locked, if I want to ask anything and say Ok Google, my phone wakes up and makes the normal noise that the assistant is listening although nothing happens. Is there something I am missing?
Do you have any kind of unlock screen protection? (password, patern, fingerprint,....)
I have fingerprint and a backup password although I have always had that on other Android phone and the assistant would always work to make calls or answer questions
...I think it is because of your profile pic
Beauty is in the eye of the beholder.
seal said:
I have fingerprint and a backup password although I have always had that on other Android phone and the assistant would always work to make calls or answer questions
Click to expand...
Click to collapse
I always have all that desactivated, don't really like to having my phone listening to me every hour of the day....anyway, if that works in other phones, for me it's a serious security risk. Why would anyone want to let the phone make calls and answer questions if it's locked?? The lock is exactly for preventing anyone to do those things without autorization, but ho well......
https://support.google.com/assistant/answer/7394306?co=GENIE.Platform=Android&hl=en
Hope it helps...
seal said:
Beauty is in the eye of the beholder.
Click to expand...
Click to collapse
I don't use that feature but wouldn't you have to train the assistant to match your voice for security clearance? Perhaps that'll open the phone without the fingerprint.