FP5 Fingerprint Sensor - further customization needed?

[yvmuell]

Continuing the discussion from Instant fingerprint unlock is the default and no way to disable it:

@PSZ

Maybe what’s frustrating me is slightly different, though, because at least once or twice, I have still ended up locking the phone, and then having it unlocked again before it lands in my pocket. This seems to be because I have it set to show the time when I lift the screen, and that counts as waking the phone.

So after the update and you have set the new toggle reg the fingerprint behaviour to off, i.e. when you touch the sensor it should not unlock, however because of the movement to put it back in the pocket, lift to wake is activating/showing the lock screen and therefore the fingerprint reader is active and unlocking when you touch it? Just to ensure I understand you correctly.

For me lift to wake in general is too sensitive so I have it turned off, will see if I can enable it today and test it.

This would bring us probably to this request

@Nabalazs

Please make it so that I have to actually press the button to unlock the phone, and it should read my finger while I’m pressing it.

Currently tap to wake is also no perfect alternative to circumvent this

FP5 Tap to wake wakes up phone in pocket

Concerning battery life I have the feeling that tap to wake also activates in my pocket. It happens too often that I fish my phone from my pocket and the screen is on, with … (a whole row of dots) as if a child has been trying to unlock my pin code. I’ve turned off tap to wake for now…

Overall a new topic I think, what I opened now for further discussion.

@all who see issues, please contactsupport

[OldRoutard]

In my experience the use of a flip case is ideal. Only the proximity sensor is necessary to turn the phone on and off, and the fprint sensor can be set to not function when the phone is turned off.

To judge from users’ experience recounted in the forum, the less use is made of the power button (for turning on and off), the better.

Thanks to the power menu access in the notifications pane, I now only use mine to actually turn the phone on, and that’s rare, since I hardly ever turn it off.

[PSZ]

@yvmuell

So after the update and you have set the new toggle reg the fingerprint behaviour to off, i.e. when you touch the sensor it should not unlock, however because of the movement to put it back in the pocket, lift to wake is activating/showing the lock screen and therefore the fingerprint reader is active and unlocking when you touch it? Just to ensure I understand you correctly.

For me lift to wake in general is too sensitive so I have it turned off, will see if I can enable it today and test it.

Thanks; yes, that is correct. Sorry for the delay in checking back in.
My experience, at least, is that Lift to Wake kicks in, and then the the system automatically checks for a fingerprint there. Because I first set it to use the finger that most conveniently finds that button, it very frequently unlocks accidentally.

Another solution is just to be more selective in which fingerprints are used, which is a partial solution. That makes the gesture more awkward, though, and I still get incorrect scans from the finger that isn’t registered, potentially triggering it to require the code again.

As I think I said in my original comment, it isn’t a huge deal, and I would have been content with the phone without a fingerprint scan feature at all. The fact that it is there and potentially problematic, though, makes the phone design feel a bit more messy.

[OldRoutard]

@PSZ

I would have been content with the phone without a fingerprint scan feature at all.

You can achieve this simply by deleting your registered fingerprints. If no fingers are registered then the sensor will not work.

However, you may find that certain higher-security apps (notably banking) require the use of the sensor.

[PSZ]

Yes, disabling it entirely is the next step, if it does end up being more frustrating than it is worth.
What seems like a simple solution, in my mind at least, would be an option to only have it scan when the button is actually pressed. Maybe there’s extra problems there that aren’t clear from where I’m sitting, though.