Device gets locked in background while being used [released]

device-lock

asked 2016-11-23 10:55:19 +0200

schmittlauch
4334 ●60 ●75 ●71

updated 2017-10-04 09:54:24 +0200

nthn

12631 ●154 ●230 ●225

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:

Enable automatic device locking after a certain (short) time
Launch an app and use it at least as long as the device lock timeout is.
Swipe to access the home screen

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.

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by daywalker
close date 2017-10-04 14:22:18.077234

Comments

I think this is a duplicate and/or a widened bug like the one decsribed here: https://together.jolla.com/question/141260/bug-broken-display-timeout-after-receiveing-notification/

I am still unable to find a clear pattern for the reproduction of this issue. But after upgrading to 2.0.5.6 I also noticed that my Jolla phone just locked iteself and showed me the LPM screen while using it (like described in your question).

Alex ( 2016-11-23 11:00:14 +0200 )edit

@Alex The symptoms seem quite different, the issue behind it could be the same though.

schmittlauch ( 2016-11-23 11:10:20 +0200 )edit

@schmittlauch what is the certain short time for you? there are 5, 10, 30, 60.
With which app happened when you use it, and which one not?
And Which phone do you have? please

cemoi71 ( 2016-11-23 12:15:45 +0200 )edit

About this one: "2. Launch an app and use it at least as long as the device lock timeout is." I assume this includes taping and swiping, right?

jiit ( 2016-11-23 12:43:38 +0200 )edit

@jiit may i ask you why the detail with swiping and taping is important? you means because of user activity on it?
That could be apps which need to hold the phone unlock as long as no activity is done. Is there an sfos function which could be used from an app, which avoid the device to get locked (as long as it is on foreground)?
Maybe it would be interesting to make a list of app which use it... if it exist

cemoi71 ( 2016-11-23 13:04:57 +0200 )edit

6

answered 2016-11-23 11:18:27 +0200

jiit

2678 ●32 ●58 ●59

admin

updated 2016-11-24 12:03:39 +0200

spiiroin
13237 ●151 ●224 ●199

moderator

This is a known issue and currently being investigated, thanks for reporting.

EDIT:

"Device gets locked in background" = feature. But "device gets locked in background while being used" = bug, with same cause as https://together.jolla.com/question/151457/bug-auto-lock-time-out-dont-work-properly/

edit flag offensive delete publish link

Comments

2

We recommend selecting a longer time for "Automatic locking" in Settings > Device lock for now. This would save you from having to unlock all too often. We are sorry for the inconvenience.

The problem is that the auto lock timer is not reset by user actions as it should.

jovirkku ( 2016-11-24 12:22:43 +0200 )edit

1

answered 2017-09-20 15:00:57 +0200

cemoi71

14264 ●310 ●434 ●439

Issue not seen in 2.1.1.26 .
seems to be fixed

edit flag offensive delete publish link

1

answered 2017-10-04 09:46:49 +0200

daywalker

1570 ●31 ●46 ●43

updated 2017-10-04 09:48:38 +0200

Updated to 2.1.2.3 yesterday in the evening. Issue is not resolved for me.

Steps to reproduce:

Open Browser
Watch streaming video in fullscreen (e.g. on vivo(dot)sx)
Swipe after some minutes (can't tell actual timespan, i have watched a 20 minutes episode)

Actual behaviour:

Screen is locked, you have to enter your code

Expected behaviour:

Landing on Homescreen

Don't get me wrong i like this behaviour as a 'feature'. Devs should enable this as an option whether the screen should be locked in background or not.

I'm just reopening this as i observed this not to be solved as stated in the changelog.

edit flag offensive delete publish link

Comments

steps to reproduce happen every time`? or sometimes not?

cemoi71 ( 2017-10-04 11:58:05 +0200 )edit

Every time.

Just to be sure... i set 'lock after 5 minutes'

So is the device supposed to be locked after 5 minutes even when it is in use?

Or should it be 'lock device after 5 minutes only when not used' ??

Because right now the first thing happens...

Edit: i have to add that i only observed this with browser videos - never tested something else

daywalker ( 2017-10-04 12:42:21 +0200 )edit

@daywalker: Think in terms of "user interacts with the device". Watching video / something similar does not count as active use -> device gets locked in background after the specified timeout -> you can still watch the video, but switching to some other app requires unlocking -> as expected.

AFAICT the bug referred to in the changelogs was about something similar but still significantly different: The locking occurred already before the specified timeout.

spiiroin ( 2017-10-04 14:12:34 +0200 )edit

@spiiroin ok then my bug report is invalid as it only gets locked while watching a video, closed it again...

daywalker ( 2017-10-04 14:21:37 +0200 )edit

Device gets locked in background while being used [released]

The question has been closed for the following reason "released in a software update" by daywalker
close date 2017-10-04 14:22:18.077234

Comments

3 Answers

Comments

Comments

Question tools

Stats

Related questions

Device gets locked in background while being used [released]

The question has been closed for the following reason "released in a software update" by daywalker close date 2017-10-04 14:22:18.077234

Comments

3 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "released in a software update" by daywalker
close date 2017-10-04 14:22:18.077234