Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Don't delay frame scheduling

Browse Source 
Doing so will lead to state inconsistencies. setExpansionAffectsAlpha
won't enque opacity requrests because mUpdatePending won't be true yet,
causing sudden opacity changes.

The much longer mAnimationDelay will already take care of waiting for
a while before starting the scrim animation.

Test: manual, with fp sensor
Fixes: 158955776
Change-Id: I9f7342f01de36576ba0108edfecbfc97448c8756
This commit is contained in:
Lucas Dupin
2020-07-06 18:04:47 -07:00
parent f9301fd850
commit d38fed16c8
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
packages/SystemUI/src/com/android/systemui/statusbar/phone/ScrimController.java
View File

@@ -348,10 +348,8 @@ public class ScrimController implements ViewTreeObserver.OnPreDrawListener, OnCo
}
if (mKeyguardUpdateMonitor.needsSlowUnlockTransition() && mState == ScrimState.UNLOCKED) {
// In case the user isn't unlocked, make sure to delay a bit because the system is hosed
// with too many things at this case, in order to not skip the initial frames.
mScrimInFront.postOnAnimationDelayed(this::scheduleUpdate, 16);
mAnimationDelay = StatusBar.FADE_KEYGUARD_START_DELAY;
scheduleUpdate();
} else if ((!mDozeParameters.getAlwaysOn() && oldState == ScrimState.AOD)
|| (mState == ScrimState.AOD && !mDozeParameters.getDisplayNeedsBlanking())) {
// Scheduling a frame isn't enough when: