MX4 button sometimes remains active with the screen off

[Pat McGowan]

On last few weeks of rc-proposed and ota6 on MX4
On occasion when the phone resumes, either through a power button press or an incoming event, the greeter is not shown and either the passcode entry page or the last running app is shown directly.

This is intermittent but once in this state it is very consistently behaving this way.
Update: while that was originally true now (build 136) it seems to clear once the button is pressed, the greeter is shown next resume.

(was Greeter not always shown)

I reproduced it a few times after an incoming text but its not consistent

[Pat McGowan (pat-mcgowan)]

This was happening around 8:30 pm as I recall

[Pat McGowan (pat-mcgowan)]

previously time period

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pat McGowan (pat-mcgowan)]

Still seeing this in latest images fwiw

[Josh Arenson (josharenson)]

I've spent about an hour on r128 and r131 with no luck reproducing. I'll start using this as my main phone tomorrow in hopes of reproducing. Any idea when the issue started occurring WRT to the logs? (I assume the logs contain info before _and_ after the bug occurred).

[Josh Arenson (josharenson)]

I used my MX4 for a few days and never way able to see this... I have a patch that would enable timestamps in the logs, but at this point, I don't know how that would be helpful as the logs contain nothing remarkable. I'll discuss with the team some ideas and get back.

[Josh Arenson (josharenson)]

was*

[Pat McGowan (pat-mcgowan)]

The shell is showing the greeter on the suspend button press. The show is delayed by a 1 millisecond timer.
What could prevent that from executing properly?

[Josh Arenson (josharenson)]

@Pat that timer is the first thing I thought of when I saw this bug. I looked into it a bit, and found that the timer is synchronized with the animation timer. This means it has 16 ms resolution. This shouldn't matter as the only purpose of the timer is to ensure that the greeter is shown after the current event is processed. That said, I think we should log when/if the timer is triggering. Since I still can't reproduce this, I was hoping you could run an instrumented version of Unity8. If you are able to, would you prefer a patch (just qml/init changes, so you shouldn't have to recompile anything) or a deb?

[Pat McGowan (pat-mcgowan)]

@josh sorry I missed that comment, I can take either

[Pat McGowan (pat-mcgowan)]

@josh still seeing this occasionally so shoot me some qml or whatever

[Pat McGowan (pat-mcgowan)]

I just discovered a feature - double tapping the button at the bottom of the MX4 opens the greeter. on the device I use daily it seems this also works with the screen off. On another test unit I was able to get it once buts its not consistent.

Somehow my phone is in a state such that the button is not disabled when the screen is off, tapping the button lights it up.

[Pat McGowan (pat-mcgowan)]

A reboot cleared that state and the button is no longer active.

[Josh Arenson (josharenson)]

@Pat I can absolutly reproduce this using the following sequence

1. Set phone to unlock on swipe
2. Rapidly tap the "home" button
3. Simultaneously tap the power button to lock the screen
4. Stop tapping the "home" button after the screen darkens
5. Unlock the device

Expected: greeter is shown
Actual: Dash is shown

I can visibly see the "home" button blink well after I've pressed it (and well after the screen blanks. This seems like a good place to start looking around.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.