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

[Bug] Broken display timeout after receiveing notification [released]

Tracked by Jolla (In release)

asked 2016-08-09 23:40:48 +0300

Alex gravatar image

updated 2016-08-10 12:31:51 +0300

After receiving a new notification and unlocking the device the display will blank/go to standby even though it shouldn't while beeing used.

How to reproduce

  1. Lock the device so that the display is blank
  2. Receive a notification, e.g. a SMS message or E-Mail notification
  3. After receiving this notification the display turns on and shows you the message
  4. Now wait about 1 to 3 seconds and unlock the device while the message is displayed (so the display is still turned on) e.g. by swiping to the right (so you get to the events view) - also don't touch the display after unlocking anymore
  5. After 'unlocking' your device the display will nevertheless go to standby even though the touchscreen has been used, maybe you need to wait a few seconds to see it going blank

Additional information

It also seems that after reproducing this bug the device won't respect the display timeout time set in Settings > Display anymore (until locking it manually once!) since the display of my Jolla will stay on forever after reproduction (timeout is set to 30 seconds).

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by Alex
close date 2017-10-12 18:35:53.110837


Which device? I can't reproduce it on my Jolla1.

atlochowski ( 2016-08-09 23:56:08 +0300 )edit

I am using the Jolla 1. At which part you are unable to reproduce? Your display will stay on?

Alex ( 2016-08-09 23:57:38 +0300 )edit

My display going to blank without any problem. Checked on Jolla C and Jolla1 and it's working ok for me.

atlochowski ( 2016-08-10 00:04:36 +0300 )edit

Yes but the display should NOT directly turn off while you are using your device - the bug is that the display turns off even though you are using your phone. :D

Alex ( 2016-08-10 00:08:23 +0300 )edit

never happened to me.

atlochowski ( 2016-08-10 00:09:36 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2016-08-10 14:35:37 +0300

spiiroin gravatar image

This could have some relation to known issue: Standing rule "there is no user activity in lock screen" + sfos2 doing more things without declaring exit from lock screen context -> the temporary display on states like the ones due to email/sms notification do not get canceled due to user activity -> there are situations where display blanks unexpectedly.

The after effect where display stays on forever would be something new though.

@Alex: For reproducing it would be helpful to know:

  • When blanking in (1): Did you use power key or top swipe? What was shown on screen before blanking - some application, app grid, something else?
  • When unblanking in (3): Was the lock screen shown, or some application?
edit flag offensive delete publish link more


@spiiroin Thanks for your answer. :)

  • Iirc I used the top menu to lock the screen. The lastly shown screen should be either the homescreen or the events view since I configured my top swipe gesture to close applications. It is also possible that the display timed out and locked itself (but unfortunately I don't remember this exactly anymore).
  • After/While receving the notification the lock screen was shown and I swiped to the events view.

I have to admit that the above steps for reproduction are not working reliable. I experimented some days to find some reliable steps to reproduce this behaviour but was not successful till now.

I will update this post once I find some good steps for reproduction and will let you know.

Alex ( 2016-08-15 14:08:15 +0300 )edit

answered 2017-10-12 18:35:27 +0300

Alex gravatar image

This bug has been fixed with SailfishOS

edit flag offensive delete publish link more

Question tools



Asked: 2016-08-09 23:40:48 +0300

Seen: 257 times

Last updated: Oct 12 '17