Hello everyone, I have an unlocked international Play and I've set only security pattern and several fingerprints activated start-up security, which means every time it boots up requires a pattern input before loading the system.
However it just happened to me that after I shut down and reboot, it asks me for a password which I have never set. I've tried also my google account password and it doesn't work and in the end I have to hard reset my phone and lost all data.
Before this happened I've used this phone normally, updated to October security update, installed normal apps... the last two app I've installed is Fingerprint Quick Action and Disable Increasing Ring. I suspect it was one of these two or the security update... but honestly speaking I have no idea what just happened.
So now after reset I abandoned pattern and just use password directly just in case this happen again, FYI.
When you set a pattern or a fingerprint, you are required to supply a PIN to get into the system in case you forget your pattern or for some reason it won't accept your finger.
I have no idea how you'll get around this without flashing and starting over.
Hope this helps in the future.
ch3wt0ys said:
When you set a pattern or a fingerprint, you are required to supply a PIN to get into the system in case you forget your pattern or for some reason it won't accept your finger.
I have no idea how you'll get around this without flashing and starting over.
Hope this helps in the future.
Click to expand...
Click to collapse
Hi, on my device password is not required to set a pattern... perhaps you can try to clear your security pin and try to set a pattern, Play will not ask you to set a password.
ch3wt0ys said:
When you set a pattern or a fingerprint, you are required to supply a PIN to get into the system in case you forget your pattern or for some reason it won't accept your finger.
I have no idea how you'll get around this without flashing and starting over.
Hope this helps in the future.
Click to expand...
Click to collapse
This is right actually, this has been my experience with all my devices, whether they had a fingerprint scanner or not.
If you didn't have to set a PIN then I don't think it is normal.
RenoYeh said:
Hello everyone, I have an unlocked international Play and I've set only security pattern and several fingerprints activated start-up security, which means every time it boots up requires a pattern input before loading the system.
However it just happened to me that after I shut down and reboot, it asks me for a password which I have never set. I've tried also my google account password and it doesn't work and in the end I have to hard reset my phone and lost all data.
Before this happened I've used this phone normally, updated to October security update, installed normal apps... the last two app I've installed is Fingerprint Quick Action and Disable Increasing Ring. I suspect it was one of these two or the security update... but honestly speaking I have no idea what just happened.
So now after reset I abandoned pattern and just use password directly just in case this happen again, FYI.
Click to expand...
Click to collapse
I had also faced this, I think it occurs if you enable encryption. What you need to do is enter the numbers corresponding to the pattern in sequence. For eg, if your pattern is the first row, you'd enter 123.
This is in case you have set pattern as the security feature instead of security pin. Sorry you had to wipe your device but quick googling would have helped you out.
Hope this will be useful to someone else in the future.
peterlazar1993 said:
I had also faced this, I think it occurs if you enable encryption. What you need to do is enter the numbers corresponding to the pattern in sequence. For eg, if your pattern is the first row, you'd enter 123.
This is in case you have set pattern as the security feature instead of security pin. Sorry you had to wipe your device but quick googling would have helped you out.
Hope this will be useful to someone else in the future.
Click to expand...
Click to collapse
Apparently my Google skill requires improvement... Thank you so much anyway, so the pattern is actually treated as number pad, gosh.
Related
The wildest thing happened to me when I flashed the latest nightly. I originally had a pattern set to unlock the screen and that was backed up in titanium backup. When I flashed the nightly I changed it to a PIN. Here's where the issue comes in - I restored my backup (to get apps and settings back) in titanium then rebooted. Now I can't unlock it. I type in the PIN since it shows the PIN ui but it's actually looking for a pattern though the ui for that isn't showing up. Obviously this is my fault, however I'm wondering if anyone else has had this happen before? I don't want to do a data/factory reset but I see that being the only simple fix. Anyone have another idea though?
I think I know what you mean.
Every once in a while when I have to unlock my SIM it doesn't recognize my pin.
I just blackout the screen and go back, usually it gets the pin right.
Sometimes I get scared when it happens lol.
Yeah that's what I thought it was at first, until I saw the message that I entered the pattern wrong 10 times, now I have to wait 30 seconds. I got it fixed now so I'm happy. I just wonder why or how this would occur. It seems to me that 'if X is true>then Y is true, Z is false' doesn't exist for the lock screen, it's more like 'if X is true>then Y and Z are true'. I guess it's just a quirky argument bug in the system, oh well. It can always be fixed
All,
earlier last week my T835 got the OTA upgrade to Pie, upgrade went quick and smooth ...
Yesterday however, took the tablet from the charger and wanted to unlock by entering my PIN, got message "PIN incorrect", Thought I made a typo and re-entered my PIN, same result ... my PIN would no longer be accepted !!! Now, I was 100% sure I didn't change my PIN, so got really confused & scared .
Now I have my Screen Lock Type set to "PIN, Intelligent Scan", so managed to unlock using my face (had to change glasses ).
So I thought to check & change the PIN, but when you want to enter the "Secure Lock Settings" menu, your PIN is requested and again I got stuck, my PIN was not accepted and reported incorrect ...
So a catch-22, decided to restart the tab and see ... and guess what, after the restart, my original PIN is working/accepted again , anyone had this before??
thanks, Marcher
It could be your keyboard got into a funky state and it cleared from the restart. This could have been accidentally swiping something from a previous session or your cat walked across the tab or the dog licking it? Good to hear restarting resolved the issue.
I have the same thing on my Tab S4 since the Pie update installed. It's happening overnight, every night and it's not just the PIN. It is affecting Pattern and Password also. Resetting the tablet fixes it. I assume this is some third party software that Pie doesn't play nice with rather than a lack of QA, although I don't see anything other than Nova and Swiftkey that could be affecting it and my virus scans are coming up clean. Has anyone else seen this? Any ideas what it could be?
PhatPablo said:
I have the same thing on my Tab S4 since the Pie update installed. It's happening overnight, every night and it's not just the PIN. It is affecting Pattern and Password also. Resetting the tablet fixes it. I assume this is some third party software that Pie doesn't play nice with rather than a lack of QA, although I don't see anything other than Nova and Swiftkey that could be affecting it and my virus scans are coming up clean. Has anyone else seen this? Any ideas what it could be?
Click to expand...
Click to collapse
ok, so I am not the only one ... however can add now that this keeps on happening, every 2-3 days of usage, all of a sudden " wrong PIN "
Restarting fixes it ... I have no other tools running on mine ...
Marcher
Marcher said:
ok, so I am not the only one ... however can add now that this keeps on happening, every 2-3 days of usage, all of a sudden " wrong PIN "
Restarting fixes it ... I have no other tools running on mine ...
Marcher
Click to expand...
Click to collapse
just a quick update, running the BSF4 firmware now for a few weeks and the issue is gone :good:
Marcher
I previously had a Galaxy S9+ (android 9).
I wirelessly (and wired) charged it overnight.
In the morning, the fingerprint reader would unlock the phone - no problems.
I (only) ever needed my PIN to unlock it after a reboot, or after what "seemed" like many "days" of use.
Now, I have a new S20+ (android 10).
Every morning, after wirelessly (or wired) charging overnight, the phone forces me to use my PIN to unlock it.
There has been NO reboot. The auto-optimize and auto restart are (not) enabled.
Is this forced PIN unlock requirement normal behavior - or is there a setting where I can change this ?
I am half-asleep in the morning, and would like to be able to use my fingerprint to get into my phone - as entering a PIN is annoying and slow.
I have searched around for an answer to this and have seen all kinds of conflicting information - but none relevant to what I am experiencing.
I have seen: PIN unlock needed if --> reboot, or 72, 48, and 4 hours of non-use, or xxx number of fingerprint unlocks, etc.....
My case is simply (overnight) - which is 7 hours, max - so this makes no sense.
Obviously, on Android 9 with my previous s9+ this was not happening.
Anyone have some ideas on this ?
Maybe it's auto restart...
Check under advance menu in device care and uncheck it.
My auto reboot is set during the day but I noticed it rebooted over night so maybe its something else.
I know you say auto-restart is disabled but maybe you can check the battery usage graph and see if your phone did in-fact restart during the night. Maybe due to a crash/bug.
Other than that I'm not sure. And FYI this is NOT normal behavior. I haven't had to use a pin on my S20+ to unlock it a single time since initial setup on day 1.
Hi, hope this answers your question.
https://drive.google.com/file/d/130zA0UjhaCl32jrK63iI-UFe3nkFZmZG/view?usp=drivesdk
Sent from my SM-G988B using Tapatalk
i believe new samsung policies is now asking for pin to be entered every now and again but shouldnt be so often - i get it like once or twice a week
Innit
Wonderful.
Thanks for that !
Indeed that is exactly what seems to be going on.
I use both face unlock and fingerprints.
From that document you linked, it is obvious that when my phone is idle for 4 hours while I am sleeping, that because I use face unlock, it makes me use my PIN to unlock it
I surely do not like this behavior/rule, but at least I now have the answer to what is going on.
You just saved me the hassle of doing a factory reset !
Tonight, I will remove the face unlock completely and test this to see if I am required to use my PIN in the morning or not.
I will report back here what happens.
This is a great topic. I was just wondering this AM why I need to keep entering in my code every morning.
innit said:
Hi, hope this answers your question.
https://drive.google.com/file/d/130zA0UjhaCl32jrK63iI-UFe3nkFZmZG/view?usp=drivesdk
Click to expand...
Click to collapse
Nice find! Thanks
I've noticed this also.
I just wanted to confirm that last night I removed face unlock and this morning I was able to unlock my phone using my fingerprint without the need to use my PIN.
I definitely preferred the quickness of face unlock versus the awful fingerprint reader on this phone but at least now, when I get up in the morning, I can easily get into my phone without having to enter a pin.
Thank you so much for your assistance here.
Innit, by the way, where did you get that information from in the first place ?
Settings - > Lock screen - > Click on Fingerprints or Face recognition (at the bottom) - > Choose About unlocking with biometrics.
Samsung Galaxy S20 Ultra 5G (SM-G988B)
mycomputerisjunk said:
This is a great topic. I was just wondering this AM why I need to keep entering in my code every morning.
Click to expand...
Click to collapse
i havent had to enter my pin not even once - must be something to do with your settings - used mine since 11th of march
Running lineageOS 17 on a xiaomi mi 9 lite, loving it, but i made a mistake.
I have my phone rooted and have been messing around with edxposed and magisk and i was trying to see if i could enable some sort of face unlock feature through a mod. found one called hidden settings and i started poking around, and i tried to change the value of this one called "lockscreen.options=enable_facelock" through the terminal, hoping it would enable a face recognition header in the settings somewhere, but instead, it had a very strange effect. first, that string no longer exists in android secure settings on my phone, and second, now my phone will not lock through normal means. using the power button, waiting for timeout, nothing, as soon as i wake the screen, the padlock icon is already open and the screen swipes itself up and goes to my unlocked home screen as though it had recognized my face and unlocked itself...only it didn't, because even trying this with my thumb over the camera has the same result.
anyway, i don't know what to do, but i need my phone to lock. so far the only thing ive tried that works is to use the lockdown mode button in my power menu, but that's a hassle. anyway, any help would be appreciated, my goal is to avoid a factory reset as well.
thanks in advance
Sorry, unofficial lineageOS 17 and magisk and edexposed. That is a highly experimental setup. You should be aware, there you have to start from scratch at some point. Be happy, if it's enough to wipe system and data. Others flash stock ROM to fix things.
kurtn said:
Sorry, unofficial lineageOS 17 and magisk and edexposed. That is a highly experimental setup. You should be aware, there you have to start from scratch at some point. Be happy, if it's enough to wipe system and data. Others flash stock ROM to fix things.
Click to expand...
Click to collapse
actually it was simpler than I thought...turns out nothing was broken at all. in fact one element was functioning better than i expected it to. a while back i was messing around on my previous phone, a rooted oneplus 5 running resurrection remix, and i started fiddling with tasker...anyway, at some point i had issues with the native smart lock features so i set a profile in tasker to unlock the phone when the screen turns on as long as i am connected to my home wifi network. apparently when i restored all my apps to the new phone through my google account it saved a ghost of that profile...i didn't catch it because it wasn't listed in the tasker interface, so i assumed none of my old automations had transferred. i figured it out when other old profiles started to activate, and eventually i remembered that i hadn't set any of that stuff up on this phone yet :victory::laugh:
in any case, thank you for the input...to be honest i would rather have a less experimental setup, but the mi 9 lite doesn't have much development yet so i'm choosing the best from what is available.
Hello,
So I am adjusting the phone of my little brother, the problem is that his SIM card is blocked.
So without doing anything on purpose, I realized that there was a little bug that would let anyone have access to your phone without entering the SIM card PIN code! Nice security OOS13!
Watch this..
I don't think this is normal.
Edit: Maybe it should work on OOS12 too, since it's because of Google Assistant on the power button.
Edit: I changed the action to power menu instead of the assistant to prevent it.
if the sim card is blocked why not just remove it instead of doing that!? seems pretty dumb to me lol
Well i also have os13 I'll chk
Unless it has bee manual changed, on my fully 9 pro, fully stock A12 - On os12, the default action for power button is to launch the camera, click and hold launches the NFC payment cards stored on the phone.
I attempted to copy what you did.
The pin entry screen you used, is that from a cold start? Meaning is that the one that appears when you turn the phone on?
Great find through, hopefully it will work for others on A13!
AndyC76 said:
Unless it has bee manual changed, on my fully 9 pro, fully stock A12 - On os12, the default action for power button is to launch the camera, click and hold launches the NFC payment cards stored on the phone.
I attempted to copy what you did.
The pin entry screen you used, is that from a cold start? Meaning is that the one that appears when you turn the phone on?
Great find through, hopefully it will work for others on A13!
Click to expand...
Click to collapse
Indeed it's a great find.
Did you set a SIM PUK lock pin or just a pin passcode? With google assistant on. I believe the video is showing the SIM PUK lock as attached. I will turn on assistant for a11 and report back.
Edit: I created a power button macro on Android 11 to open assistant, it does not bypass the PUK
LOL
Jed!Master said:
if the sim card is blocked why not just remove it instead of doing that!? seems pretty dumb to me lol
Click to expand...
Click to collapse
Because I was going to unlock it before I see this!
I
Appreciative said:
Indeed it's a great find.
Did you set a SIM PUK lock pin or just a pin passcode? With google assistant on. I believe the video is showing the SIM PUK lock as attached. I will turn on assistant for a11 and report back.
Edit: I created a power button macro on Android 11 to open assistant, it does not bypass the PUK
Click to expand...
Click to collapse
I just blocked the SIM card then I wanted to turn off the phone, I pressed the power button and the google assistant appeared and bypassed the phone.
AndyC76 said:
Unless it has bee manual changed, on my fully 9 pro, fully stock A12 - On os12, the default action for power button is to launch the camera, click and hold launches the NFC payment cards stored on the phone.
I attempted to copy what you did.
The pin entry screen you used, is that from a cold start? Meaning is that the one that appears when you turn the phone on?
Great find through, hopefully it will work for others on A13!
Click to expand...
Click to collapse
Not really a fresh start since I first used the phone without SIM card, then put the SIM card in, and discovered the bug.
Edit: Even after a restart of the phone, so a fresh start, it works... I don't know what the reason behind this...
Kydaix said:
Not really a fresh start since I first used the phone without SIM card, then put the SIM card in, and discovered the bug.
Edit: Even after a restart of the phone, so a fresh start, it works... I don't know what the reason behind this...
Click to expand...
Click to collapse
My guess is they had a big brain idea at the end and said "let's add google assistant to the power button!" And integrated it too low in system loading. On a11, I can't get the macro to do anything before puk code, probably as it's not got system loaded yet. But in (a12 supposedly has an option in pixel phones for long press assistant also )a13+, that assistant is integrated as system. In A11, It's locked down. I didn't try with my password removed so it can be unencrypted, maybe it would load some of the system.
At any rate, it's a really funny find and if it's existed since a12/a13 and nobody has mentioned it, that may tell us how many people use the sim lock.
Did you try it on a reboot with a regular pin/passcode on the device as well?
Appreciative said:
My guess is they had a big brain idea at the end and said "let's add google assistant to the power button!" And integrated it too low in system loading. On a11, I can't get the macro to do anything before puk code, probably as it's not got system loaded yet. But in (a12 supposedly has an option in pixel phones for long press assistant also )a13+, that assistant is integrated as system. In A11, It's locked down. I didn't try with my password removed so it can be unencrypted, maybe it would load some of the system.
At any rate, it's a really funny find and if it's existed since a12/a13 and nobody has mentioned it, that may tell us how many people use the sim lock.
Did you try it on a reboot with a regular pin/passcode on the device as well?
Click to expand...
Click to collapse
Maybe, we will probably never know why...
I did not, I've removed the macro because I don't want the phone to be open to everyone, now it's in my brother's hands!