Question OneUI 5.0 - Too many incorrect unlock attempts - Samsung Galaxy S22 Ultra

My S22 Ultra updated to Android 13 this morning. Since then on two separate occasions when I took the phone out of my pocket, it says 'Too many incorrect unlock attempts' and it makes me wait before I can do anything with the phone. The first time it made me wait 5 minutes and the second time 11 minutes.
I cannot enter the PIN and I cannot even turn off the phone until the time has expired. Never experienced this before.
What on earth is going on and how do I stop it? Anyone else had this?

Turn on accidental touch protection under settings / display

raul6 said:
Turn on accidental touch protection under settings / display
Click to expand...
Click to collapse
It was already on. I have now turned off touch sensitivity and also double tap to wake. I will see what happens.
However, I don't understand why this has only happened since I updated to OneUI 5.0 today. In the past if I had an issue with my fingerprint, it would tell me to use my PIN. It never locked me out completely for a period.

Related

[Q] Galaxy S5 turns display on randomly

Was anyone experiencing the display randomly turning on & won't dim itself off. I am using the fingerprint lock so it stays on the screen asking for the alternate password. This happens while charging & when idle. The phone stays on until you press the power button. I am testing if is something to do with the fingerprint lock, switching to pattern lock. any ideas?
I also use fingerprint unlock and have noticed that the display will randomly turn on and ask for the alternative password. I just got the phone this past Sunday (6/8) and all I've really done to it is add the fingerprint security.
what ROM are you running?
youdoofus said:
what ROM are you running?
Click to expand...
Click to collapse
Stock ROM, no changes.
I've also seen this. Usually happens to me at night for some reason. Screen turns on and when I hit the side button to turn off the screen it goes out for a few seconds then lights up again. Have to reboot to fix it.
Mine does it during the day at work quite a bit, I think it is from the home button being pushed in my pocket. It really should be associated with the light/proximity sensor as to when the button will work.
Having the same problem with both swipe and fingerprint unlock. I can understand swipe, fingerprint works better in my pocket then with my finger
Mine is constantly turning on in my pocket now. I have an otterbox commuter on it and edges are raised pretty good, doesn't seem like my leg would hit the home button but it's hard to tell
Only happens to me when connectivity state changes, or music skips for a notification
Sent from my SM-G900P using Tapatalk
I am having this problem on stock unrooted ND2 as well as RDDT. I also noticed on both that I get notification sounds with NO notifications showing up. So I have my notification sound going off a few times each hour for no reason unless I leave my phone on silent.
As far as the screen coming on randomly, I found that disabling air wake has helped a little bit. Especially overnight, I leave my phone next to my pillow (yea, I am a junkie...) and the screen would turn itself on every time I rolled over, and the screen would stay on after that until I woke up and turned it off. I know it was staying on because a couple of times I reached over the phone, screen turned on and I watched it for about 5 minutes (screen time out is set to 15 seconds) and it didn't shut off.
TL;DR Turn off air wake - Need help figuring out phantom notifications (still exist after multiple factory resets and almost no apps installed)
My issue stopped once I installed a glass screen saver. Home button is now countersunk with the 0.33 mm. Cover & review.
http://www.amazon.com/Tech-Armor-Samsung-Ballistic-Protector/dp/B00IGISUTG/ref=cm_cr_pr_product_top
http://www.amazon.com/Tech-Armor-Sa...tBy=bySubmissionDateDescending#R1R8876D8WLXE3
I installed the same one, lol. It still does it, not as often though
I was using standard pattern lock screen on stock rooted and had this issue. It was the wave to wakeup feature that was causing it. I turned it off and it went away. 3 days with no waking by itself.
I've never had that turned on.
looks like you guys turn on air wake and it's working sensetively. on the contrary, mine is numb
yueyejinghun said:
looks like you guys turn on air wake and it's working sensetively. on the contrary, mine is numb
Click to expand...
Click to collapse
It was numb for me too when it wasn't being awakened by ghosts. The other guy said he didn't have that feature on so not sure what the other issue(s) is/are.
GorillaPimp said:
It was numb for me too when it wasn't being awakened by ghosts. The other guy said he didn't have that feature on so not sure what the other issue(s) is/are.
Click to expand...
Click to collapse
air wake is a nice feature to extend the lives of home & power button, except it always makes me look like an idiot when I am waving my palm over the phone again and again.
I tried to set the mode to unlock by fingerprint and keep air wake on for a whole day, but I didn't encounter that problem. maybe it just affects some devices, maybe it's not air wake.
Anybody found a real solution for this inconvenient?!
This only happens at Lollipop... 2 months ago I updated and because this annoying issue that was draining my battery I downgraded to Kit Kat...
Last weekend I decided to give another shot to Lollipop, but the issue remains...
I tried all settings relative to screen and lock screen and nothing worked!
andreluigo said:
Anybody found a real solution for this inconvenient?!
This only happens at Lollipop... 2 months ago I updated and because this annoying issue that was draining my battery I downgraded to Kit Kat...
Last weekend I decided to give another shot to Lollipop, but the issue remains...
I tried all settings relative to screen and lock screen and nothing worked!
Click to expand...
Click to collapse
I have the same problem. My battery has been life does not even last me until the end of work. Trying a fix now that I just thought of though. This problem is incredibly frustrating at night too.
I believe its the connection optimizer. Go to Settings > More networks > Mobile networks > Connections optimizer:
Then Uncheck "Connections Optimizer"
Seems to be working so far! So hopefully this helps the rest of you!
This Fix did not work still perplexed by this problem.
After rooting and removing a lot of bloat, I got rid of it. I have no idea which app it is though. Maybe an xposed module logging screen wakes could be of assistance. But I too noticed it immediately after flashing a lollipop ROM.

