Bug: Unlocking device with swipe-to-right does not always go to events screen

bug
3.0.0.8

asked 2018-11-15 18:31:29 +0300

juiceme
4027 ●54 ●78 ●89

Test case:

Leave an application in foreground and lock the device either with double-push-powerbutton or wait for the security locking timeout to activate
Unlock the device by swipe-to-right and enter the security code

Expected outcome:

The device is unlocked and the events view screen is shown

Actual outcome:

This happens only if the foreground application is the Sailfish Browser
The device is unlocked and the events view screen is shown for very short time, and immediately the screen scrolls to left by itself and the Sailfish Browser is activated and maximises to foreground application

Note:

This has been tested on both Jolla sbj1 and Sony XperiaX devices running 3.0.0.8

edit retag flag offensive close delete

Comments

Same issue with XA2 with SFOS 3.0.0.8

raketti ( 2018-11-15 19:29:19 +0300 )edit

can reproduce on Jolla C

balta ( 2018-11-15 19:31:19 +0300 )edit

Same issue

Mariusmssj ( 2018-11-15 19:44:29 +0300 )edit

And also this. If the browser is in foreground and screen is locked either by pressing power button once or by swiping down and tapping lock icon, screen goes blank. If the power button is pressed again or double tapped to unlock, device skips the lock screen and opens the browser straight. In every other case, when woken up, device presents the lock screen to either swipe left or right. edit: looks like this happens only immediately after the reported bug is executed at least once.

lal ( 2018-11-15 21:05:46 +0300 )edit

Using latest 3.0.0.8 on Aqua Fish, I cannot reproduce the issue. Swipe from left always lands me on the Events screen, from right on Home.

addydon ( 2018-11-16 08:43:31 +0300 )edit

answered 2018-11-15 22:21:13 +0300

olf
10393 ●104 ●201 ●158

updated 2018-11-15 23:17:31 +0300

On first sight (i.e. hopefully not missing any aspect), I don't think that the original or @lal's report constitutes a bug:

The lock-screen currently consists of two panels (additional ones could be inserted in the future): The lock-screen proper panel and the unlock panel (with the vKBD). One switches between panels by swiping either left or right, due to the panels being arranged as a "carousel". The default panel of these two, when the device is woken up (by a double tap or the power button) in locked state, is the lock-screen proper.
The unlocked, regular screen also consists of two panels: The home-screen and the events-view. One switches between these by swiping either right or left (if Settings -> Gestures -> Quick Events access is set), in a similar manner as the two lock-screen panels. The default panel of these two, when the device is being unlocked or woken up (by a double tap or the power button) in unlocked state, is the home-screen.
Why should unlocking ever send one directly to the events-view (as long as there is no explicit setting for that)?
@lal, single-pressing the power button merely triggers the screen blanking. Then a double tap or pushing the power button just un-blanks the screen, thus no need to unlock the device.

What might be a bit confusing in terminology and behavior, is that after a screen un-blanking (by first single pressing the power button, followed by a double tap or pressing the power button again) the lock-screen panel is displayed (IMO this is not the lock-screen, as the device is in unlocked state!). Then a left swipe goes to the events-view, while a right swipe to the home screen.
IMO this behavior is absolutely fine (i.e. I wouldn't want any other behavior).

edit flag offensive delete publish link

Bug: Unlocking device with swipe-to-right does not always go to events screen

Comments

1 Answer

Question tools

Stats

Related questions

Bug: Unlocking device with swipe-to-right does not always go to events screen

Comments

1 Answer

Question tools

Public thread

Stats

Related questions