Unblanking Issue

Question

3

Unblanking Issue

Tracked by Jolla (In release)

asked 2018-06-08 00:26:08 +0300

LVPVS

3306 ●58 ●87 ●78

updated 2018-11-01 19:45:34 +0300

Hei,

I just updated my SailfishX to the latest EA. I wanted to configure unlocking to a similar method than that of the fruitphone has:

when locked, press power button to unlock.
when unlocked, press power button to lock.
autolock timeout set to immediately.

Now when unlocked, and I press power button to lock (immediately), and then try to unlock the phone, the lock screen remains. When swiped away, an empty screen (like an overlay) comes up. When locked from this screen via the power button, the same happens over and over. But when locked via top swipe, the phone can be unlocked (with fingerprint, or PIN).

Anyone else experiencing the same?

EDIT

Response to @spiiroin's comments: First of all, thank you!

The tag states the version: 2.2.0.29

So, the only thing I modified was this (from single unblank):

mcetool --set-display-off-single-powerkey-press=unblank,tkunlock

This way the phone is supposed to directly unlock if the fingerprint is recognized while pressing the power button. If not so, the keypad should come up requesting the unlock code.

I never ever installed any patches on any of my phones running SailfishOS.

For now, as a workaround, I set the autolock time to 5 minutes. This more or less helps, but it is not what I would like. My goal is to lock immediately (with or without power key).

End of EDIT

EDIT 3.0.0

Hi @spiiroin,

I gave it another try with the latest EA. This time it is 100% reproducable. Here is how:

mcetool --set-low-power-mode=enabled

Now, when LPM screen is on, touch the biometric sensor and press the power button. The phone seems to be unlocked as no keypad comes up, however; by swiping to either side the "ghost screen" slides in.

Falling back to the original setup for the time being, as the prvious version gave this issue only occassionally.

End of EDIT 3.0.0

LVPVS over.

edit retag flag offensive close delete

Comments

@LVPVS Does "I wanted to configure" indicate that you changed something somewhere?

Assuming you did change settings/patched something: "an empty screen (like an overlay) comes up" sounds like what has happened earlier when some state handling logic manages to not handle a state the device has arrived to, or a unusual route taken to that state -> Exact steps to reproduce would be useful (and while "the latest ea" is valid _now_, specifying actual sw version is more useful for anybody trying to reproduce this later on).

spiiroin ( 2018-06-08 09:01:55 +0300 )edit

@LVPVS I think I know where it goes wrong for you i.e. "autolock timeout set to immediately". Technically "lpm" is considered equal to "display off" blanked. So if you manage to unlock device in lpm, it should / tries to lock immediately again. Haven't checked yet in more detail, but I'd imagine that would be excellent source for some hiccups.

Personally I prefer to have some slack in the automated device locking and explicitly lock with double power key press when needed, so this aspect completely escaped me while debugging the issues.

spiiroin ( 2018-11-01 16:42:17 +0300 )edit

@spiiroin,

I see your point. I set my device to 5 min delay from lock immediately and re-enabled LPM. Now it works more or less the way I think it should be. At least, I did not experience any "ghost screen"-s so far.

Kiitos,

LVPVS

LVPVS ( 2018-11-01 19:49:18 +0300 )edit

@LVPVS Does "I wanted to configure" indicate that you changed something somewhere?
Assuming you did change settings/patched something: "an empty screen (like an overlay) comes up" sounds like what has happened earlier when some state handling logic manages to not handle a state the device has arrived to, or a unusual route taken to that state -> Exact steps to reproduce would be useful (and while "the latest ea" is valid _now_, specifying actual sw version is more useful for anybody trying to reproduce this later on).
spiiroin ( 2018-06-08 09:01:55 +0300 )edit
@LVPVS I think I know where it goes wrong for you i.e. "autolock timeout set to immediately". Technically "lpm" is considered equal to "display off" blanked. So if you manage to unlock device in lpm, it should / tries to lock immediately again. Haven't checked yet in more detail, but I'd imagine that would be excellent source for some hiccups.
Personally I prefer to have some slack in the automated device locking and explicitly lock with double power key press when needed, so this aspect completely escaped me while debugging the issues.
spiiroin ( 2018-11-01 16:42:17 +0300 )edit
@spiiroin,
I see your point. I set my device to 5 min delay from lock immediately and re-enabled LPM. Now it works more or less the way I think it should be. At least, I did not experience any "ghost screen"-s so far.
Kiitos,
LVPVS
LVPVS ( 2018-11-01 19:49:18 +0300 )edit

Answer 1

2

answered 2018-06-11 10:10:09 +0300

spiiroin
13237 ●151 ●224 ●199

moderator

updated 2018-11-02 13:06:45 +0300

@LVPVS: Thank for the clarification.

Note that the discussion here has quite much overlap with: https://together.jolla.com/question/184549/inconvenience-22029-fingerprint-unlock-only-works-on-lockscreen/

A bit of terminology: "tklock" = touchscreen & keypad lock, which is not the same thing as "device lock" i.e. the thing that requires entrering security code / fingerprint authentication.

While separate entities, these two lock states have interdependency, roughly:

If device is not locked, tklock can be on or off
if device is locked, tklock must be on.

Now, how this relates to the above mentioned mcetool tweak is:

If device is not locked, "tkunlock" action switches from lockscreen to home screen / application
If device is locked, "tkunlock" action gets transformed into "show device unlock view" action

Basically what happens in the latter case is:

