Sending for result should only opt-in the real caller (sender) of the
PendingIntent and not the creator.

Test: atest BackgroundActivityLaunchTest
Bug: 325504942
Change-Id: Idebbf687d609998b166b702435f78ea9fb629a30

+ Also fix the dumpsys format

BUG: 324422097
Test: builds

Change-Id: Ic7257971e2a80462dbc2504c4c1f8128969e2867

Merge "Update the test mapping to remove the classes which moved to mediaprovider mainline module." into main

Fixes: 325630216
Test: N/a
Change-Id: Ide87995707501d9465de9e335ec9f99aec4e0de3

ebiggers@ identified some problems:

1. The formatting of the persistent data block was incorrect, it
   shortened the FRP challenge section by the size of the FRP
   secret and magic, but then failed to advance the channel write
   position past them, causing subsequent sections to be written
   at the wrong locations.  The data being written to incorrect
   locations was all zeros and it seems unlikely that this could
   have caused any problems, but this fixes it.
2. `writeFrpMagicAndDefaultSecret()` failed to recalculate and
   write the digest, meaning that the PDB would subsequently be
   viewed as corrupted and reformatted on the next boot in some
   obscure cases.
3. `setFactoryResetProtectionSecret()` failed to check that the
   caller has permission to configure FRP.  This isn't strictly
   necessary (nor is the similar check on
   `deactivateFactoryResetProtection()`, but it's also not the
   case that anyone without the permission needs to be calling
   these methods.
4. There was a bug in the FRP secret file display in the status
   command of the persistent_data_block shell command.
5. `deactivateFrpWithFileSecret()` logged a warning if the secret
   file was not found, but this could happen in correct
   operation, so it should be an informational log.  (In general
   FRP hardening makes PDBService too noisy, but this is good in
   the short term; logging will be reduced in the future).

Test: atest PersistentDataBlockServiceTest
Bug: 290312729
Change-Id: Ief505a634d355a97bb6b99efc52cef68649a025f

Got a crash while testing the German layout, and it seems like the
current "show key presses" functionality will crash when using
an unsupported Unicode character. This CL addresses this issue by
adding support for dead characters, pulling the actual combining
character from the KCM if needed.

Bug: 325420862
Test: Flashed on device
Flag: NONE
Change-Id: Ia70685fbfae5bf81a71b346a24ff0e73c8d8d932

* changes:
  Avoid side effects in MediaCoordinator notif filter.
  Add bugfix flag for bg icon updates for media notif

- The change is required to avoid trigering all the CTS test cases when a file is change from framework/base.

Test: m
BUG: BUG:325580144
Change-Id: Ib763cd2c570f82aae73f98507a9a5e0ba5b9b0c9

In discussion with material/shape team the consensus is that
a more flexible/scalable path forward should rely on material
token generation rather than framework resources directly.

Bug: b/324928718
Test: m update-api & presubmits
Change-Id: I887d26e54fa78f5a5279995791d49edfe66cd22e

Merge "Renamed thread_enabled flag to thread_enabled_platform" into main am: 771e5d91 am: da16e050

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



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

Fix: 324934385
Bug: 305193969
Change-Id: I859f5b88adf26a34b6f499dc2c24ded543a5b682
Test: v2/pixel-health-guard/device-boot-test
Flag: ACONFIG com.android.systemui.enable_vector_cursors DEVELOPMENT

A normal flag can't just be turned into a bug fix flag. It has to be
renamed.

Bug: 317199366
Test: NA
Flag: ACONFIG com.android.systemui.centralized_status_bar_height_fix DISABLED
Change-Id: Id41e2017ca3016bd2a331b5d52b897ca232ae495

Bug: 295518668
Test: Manual Playback
Change-Id: I2f0bde0a426b83cb2a8bd9fc69d767dcf6efeaaf