Callback methods of callbacks registered by IME should be run on the same thread the ViewRootImpl holding IME's WindowOnBackInvokedDispatcher is created on.

Bug: 345427620
Test: Manual, i.e. verifying that IME is dismissed by back gesture without throwing IllegalStateException
Change-Id: I2883201aa59bb264e4c02246007c7c4788e8b07c

Merge "frameworks: updates to use new aconfig storage read api and add storage files into allow list so these files can be accessed." into main

This pulls the FlingAnimation from the AndroidX SpringAnimation library into core, which was left out in the CL with change-id Ifdf847da0aa2a6cf57e18f9ac7c91bb0fe3b12c2 when other parts of that library were added to core.

Bug: 333957271
Flag: com.android.systemui.predictive_back_system_anims
Test: atest BackProgressAnimatorTest
Test: atest FrameworksCoreTests:WindowOnBackInvokedDispatcherTest
Test: Manual, i.e. testing flings in app callbacks and analysing screen recordings
Change-Id: Idb64721703121414da847b11915a9c19e6bc2686

ActiveTransition is a somewhat-heavy object because it references all of
the TransitionInfo and SurfaceControl.Transaction data, meaning they can
not be released if another object or process is still holding onto them.

Passing out just the IBinder reduces the potential damage of a ref cycle
or slow GC from several megabytes to a few hundred bytes. We alo

Flag: EXEMPT bugfix
Test: atest WMShellUnitTests:ShellTransitionTests
Test: manually run a few transitions and use ahat to check the dumpheap
Bug: 338077587
Change-Id: Ib15c5281a284a920f3098c30f8dc401efcd475ad

* changes:
  Load monochrome app icon in SBIV
  Introduce StatusBarIcon.Type

[automerger skipped] Merge "[RESTRICT AUTOMERGE] Messaging child requestLayout" into 24D1-dev am: fcf13527 -s ours

am skip reason: Merged-In I53705d614efcb73fefc5a90c09e189b8aa0fa172 with SHA-1 fc64eee9 is already in history

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



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

am skip reason: Merged-In I53705d614efcb73fefc5a90c09e189b8aa0fa172 with SHA-1 fc64eee9 is already in history

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



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

LocalServices

- This is not fixing the bug in questions, but removing the extra
 `getIsolatedOwner` call that was being made for all isolated uids,
 which was increasing the error log rate significantly.

Bug: 286903116
Test: atest android.ondeviceintelligence.cts.OnDeviceIntelligenceManagerTest#inferenceServiceShouldReturnParentPackageName
Change-Id: I63e94b567f5fe1f3711e7eaa79298b88d6ef9e58

This helps us trace calls to register/unregister observers and makes it
easier to track them down.

Bug: 330299944
Test: took a trace
Flag: EXEMPT logging only
Change-Id: I32907c6d048b156a709d5eafb5dd4017ff7ae652

When we receive a new alerting notification while we are already
pulsing, we make another request to DozeTriggers.requestPulse, which
rejects it, because we are already in a pulse state. This rejection
executes a callback, which removes our 2nd pulsing notification from the
alerting entries.

This CL allows calling DozeTriggers.requestPulse multiple times for new
notifications, without executing their suppression callback.

Fixes: 335560575
Test: atest DozeTriggersTest
Test: setup AOD, receive 2 pulsing notifications, check if the 2nd one
shows up
Flag: com.android.systemui.notification_pulsing_fix

Change-Id: I5e04e9d76ddf5df54ff05512b6645af29b9f238e

* changes:
  Force new fading elements to fade from 0 alpha
  Prevent outdated layers to update Element.SceneState.lastAlpha
  Move the Element placement logic into ElementNode

Bug: 341013064
Test: atest FrameworksCoreTests:WindowOnBackInvokedDispatcherTest
Test: Manual, i.e. testing IME behaviour in test app when using onKeyPreIme.
Change-Id: I698577f0a1de69a0f5db1006e52f669cee2df5a1

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



Change-Id: Ia6f2fa128358a0766954c4cbefc3b3f86e49e561
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/+/3116267



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

* changes:
  Use the latest temperature read as base for headroom calculation
  Revert "Use the latest temperature read as base for headroom calculation"

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



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

* changes:
  chore(magnification): wait sysui connection to control fullscreen magnification
  Revert "chore(magnification): add magnification sysui connection..."

Bug: 340137127
Flag: EXEMPT bugfix
Test: manually checking a split screen pss session with Meet
Test: atest SystemUITest:ShellRecentTaskListProviderTest
Change-Id: I01b60a357f312d51807bc6469998880e017d9240