Hello all, once again.
As the title says, I am being prompted for my passcode even though I set up fingerprint unlock. Is this a normal behavior? I can unlock my phone if I scan my finger once again (as I will show in the attached video). Is there a way to simply disable this behavior if I have already unlocked my phone with the passcode once after booting?
Below it’s a video with the issue:
In order to wake up the screen (open the lock screen). Double tap the screen, or press properly power switch. After that read fingerprint.
So it doesn’t just unlock the device while the screen is off? Back on Android I am only prompted for the code unlock if this is the first lock after boot. Once that’s out, I can simply unlock my phone with my fingerprint straight away unless I turn my phone off/restart it.
You’re right, the message could/should mention something like ‘or hold your finger on the fingerprint reader’.
@Keto, what do you think about changing the string?
That’s a solution, but it is still a bit confusing. Like, when I touch the power button it is vibrating, so I’m assuming it’s definitely reading my fingerprint. However, the screen only unlocks if I touch the fingerprint reader once again - which I find a bit weird too.
I believe that idea is that you can peek lock screen without opening the phone.
Yea, but I am only peeking the numpad :)) as you can see in the video. I still have to swipe sideways once in order to properly peek on the lockscreen.
I think it goes like this: people were saying that the way the fingerprint reader works is kind of pointless, but when you think about it a bit more, let’s say you just want to press the button once to check the time and look at the lock screen—how are you supposed to do that if your fingerprint gets instantly recognized every single time? That becomes annoying too.
Of course, you’re right as well, because to unlock the phone with your fingerprint, you basically have to scan your finger twice. I think the solution would either be to leave it as it is, or set a specific timing threshold for the fingerprint reader.
If the user only wants to go to the lock screen, they could press the button for something like a millisecond, so the fingerprint reader wouldn’t kick in. But if the user actually wants to unlock the phone with their fingerprint in one go, they could hold their finger there slightly longer than that threshold, and the phone would take them straight to the home screen.
Yeah, I think that would probably be the best middle ground. Does anyone else have another idea?
The latter is a good idea for me too. Especially as, the way I see it currently works, pressing the button already gets you to the lock screen. Only taping my finger against the fingerprint reader brings me the numpad.
That is the way it works on SFOS, since years.
Please. Just try to get used for aAbitur of time* and do not come up with: but I am used to that and I want it like this.
I do prefer the way it is!
Yea, I don’t disagree with you. You’ve been on SFOS since years, and I’ve been on Android since years. You are used to some stuff working the way it works, and I am used with some stuff the way it works there. I am not going to go and mention all the stuff that “iS cOmPleTeLY bRoKeN” like the other user(s) did in various threads across this forum and bash everyone around - because I know that.
My only question is just: Why? Why does it have to be like that? Wouldn’t there be an easier option to do exactly the same thing?
(Disclaimer: I assumed you were not being sarcastic in your response)
The fingerprint reader can regognize a touch as well. So it would be possible, for example, to make it turn on the screen if you just touch it and then unlock the screen if you actually press on it. You could also just make the behaviour configurable. For me, the “press it twice”-Interaction is (and has always been) a bit of an annoyance - it’s individual, I know, but I never press the lock button if I just want to glance at the screen. I always double-tap it for that.
Because this annoys me (slightly) on a regular basis, I did a bit of research on modifying the behaviour but if I understand it correctly, it cannot really be patched at the user level. And (I think) the fingerprint daemon would have to run more or less continually to enable this behaviour because (again, I think) at the moment, the first press of the button just wakes up the system and that is what then fires up the fingerprint reading which probably also involves some libhybris-magic, so there is a bit of a delay between the screen waking up and the fingerprint reader actually being ready to scan a print. So, enabling the “unlock immediately”-behaviour would probably be rather more involved than just adding an option to change the flow in the UI and involve some more deep work. However, more knowledgeable developers, please correct my understanding.
Depends on your settings. Go to Settings -> Device Locking and the first setting should set how long the device waits before it locks the phone. You can turn it off, or to Manual only (it asks for the fingerprint/PIN only if you double press the Power Button and the phone will vibrate once when successfully locked). If you set it up with time from the list, you can open the phone without the fingerprint/PIN with in the set time period and after that you need to provide either fingerprint or PIN.
It could probably mention the fingerprint option, but that doesn’t seem like real solution to the problem.
I am too a bit annoyed by the power key / fingerprint reader behavior, but also not sure how it should behave, or know the technical details on what kind of behavior is easily possible 
Either way, the fingerprint reader recognises fingerprints whether the device is locked or unlocked. Try turning on the screen by holding a finger you didn’t scan on the reader - it won’t do anything. The screen only turns on if the fingerprint reader recognises the fingerprint.
No, that still doesn’t fix my issue. I mean, it kinda does, but now the screen can be bypassed with just a swipe by anyone, rendering the fingerprint reading process useless in itself. If I actually lock the phone by pressing the lock button twice, then I am prompted again for the code/fingerprint, which was the problem in the first place.
I do however get what would be the functionality of this whole thing. So here’s an idea:
How does that sound?
Not bad!
Did you try that with power button (first press)?
Exactly as you describe…
At first (after having been taken away the double-tap to wake on Sony) I was also irritated by the fpd behaviour, but now I do like it.
With JP26 you might just use double-tap and/or power button once-press and then fpd.
Just tested it out.
Not sure if I mentioned that before but yes, when I press the power button it takes me to the lockscreen. Only when I scan my finger it takes me to the numpad.
Edit: I initially thought that this was some sort of 2FA thingy (i.e. it checks both what you know and what you have before letting you in). But nope, you just ought to have your finger scanned twice to get through.
Yes, that’s exactly what I do to unlock the screen currently (albeit there’s indeed a bit of a delay between the taps which slows the whole unlock process down a bit). What I said is that when I tap it once (or rest my finger as you said), it takes me to the numpad where I can insert my code to unlock the screen. If I actually press the lock button, then it takes me to the lockscreen. If you want I can make another video with the whole process if I did not make myself so clear 
Yep, that’s exactly what I was saying. And when you have the numpad on the screen you can still unlock it with the fingerprint - like, if that happens then why are you bringing that up anyway, glad I made myself clear I guess.