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

[bug] Sailfish X display turns off while holding pulley menu [released]

asked 2017-10-17 22:34:56 +0300

lumen gravatar image

When you press power button on Xperia X so you get the screen on (with lock code) or just the screen with time and date (whatever it is called). There is the pulley menu with 3 programmable choices for action. When I pull that menu down and hold it pulled, it will disappear after short time (maybe 8 seconds?). I feel that this is a bug, because a smart phone should be smart enough to wait although user would be slow/dumb one :-)

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by lumen
close date 2018-08-03 12:04:46.426767



Interesting... The same thing occurs, when swipe to left/right is started but not released, aka. finger held in place instead.

I'm not sure if it is a bug or a feature, but to be this is a good thing: it helps in the helpless fight against pocket calls... I vote for feature, actually :)

Direc ( 2017-10-18 00:18:14 +0300 )edit

Happens also on J1 with If the screen turns black during a sideways swipe, you will be taken directly to the home screen or notifications screen the next time you wake up the phone, so it's at least partly a bug.

luen ( 2017-10-18 01:27:52 +0300 )edit

I also note that in the lockscreen shortcuts it should open, say a camera or browser but not let you access cookies, history previously taken photos, it should not ask you for the lock code but allow launchjng of pulley shortcuts for creating new photos (just like iOS does) or websites without saving anything (essentially that shortcut with locked phone will always take you to browser privacy tab) - probably slighly beyond the posted topic but somewhat related to locking security balanced by quick actions, balanced by preventing of pocket gallery show of last night at your mistresses house series.

XFish ( 2017-10-18 05:03:39 +0300 )edit

@XFish Great comment, and I agree how the behaviour should be. That is a separate issue, so please consider searching for a related question or asking a new one. :)

Direc ( 2017-10-18 14:36:02 +0300 )edit

It happens with all my Saifish devices, so I don't consider it a bug.

Actually I consider it a delibrate misuse by the user, I see no real use for making gestures so slowly. You either want to unlock the device or commit some action, or not. If you are too slow, well it's your own fault.

juiceme ( 2017-10-18 17:51:43 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-10-18 17:39:20 +0300

spiiroin gravatar image

The rule of thumb is: In lockscreen view user actions do not postpone display blanking. So, unless you escape the lockscreen (where date & time is shown), the display will blank in 10 seconds. This is done to minimize chances for things like: For whatever reason/fault display wakes up in pocket and then stays on perpetually due to capacitive touch registering through cloth.

There are exceptions like: Entering device lock code, invoking camera without unlocking, pin/puk code entry, ... possibly the pull down menu could count as one too as it requires proper swipe to trigger (i.e. not just random touch points getting through).

edit flag offensive delete publish link more



It makes sense. Then I guess that coming to the home screen the next time you wake up the phone (bypassing the lock screen), if you have swiped sideways while the display turned off, is a bug?

luen ( 2017-10-18 17:44:54 +0300 )edit

@luen If not an obvious bug, at least it is a shadowy corner case: User is performing unlock gesture - pending only the final release event. Blanking screen basically equates to touch release -> the unlock gesture should be finalized and acted on. And automated timer based blanking should not immediately (re)activate lockscreen. But on the other hand deactivating lockscreen while display is off should not occur ...

spiiroin ( 2017-10-19 10:02:59 +0300 )edit

@luen After some testing and thinking: It is a bug. While the effects are rather benign with default settings, having the "lpm" feature enabled makes things a bit more nasty -> Need to enforce the "no lockscreen de-activation while display is blanked" -rule. Filed mer bug for this, so details at: https://bugs.merproject.org/show_bug.cgi?id=1831

spiiroin ( 2017-10-19 13:45:03 +0300 )edit

@spiiroin Thanks!

luen ( 2017-10-19 20:21:33 +0300 )edit

Question tools



Asked: 2017-10-17 22:34:56 +0300

Seen: 195 times

Last updated: Oct 18 '17