Problem with screen lock and suspend

Hi,
I have found 3 mornings in a row that when the phone is in my pocket and I walk to work its clearly trying to turn itself on, as when I pull it out the phone is in suspend mode and says I can't unlock it for 15 mins. It must be responding to sensors or the power button isn't strong enough to avoid accidental presses.
It says "fingerprint suspended try again in x minutes". The pin entry is non responsive during this time so its clearly a security lock which is being triggered by false movements.
Its a pita and clearly shouldn't be occurring. I've never had the problem before with any other phone.
Any ideas as a workaround or solution?
thanks
Could it be you are accidentally touching the fingerprint sensor while walking? In smart assistance settings there is an option to disable touch while device is in your pocket. Have you tried turning this on?
Those are the only tips that come to mind, tried it with my mate9 but cannot seem to reproduce this.
djmvt said:
Could it be you are accidentally touching the fingerprint sensor while walking? In smart assistance settings there is an option to disable touch while device is in your pocket. Have you tried turning this on?
Those are the only tips that come to mind, tried it with my mate9 but cannot seem to reproduce this.
Click to expand...
Click to collapse
YES! Thats just the setting I was looking for thanks it was driving me nuts but I couldn't find the setting! EMUI is subtly different having been used to Samsungs for the last 6 years!
Still have pocket reset
bonerp said:
YES! Thats just the setting I was looking for thanks it was driving me nuts but I couldn't find the setting! EMUI is subtly different having been used to Samsungs for the last 6 years!
Click to expand...
Click to collapse
Hi guys, even if the setting has been enabled on my Mate 9, the phone still try to open itself when I'm walking around.
Do you know if I can turn off the reset function after 10 failed password?
Honestly, this is getting so annoying that I'm thinking about changing phone again...
Thank you!
Vince

Double tap wake up - lag

