diff options
| author | wilsonshih <wilsonshih@google.com> | 2020-09-22 13:20:57 +0800 |
|---|---|---|
| committer | wilsonshih <wilsonshih@google.com> | 2020-09-29 10:53:35 +0800 |
| commit | 556a113a19d71197d921410d4d6cb4c3f07316f0 (patch) | |
| tree | 3d14db7ba2a98d3c3a157e26d32f81d138a793b8 /rs/java/android/renderscript/ProgramVertexFixedFunction.java | |
| parent | a0b1e8ecd4c3bfce83ba6c036fa9f3e8bee11f94 (diff) | |
Only update keyguard status from top focusable visible task.
In original sequence we do KeyguardController#visibilitiesUpdated
at endActivityVisibilityUpdate, so without the check from
mVisibilityTransactionDepth, KeyguardController#visibilitiesUpdated
can actually do RootWindowContainer#ensureActivitiesVisible again
if occluded state has changed. But actually only the top non-pinned
activity on each display can affect the keyguard status. So to make
ensureActivitiesVisible faster, update keyguard status from this task
at beginActivityVisibilityUpdate, then update visibility for each
activities after sleep token is stable.
Bug: 163993448
Bug: 168776729
Test: atest ActivityVisibilityTests KeyguardTests KeyguardLockedTests
KeyguardTransitionTests AppConfigurationTests ReplaceWindowTests
Test: atest ActivityRecordTests RecentTasksTest ActivityStackTests
DisplayContentTests
Change-Id: I6428c59245fc84b0093778d4aaa5906a0b1a26e3
Diffstat (limited to 'rs/java/android/renderscript/ProgramVertexFixedFunction.java')
0 files changed, 0 insertions, 0 deletions