diff options
| author | 2025-02-27 15:42:59 +0000 | |
|---|---|---|
| committer | 2025-02-27 16:37:50 +0000 | |
| commit | 894de67e572e9750b206d476961848f313f49206 (patch) | |
| tree | d6f69568574b999836cdf68eb0a4249bb76b29fc /cmds/bootanimation/BootAnimation.cpp | |
| parent | b9a9cd5f30df9994e4e3eb7e10cb7820f3fe4f6f (diff) | |
Check shade expansion fraction to allow animation
In compose, it seems that values doesn't get updated before the time of
the transition of UMO from QS to QQS. Therefore, the UMO is still marked
as if it's visible and animation is executed, which leads to the flicker
effect. Checking the shade expanded fraction and decide whether
animation is needed fixes the issue.
Flag: com.android.systemui.qs_ui_refactor_compose_fragment
Fixes: 389576164
Test: Checked UI.
Change-Id: I741f5118ab9d1f66cd10dfe236a374184b3908b6
Diffstat (limited to 'cmds/bootanimation/BootAnimation.cpp')
0 files changed, 0 insertions, 0 deletions