This reverts commit 6dc967b4.

Reason for revert: Likely culprit for b/342044448  - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.

Change-Id: Iaf9540ac9f139ede43f22752e67046847416f507

Using the exported Bt flag supported_metadata_device_types_apis to
determine whether to use the BtDevice constants. We are duplicating the
constants for clients that have written values with the given metadata
keys (see FastPair initial implementation)

Flag: com.android.bluetooth.flags.Flags.supportMetadataDeviceTypesApis
Test: manual device type change
Bug: 335936458
Change-Id: I582e12967bbc4787d278964beb7a450518bc93f9

Bug: 338007388
Test: atest FrameworksMockingServicesTests:FlexibilityControllerTest
Change-Id: I6ea3c236c5bca963fd859b9519db01c5902da0b6

* changes:
  Revert "Flag off all edges leading KTF out of the Lockscreen scene"
  Revert "Fix WindowManagerLockscreenVisibility"

- Add the new bits to BubbleBarUpdate
- Include them in the state change

Test: none
Bug: 334175587
Change-Id: Iee94156b236f814a9363cf2182e333a1138a4162

Regression from ag/27145767 -- need to also clear the magnetized
object in the click listener (not just the touch listener like that
change does).

Test: manual - 1 add some bubbles
             - 2 expand the stack, select a different bubble
             - 3 open the overflow, add a bubble
             - 4 collapse the stack
             =>  verify the bubble added in (3) is at the top of the stack
Bug: 339711720
Change-Id: I2090e0a365df39542676d5a9d0b98c85450f760e

Test: demo app in bug
Fixes: 289571232
Change-Id: I38cf82903cbb15a53c48240eb001be40454e7234

Revert submission 27057737

Reason for revert: Droid-monitor created revert due to breakages in b/339822929. Will be verifying through ABTD before submission.

Reverted changes: /q/submissionid:27057737

Change-Id: I9d5eb13c5f19f348efa98fab9cbad7e6db7a5d41

Revert submission 27057737

Reason for revert: Droid-monitor created revert due to breakages in b/339822929. Will be verifying through ABTD before submission.

Reverted changes: /q/submissionid:27057737

Change-Id: I6563fdc760e86b10bf48af3e8f02100b1c3591df

all-updatable-modules-system-stubs is a stub, so it should be included
at the end, to avoid overriding real implementation.

Bug: 292141694
Test: ./ravenwood/scripts/run-ravenwood-tests.sh
Test: run `m` and make sure out/host/linux-x86/testcases/ravenwood-runtime
  doesn't have the un-renamed jar file.
Change-Id: I474f46b7e0844e5a887914226e5388bdf9486eb7

Merge "[DeviceAwareAppOp] Fix the bug that misuses device Id in proxy and proxied attribution source" into main

In Android U, all receivers registering for non-system broadcasts
are required to include a flag indicating the receiver's exported
state. Apps registering for non-system broadcasts should use the
ContextCompat#registerReceiver APIs with flags.

Fixes: 339811510
Bug: 331804186
Test: lunch sdk_phone64_x86_64-trunk_staging-userdebug; time m -j90; \
emulator -wipe-data -no-snapshot -logcat *:V -logcat-output logcat.txt
Test: m RUN_ERROR_PRONE=true
Test: atest FaceInternalEnumerateClientTest
            FingerprintInternalEnumerateClientTest
	    BiometricDanglingReceiverTest
Flag: NONE
Change-Id: Ie4d438cc76b3bb2fbd39af999332fcd5e4a52427

Dropbox sends two DROPBOX_ENTY_ADDED broadcasts at the same time to
handle a CompatChange. The two broadcasts need to have different
DeliveryGroupMatchingKeys or one of them will get replaced by the other.

Fixes: 323450448
Test: atest CtsDropBoxManagerTestCases
Change-Id: Ibdf7439cf5eb86b0c267ebe7ddc6962912dcdfd6

Merge "[flexiglass] Ignore window insets in scene container root, and adjust Shade/QS layouts accordingly" into main

Merge "Merge "Add flag dump_verifications for attestation_verification" into main am: ad5e62b9 am: 16e3be89" into main

Merge "Add flag dump_verifications for attestation_verification" into main am: ad5e62b9 am: 16e3be89

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



Change-Id: I89d06c0e6072f926bdd7d66b5a7f073544f4ff1d
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/+/3081526



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

Adds FLAG_ONLY_ALERT_ONCE to the update we sent from system_server to
systemUI on direct reply, to transition the notification out of the
sending state and to the sent state.

This update should only be used to update the appearance of the
notification; it should not alert, because it's triggered by the user's
direct reply action, and the user already knows they direct replied
(they're the ones who did it). We already setPostSilently on the
notification record, but that just prevents beeping, buzzing, and
blinking; it doesn't prevent the notification from HUN-ing if, for
example, the enqueued update somehow gets re-triggered by the app (see
attached bug).

Modified unit tests to check we're adding this flag.

Bug: 335106917
Test: atest NotificationManagerServiceTest
Flag: ACONFIG android.app.lifetime_extension_refactor STAGING
Change-Id: I521d83eea27e7026e1050a27856ef86013fd659f