We have moved to a new Sailfish OS Forum. Please start new discussions there.

[3.2.1-3.3.0] Screen unlock with fingerprint does not work before automatic locking timer has elapsed

Tracked by Jolla (In release)

asked 2019-12-12 08:36:01 +0200

sashikknox gravatar image

updated 2020-04-16 13:28:19 +0200

jovirkku gravatar image

Sailfish won't switch from lock screen to home screen with a fingerprint in case automatic locking is configured to happen in 5/10/30/60 minutes or "not in use".

Affected: XA2, XA2 Plus, 10 and possible all devices with a fingerprint sensor.

There is no problem in the following cases:
- if "automatic locking" (of the touch display) is set to "no delay"
- if "automatic locking" (of the touch display) is set to "5/10/30/60 minutes" and the given number of minutes has elapsed from the last user action (so the touch screen was truly locked)

How to reproduce (its seems i found a way how to make this bug occur):

  1. Set an automatic lock time in Settings > Device lock
  2. Open any application (native, or android app)
  3. Turn the screen off by pressing the power button (or close cover), while the app is opened (you shouldn't see home screen or notifications area at this moment)
  4. Press the power button again (or open the case) - the device screen now correctly shows the lock screen
  5. Try to unlock device with your fingerprint. The touch screen is not locked now as the automatic lock time did not pass yet. However, you cannot open the home screen with your fingerprint but you need to swipe the screen. Using the fingerprint sensor now only let's the device vibrate (fingerprint is recognized, but home screen won't show up)

Expected behavior: Home screen is shown after the fingerprint is recognised (be the touch screen locked or not).

NOTE: After step 3 (when the screen is black/blank), if you do not use the Power key but skip step 4 completely, THEN step 5 works fine: the fingerprint gets recognised (vibra) and the home screen appears. No problem at all.

Also affects


EDIT/2020-04-16/jovirkku: 1) Clarified the description 2) Also happens on Xperia 10 3) Note added.

edit retag flag offensive close delete


stupid question, what is timeout? an app or the time-out trigger to turn off the screen?

cemoi71 ( 2019-12-12 12:38:03 +0200 )edit

time out trigger to lock device when screen is off (in device settings)

sashikknox ( 2019-12-12 12:44:40 +0200 )edit

I can reproduce this with my XA2 which has fingerprint + timeout. I can't reproduce this with my XA2 Ultra, which has fingerprint + immediate lock. I can switch the settings and test it again later.

Direc ( 2019-12-12 16:48:32 +0200 )edit

I'm able to reproduce.

However I think this is desired behavior. If you follow the steps and get to 4, you don't need the fingerprint reader to unlock. Just swipe to the left. As the device is not locked yet and the timer to lock the device has not passed. Unlock is A different action compared to the swipe action as that is an action to open the screen.

tneo ( 2019-12-12 17:14:14 +0200 )edit

sorry mates i have an xa2+ too and followed the steps but it's not reproducible.
What has the timeout to do? should we wait a couple of time too? if yes please add it in the steps. i'm really curious. thx

cemoi71 ( 2019-12-12 17:14:47 +0200 )edit

2 Answers

Sort by » oldest newest most voted

answered 2020-04-14 22:00:17 +0200

cemoi71 gravatar image

sorry, it's not really a response but have a similar issue, but not with this reproducibility.
And i had a total lost of service without vibration response totally crashed.
Only way was to restart sfos (forgot the cli command given on upper thread).

Sad that is not possible to restart the service with an utility...

edit flag offensive delete publish link more


found this thread afterwards https://together.jolla.com/question/221983/fingerprint-sensor-stops-working/

cemoi71 ( 2020-04-15 02:02:54 +0200 )edit

answered 2020-04-16 10:00:42 +0200

spiiroin gravatar image

Reproduced according to the provided steps - thanks! I filed internal ticket about this.

It requires that screen is locked but device is not. Which becomes possible when automatic (device) locking with delay is used (vs automatic locking without delay). In which case fingerprint wakeups get ignored due to code shared with handling doubletaps.

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

Question tools



Asked: 2019-12-12 08:36:01 +0200

Seen: 948 times

Last updated: Apr 16 '20