Hello All.
Anybody else have the same issue like me?
I have around 4 seconds lag during wake-up phone with double-tap. But only when phone goes to sleep with camera application opened in front.
This is strange.
If camera app is opened in front and phone goes to sleep - long wake-up with double-tap.
With power button wake-up -> phone wake-up immediately.
If phone goes to sleep with any other application opened in front (home screen, any other app) -> double-tap wake up phone immediately.
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?[/QUOTE]
Just tried mine and seems to work fine on double tap
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
nedalnib said:
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
Click to expand...
Click to collapse
Now that I have watched the video,, mine acts the same.
That's a "normal" behavior, on android when the screen brightness needs to change this lag always appear. I develop an app to turn screen off by changing the brightness and timeout times, and happens this same lag in a various devices seems to be an android issue.
So what I did to "hde" the lag was to add a screen with some info like day, date and time.
But on your case there is no solution yet.
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
nedalnib said:
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
Click to expand...
Click to collapse
Because camera change the screen brightness, the problem is in changing screen brightness and not the action that you are performing.
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
nedalnib said:
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
Click to expand...
Click to collapse
That one I don't know for sure, but I think that can be due to the way the it turn the device.
Double tap is controlled by "lockscreen app/kernel", the power button and fingerprint it android native code and kernel, can be that but just htc knows!
Did you tried to ask then about that in twitter or via support emaill?
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
nedalnib said:
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
Click to expand...
Click to collapse
Hum, nice ideia.
Ok, let us know what they answer

Improve face unlock

