diff options
| author | Josh Tsuji <tsuji@google.com> | 2021-07-22 15:12:10 -0400 |
|---|---|---|
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | 2021-07-23 17:55:19 +0000 |
| commit | 73774fc8f3afb47c1166c75b471839d1af634384 (patch) | |
| tree | 09fc045318e985f2e93a270bf6f1df83f83c7698 /packages/SystemUI/src/com/android/keyguard/KeyguardAbsKeyInputView.java | |
| parent | 78d4c72e53da68f9a7a7b1deb520c7e19025c191 (diff) | |
Reset to LiftReveal when going to sleep due to timing out, after a biometric auth.
This was causing the device to sleep using the CircleReveal, since it wasn't allowed to be reset to LiftReveal if we went to sleep from timeout (vs. a power button press, where it'd be reset to PowerButtonReveal).
If the device was subsequently woken up via a tap (not a power press or a lift), the CircleReveal remained as the reveal effect. The reveal amount for a CircleReveal is controlled by the biometric auth controller, but since we weren't actually waking up from a biometric auth, nothing happened and the reveal amount remained at 0f.
Since you can't "go to sleep from a biometric auth", this is a safe fix to make sure we don't leave the CircleReveal set as the reveal effect.
Fixes: 192912744
Test: wake the device via fingerprint while it's asleep, then let it time out and receive a HUN
Change-Id: I86f2ad17d175c40c159de9ed6372490fb6e276f0
(cherry picked from commit 9ea5d02507b0ea9060642da81d971d118b579e1c)
Diffstat (limited to 'packages/SystemUI/src/com/android/keyguard/KeyguardAbsKeyInputView.java')
0 files changed, 0 insertions, 0 deletions