Mostly I turn the screen on by pressing power button (aka fp scanner).
Sometimes the fingerprint scanner doesn’t work then at all.
So I have to turn the screen off and then turn on again, and only then the fingerprint scanner works and I can unlock the phone.
Also enabling LED patterns finally allowed me to confirm what I was suspecting. With screen turned off if you put your finger on the sensor it will only turn the screen on if it recognises the fingerprint. And even though it recognised the fingerprint it will not unlock the phone, you still need to put the finger on the sensor again. This is kind of stupid, because often it won’t recognise it for the second time, even though it did just 2 seconds before.
So shouldn’t it unlock the screen immediately after it recognises a valid fingerprint?
Well, it is… Just like requiring to manually enter the security code two times in a row during boot. But I wish SFOS only had such problems 
Of course it should. There is absolutely no reason to show an unlock screen after recognizing a valid fingerprint. To compare, iOS turns on the screen and unlocks the device at once if a valid fingerprint is recognized.
I can confirm. That is also my experience with the fingerprint scanner (on Xperia 10 III).
Also sometimes it doesn’t seem to scan, and 2-3 seconds later it prompts with unidentified print.
While this behavior is somewhat annoying, i’m actually surprised how well the scanner works compared to my earlier Xperia X and XA2.
After a few succesful unlockings fingerprint didn’t work anymore. Tried it a second time: same story. It worked a few times, had to tap my finger several times quite firmly against the button. Then it stopped working… It’s not a key feature to me, so I leave it.
I created a bug report for the fingerprint sensor stopping to work, so this topic can be just for discussion of the improvement, and not the bug.
Another consideration regarding fingerprint scanning, if the first touch immediately unlocks:
accidental unwitting unlocking.
I’ve already posted that this is not required.
If only Jolla could take a look into it and implement simple 60 seconds caching in Linux kernel keyring via keyctl, just like cryptsetup in Linux already does it.
PS I’m at the point where I just stop caring.
That was my original suggestion in the first post, just some people wanted the sensor to work with screen off too
My suggestion is for the sensor to be inactive with screen off, and only start scanning when you press the power butto, same behaviour as with my XZ1 Compact on Android. This prevents accidental unlocks, allows you to see lockscreen (by lifting your finger) and is much faster than current setup on SFOS.
Fine, but the question is how many clicks is that fragile Power button expected to withstand. Half of it is the sensor, so its clickable part is probably much less sturdy than “full” button. In general there are problems with buttons which require dozens or hundreds of daily clicks - sooner or later they break. Like home buttons on iPhones, which were one of the most popular replacement parts. Now they’re sensor-only, no clickable part at all… Whereas you’re proposing the opposite way…
And, one again: maybe we should first check how much current does this sensor draw when the screen is off. If its power consumption is negligible (say some microamperes) then why bother at all to turn it off and require button clicks? Note that it is a different thing than requirement to scan fingerprint twice, which I fully agree is annoying and should be changed.
I’m pretty sure Sony engineers know their job.
Xperia X has the same power button+sensor and there were no mass problems with it. Hell, I have one and it is still going strong.
My kind wish is to make this configurable and keep pushing the power button optional. As it is stated above, buttons wear, and i would save mine as long as possible.
Yeah, I suggested that because that was the default on multiple generations of Sony phones, and was super nice to use. My XZ1c also shows no problems with the sensor. So not sure if it really is dangerous, but if it could be configurable, then even better!
Hmm… I did mcetool --disable-led-pattern=PatternScanningFingerprint and now I can’t turn it of.
Obviously I tried mcetool --disable-led-pattern=PatternScanningFingerprint and I also tried mcetool --deactivate-led-pattern=PatternScanningFingerprint including reboot but nothing helps. Green light is permanently lit when screen is of. Hints anyone?
Never mind. It went out when I deleted the fingerprint and reinstalled it.
Sure they do.
You need to restart mce. In terminal type systemctl restart mce or reboot the device.
That is also known as “the KDE Way” of doing things…
meaning:
just add a whole bunch of settings so Everyone can do his own thing:joy:
While too high power consumption of the 10 III is what worries me a lot, after months of use I came to the conclusion that the most annoying thing about this device is its fingerprint sensor experience. It really drives me nuts the way it falls asleep / freezes / locks up / whatever every now and then. And this is where - again - the XA2 Ultra provides a wholly different (excellent) experience. Despite the XA2U itself being quite sluggish, its fingerprint sensor works every single time, 100/100. It didn’t happen a single time for it to fall asleep or stop reacting to touch the way the 10 III sensor does all the time. So if I had to nominate something for most urgent improvement, it’d probably be that freakin’ annoying fingerprint sensor.
agree, it’s annoying on whole another level
In 10ii I have similar problems too some times. Most of times it helps to restart fingerprint sensor service from Settings → Utilities. Very few times I had to restart the phone, since the service was working with high CPU and the phone was getting warm. As I understand the problem is the “low memory kill” feature.