Anyone have problem with face unlock about bad angles or not working under bright sunlight! Just set up face unlock under direct sunlight! make sure sunlight sight direct into your face when setting up. Hope that's helpful, it works for me at least
Ps: if you are wearing glasses, put them on when setup.
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Sent from my Pixel 4 XL using Tapatalk
samep said:
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
your problems is totally different with what I mean to. However, It think your problem could be from software or setting. you would reset your phone. And if that keep going, using google warranty is best choice.
nguaogioi said:
your problems is totally different with what I mean to. However, It think your problem could be from software or setting. you would reset your phone. And if that keep going, using google warranty is best choice.
Click to expand...
Click to collapse
Thanks. I should talk to Google Pixel support again. I've been reluctant since they couldn't resolve an issue with Google Home app. They referred me to Google Home app support but they kept getting stuck on the fact they support hardware, not the app. I could link Google and Philips Hue but couldn't add Philips Hue to Google Home app. Failing every time.
Long story but the mobile apps kept telling me that that there was an issue getting provider information for Philips Hue. Yet it went through all the steps and failed at the end, never adding Philips Hue. This once worked until it stopped; nothing I was doing was working, even asking Google and Philips for support was pointless with them refusing to talk to each other or continue support with me until resolution. One day my phone had a notification to control my lights and the linking and final step worked that time. I followed the notification and seemingly skipped several steps I've went through to failure but this time everything went as expected and I can control my lights again. Finally! What was the issue? Google won't say but I suspect they discovered it long after I gave up. Months!
I've seen face unlock improvements in the notes of the monthly updates so I've thought Google is aware but like before, not on my timetable. Low priority. With my past slate now clean, start a new one.
Sent from my Pixel 4 XL using Tapatalk
samep said:
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Click to expand...
Click to collapse
The issue you explained about the seemingly random pin requirement is actually not an issue at all. It's coded into the software as an extra security measure. If you lock your phone and do not unlock it for XXX amount of time (eg. 1 hour) then the phone requires your pin or pattern to verify its still you and your phone hasn't been physically compromised. The other trigger for this happening is at or around 6 hours since the last time your pin was physically entered, it will require you to enter it for the same reasons I listed before. Using face unlock doesn't reset the 6 hours, only physically entering your pin code will.
Hope this helps you understand a little better what's going on with your phone. We all have the same thing happen to us, just most don't notice it when it happens.
1dopewrx05 said:
The issue you explained about the seemingly random pin requirement is actually not an issue at all. It's coded into the software as an extra security measure. If you lock your phone and do not unlock it for XXX amount of time (eg. 1 hour) then the phone requires your pin or pattern to verify its still you and your phone hasn't been physically compromised. The other trigger for this happening is at or around 6 hours since the last time your pin was physically entered, it will require you to enter it for the same reasons I listed before. Using face unlock doesn't reset the 6 hours, only physically entering your pin code will.
Hope this helps you understand a little better what's going on with your phone. We all have the same thing happen to us, just most don't notice it when it happens.
Click to expand...
Click to collapse
Your hour or six a guess, estimation or actual?
What you described seems true but my use would likely indicate more quiring for PIN than I experience. Just asking.
But if this is intent, I don't agree PIN is added security. Sure face ID can be duped in many ways but at the very least what I'd prefer is safe zone like home where face unlock never dupes to PIN or added security. As I recall, total unlock is only option for designated safe zone like home, unless considering Bluetooth device which I don't prefer unless it can distinguish my Fitbit Versa 2 watch is very near and worn?
Surely there's less invasive methods users can deploy to not be so inconvenienced at home. I've even seen this at work with my wife's iPhone X. More choices seems a logical approach to consider. Why hasn't it?
Phone on charger just now, after just talking to Google Assistant, give a smart home command it interprets correctly, the smart assistant says sure, after you unlock your phone. I dismiss the Google Assistant and promptly unlock my phone without the stupid PIN. Not being very user friendly. I'm under the impression many developers don't just use the device and rethink their intents to be most user friendly.
Sent from my Pixel 4 XL using Tapatalk
I feel like I don't see this message more than twice a week... which certainly goes against the every 6 hours idea. My impression was that sometimes movement or Soli will wake it up and it sees something it thinks is a face but it can't unlock with it. If it sees this enough, it may prompt for a PIN unlock with the different message. But sometimes, I think I see this message taking it out of my pocket... where it can't possibly see a face. But maybe it saw part of my face as I was putting it in. It would be interesting to know what the actual rules are regarding this.
I know that when I have the screen upside down, the screen wakes but gives me time to get it upright. Seconds. I don't recall seeing this fail me, thankfully.
I don't have much or any of the Soli features enabled but have screen tap to wake and skip unlock screen enabled.
I've wondered if having the generic stand was causing random face unlock errors but reach for phone is disabled. And I've tried placing my screen down flat instead of the stand and still got prompts to unlock with PIN.
Sometimes I grab my phone and tap to wake doesn't work. But it doesn't mean I get a prompt for PIN every time either. Yesterday, I tapped on the screen repeatedly and it woke and unlocked when it recognized my face. Maybe it's a latent response but I'm usually using the power button to wake by then.
Sent from my Pixel 4 XL using Tapatalk
So I did a chat with Pixel support today.
For the issues with frequent queries for PIN and Voice Assistant asking me to unlock my phone first, the agent had me delete storage and cache for Google and Phone app, delete face unlock and add it back. Reboot phone and get back with them if this doesn't help.
The agent indicated there's not a timer that cannot be reset with unlock that would naturally challenge for PIN after counting down. His advice is to do the above for that issue. The face unlock is suspect. I hadn't done this until today. For kicks, I tried it outside in daylight though the agent didn't recommend this idea. Fwiw, I can unlock my phone in the dark but maybe daylight helps better see contours of the face.
I have a case number to chat again if this continues. Agent says it shouldn't reoccur.
Sent from my Pixel 4 XL using Tapatalk
I only have a basic understanding of how face unlock works... but from what I understand it uses an IR dot projector and two IR cameras to stereoscopically sense the depth of your face. This is why it works in the dark to begin with and based on this, I would think direct sunlight would be a detriment rather than a boon in this sensing method. But it may not have any effect at all as I don't know exactly how the sun and the dot projector overlap in wavelength and strength.
Having a "bad" face calibration might explain it as the phone is more often unconfident about it being your face. So it triggers more failures which prompts the increased security message.
jljtgr said:
I only have a basic understanding of how face unlock works... but from what I understand it uses an IR dot projector and two IR cameras to stereoscopically sense the depth of your face. This is why it works in the dark to begin with and based on this, I would think direct sunlight would be a detriment rather than a boon in this sensing method. But it may not have any effect at all as I don't know exactly how the sun and the dot projector overlap in wavelength and strength.
Having a "bad" face calibration might explain it as the phone is more often unconfident about it being your face. So it triggers more failures which prompts the increased security message.
Click to expand...
Click to collapse
Agreed. It's unknown if added light is a help, hindrance or placebo. But the agent seemed confident just replacing the face unlock would solve my issues.
Not all of my issues sounded familiar was the reason for suggested extra storage wipes and reboot.
Sent from my Pixel 4 XL using Tapatalk
I spoke from my experience. Before that if i will to unlock i have to keep it direct to my face as the right distance or angles and it hardly work with changing light conditions like under direct sunlight. But after set up with aid from sunlight i could say it work quick and more reliable as my iphone xr even in dark or direct sunlight.
I dont know if that is hardware or software problems.
73 hours of uptime. Random PIN for added security prompt has returned when Google Pixel support said it shouldn't after deleting and adding face unlock.
Taking my case ID back to Pixel support. I'm not sure the agent was right about face unlock not occasionally duping to PIN unlock. Very annoying if this is intended or not.
72 hour bug?
Sent from my Pixel 4 XL using Tapatalk
So my Pixel 4 XL face unlock did the same prompt for pin after another 72 hours. No reboot; no error or explanation why other than added security. I'm at 146 hours uptime.
I asked Pixel support again about this. They're researching but want me to do a factory reset now and get back to them.
Sent from my PH-1 using Tapatalk

