Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2952994



Change-Id: Iba060ee7417ada6cb41a1f9d9020fd8a259ae199
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2952994



Change-Id: Ie91b90300bbfe0214de20e8254a0006cf4249eef
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

* changes:
  KeyguardMediaController: Invalidate NSSL only for MediaContainerView
  KeyguardMediaController: Log Active Container on refreshMedia

* changes:
  Fix clock flicker after unlock
  Fix hun/pulsing swipes

Bug: 318310357
Bug: 298898436
Bug: 298891941
Test: build pass.
Change-Id: I009d8a25ae738f98c2f02f70eb4ee414e1c0ddef

Merge "Updated BackgroundInstallControlService to use historical sessions to retrieve install start time." into main

setVisibility method has two major problems:
  1. Both singlePaneContainer and splitShadeContainer triggers visibilityChangedListener. That invalidates NSSL. We should invalidate NSSL only for MediaContainerView.
  2. Null View might trigger visibilityChangedListener. Null View's visibility is going to be null and it is not equal to the new visibility. So, the controller ends up invalidating NSSL.

This CL address these two problems by null check and container type check.

Bug: 298213983
Test: Play song in splitShade and check NSSL invalidation.
Flag: None
Change-Id: I7d75fe57b78efc3903b6d590cc00ee7ccd9e9a90

This CL logs active media before and after applying visibility change on refreshMediaPosition.

Bug: 298213983
Test: BR
Flag: None
Change-Id: I6c5c869e1b0ce6c9736f7c71f7faa7c06d0817f7

Since rules can be triggered externally on V, apps need a way to query their current state.

Test: atest ZenModeHelperTest
Bug: 326047233
Change-Id: I245408f631b3cc5b558df3c7ae2f73762459c616

- The logic for Fgs will be different (For the PAUSED state) there
will be a time window before calling stopFgs.

- UsageStats reporting has its feature flag, so it shouldn't be hidden
by Fgs flag.

- Fgs will not support MediaSesson2 because it is not linkable to
notifciations, this doesn't apply to UsageStats reporting.

Bug: 295518668
Bug: 297052684
Test: Non functional change
Change-Id: If06fc75a7f83e49759264aa30cda3c7834bbf1b6

This CL removes invalid assumptions made in
elementIsReusedInSameSceneAndBetweenScenes and renames it to
elementIsReusedBetweenScenes. See b/325120420 for details.

Bug: 326021461
Test: atest ElementTest
Flag: N/A
Change-Id: I7540b3265d501c086cd39e7e6f57309fb702abfb

[automerger skipped] Merge "Update owner to team" into main am: ff40f2a4 -s ours am: e8004d0a -s ours

am skip reason: Merged-In I1b35078cbc5f581b6b13daa8afcb6eee1aa2a15f with SHA-1 abb2ea62 is already in history

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2968942



Change-Id: Idc0adbc0ac6a0f931898db3fcb84ce5ff453b4e2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

am skip reason: Merged-In I1b35078cbc5f581b6b13daa8afcb6eee1aa2a15f with SHA-1 abb2ea62 is already in history

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2968942



Change-Id: I2de05a8f3c40de56cf5b645d9ce1c130e5a23230
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>