Display is turned on as response to "unblank" powerkey action
Device lock ui activates fingerprint authentication (i.e. as things are now, fp scanner is not active while display is off -> fp scanner can't be used for waking up the device)
Fingerprint hal is instructed to go to authenticate state
The fingerprint hal in Xperia X wants to see "no finger on scanner" state before it starts authenticating
Nothing happens until user lifts finger off the power key doubling as fp scanner

-> At least for now "unlock if the fingerprint is recognized while pressing the power button" is not possible

As to the "as a workaround, I set the autolock time to 5 minutes ... My goal is to lock immediately (with or without power key)."

-> Doing double power key press locks device immediately regardless of the timeout/immediate devicelock setting -> Might make your workaround a bit more pleasant/useful?

EDIT - SFOS 3.0.0

Some bugs in "tklock" state synchronization between mce and lipstick have been fixed. This was probably the root cause for the empty "ghost of unlock ui" screen and possibly other glitches too.

EDIT:

There is another glitch that surfaces when lpm is enabled along with no delay automatic locking. Basically a) device can be unlocked while lpm screen is visible, but b) when that happens the device is locked again immediately -> The view used for unlocking the device breaks.

This will be addressed in future updates, but for now one can work around the issue for example by using 5 minute autolock delay and explicitly locking the device with double power key press.

edit flag offensive delete publish link

Comments

Hei,

@spiiroin, thank you for your detailed answer!

What you described in your 4th point makes sense to me, based on my experiences with the case. Actually, my method only worked when the screen was on while locked (LPM screen).

Double clicking the power button to lock immediately gives the same unblanking issue every once in a while. In fact, if I disable fingerprint sensor/authentication, the same happens. So whenever I use the power key to lock the phone, there is a slightly high chance of experiencing what I described.

On the footnote, I reflashed my Xperiax Dual SIM with the proper official image (for F5122), and the issue is still there. The UI works as swiping down to lock works. I can also take screenshots.

Kiitos,

LVPVS over.

LVPVS ( 2018-06-11 20:55:54 +0300 )edit

Answer 2

0

answered 2018-06-12 10:38:38 +0300

spiiroin
13237 ●151 ●224 ●199

moderator

@LVPVS When/if you use "LPM", you need to remember that it is not an officially supported feature, it is ulikely to get any development time ad-hoc / proper qa testing and one must more or less expect that it will cause some amount of issues of "some state handling logic manages to not handle a state the device has arrived to, or a unusual route taken to that state" -kind - and thus mentioning it is important if you have any issues. For example it seems that authentication from lpm "works" but does not cause exit from lpm / lockscreen.

Anyway, I think I got your issue reproduced:

settings -> device lock -> automatic locking = no delay
mcetool --set-low-power-mode=enabled
mcetool --set-display-off-single-powerkey-press=unblank,tkunlock
unblank + unlock device
blank (implicitly locks device due to no-delay)
cover proximity sensor for 5 secs or so
uncover p-sensor
once lpm screen shows up -> press power key

Some variation and does not happen every time, but: Lockscreen remains on display & swiping that ought to show unlock ui shows blank view without any controls / goes directly to the "blank view".

I'll file a bug about this, but unless it can be triggered without involving LPM it will have a low priority.

edit flag offensive delete publish link

Comments

Hei,

@spiiroin, thank you again!

What you put down step-by-step correctly represents my setup. Now I remember sometimes having similar issues with my JP1301. I have been using LPM since it came to my attention.

Now I disabled LPM and I will put my phone to some testing. This way, though, mcetool --set-display-off-single-powerkey-press=unblank,tkunlock definitely does not work. So I disabled it as well.

So far, the issue seems to be gone. Which is bad news in terms of priority...

I will come back, should anything worth of noting come up in this topic.

Anyways, thank you very much!

LVPVS over.

LVPVS ( 2018-06-12 20:10:39 +0300 )edit

@LVPVS I'm not sure what you mean by that powerkey tweak not working. It just makes single press behave the same way a double press already behaves by default. (Well, there is slight timing difference due to not waiting for the second press, but apart from that ...)

spiiroin ( 2018-06-13 10:24:10 +0300 )edit

@spiiroin, I did not mean it not working at all, rather it does not unlock the phone without releasing the powerkey. While LPM was active, the phone did unlock with fingerprint via a single click on the powerkey.

LVPVS over.

LVPVS ( 2018-06-13 21:45:39 +0300 )edit

@LVPVS Thanks for the clarification, now I think I know what you mean.

Fp auth is active in lpm (by accident/oversight/stte) and can unlock the device, but it does not exit lpm / hide lockscreen.
You tweaked single power key press to: unblank + hide lockscreen / show unlock view.

Together (1) + (2) can result in: fp auth -> devunlock; press -> unblank + exit lockscreen -- or press -> unblank + show unlock view; fp auth without lifting finger from power key -> devunlock + exit lockscreen. Just that it does not always work like that without hiccups.

spiiroin ( 2018-06-14 14:10:29 +0300 )edit

Hei,

@spiiroin, I don't know wether this is good news or not, in regards of priority, but... I have been using my phone for a week without my "tweaks" (LPM and other stuff) and today, just a few minutes ago the unblanking issue was back. With the standard, out-of-the-box setup.

Just wanted to let you know.

Kiitos, LVPVS over.

LVPVS ( 2018-06-21 12:28:14 +0300 )edit

Unblanking Issue

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Unblanking Issue

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions