knock code unlocks the screen, but not the security options? - LG V30 Questions & Answers

Hi,
So I have this strange issue which I cannot figure out. I set up the knock code when I got the phone, as well as one fingerprint to unlock it. It works fine both ways in everyday use. But recently I wanted to add more fingerprints to my phone, and when I try to add them, I am prompted to input my knock code, which I do. The weird part is that the phone says that it's the wrong code. Now, I am sure that I am not inputting it wrong. It always unlocks my screen, just not the security options.
Is there an another code I am not aware of? Maybe a default one for the security options? Has anyone had an issue like mine, and can help me?
Thx in advance.

sbto said:
Hi,
So I have this strange issue which I cannot figure out. I set up the knock code when I got the phone, as well as one fingerprint to unlock it. It works fine both ways in everyday use. But recently I wanted to add more fingerprints to my phone, and when I try to add them, I am prompted to input my knock code, which I do. The weird part is that the phone says that it's the wrong code. Now, I am sure that I am not inputting it wrong. It always unlocks my screen, just not the security options.
Is there an another code I am not aware of? Maybe a default one for the security options? Has anyone had an issue like mine, and can help me?
Thx in advance.
Click to expand...
Click to collapse
Its definitely an issue with your device. I just checked and it works like it's supposed to. There is no other code for security options, it's the one and same, no matter PIN, PW or Knock Code.

Related

[Q] Q: Android Causing Problems with WinMo PIN recognition?

