tree eb33756d724a257679156b33a38ea94c0416b3eb
parent bd24d07497b558641521257b1040b9a32fd872d0
author Winson Chung <winsonc@google.com> 1670976184 +0000
committer Winson Chung <winsonc@google.com> 1670977381 +0000

Force update the disable flags following status bar registration

- CentralSurfacesImpl currently takes a long time to initialize, so in
  between registration and updating CommandQueue with the registered
  bar's disabled flags, the service may already have updated its
  disabled state.  This state would have already come into CommandQueue
  but would be clobbered by CSI in the post-init task.

  Since there are some legacy constraints in ordering of the
  initialization, we'll unblock the tests by forcing a disable flag
  update following the update to CommandQueue with the previous disabled
  flags.  We can later investigate applying the returned flags earlier
  in the cycle, or add a mechanism to skip apply the registered disable
  flags if they were updated mid-init.

Bug: 260615374
Test: atest WMShellFlickerTests:com.android.wm.shell.flicker.splitscreen.CopyContentInSplit
Change-Id: I98943292ecab5cdc693149f417e5c4e8af137d1d