Revision history [back]

When device is (code) locked, a double press on power key should display the lock input screen. Currently on SailfishOS 2.0 (i.e. 1.1.9+) it shows the lock screen.

To reproduce the bug:

1. Enable device lock
2. When the display is on, double press the power key to lock the device
3. Double press again when the display is off

It should show the lock input screen to enable the user to rapidly unlock the device as in previous releases, but it shows the lock screen; therefore on locked device there's no difference between single press and double press.

I'm not sure if it's related, but in 1.1.9 changelog this is mentioned:

[lipstick-jolla-home] Show device lock on power key double press. Fixes JB#28648

It's not even possible via mcetool command:

mcetool --set-display-off-double-powerkey-press-actions=<actions>

because the valid actions are:

• blank - turn display off
• tklock - lock ui
• devlock - lock device
• dbus1 - send dbus signal or make method call
• shutdown - power off device
• unblank - turn display on
• tkunlock - unlock ui
• dbus2 - send dbus signal or make method call

Or, I think, tkunlock should display lock input screen when device is locked. Default actions for display-off-double-powerkey-press are unblank,tkunlock.

When device is (code) locked, a double press on power key should display the lock input screen. Currently on SailfishOS 2.0 (i.e. 1.1.9+) it shows the lock screen.

To reproduce the bug:

1. Enable device lock
2. When the display is on, double press the power key to lock the device
3. Double press again when the display is off

It should show the lock input screen to enable the user to rapidly unlock the device as in previous releases, but it shows the lock screen; therefore on locked device there's no difference between single press and double press.

I'm not sure if it's related, but in 1.1.9 changelog this is mentioned:

[lipstick-jolla-home] Show device lock on power key double press. Fixes JB#28648

It's not even possible via mcetool command:

mcetool --set-display-off-double-powerkey-press-actions=<actions>

because the valid actions are:

• blank - turn display off
• tklock - lock ui
• devlock - lock device
• dbus1 - send dbus signal or make method call
• shutdown - power off device
• unblank - turn display on
• tkunlock - unlock ui
• dbus2 - send dbus signal or make method call

Or, I think, tkunlock should display lock input screen when device is locked. Default actions for display-off-double-powerkey-press are unblank,tkunlockunblank,tkunlock,dbus2.