OnePlus 8T KB2003 Model - fingerprint issue

Hello,
I have this phone for near 1 year and I always had this problem.
The problem is not happening very often but it happens by time on time.
It was happening more often before, when the phone stays with locked screen for a longer period.
But now it happens whenever it wants and I can't understand what could be the issue.
Maybe some process is failing by my opinion.
So the problem is that sometimes when I put my finger on the fingerprint icon on the screen while the phone is locked, nothing is happening, the fingerprint icon is not active and it doesn't read my finger. So I need to enter my pincode, the fingerprint sensor is just not working at all. When I unlock the phone with pincode and then lock it, the fingerprint is now working, until sometime later.
I'll be very thankful if someone can help me with this.
Thank you!
AndroidIsTheBestt said:
Hello,
I have this phone for near 1 year and I always had this problem.
The problem is not happening very often but it happens by time on time.
It was happening more often before, when the phone stays with locked screen for a longer period.
But now it happens whenever it wants and I can't understand what could be the issue.
Maybe some process is failing by my opinion.
So the problem is that sometimes when I put my finger on the fingerprint icon on the screen while the phone is locked, nothing is happening, the fingerprint icon is not active and it doesn't read my finger. So I need to enter my pincode, the fingerprint sensor is just not working at all. When I unlock the phone with pincode and then lock it, the fingerprint is now working, until sometime later.
I'll be very thankful if someone can help me with this.
Thank you!
Click to expand...
Click to collapse
I believe that's by design. After a certain amount of time you're asked to login using you password. Once you've entered your password the timer gets reset.
I've seen this on other phones and it also happens on both of my 8Ts.
BillGoss said:
I believe that's by design. After a certain amount of time you're asked to login using you password. Once you've entered your password the timer gets reset.
I've seen this on other phones and it also happens on both of my 8Ts.
Click to expand...
Click to collapse
Thank you, Bill. This kinda answers my question, too bad there is no security option to define if you want this or no.
On my OP 8T the fingerprint stopped working well after gluing the protective glass. Without the glass it works fine.

Categories

Resources