Second factor PIN doesn't always open/register the "enter" key

UseLinux

I've been having some problems with my up-to-date Pixel 6a using fingerprint + 2nd factor PIN.

The "enter" key, meaning the arrow pointing at the bottom right corner doesn't always unlock the phone when I type my PIN correctly and press it. The numbers have worked fine always, and I've been able to resolve the problem by shutting down the screen and trying again.

It also doesn't happen everytime, but I've had it at least a few times now in the last couple of days or so..

Anyone else noticing same problematic bug/behaviour on any of their phones with GrapheneOS and fingerprint+2nd factor PIN?

phone-company

UseLinux do you use a screensaver glass or something like that?

Bimmy

UseLinux

Me too for Pixel 8. I believe I once even had it with primary unlock, with low certainty.

UseLinux

phone-company
Nope, no screen protectors on the phone.

phone-company

In other Situation do you have same dissfunction?

other8026

I used to notice some weird stuff like that when switching profiles, so I am in the habit of dismissing the keyboard then swiping up to unlock. I don't encounter any issues anymore. What you're describing here sounds like some upstream issue, probably when using a secondary user profile? Maybe issues are more common right after switching to another profile?

UseLinux

other8026
I'm actually using ONLY the main/owner profile also as @Lilac6044

Lilac6044

Hi, I also experience this occasionally. I only use the main/owner profile, but I have never given it much thought as when it doesn't register the enter key, I quickly press the lock button and then it will register then enter key when I press it the second time

UseLinux

Interesting. Is this affecting all Pixel models or just some? What could be the underlying reason then, hmm.. Any other guesses @other8026 as it's probably not something to do with a secondary user profile (?).

Lilac6044 Exhort14 What Pixel model are you using if you don't mind me asking and sharing with everyone.

Exhort14

UseLinux +1 to @Lilac6044 and @UseLinux. I do use a screen protector, but otherwise same setup. Owner only use.

overstep

i have noticed this behaviour when i scan my fingerprint as the screen is about to turn off

other8026

UseLinux only thing I can think of would be you're using a different keyboard to log in? If so, when it happens again you can try tapping the globe in the bottom right hand corner to switch to a different keyboard.

Lilac6044

UseLinux Hi, I am using P9

NetRunner88

I have the same, I don't know since when (p6a current 2025081400 with a cheap screen protector)
But it is sometimes, I do not know how to trigger the behaviour. As it doesnt annoy me too much I just off/on screen again and it works ..

If someone know how to trigger that it will be great

Lilac6044

other8026 Cannot speak for OP but the issue happens with me using the default keyboard.

Exhort14

other8026 - there isn't an option to switch to a different keyboard here. I suppose I could switch to the password screen, swap, and then try again... But it usually works for me the next time anyway. Is the keyboard related to the pin code submit button?

The workflow is:
Fingerprint ✅
Enter 8 Digit Pin Code ✅
Press Button to Submit Pin Code ❌
Returns to Default Lock Screen

SETUP
9 pro
Latest stable release (auto updates ON)
Futo keyboard (edit-no issues with submitting passwords after reboot)
Fingerprint unlock with 2nd factor pin (scrambling and privacy toggles both ON)
Screen protector applied
screen protection touch mode ON

UseLinux

other8026 I'm using the default keyboard strangely enough. This earlier mentioned "bug" haven't happened in a while now though for me personally.. Other peoples' mileage may vary.

graphuser

Hello,

I have noticed the same issue on P8 with a main profile, a private space and Gboard. This has happened since the upgrade to Android 16.

Interestingly entering a wrong PIN and pressing enter logs a wrong attempt, but entering the right PIN and enter does not unlock. Going back to the lock screen and trying again does work.

No screen protector or any other funky settings.

GOS noted here that the unlock code significantly changed and so that is likely due to this.

UseLinux

Sorry for bumping this old-ish thread but I'm still having these same kind of problems from time to time, very infrequently thou.. But no worries, I just turn off the screen, try again and it works.

By the way, does it happen at all for Pixel 10/10 Pro models, has there been any talk about this kind of bug behaviour in the experimental releases?