Device lock activated if screen times out, even if awakened within 30 seconds, but application is shown [answered]

asked 2014-02-03 15:06:02 +0200

Mohjive

8581 ●166 ●226 ●250

http://www.y3k.se/

updated 2014-02-03 19:14:02 +0200

rainisto

6348 ●69 ●98 ●112

moderator

If device lock is set to "automated locking: no delay", the device lock is activated directly when the screen blanks. If one wakes the screen within the grace time (30 s), the last application is shown. But when one tries to swipe to home screen the pin entry screen is shown. Either the device should lock, not showing the app at all, or it should not lock, giving me the possibility to swipe to the home screen.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Mohjive
close date 2014-04-16 18:14:33.313342

Comments

@Mohjive Nice catch. I retagged, as this bug showed up after the latest update

simo ( 2014-02-03 15:21:54 +0200 )edit

In this case (automated locking: no delay), returning to the last app (within 30 sec) should happen via lock screen. Additionally, it would be good to stop the countdown for the time the lock code is entered. (eg. double tap done after 29 secs -> you could still get back to the latest app after entering the code)

simo ( 2014-02-03 15:35:34 +0200 )edit

My feelings about this can be found here, not good design in my opinion.

MMori ( 2014-02-05 13:28:22 +0200 )edit

@MMori You're very welcome to bring your feelings here (even edit the question above with additional info if needed). There's no idea to handle one issue in two topics, in this case a newer one should be closed as duplicate.

simo ( 2014-02-05 13:37:45 +0200 )edit

@simo Here I am, does closed threads go to trash can? In the duplicate thread I had so many feelings that I got lazy and did not write those here again. That's the only reason I linked the duplicate thread.

MMori ( 2014-02-05 13:50:21 +0200 )edit

1

answered 2014-03-04 14:45:58 +0200

spiiroin
13237 ●151 ●224 ●199

moderator

Updated behavior is: if the device enters state where display is off and device lock is active, the ui is locked too.

In practice this is "the device should lock, not showing the app at all" as suggested above.

edit flag offensive delete publish link

Comments

Great! That is what I'd expect as a user when I set the device lock to "No delay". With 1.0.3.8 behavior it was just confusing when some actions work and some doesn't. I'll wait for the update to accept the answer and close.

N.B. The implementation @rainisto suggested with an entry as "After grace period", would be even better, but then that behavior would be selected explicitly. Also that would be a enhancement and not a bug such as this question.

Mohjive ( 2014-03-04 15:30:37 +0200 )edit

Absolutely fantastic, thank you for this! :)

MMori ( 2014-04-26 09:10:07 +0200 )edit

0

answered 2014-02-03 19:15:13 +0200

rainisto

6348 ●69 ●98 ●112

moderator

updated 2014-02-07 18:22:26 +0200

Unfortunately this is not a bug, but intented behaviour by design for 1.0.3.8.

But thanks for the feature suggestions. We are working on making things better in future sw updates.

edit flag offensive delete publish link

Comments

I do appreciate the grace timer doesn't lock the display, but I don't understand why the device lock would be activated. I think this is a bit inconsistent.

Mohjive ( 2014-02-03 21:16:03 +0200 )edit

Well yes we had same discussion internally too, but definition of immediately is immediately and not that grace timer would be able to cancel it. One possible improvement at some point would be a new setting between the immediately and 5 minutes. Something like immediately, after grace, 5mins...

rainisto ( 2014-02-03 21:35:44 +0200 )edit

Then, for consistency, I'd say disable the grace timer if immediately device lock is set. Now it's actually confusing (for me).

Mohjive ( 2014-02-03 21:57:36 +0200 )edit

It is confusing that the lock activates. It should pop up before navigating back to app or not at all. Now it's just an annoyance and security threat. When I say the lock should activate immediately after display turns off, I also assume the lock activates and prevents the usage of all apps. Not good design. The only other viable option would be that the lock is activated only after the timer has been set off.

MMori ( 2014-02-05 13:34:38 +0200 )edit

1

The current behavior is confusing and needs to be changed. For example, if you return to the app and then try to open the notification screen, it just refuses to stay open. There is no indication that the phone is locked. Furthermore, opening links from an app like Tweetian now longer works in this situation – you can tap on them, but nothing happens without an indication why this won't work.

raimue ( 2014-02-07 15:34:24 +0200 )edit

Device lock activated if screen times out, even if awakened within 30 seconds, but application is shown [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Mohjive
close date 2014-04-16 18:14:33.313342

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Device lock activated if screen times out, even if awakened within 30 seconds, but application is shown [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Mohjive close date 2014-04-16 18:14:33.313342

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by Mohjive
close date 2014-04-16 18:14:33.313342