asked 2017-09-20 14:57:21 +0300
If I receive an event and tap the notification while my phone is locked I have to type my code (which is natural), but while entering the code the device turns the screen off, even though i regularly enter new digits. When I wake the screen again I have to start over (and I can no longer go directly to the event source).
answered 2017-09-20 23:29:21 +0300
Looks like a dup of https://together.jolla.com/question/141260/bug-broken-display-timeout-after-receiveing-notification/
This should be fixed in >= 2.1.2
Edit:
This bug has been fixed with SailfishOS 2.1.2.3.
Seems related, but that doesn't describe the issue exactly as I see it. For me the screen blanks only on the device lock screen. If I manage to unlock, ie of I'm fast enough or the device lock isn't active, the screen doesn't blank. It only happens when I type the device lock code and between taps.
Mohjive ( 2017-09-21 03:13:19 +0300 )edit@Mohjive There are loads of issues that boil down to: "User activity does not prolong display blanking while lockscreen is active". In 2.1.2. the rule was augmented with "... and lockscreen does not expect user interaction". Which should mean normal (30 secs to dim + few secs to blank + reset timers on user activity) logic is used within lock code entry, lockscreen camera, etc - instead of the (10 secs to blank + do not reset timers on user activity) that now is used only when lockscreen is showing the basic view with date and time.
Recently it was noticed that pin/puk code entry was still another exception within already exceptional situation and display still blanked abruptly - a separate fix for that was needed.
spiiroin ( 2017-09-21 08:39:33 +0300 )editAsked: 2017-09-20 14:57:21 +0300
Seen: 212 times
Last updated: Oct 12 '17
