Fingerprint misbehavin'

Emphrath

Hey folks ! I had a couple UT phones before but Pixel 3a works so good I had no idea this was actually a thing with UT ^^ Annoying little bug though: fingerprint reader, while working, does so very inconsistently. When it works, it works. But sometimes - and I can't figure out the pattern here - only my code will unlock the phone. I would then unlock it, re-lock it, and then, fingerprint reader works. Any idea why ? Cheers and long life to anyone contributing to this awesome OS !

kugiigi

@emphrath I have an S10 and I also can't figure out the pattern of its behavior. My guess is that it's kind of a messed up version of requiring the pin/password after some time of inactivity. On Android it happens but happens a lot less often. I haven't found the code for this behavior though so not really sure.

Moem

@emphrath My Oneplus 5T behaves similarly.

arubislander

@emphrath the only time my Pixel 3a insists on having the pin entered is the first time after a reboot. Otherwise the fingerprint reader works every time.

Ian

@emphrath My Volla Phone X exhibits similar behaviour. I put it down to 'accidental' touching of the fingerprint reader with a finger other than the one I use for unlocking. The phone sees this as an attemot by someone else to unlock it and draws my attention to this by insisting on PIN entry. I see it as a useful feature.

dizzy

@emphrath its the same on mine. No pattern what I can see. I think "fingerprint unlock" working should be changed to partially. The same goes for bluetooth.
Dont get me wrong, Im fine with it not working 100% and I understand it too but it should not be advertised to be working. Thats all I say.

fredldotme

The fingerprint reader has been improved in accuracy in devel and will have the fix shipped as part of OTA-23. Problem was that it was always active in your pocket, causing the applet responsible for verifying the fingerprint to be confused.

fredldotme

@dizzy Don't know what you're talking about, Bluetooth works pretty well here. Please be more specific, collect logs and let us know in a proper bug report what's not working as intended.

Lakotaubp

@fredldotme Did you maen to post that here?

Keneda

@lakotaubp said in Fingerprint misbehavin':

@fredldotme Did you maen to post that here?

I guess it's a "yes" as :

@dizzy said in Fingerprint misbehavin':

The same goes for bluetooth.

Lakotaubp

@keneda Need to read a bit slower next time

dizzy

@fredldotme Well, a lots of others do know what Im talking about. Just search for it here for example. The last thread about it would probably be "Sound not going through bluetooth headphones". So I would say working partially, not more.

arubislander

@dizzy said in Fingerprint misbehavin':

@fredldotme Well, a lots of others do know what Im talking about. Just search for it here for example. The last thread about it would probably be "Sound not going through bluetooth headphones". So I would say working partially, not more.

I think you misunderstand what is meant when a feature is marked as working 100% on a ported device. It means there are no device specific issues with that feature.
There might still be OS based issues but these would be impacting all devices to a greater or lesser extent. In the case of bluetooth, part of the problem is that, being on 16.04, the bluetooth stack that is shipped on the devices does not support all of the protocols that car systems and Bluetooth speakers use. The situation could see some improvement with the rebasing on 20.04.

dizzy

@arubislander You are right, I did missunderstand that. Thanks for the explaination!