Merge "Update biometric message to allow identifying special messages like auth failure and auth lockout." into main

Merge "Change usages of flags within bouncer to consider both compose bouncer and scene container framework flags" into main

Merge "Refactor category and action into a constant to provide more context in a comment." into main

Test: atest WMShellMultivalentTestsOnDevice
Test: atest WMShellRobolectricTests
Bug: 308004028
Change-Id: I384ae5afd57c020f098046a0b204fd2bb4123ef8

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



Change-Id: Ibd14c2bd9451dc3c9b2ded5c4c4928733c5059e8
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/+/2981831



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

* changes:
  Update Perfetto Protolog flag name
  Add read only perfetto protolog flag
  Increment protolog version

When the view is not attached to a view tree, we used the display
getRealSize to get an estimated result. This will be affected by the
Configuration hidden fields. It will not always have the stable result
with changes in the configuration.

Use the window metrics instead to estimate the result when the View has
access to the WindowManager to make the result better matches the
description of the public API.

Test: CTS ViewTest
Bug: 321143205
Change-Id: I823acadb0a50272b74288cfcefea2843c07a26c5

Revert submission 25506346-296558535

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

Reverted changes: /q/submissionid:25506346-296558535

Change-Id: I7f400d2f5ae77281614f49b760301b5b396e4475

Which was causing old onClick was used when click.

Bug: 327425969
Test: manual - on Mobile Settings
Change-Id: I1af16869d6ecf057e23115bfc86d9b656347d9fb

We introduce keyboard category in CL[1] to support
independent keyboard vibration. However some non-ime
apps also use the KEYBOARD_* api to simulate keyboard
vibration.

Check the caller is an input method before applied the
keyboard category.

[1]: I67c95718d11fb429083e1bc9dcab6e1bc85249fc

Bug: 324548203
Test: verify with issue apps
Test: atest HapticFeedbackVibrationProviderTest
Change-Id: I9e755ed2f30d72e5cdc8c1f6018643867db89ff9

Some of the runnables will assume the transcation has been committed by
the surface flinger before getting run. For example, the leashes of
insets need to be setup before dispatching to the client. If the order
is not ensured, the transaction sent from the client might be executed
earlier than the one sent from system server which might override the
state of the leash unexpectedly.

This CL executes the runnables when the transaction has been committed.

Fix: 298018626
Test: atest InsetsPolicyTest InsetsStateControllerTest
Change-Id: Ie7bb268f228ae8a8ed15e49b193aa2d0183f31ac