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

Display turns off while recording video when activated from lockscreen

Tracked by Jolla (In release)

asked 2018-03-13 02:26:47 +0300

naytsyrhc gravatar image

updated 2018-03-13 02:28:14 +0300

Today I experienced a possible bug for the first time. When I activate the camera from lock-screen with the newly introduced swipe up gesture from lock-screen (without entering a lock code) and starting a video recording, the display will blank after 30 seconds (as configured in settings I presume) and lock the device again. Unfortunately the video recording is stopped and no video is stored. If I tap on the screen while recording and manually stop the recording, everything is fine (i.e. screen doesn't blank).

I'm on a community build so this may be a bug of this particular build, but maybe it's same behaviour on official image and/or Jolla 1/JollaC/Intex?

edit retag flag offensive close delete


The same kind of thing happens when browsing through a playlist from the lockscreen. Pressing the button "next" does not delay blanking and eventually the screen turns black again.

pstassen ( 2018-03-14 10:29:12 +0300 )edit

@ptassen: That is yet another exception² as the media controls live in a view where "interaction is not expected" -> Fix for that already exists and should be available in sfos >= 2.2.0.x.

spiiroin ( 2018-03-14 10:55:27 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2018-03-14 09:24:39 +0300

spiiroin gravatar image

updated 2018-03-21 09:19:11 +0300

We have age old (all the way from maemo/meego devices) rule that having lockscreen active requires that: Display is blanked faster than normally (by default 10 seconds instead of 30 seconds), user activity does not postpone blanking, and blanking pause requests are ignored (= applications can't delay blanking).

Having device unlock prompt occur in the context where lockscreen is active (sfos1 -> sfos2) meant that in order for users to have time to enter the unlock code, blanking timers are reset when lockscreen is in a state where interaction with user is expected.

After it became possible for select applications like the camera to be launched on top of lockscreen, it became necessary also to switch from 10s blanking delay to longer (30s) one.

What still remains is cases like having application on top of lockscreen, performing useful function that does not require constant user interaction - e.g. camera application in video recording mode. This is a bit troublesome obstacle to work around as (to avoid unwanted hiccups) it requires more state data to be shared between lipstick, mce and applications.

Filed an internal ticket about this.

EDIT: Should be fixed in sfos >= 2.2.0.x

edit flag offensive delete publish link more



Thanks for the feedback and hopefully a fix in some near future ;-)

naytsyrhc ( 2018-03-14 14:07:15 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2018-03-13 02:26:47 +0300

Seen: 320 times

Last updated: Mar 21 '18