I'm not sure exactly where this goes, but I think it belongs here and I haven't been able to find any other threads about this issue.
It's going to seem like a WinMo issue, but I'm pretty sure it's Android related.
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Today, I shut down Android (properly) and turned the phone on to return to WinMo. On the 4 digit numeric PIN screen (I Activesync with Exchange at work and this is part of the security requirement; it's not the SIM or GSM PIN), I enter my pin and ... I get an error message that I've entered the wrong PIN and I just used 1 of 8 turns. I tried carefully to enter the PIN to make sure I didn't fat finger the button - strike 2. So, I open the keyboard to try using that, and still no dice. Now I'm worried about getting my device wiped and starting from scratch.
The reason I think this is Android related is that this has happened to me one other time. This problem was the main reason I stopped using BLAZN about 6 months ago. In the almost 2 years that I've had this phone, this hasn't happened when rebooting from WinMo back into WinMo.
Any suggestions or ideas about what's going on? I don't even want to touch my phone without having a plan of attack. My contacts are backed up (first thing I did before I installed FRX06), but would rather not have to re-install stuff if I don't have to.
By the way, until this little incident, Android had been running great - it's been a big improvement over where it was 6 months ago.
Thanks in advance for any help.
-David
LeStone08 said:
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Thanks in advance for any help.
-David
Click to expand...
Click to collapse
I think you need to rename/delete your data.img.
But first you need a real fresh start so don't install FRX06 on top of BLAZN. Delete the old and download the FRX06 package from the thread
Thanks for the reply. Those are some good suggestions in general, but doesn't address my immediate need: Is there any way to get past the PIN check now (maybe the PIN was reset to some default)? Or is there an explanation for what is going on? AS it is, there's nothing I can do with the phone if I don't get the PIN correct (can't reboot into Android).
Also, in order to get FRX06 to work, I did delete the data.img file, so that is fresh. Also, the first time a few months ago, I ran into this problem was on my original (clean) install of BLAZN. Until this problem happened, Android had been working great in most other respects.
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
arrrghhh said:
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
Click to expand...
Click to collapse
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
Normally, I wouldn't think Android would impact my winMo setup. But this has only happened to my twice and both times occured after shutting down Android and rebooting the phone.
No one else has access to my phone - so I can't blame anyone else.
I did install the trial version of Touchdown in my Android installation, but I don't think that's part of the problem (the last time it happened, I used the standard Exchange functionality of Android).
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
LeStone08 said:
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
Click to expand...
Click to collapse
These are questions for your IT dept I would think...
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
I would agree with rpierce99. I use MS Exchange (2007) on both wm & frx06 with password policy enforced and never experienced this issue. I chose to use a 6 digit numeric pin on both OS.
I remember having this issue. Pissed me off beyond belief. Same thing happened, booted out of android, when I tried unlocking, it kept saying the password was incorrect. For some reason I can't remember what I did to fix it... I think I just did a forced hard reset (click reset button, hold send key + end key + power key all at once). I know it's not what you want to hear but hard reset might be the only/quickest fix.
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Raa_1 said:
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Click to expand...
Click to collapse
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
slapshot30 said:
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Click to expand...
Click to collapse
You're right, it wasn't my SIM lock that was causing the problem. I don't remember if my battery was low or dying. I do know that the last thing I had running was the Youtube app that was having problems with buffering a video, then it started getting non-responsive, which was why I decided to shut down my phone and reboot.
I checked with our IT department and besides them trying not to support it because it's not an eye-phone, there were no known MS Exchange changes at our company that would have caused the problem. I did find out that the webmail client for Exchange now shows the clients that connected - I could see a listing for my WinMo install and a couple for my Android install (my original install from 6 months ago, and my current install - the different builds had different system names). There is a feature to request a recovery PIN there, but my HTC Sense simple PIN entry screen didn't have a recovery pin option that's needed - or I didn't see it in the last try I had to get my PIN correct. Maybe I'll play with that more if I start using WinMo again.
My phone did get wiped and so far, I haven't loaded anything back into WinMo - I've been running off my Android install (didn't reinstall - since my SD Card didn't get wiped) for the last 1.5 weeks.
I know it's not a large sample size, but the two times this has happened in the almost 2 year time period that I've had this phone occurred when booting out of Android. I'm glad to hear that I'm not the only one with this issue, but it would be nice to have the problem diagnosed.
I'm hoping that one of the brains doing all of this cool stuff will find the root cause and show us (at least me and Slapshot) how to avoid the problem.
Thanks. I'm still really happy about the state of the Rhodium projects.
Raa_1 said:
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
Click to expand...
Click to collapse
I've never set any type of PIN on my Android phones. What are you setting?
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Raa_1 said:
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Click to expand...
Click to collapse
I'll take your word on the SIM PIN business, as I've never actually set my SIM pin. I wouldn't do this in general, but also especially knowing that there's a conflict between SIM pins and the XDAndroid projects.
In WinMo (I believe there's a way to do this an Android also, but not quite sure), there are two ways that I know of to set up a startup PIN on your phone (at least on my Tilt2):
1) You can go into Settings, Security, Phone Lock: here you can set up your phone to lock itself after a set amount of time. You can use either a Simple PIN or a strong alpha-numeric PIN. Whenever your phone is idle for a time period exceeding the threshold you have set, the phone will lock itself so that you have to enter your PIN to access the phone again. Again, this is not the SIM pin.
2) Some of us work at companies that use this little email package called Exchange by a company called Microsoft . In order to protect employee's and (mostly) company data, some of these companies will leverage security features in Exchange to mandatorily set policies on any mobile devices that want to access the corporate email system. If you want access to the system, you have to accept whatever policies the company chooses to enforce. Some of these policies include: 1) Requiring a PIN (not a SIM pin) on your device; 2) requiring a max idle time before the phone locks itself; 3) requiring a phone reset (including data wipe) after a certain number of missed passwords; 4) allowing a phone wipe/clear on demand in case of theft; etc. My company requires all of these - there are more, but I'm not familiar with all of the options.
When I boot into Windows Mobile, Exchange sees my phone as one device and sets the policies accordingly (basically the email software has to be able to receive the policies and interpret them). When I boot into XDAndroid, Exchange sees my phone as a different device and sends the same set of polices. For my original problem, I set the PIN to be the same for both instances to make like easy for my tiny little brain.
I reiterate that this is not a SIM pin issue. I want to make it clear so we can keep this thread on topic in case anyone else has some insights into the problem. I don't want it to be derailed into a SIM PIN discussion since I'm sure there are lots of threads about that. (Now, I've probably polluted the index with that term and anyone looking for that will find this instead )
I would love to know if anyone gets any insights here.
Thanks for reading.
David
Yes I see what you mean now, and my issue is a different one (SIM not device PIN).
Since your work is issuing device policies, my thought would be it's a policy issue, and quite honestly, I wouldn't try and mess around with a device that's under I.T. direction.
Having said that, i'd likely say your problem is a corrupted WinMo password as Android has nothing whatsever to do with WinMo's side of things. And as mentioned before, it can happen with varying (mainly unknown - grr) reasons why.

Tablet keeps switching to PIN unlock

I bought my Tablet S yesterday and applied the 4.0.3 OTA update overnight so I can't say whether it was caused by the update or not, but here's what happens:
My phone keeps reverting back to PIN unlock. I never set it to PIN unlock before, and even when I change it back to slide unlock, after a little while it'll be back to PIN unlock.
Hi poebae,
that's a strange bevaior. Since u just bought ur tablet I'd assume u dont have much on it by now. So I'd factory reset it and see if it'll solve my problem.
Outta curiosity, how the hell do you get back in your tablet if it sets a PIN code you dont know?
Are you syncing corporate email? Some companies configure the exchange server to require Android and iOS phones to add extra security and one of those security options is to require a PIN.
However, it should have alerted you and prompted you to set the PIN rather than just changing the setting.
Lunat1c said:
Hi poebae,
that's a strange bevaior. Since u just bought ur tablet I'd assume u dont have much on it by now. So I'd factory reset it and see if it'll solve my problem.
Click to expand...
Click to collapse
Yep, I ended up just doing a factory reset and that seems to have solved it.
Lunat1c said:
Outta curiosity, how the hell do you get back in your tablet if it sets a PIN code you dont know?
Click to expand...
Click to collapse
I just used '0000'. I either got lucky and guessed the PIN that the original owner used (I bought it second hand), or that's some kind of default code.
Gramon said:
Are you syncing corporate email? Some companies configure the exchange server to require Android and iOS phones to add extra security and one of those security options is to require a PIN.
However, it should have alerted you and prompted you to set the PIN rather than just changing the setting.
Click to expand...
Click to collapse
Nope, not syncing corporate e-mail, but thank you for the suggestion!

[Q] Knock On to Wake

Coming from Samsung here, so this feature is very new for me.
Does the knock to wake feature work if you're set on pattern lock? Or does it only work when you have knock code set as your security?
Reason I ask is because I initially had the knock code set as security, then changed to pattern after I set Android Pay. BUT, knock to wake has been working for me the past two days (even with the pattern lock ON)...until 2 hours ago.
Now the only way I can knock wake the device (or even access the second screen) is either to set the security as Knock Code, or press the power button.
Is this behavior normal? I found it weird that the second screen is untouchable with the pattern lock ON.
Knock On will work everytime regardless of your lock screen setting (double tap on the center of the screen to wake device up into lock screen).
Knock Code, however, need to be set to unlock your device, the pattern is of your choice.
Android Pay doesn't accept a knock code as a security measure. I was using it, then was forced to switch to pin after setting up Pay.
Ryu Kenshin said:
Knock On will work everytime regardless of your lock screen setting (double tap on the center of the screen to wake device up into lock screen).
Knock Code, however, need to be set to unlock your device, the pattern is of your choice.
Click to expand...
Click to collapse
ok so correct me if I'm wrong: regardless of your security settings, KNOCK ON will work to wake the device up. Yes?
In that case, something has gone wrong with mine as I can only do knock on when Knock Code is set. Even worse, the second screen shortcuts are only accessible in that mode as well.
I think I just encountered a similar if not the same problem but I'm not sure if it's an app or if it coincides with something I accidentally tapped in the hidden menu last night.
I had been using pattern unlock since I got the phone on friday and double tap to wake the screen was working fine along side fingerprint unlock, now double tapping doesn't work and the second screen does not respond when locked.
EDIT: I just tried knock pattern and it allowed me to wake the screen but the moment I switched back to pattern it stopped responding to screen wake tapping.
mastarpete said:
I think I just encountered a similar if not the same problem but I'm not sure if it's an app or if it coincides with something I accidentally tapped in the hidden menu last night.
I had been using pattern unlock since I got the phone on friday and double tap to wake the screen was working fine along side fingerprint unlock, now double tapping doesn't work and the second screen does not respond when locked.
EDIT: I just tried knock pattern and it allowed me to wake the screen but the moment I switched back to pattern it stopped responding to screen wake tapping.
Click to expand...
Click to collapse
sorry to hear about that, seems like you have exactly what I had. Knock on just stopped working out of nowhere.
Good news is, I did a factory reset and it fixed the issue. Albeit, without access to Titanium Backup, it's quite a chore right now to redo all of my setups. Trying LG Backup now just in case.
Give factory reset a try and hopefully it'll solve your issue as well.
baymon said:
sorry to hear about that, seems like you have exactly what I had. Knock on just stopped working out of nowhere.
Good news is, I did a factory reset and it fixed the issue. Albeit, without access to Titanium Backup, it's quite a chore right now to redo all of my setups. Trying LG Backup now just in case.
Give factory reset a try and hopefully it'll solve your issue as well.
Click to expand...
Click to collapse
Yeah I was kind of afraid I'd have to reset already, barely a week in, lol!
Thanks for letting me know a reset worked, hopefully it doesn't happen again.
I think @knifedroid had the answer. AndroidPay doesn't allow you to use knock. I have the same issue as well...well i guess it's not an issue...it's a feature.
Sent from my LG-H901 using Tapatalk
KwestJones said:
I think @knifedroid had the answer. AndroidPay doesn't allow you to use knock. I have the same issue as well...well i guess it's not an issue...it's a feature.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Knock Code is a security method, Knock On is a feature that LG implemented at kernel level to wake up/turn off the device. The issue that we've been having is with the Knock On not functioning anymore.
Long story short the reset restored Knock On (wake).
Long version, I gave the LG Bridge software a shot to do a backup to the PC.
It let me backup just about everything including apps and data, including Humblebundle apps and stock homescreen layouts, so it's probably as close to tatanium as you ca get.
I Haven't gone through updates yet but so far Knock On is still working after a restore, I'll edit if that changes. *crossing fingers*
oh man I'm glad i came to peek this section for this, as i feel like i tapped something wrong in the hidden menu as well. i might wait a little bit to do a reset and see if someone finds out a way to keep the KnockON thing running when screen is off.
joachim123 said:
oh man I'm glad i came to peek this section for this, as i feel like i tapped something wrong in the hidden menu as well. i might wait a little bit to do a reset and see if someone finds out a way to keep the KnockON thing running when screen is off.
Click to expand...
Click to collapse
hey someone on another thread said that deleting all the fingerprints solved his Knock ON issues. Can you try this out?
baymon said:
hey someone on another thread said that deleting all the fingerprints solved his Knock ON issues. Can you try this out?
Click to expand...
Click to collapse
Just tried it, no luck. Both knock on and off are still not working.
The issue started for me last night after going to the hidden menu and enabling Fast Dormancy. Disabling it again doesn't help. I guess just avoid the hidden menu is the takeaway here.
Sent from my LG-H901 using XDA Free mobile app
pakraider said:
Just tried it, no luck. Both knock on and off are still not working.
The issue started for me last night after going to the hidden menu and enabling Fast Dormancy. Disabling it again doesn't help. I guess just avoid the hidden menu is the takeaway here.
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
ok, sorry bud. Hard reset did the trick for me, but it'll be good to know what caused this and what can we do to solve it.
Now that you mentioned it, I think my issue started after I was playing around with hidden menu as well. Although I didn't recall changing anything.
baymon said:
ok, sorry bud. Hard reset did the trick for me, but it'll be good to know what caused this and what can we do to solve it.
Now that you mentioned it, I think my issue started after I was playing around with hidden menu as well. Although I didn't recall changing anything.
Click to expand...
Click to collapse
Yeah, tbh it sounds like a software bug by LG. Just going to the hidden menu seems enough to break the knock on/off. Makes you wonder what else might be getting messed up too that we haven't noticed.
p.s. this thread is why XDA is awesome.. everyone thinking 'omg what happened?' only to see others in exactly the same boat.
This makes sense. I think my knock on stopped working after using the hidden menu to look at the dB on the LTE signal.
Sent from my SM-N900T using Tapatalk
So in this case of resetting, would I be able to just grab the system img and flash it without actually doing a hard reset? I don't want to have to set up everything, again.(i had forgotten it was going to reset when I unlocked the BL)
Just confirmed it. Knock on breaks when you try to enter the ims settings menu inside the hidden settings menu. It crashes, then knock on stops.
Sent from my SM-N900T using Tapatalk
I am having an issue where it is grayed out and stating something else has an administrator lock. Any idea on what's holding it up?
Sent from my LG-H901 using XDA Free mobile app
MacMitten said:
I am having an issue where it is grayed out and stating something else has an administrator lock. Any idea on what's holding it up?
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
That looks like you are in the android pay security options. If so, android doesn't think that knock is secure enough for androidpay. Don't think there is anything we can do about it yet.
If you decide to use android pay you cannot use KnockOn pattern unlock to open your phone.
Sent from my LG-H901 using Tapatalk

Fingerprint scanner with insecure lockscreen?

Is this possible. I've tried everything the fingerprint scanner doesn't work unless you have a secure lock screen. I have used knock code since I got the V10 along with fingerprint so I can use the fingerprint, but I don't want to have to put a knock code in if my fingerprint doesn't work or its on the table...
Anyone got a workaround? I'm still searching.
Matt
Does no one know how I can do this?
Matt
I'd like to know the same thing. I know LastPass just added fingerprint support (for marshmallow) and I'd love to be able to use my fingerprint to unlock that (when marshmallow comes) without having to have a secure lockscreen. I don't really care if someone can get into my phone. I just don't want to have to type in my password to use lastpass
I've searched around everywhere for this option .... I just don't think it exists.
So just don't use any lock to get into the phone now. I've got the stuff I want secure in locked files/apps section. Makes using and accessing the main functions of the phone much more accessible. Only doing this for a few days now as a test, but I think it'll be the way I keep it.
My Two Lock Screens Worth
I've addressed the issue another way. I added several more "trusted" places, devices, and connections as well as "trust while moving" which means as long as the phone senses it's on me, I'm at home, connected to Bluetooth devices I know, and more, there's no secure lock but fingerprint still unlocks it. Perfect. Still testing it
Matt

Question Security check

Is there any way to disable the "routine security check" that makes the phone ask for your password to unlock the phone rather than using the fingerprint sensor?
I'm getting real ****ing tired of trying to quickly unlock my phone, just to see that I have to type my password in for some stupid security check.... like WTAF?!
Any help or info is appreciated, thanks in advance.
zelfez said:
Is there any way to disable the "routine security check" that makes the phone ask for your password to unlock the phone rather than using the fingerprint sensor?
I'm getting real ****ing tired of trying to quickly unlock my phone, just to see that I have to type my password in for some stupid security check.... like WTAF?!
Any help or info is appreciated, thanks in advance.
Click to expand...
Click to collapse
go to the settings in your phone and try to look for anything that can help then you should be able to disable it.
I have not found any way to stop the routine security check...yet! It happens randomly. Sometimes it seems to happen every few unlocks and at other times I don't see it for a few days! No rhyme or reason here, and for now no apparent way to turn it off.
jaseman said:
I have not found any way to stop the routine security check...yet! It happens randomly. Sometimes it seems to happen every few unlocks and at other times I don't see it for a few days! No rhyme or reason here, and for now no apparent way to turn it off.
Click to expand...
Click to collapse
Roger that, Thank you!

Categories

Resources