To monitor stability before moving to presubmit. There are no tests configured to this module other than on cf_gwear_x86-userdebug target

Bug: 345544760
Test: N/A
Change-Id: Ibe888bdac3d97284cf723a2077ea922d83343f6b

Bug: 305193969
Test: PointerIconLoadingTest
Flag: com.android.systemui.enable_vector_cursor_a11y_settings
Change-Id: I0baaa3840e6986bed8875124fb5cab251a2e23ab

Reverts changes from ag/27512378.

Bug: 342596801
Test: atest FlickerTestsOther:EnterSystemSplitTest
Change-Id: I94569986ba89b6c9156fc9baa8fa0244aa0f2829

Bug: 345557347
Test: tested on cf_x86_64_only_auto_md emulator
Test: atest ConcurrentMultiUserTest
Change-Id: I7288e775ae085bb3bbdacf1b7b37766b340b02d6

This is almost certainly a mistake in all cases, and any files that are
text-based have been spot checked to make sure they don't contain a
shebang or have any other indications of intentionally being executable.

Commands run:
    fdfind -t x -e java -x chmod -x
    fdfind -t x -e kt -x chmod -x
    fdfind -t x -e ogg -x chmod -x
    fdfind -t x -e xml -x chmod -x
    fdfind -t x -e aidl -x chmod -x
    fdfind -t x -e html -x chmod -x
    fdfind -t x -e png -x chmod -x

Bug: 345485143
Test: N/A
Flag: Exempt, mechanical change
Change-Id: I2902380611eb51d0c0e18f2f31e41f37163bd922

Test: atest FlickerTestsRotation
Fixes: 345401017
Change-Id: I73ad4e09253acde70d3109e368354fec75dbd7bc

There are still flakes reported in this test. Add DebugInputRule
annotations so that we can use the logs to figure out what went wrong.
The failures are not reproducible locally.

Bug: 339924248
Test: atest AnrTest
Change-Id: I0140b30b7754a66098b580f877a5d17bdd6e4d48

Bug: 305193969
Test: PointerIconTest
Flag: com.android.systemui.enable_vector_cursor_a11y_settings
Change-Id: Ia34f925a4452ad8c410d57b29d431d8afa6b8aa8

When AnrTest was switched to uinput, we lost the behaviour of waiting
for animations to complete prior to injection.

Likely, this caused the test to become flaky, because the activity
sometimes is not launched when we try to send input.

In this CL, we are adding a speculative fix for this by waiting for the
window geometry to stabilize before the injection starts.

Bug: 339924248
Test: atest AnrTest
Change-Id: I60ce69ce4ce8afe8b8fa3c9f48ff82c1a1ec9936

So that at runtime we can dump the id of the group when using protolog without pre-processing the source code.

Test: n/a
Change-Id: If7441fb408203b79193d6e3d9080290edae5dcda

This reverts commit c996b909.

Reason for revert: Fixed CTS tests

Change-Id: I4ebb7d1a05eec41e8c5f603c42972c2e16d60b3d

Prior to this CL, we were injecting events into the unresponsive
activity using "injectInputEvent". The up event was missing, which would
cause the pointer to linger in the gesture monitors. Later in
the test, we were clicking the "close" button. This click would start to
interact with the previous unreleased pointer, causing the notification
shade to get pulled down.

In this CL, we switch to uinput-based injection to make it hermetic.

Bug: 343912075
Test: atest com.android.test.input.AnrTest
Change-Id: I295963080203ee64f50ed9890086b945665c204e

3bebb903

Change-Id: I605177fabae80ea68399aa42a66419119cf02cd3
Bug: 343583446
Bug: 343690533

The downstream effects of an unlock attempt using a pin/password were
not previously tested within the TrustTests. Add these tests in
preparation for further changes to pin/password unlock reporting to
TrustManagerService.

Add options within ScreenLockRule and TrustAgentRule to allow for test
cases to start with strong auth being required, and the device locked.

BUG: b/323086607
Test: `atest TrustTests`
Flag: TEST_ONLY
Change-Id: I1c8eaacc9c20284ef2783bcd65c14f68b0b444e8

Mark the test as flaky since its blocking presubmit
until we've a fix.

Bug: 330486656
Test: atest FlickerTestsIme1
Change-Id: I67cc3ec514c32e85f5e842d8fb9acc628882ab89

