We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2016-11-23 10:55:19 +0200 |
2.0.5.6 introduced a weird behaviour: If automatic device locking after a certain time is enabled, the device get's locked after this time even when using the device. The device lock gets activated in background of the running app and becomes visible when trying to access the home screen.
How to reproduce:
Actual behaviour: Accessing the home screen is prevented by the security code input dialog. Expected behaviour: Accessing the home screen is possible as device only gets locked when it's inactive.
I assume this to be a bug. If it isn't: Why was this new behaviour introduced? IMHO this makes the OS less usable.
2 | retagged |
2.0.5.6 introduced a weird behaviour: If automatic device locking after a certain time is enabled, the device get's locked after this time even when using the device. The device lock gets activated in background of the running app and becomes visible when trying to access the home screen.
How to reproduce:
Actual behaviour: Accessing the home screen is prevented by the security code input dialog. Expected behaviour: Accessing the home screen is possible as device only gets locked when it's inactive.
I assume this to be a bug. If it isn't: Why was this new behaviour introduced? IMHO this makes the OS less usable.
3 | No.3 Revision |
2.0.5.6 introduced a weird behaviour: If automatic device locking after a certain time is enabled, the device get's locked after this time even when using the device. The device lock gets activated in background of the running app and becomes visible when trying to access the home screen.
How to reproduce:
Actual behaviour: Accessing the home screen is prevented by the security code input dialog. Expected behaviour: Accessing the home screen is possible as device only gets locked when it's inactive.
I assume this to be a bug. If it isn't: Why was this new behaviour introduced? IMHO this makes the OS less usable.