Ask / Submit

[BUG] fingerprint HAL failure results in enrolled fingers lost from SFOS side

Tracked by Jolla (In release)

asked 2019-01-07 01:13:30 +0200

Keeper-of-the-Keys gravatar image

updated 2019-01-07 20:10:36 +0200

There are several questions open about fingerprint sensors stopping to work, since the level of involvement of Jolla Sailors is unclear here is (what I hope is) a concise bugreport/summary of these questions.

As far as I gather the sequence of events is:

  1. fpslave fails for some reason or other
  2. SFOS tries to recover/restart the service but fails
  3. after manual restart/device restart the service runs again but enrolled fingers are no longer valid on the SFOS side of things (they are still enrolled in the fingerprint scanner as evidenced by the fact that a reset is needed if/when 5 finger enrollment is reached).

Some of the questions involved:

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted

answered 2019-01-17 11:42:33 +0200

spiiroin gravatar image

Thanks for reporting

Looks like the cause is: If slave startup bumps into problems after reading cached fingerprint data, but before having had a chance to validate the cache content -> the data gets discarded as invalid -> hal init hiccups cause loss of data.

Note that in devices where underlying hal implements working fingerprint template enumeration functionality, the lost data can be automatically recreated and the issue witch cache management gets hidden - however Xperia X is one of those devices where enumeration does not work.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2019-01-07 01:13:30 +0200

Seen: 339 times

Last updated: Jan 17 '19