Change-Id: I26bf9f4df26576ac769ee5da6a74e605fb358a4b
Fixes: 342551612
Test: FlickerTestsNotification com.android.server.wm.flicker.notification.OpenAppFromLockscreenNotificationColdTest
Flag: TEST_ONLY

it's used in v2/android-platinum/suite/test-mapping-staged-platinum

Change-Id: I87d9aff0dea6344908e44ed693730143f504dbf8
Test: presubmit
Bug: 341947105

Set team to `team: "trendy_team_windowing_sdk"` at per go/flicker-ownership

Test: atest FlickerTestsOtherOpen FlickerTestsOtherRotation FlickerTestsOther
Bug: 342235988
Change-Id: I16cfd92d8ef7c9ff50a8ef3a9345c0b79c9518f9

As strict mode is in place, the default strict_mode is now set to true. We are encourage teams to write tests in strict_mode to make tests Bivalent (able to run on device and devicelessly)
For more info on strict mode: go/roboStrictMode

Flag: NONE
Test: atest SystemUiRoboTests, SpaRoboRNGTests, SettingsLibRoboTests, FrameworksServicesRoboTests, BackupFrameworksServicesRoboTests, InputRoboRNGTests
Bug: 334089788
Change-Id: I9827910496af67eab33efddb7c32d8e40b497c13

To unblock

Bug: 342596801
Test: atest FlickerTestsOther:EnterSystemSplitTest
Change-Id: I117355cfa826ad2f3586a5fcd92ad4a69701cdd1

This reverts commit ec7f7207.

Reason for revert: Fixed tests

Change-Id: Iadd0ea6f09f7f3159f94489c03f28c326bbbb664

The test verifies that there won't be a rotation animation layer for
the rotation change with a show-when-locked seamless rotation activity.

Bug: 333557024
Test: atest OpenShowWhenLockedSeamlessAppRotationTest
Change-Id: If525192159c8c2964a014ef19923bd1b55001c51

To bring test back to runtime SLO

Test: atest FlickerTestsAppLaunch1 FlickerTestsAppLaunch2
Fixes: 335802463
Change-Id: Ie01948f5077a7048890d905029b5e8fad94a2145

This will allow to build them more effectively.
This has no impact on the test execution itself.

Change-Id: I76bbb06b6b5f0e21f096b80da9062863294d2ff4
Test: presubmit
Bug: 341947105

This will allow to build them more effectively.
This has no impact on the test execution itself.

Change-Id: I22183f1f2176e929eb0ab82f9f7eaa20ccb770c8
Test: presubmit
Bug: 341947105

Since we have added a field for the enabled state to InputDeviceInfo, we
have also added the same status field to InputDevice.java. This way, we
won't need to call the isInputDeviceEnabled method in InputManager again
to send a request to InputManagerService to check if the device is
enabled. At this point, we can directly remove the isInputDeviceEnabled
method in InputManager, which is used as a hidden API, since it is no
longer in use.

Bug: 336420877
Test: build & atest InputTests

Change-Id: I9274f0bc66b64b81f9375049cc7bf9535c27d06f
Signed-off-by: Linnan Li <lilinnan@xiaomi.corp-partner.google.com>

So that the AE flicker test is enabled on phone target as well

Bug: 306666082
Test: atest FlickerTestsOther
Change-Id: If8f5c49e3c5f57bc0ba1bea98bbe24169daf5421

These tests are build with -Werror, so we need to migrate them.

Bug: 341129262
Change-Id: I0bd8d03f16f0fef1772826a24f663a7babe2bfcd
Flag: test_only
Test: presubmit
Merged-In: I7661dd73c3f9d0e44cabd928b96cf2affc9cae22

These tests are build with -Werror, so we need to migrate them.

Bug: 341129262
Change-Id: I7661dd73c3f9d0e44cabd928b96cf2affc9cae22
Flag: test_only
Test: presubmit

Change-Id: I523163f59b9ccd00b4b3153e91db39688df390e3

.. so that they are included in the test_suites package

Bug: N/A
Test: check general-tests_list.zip
Change-Id: I79fbb7d66e506cded5c09ae871ef185124f2ce61

include honours set noparent while file does not

https://screenshot.googleplex.com/3UpW43yXjB9fqez

Bug: 341014089
Change-Id: I60678063fbf94542218d5adca80bcf72a700563f
Test: N/A

