diff options
| author | 2023-03-16 19:24:01 +0100 | |
|---|---|---|
| committer | 2023-03-17 19:15:01 +0000 | |
| commit | 52d8053880b1be999ebc75730333b2d9ea326fb4 (patch) | |
| tree | a1ac60a836faa84acd601600be01a6a8a10ca15a /libs/androidfw/StringPool.cpp | |
| parent | aa23a487f56dd0d2fbc89e583f2bad6b38555e04 (diff) | |
Hold onto occluded change until it's committed
When we're delaying commit of setKeyguardOccluded due to a transition
taking over instead to synchronise occlude status more nicely, we hold
onto the final occlude status so we can be eventually consistent even
if the systemui restarts or gets something wrong.
The "notify" parameter in setKeyguardOccludedLw was risky because when
false it could lead to SystemUI not being informed of an update, but
the system server still considering its job done because the flag for
pending updates was cleared anyway.
This is a speculative fix to help the attached issue resolved itself
whenever it happens.
Test: atest android.server.wm.KeyguardTests
Bug: 269892931
Change-Id: I7d3ac020db34d8a15d18b25de07231bda83cbcf0
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions