This reverts commit f14fd636. ("Make isBackDisabled() not SystemAPI")
This reverts commit c49cc7d1. ("Revert "Improve StatusBarManager disable*() apis")

Reason for revert: The following bugs cite this CL as the cause of the bugs: b/332752827 , b/325856557 , and b/332647161.

Bug: 325856557
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:46dae741eee51a1dc504baee930dbbb708fb496f)
Merged-In: I16daf2373e557ba0d67edb1cdf6ac529b18ae850
Change-Id: I16daf2373e557ba0d67edb1cdf6ac529b18ae850

Bug: 325925410
Bug: 326195401
Test: atest KeyboardLayoutManagerTests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:7e400a3857455d0a040eede1e9f7df3f7cf4a5e0)
Merged-In: I58b78891e96d100f8b079b2d210d5b238d56e49c
Change-Id: I58b78891e96d100f8b079b2d210d5b238d56e49c

Currently, the test goes home after opening camera, and launches the next app before the status bar appears, making it flaky

Fixes: 327716272
Test: atest OpenAppFromIntentColdAfterCameraTest
Change-Id: I20fd043b2ea7ad989228ef83512b3ba262328159

Needed to create a new flag because we can't set flag to readonly once created

Bug: 276432490
Test: mp droid
Change-Id: I45598a8e91d8959fd957dc23af20c7817ebc31fe

Update the GTE frame rate test to use a higher refresh rate.

Bug: 327013543
Test: atest CtsSurfaceControlTestsStaging
Change-Id: Ic04c85c2476ab051e4f10561f7b53f7f3add1ba3

Pass Device Bus from the native side to the Java side. This is done so
we can log Device Bus ID in atoms.
Since the same vendor ID could mean different vendors depending on
whether the device is connected over bluetooth or USB, we require to know
the device bus to disambiguate the vendor IDs.

Bug: 308918242
Test: atest InputDeviceTest
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:b4015294e1c3452a00d4a326ca3871e6e56b5f78)
Merged-In: I0ff2e31d7a8b610b0e1208cc5c444d1f785e162c
Change-Id: I0ff2e31d7a8b610b0e1208cc5c444d1f785e162c

Since winscope no longer uses flicker code, we don't need to compile
all the code to JS. This means we can reuse the standard Android
objects and simplify the code

This CL updates the import path removing the distinction between common
and device subpackages

Bug: 311642700
Test: atest FlickerLibTest FlickerLibUtilTests FlickerLibE2eTest
Change-Id: I06bb190ed0e60336390d5c7ea72c7585ac0ef90f

Since winscope no longer uses flicker code, we don't need to compile
all the code to JS. This means we can reuse the standard Android
objects and simplify the code

This CL updates the import path removing the distinction between common
and device subpackages

Bug: 311642700
Test: atest FlickerLibTest FlickerLibUtilTests FlickerLibE2eTest
Change-Id: I99adee33658007d696d60cfff575e87e6419cf8d

ProtoLogTool now has additional parameters to support Perfetto tracing. We also need to generate and include a proto version of the viewer configuration.

Flag: ACONFIG android.tracing.Flags.perfettoProtolog DEVELOPMENT
Test: mp droid && atest FrameworksServicesTests
Bug: 276432490
Change-Id: I26929eed96faae04bec65ae5eaf86afda75cb83c

Bug: 276432490
Test: atest com.android.internal.protolog
Change-Id: Ib961bf375cc4aaa4fb1d7d31b35d06b31aacd5d4

Flag: ACONFIG android.tracing.Flags.perfettoProtolog DEVELOPMENT
Bug: 276432490
Test: atest FrameworksServicesTests
Change-Id: If95bfeeaff491ce51b61e34d2f8c22d8b635912d

Generate the impl classes and support writing the viewer config to a proto file

Flag: ACONFIG android.tracing.Flags.perfettoProtolog DEVELOPMENT
Bug: 276432490
Test: atest FrameworksServicesTests
Change-Id: I69956b5ef2b8b48a98860aa3b8579521480d7bc0

To avoid hash collisions now that we have more messages.

Flag: ACONFIG android.tracing.Flags.perfettoProtolog DEVELOPMENT
Bug: 276432490
Test: atest FrameworksServicesTests
Change-Id: Ia252f1fc60deb2beaf177b0782a8723e39f90a7e

This CL calls CarrierConfigManager.getCarrierConfigSubset instead of
getConfigForSubId to guard against crashing when phone process has gone.

The former method is designed for system components to retrieve carrier
configs with consideration of phone process may be gone (e.g. during
rebooting from previous crash).

Bug: 319791612
Test: atest TelephonySubscriptionTrackerTest
Change-Id: I784610b243db2a666c1fe89b1438950a2f6a1478

Adds flicker test for the CUJ with entering pip with source rect hint.
This specifically tests with auto enter enabled, but we can probably
add a separate case for entering manually. The test uses a rectangle
as the source rect, and there is a jump at the end of the transition
as the app doesn't update the layout for pip, but this is more of an
app issue and doesn't affect the test case.

Flags: N/A
Bug: 284200208
Test: atest EnterPipWithSourceRectHintTest
Change-Id: I47ab50f19dc421dc0e0262c7b14f5b37dfb3551e

Bug: 325652645
Test: atest InputScreenshotTests
Change-Id: I6b5a064d631e91d03c85b8f0cc2944951fa69fc8

Test: n/a
Change-Id: Id2586f04933b97e1d8562fd86dc7e65ee419c10e

CL created based on go/new-android-ownership-model

Bug: 304529413
Test: make
Change-Id: I7db3a93e8f4752591822062e043ee7126248b2cc

This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.

For more details please refer to the link below,
<add g3 doc link>

Bug: 304529413
Test: N/A
Change-Id: I6b6cf0abdd1fdb8fefa4184b3698f6951c192ac0

Before, the test gets root implicitly via DeviceSetup which
wasn't intented.

Change-Id: I4b86fd5ee31f746942a2bf073a29cb2180a39f27
Test: presubmit
Bug: 325094408

Before, the test gets root implicitly via DeviceSetup which
wasn't intented.

Change-Id: I9b34a85025a6aa4f138483202fd11db0cbb8b04b
Test: presubmit
Bug: 325094408

Test: SurfaceControlInputReceiverTests
Test: AttachedSurfaceControlTest
Test: SurfaceControlViewHostTests
Flag: ACONFIG com.android.window.flags.surface_control_input_receiver TRUNKFOOD
Bug: 287076178
Change-Id: I3b951ed62c18771661e96cffe493c44941148973

Change-Id: I6cb659d0bf3d6a905fa969465501357d22a4bb9a
Test: atest UsbManagerTests
Bug: 323470419

Change-Id: I2b36ebb174e25ebbf1b9b304a0ba7b41619fd142
Bug: 323470419
Test: Manually verified that the api is returning the internal value

Bug: 324252060
Change-Id: Iead8fd85b8d0a15f6ce2832f093f2cbf712039ad
Test: Pre-submit

Enable adding a reason to disable api to improve debugging efforts. The goal is to have attribution data for why SystemUI elements are disabled, not just at a package level (as in the status quo) but at a sub package level. Can be tested by manually disabling flags from command line with "adb shell cmd statusbar send-disable-flag clock" and checking at the dump logs via "adb shell dumpsys statusbar".

Flag: NONE
Test: Manually tested in pixel 7.
Bug: 291319588
Change-Id: I52ff935d7d095a7bb1b698207de525bc551a45f6

Bug: 302149604
Fixes: 324576535
Flag: NA
Test: atest AnimatorTestRuleOrderTest
Test: ran test case from b/324576535
Change-Id: I9735a6fd3fbb531fb75a4283401a3553703e43ab

Without transpiling the code to typescript, it is no longer necessary to keep the values as array. instead we can use Collection/List and avoid a lot of conversion

Bug: 311642700
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I43aaf5c793b97bb5b4e8568df99ed4a272e5b07b

This new API will be used to clients to determine if a connection is PD
compliant. This can be used before initiating role swaps or power
limiting.

Test: atest UsbManagerTests
Bug: 323470419
Change-Id: I3ff1ce9a2b24dd5aa818fd709882a8ea32e7bdea
API-Coverage-Bug: 324506285

Adding property android.app.PROPERTY_RESTRICT_USB_OVERLAY_ACTIVITIES
in manifest. This property will be honored only for applications which
have MANAGE_USB permission(i.e only priviledged applications). If this
property is set on application which is in foreground when usb device is
attached then, usb flow would not resolveActivity.
If there is no application in foreground with this field set,
then usb attachment will start overlay activities.

Bug: 307231174
Test: Manually tested the flow.
Test: atest UsbManagerTests
Change-Id: Ica4f557ec5eeb0887373f5bd1a44f05f1bdfeecd

Since PointerChoreographer is enabled now, disable tests for the legacy
pipeline which is no longer actively maintained by checking the device
flag value.

Bug: 324154406
Test: atest InputManagerServiceTests
Change-Id: Ibf24fe6857ac6c467bbf6ae292e2a37f5bc993fa

Rollbacks are currently stored only for some mainline packages, but
rollbacks will be added for phonesky and GMS core in V. These new
rollbacks should not be treated similar to mainline. We would want to
perform GMS core rollback only when all other rescue party mitigations
are already tried. And Phonesky should not be automatically rolled back.

We introduce a new field rollbackImpactLevel to RollbackInfo, which is
used to determine the order in which these rollbacks should be performed
relative to other mitigations in PackageWatchdog.

rollbackImpactLevel is exposed through PackageInstaller.SessionParams.

Bug: 291135724
Test: CTS test. Unit tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a3ae2464aac43d8bbc2129bdea7733d09b90e2da)
Merged-In: I723405eb62577202893ff208af2ab01b212b112a
Change-Id: I723405eb62577202893ff208af2ab01b212b112a

Split flags.aconfig to platform flags and module flags.
Platform flags are used from platform code.
Module flags are used for FlaggedAPI annotations in modules.

This CL cherry-pick ag/25977118 to aosp-main-future.
After this CL, aosp/2919289 can be merged.

Bug: 321624552
Test: TH
Change-Id: Ie8e0f911d0f7d7e81d108b8e8ab539b29a255ad0
Merged-In: Ie8e0f911d0f7d7e81d108b8e8ab539b29a255ad0

This test started failing as it was not able to access
CrashRecoveryProperties. Mocking them in the test fixed it.

Bug: b/323272250
Test: atest PackageWatchdogTest:com.android.server.PackageWatchdogTest

Change-Id: I6ec10adfc17cb85e1c370ff76d08c0aa7e14c11f

The end bounds are stored in PipBoundsState and the transition system
does not have knowledge of the proportional resize, so the value in
pipChange.getEndAbsBounds() is not the correct one.

Updating the rotation handler to correctly update the scale and max
size in OnDisplayChangingListener, so that all future calculations
are using the updated values for scale/max size.

Since the value has been cached locally in PipBoundsState, having
stale invocations would lead to artifacts such as PiP resizing in
unexpected way upon screen rotation or during fixed rotation enter
PiP animation.

Test: manually
Test: atest EnterPipToOtherOrientation
Test: 3 button nav rotation http://recall/-/ekEuGtt9d9HWqkUtAzpHx8/gxlk5IJSb0gVojnPfJvMxY
Test: gesture nav rotation http://recall/-/ekEuGtt9d9HWqkUtAzpHx8/ga3gIHEOVatMVTr6WXQnNX
Test: 3 button nav fixed rotation enter pip http://recall/-/ekEuGtt9d9HWqkUtAzpHx8/8A94b9HbYXvtlEuU8KQO5
Test: gesture nav fixed rotation enter pip http://recall/-/ekEuGtt9d9HWqkUtAzpHx8/gcJsqm3Hu3RaYagOapDXsS
Bug: 322091225
Bug: 319083003
Bug: 308093519
Bug: 323789757
Flag: none

Change-Id: Idc1429577da5c1817fe2f4ad12cefc32e0e86dd6

ViewBehavior will be a static inner class for InputDevice, providing
View-related behaviors pertaining to an InputDevice. We have added an
API in InputDevice to return its ViewBehavior.

This will be helpful if different InputDevice properties affect the way
an input- generated MotionEvent should be handled by a View. For
example, we have implemented a "shouldSmoothScroll" API in this change.
This API is to tell Views processing motions generated by the
InputDevice to prefer animating scrolls caused by such motions, to
deliver a better quality scrolling UX than compared to a regular scroll
that jumps by X pixels in a single frame.

Note that, a single ViewBehavior instance contains all behaviors for a
single InputDevice. This is unlike the other inner static class of
InputDevice: MotionRange. This decision of making a single ViewBehavior
contain all behaviors is made because not all View behaviors may depend
on source+axis (e.g. there could be a behavior that is globally
applicable to the whole InputDevice).

Bug: 246946631
Test: unit tests, manual
Change-Id: I65cf7d6556e26d199c9021f53bdae183f21d3c6d

This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.

For more details please refer to the link below,
<add g3 doc link>

Bug: 304529413
Test: N/A
Change-Id: Iee8a9d8357c174532902d88d5d59e41c6c518c2f

Split flags.aconfig to platform flags and module flags.
Platform flags are used from platform code.
Module flags are used for FlaggedAPI annotations in modules.

Bug: 321624552
Test: TH
Change-Id: Ie8e0f911d0f7d7e81d108b8e8ab539b29a255ad0

While the main fix is on the other change in the topic, this change:
 * Adjust to the installd API change by dropping userId in the call
 * Mark the test as suitable for secondary users

Bug: 319280249
Test: atest FsVerityTest
Test: atest FsVerityTest --user-type secondary_user
Merged-In: I1abc779ddc4fd79644d64b704698d0e7d67a9d75
Change-Id: I1abc779ddc4fd79644d64b704698d0e7d67a9d75

Bug: 321978150
Test: with the flag enabled, run `adb shell settings put system
    touchpad_tap_dragging 1`, try tap dragging (tapping then immediately
    putting your finger back on the touchpad and moving it)
Test: atest com.android.server.input.InputManagerServiceTests
Change-Id: Ieb9ba8961366d1cc9c6cd98e500b5be8f3b2ecac