Update the following:
1. PendingIntent requires FLAG_MUTABLE
2. Bubble/Notification requires POST_NOTIFICATIONS
3. registerReceiver requires RECEIVER_EXPORTED
4. Opt-out force edge-to-edge

Bug: 306666082
Test: pass presubmit
Test: atest PlatformScenarioTests:BackAndHomeOnGMail
Change-Id: I90de055be9c9c270b6815b719209ca8407431d39

Bug: 307359855
Test: JavaDoc update only
Change-Id: Icbc259722581bb3ca8ec40f221b6e03551a5052a

Test: atest FlickerLibTests
Bug: 288396763
Change-Id: Ie55d391d712fbcb62bc34f76b5d74dce962bd4e6

This reverts commit 40c1df0f.

Reason for revert: b/340471057

Change-Id: I7409cc8acb14a7104ce79698d9f14e553f98baf4

The interface name will be used as an additional parameter while
filtering devices based on interface class, subclass and protocol. This
will be used to correctly filter MTP devices based on interface. The
current logic of only using class, subclass and protocol will
incorrectly identify some devices interfaces as supporting MTP

Test: atest UsbManagerTests, Manually verified that interface name is
used for filtering MTP devices correctly
Bug: 312828160
Flag: android.hardware.usb.flags.enable_interface_name_device_filter

Change-Id: I7f6538864a0464cf0fedf677ef075ee98ef02b15

So that AE is enabled on phone target as well

Update the following:
1. PendingIntent requires FLAG_MUTABLE
2. Bubble/Notification requires POST_NOTIFICATIONS
3. registerReceiver requires RECEIVER_EXPORTED
4. Opt-out force edge-to-edge

Bug: 306666082
Test: atest FlickerTestsOther
Change-Id: Ib1c310795ee3723656c9ebd0557831d189eddb6c

Test: silkfx
Change-Id: I95f12306f46fcbdccf14fb7ac8a2620091df61b1

Example output:
$ adb shell dumpsys attestation_verification
AttestationVerificationManagerService
    Event Log:
        Verification #2 [2024-04-25 22:09:52]
            Result: FAILURE(2)
            Certificate Chain Valid (inc. Trust Anchor): FAILURE
        Verification #1 [2024-04-25 22:08:37]
            Result: FAILURE(2)
            Certificate Chain Valid (inc. Trust Anchor): FAILURE

Seeing a result from dumpsys that doesn't fail will need to wait until
there is a user-signed build to test on a locked device. However, here's
an example output from a unit test:

04-25 15:23:23.954   408   467 D AVFTest : Verification #1 [2024-04-25 22:23:23]
04-25 15:23:23.954   408   467 D AVFTest :  Result: FAILURE(2)
04-25 15:23:23.954   408   467 D AVFTest :  Certificate Chain Valid (inc. Trust Anchor): OK
04-25 15:23:23.954   408   467 D AVFTest :  Local Binding: OK
04-25 15:23:23.954   408   467 D AVFTest :   Binding Type: 3
04-25 15:23:23.954   408   467 D AVFTest :  System Ownership: FAILURE
04-25 15:23:23.954   408   467 D AVFTest :  KeyStore Attestation Parameters
04-25 15:23:23.954   408   467 D AVFTest :   OS Version >= 10: OK
04-25 15:23:23.954   408   467 D AVFTest :   OS Patch Level in Range: OK
04-25 15:23:23.954   408   467 D AVFTest :   Attestation Version >= 3: OK
04-25 15:23:23.954   408   467 D AVFTest :   Keymaster Version >= 4: OK
04-25 15:23:23.954   408   467 D AVFTest :   Keymaster HW-Backed: OK
04-25 15:23:23.954   408   467 D AVFTest :   Key is HW Backed: OK
04-25 15:23:23.954   408   467 D AVFTest :   Boot State is VERIFIED: OK
04-25 15:23:23.954   408   467 D AVFTest :   Verified Boot is LOCKED: OK
04-25 15:23:23.954   408   467 D AVFTest :   Key Boot Level in Range: OK
04-25 15:23:23.954   408   467 D AVFTest :   Key Vendor Patch Level in Range: OK

Bug: 335498868
Test: atest AttestationVerificationTest
Change-Id: Iea0b19b3c3a25c5800ebd6fad85c0829a2cfa2b1
Flag: android.security.dump_attestation_verifications