[automerger skipped] Merge "mMaximumObscuringOpacityForTouch should remain valid" into tm-qpr-dev am: 44e16010 am: 7e633df3 -s ours

am skip reason: Merged-In I4f15a7573913b503635995d26053bed9aa753a45 with SHA-1 bda5ee8c is already in history

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



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

Merge "Toast app icon display is inconsistent for system apps" am: 822d1a86 am: 37e216ea am: 59444f38

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



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

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



Change-Id: I42b2133b99690b8b57b98b0eb54c1100038b737c
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/+/2317710



Change-Id: I088b58514c7318dad7dc33d99bc394e114ed056e
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/+/2317710



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

* changes:
  Enable modern trim by default.
  hwui: change TRIM_COMPLETE to TRIM_BACKGROUND

UiAutomation is "implemented" as an accessibility service, and the
A11Y infra doesn't support concurrent users (i.e., it only supports
the current user and its profiles). This CL works around that
limitation by temporarily setting the current user as the visible
background user while the UiAutomation connection is set.

Test: atest CtsUiAutomationTestCases android.app.cts.InstrumentationTest # CTS
Test: atest --user-type secondary_user_on_secondary_display CtsUiAutomationTestCases # CTS
Test: atest FrameworksCoreTests:android.app.InstrumentationTest FrameworksCoreTests:android.app.UiAutomationTest AccessibilityManagerServiceTest AccessibilitySecurityPolicyTest AccessibilityWindowManagerTest # unit

Fixes: 271188189
Change-Id: I8603e09e0bc8ee2aebb43dfe28dd3531cda05c37

Test: atest FaceAuthenticationClientTest
Bug: 250071647
Change-Id: Icb845b11e592fd548679f27fd6ca567590578eb6

This has too much deadlock potential so let's fire all the callbacks
from our handler thread - we already fire the frozen state message
from there.

Test: Tested on a pixel 6
Bug: 276485767
Change-Id: Icc173b40b7fbc2a4cbbcff4375d58a0fca10bd50

Javadoc is accidentally modified in ag/20717989

Bug: 274289920
Test: atest CtsTelephonyTestCases
Change-Id: I9c5a7947c259597a19964c1084d61fe2f4a22b1d

* changes:
  Replace NSSLController usage in NotifShelf w/ NSSL
  Remove StatusBarStateListener from NotifShelf

When the app specifies a preferDefaultProvider in their create-cred
request, and the app has the CREDENTIAL_MANAGER_SET_ALLOWED_PROVIDERS
permission, then that preferred provider will take precedent over the
user specified preferred provider, only during the lifetime of this
single request.

Bug: 276777936
Test: manual (see bug for videos)
Change-Id: I70a130f4cbe3a32ce38b7b6e2925e7e52e46b727

Whenever BroadcastProcessQueue.getRunnableAt() changes, we need to
check its position in the "runnable" list to ensure it stays sorted.

We've been returning boolean values to indicate when a caller should
invoke updateRunnableList(), so we expand this to more methods that
can have side-effects, and use the "@CheckResult" annotation to
ensure callers don't forget their duty.

It's okay to err on the side of calling updateRunnableList() when
unsure, since it has a fast-path that returns quickly if a queue is
already sorted correctly.

Bug: 274681945
Test: atest FrameworksMockingServicesTests:BroadcastQueueTest
Test: atest FrameworksMockingServicesTests:BroadcastQueueModernImplTest
Test: atest FrameworksMockingServicesTests:BroadcastRecordTest
Change-Id: I877c5f179ba010c53e52d54c75c47583a608ec95

When we add the shadow right after running
SurfaceControlViewHost#setView, the shadow become visible on the screen
before the view which causes a flashing affect. This change uses a
SyncSurfaceGroup to sync set view and the application of our
transaction.

Bug: 276356641
Test: Manual Testing
Change-Id: Iecbcb0e9f7736bddfd3054f8e91c69bce41e3e78

Bug: 277187196
Test: tree hugger.
Change-Id: Ic208abb442535d01c946ce7f49022483f126279c

Fixes: 276920002

Test: btest a.d.c.BlockUninstallTest
Test: btest a.d.c.UserControlDisabledPackagesTest
Test: btest a.d.c.LockTaskTest
Test: btest a.d.c.PersistentPreferredActivitiesTest
Test: btest a.d.c.WipeDataTest
Change-Id: Ibbbd0dfd3be71fecd8e98e0137474d4cc3992941