Commit b7cceb95 authored Jun 09, 2025 by Hawkwood

Delay clock size computation

Delaying the clock size computation appears to allow the notification
flows to catch up. Since the clock size computation can evidently be
triggerred prior to the underlying data sources being updated, this
causes us to recompute the old value, and then miss when we should've
computed the new value.

Delaying the computation of clock size one frame by posting it to the
view's handler appears to correct that issue by delaying the computation
until after the data source has recieved it's update.

Bug: 423637687
Flag: NONE - Bugfix in NPVC
Test: Checked function of clock switch animation
Change-Id: I6192db3c973fd8a71796c0f9b84581fc65ed6cd2

parent 1ad9e6ac

packages/SystemUI/src/com/android/systemui/shade/NotificationPanelViewController.java

+13 −11

Original line number	Diff line number	Diff line
		@@ -1156,6 +1156,7 @@ public final class NotificationPanelViewController implements
		}

		private void updateClockAppearance() {
		postToView(() -> {
		mKeyguardClockInteractor.setClockSize(computeDesiredClockSize());
		updateKeyguardStatusViewAlignment();

		@@ -1169,6 +1170,7 @@ public final class NotificationPanelViewController implements
		mQsController.getHeaderHeight(),
		mSplitShadeEnabled);
		mClockPositionAlgorithm.run(mClockPositionResult);
		});
		}

		KeyguardClockPositionAlgorithm.Result getClockPositionResult() {