diff options
| author | 2023-02-10 17:10:28 +0000 | |
|---|---|---|
| committer | 2023-03-28 18:42:17 +0000 | |
| commit | ce3d27698d7d8614276b258f80614de849f2c3e7 (patch) | |
| tree | 291774f66935abf359cb665bcd034d4cf619d224 /libs/androidfw/BackupData.cpp | |
| parent | 25b0c7fb752e15c35241ee42d533d96eecd55f25 (diff) | |
FIx occlusion status mismatch issue when screen turns off and on quickly
When KeyguardController detects occlude status change while the keyguard
is shown, it requests (UN)OCCLUDE app transition and PhoneWindowManager
defers committing the occlude state.
However KeyguardController and PhoneWindowManager use different
predicates to decide if keygaurd is shown or not. In case the predicates
return different value, occlude state in KeyguardController and
PhoneWindowManager remain inconsistent.
Test: manual
1. set secure lock method (pattern)
2. launch calculator app
3. push power button to screen off
4. just before the screen turns off, push power button to screen on
again
Bug: 232002936
(cherry picked from commit b71c7b40e7d0ade68e1d1a0ee93c8370edf6e415)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:b323776b1b205a4b266e16fbdc4095871cc4d9ec)
Merged-In: I4cd7e62e6800897cce50a5376495c499a0b9ad10
Change-Id: I4cd7e62e6800897cce50a5376495c499a0b9ad10
Diffstat (limited to 'libs/androidfw/BackupData.cpp')
0 files changed, 0 insertions, 0 deletions