Bug: 289185969
Bug: 291689623
Test: presubmit
Change-Id: I486109b4a617b9ac3b24df59e28a7ea8b2a76c57

Extract methods for requesting IME focus on the view, on the main thread,
and asserting the request is successful.

Update assertion messages to be more explicit about the expected
outcome, and the value being asserted on.

Bug: 292086579
Test: atest InputMethodStressTest
Change-Id: I40fce41cb890349877cf1384d883599d15093378

Test: n/a
Bug: 296390700
Change-Id: I1c0a024ef6e645e6f3d9b2b041879455903be533

Test: atest
Bug: 238043427
Change-Id: I62b6dcd0c0b6ea245c25c53b2733ebcfa320f8ad

Bug: 238043427
Test: atest and presubmit
Change-Id: Idd1cf7584ff45d0e8b1ee31c62fba1330e4f2d81
Merged-In: Idd1cf7584ff45d0e8b1ee31c62fba1330e4f2d81

Bug: 294505270
Test: atest LocaleStoreTest
Change-Id: I4ed0cc6048b7a77550aef3aadc6470d415e0999d

These tests do not currently have any animated notification launch due to the keyguard being occluded. In order to instrument these correctly, we would need to have a correct animation and CUJ for this scenario.

Bug: 294418322
Bug: 290577455
Test: only disabling tests
Change-Id: I92f9d3e21d77f153bd5ff631c17e0d461818394a

This allows me to specify different configurations so that I
can write a test for validating behavior with different configs.

Test: atest this with my other CLs
Bug: 283910436
Change-Id: I2f21b03b57a7b292384380aedab27769f09f22aa

Test: atest
Bug: 238043427

Change-Id: I13b59f36d5c21f9860d3965d47ceea5bb3f40ed0
Merged-In: I13b59f36d5c21f9860d3965d47ceea5bb3f40ed0

Add a flicker test to verify animation background is no longer
visible through the transition after the fix.

Test: atest
Bug: 284148123
Change-Id: Iae41b96f097a428c3eae0e827caa026154fccf3d
Merged-In: Iae41b96f097a428c3eae0e827caa026154fccf3d

Bug: 270677470
Test: n/a, adding logs to debug raven specific flakiness in the lab

Change-Id: I5a12a08d7b804e04144f6473f8e3348ea9e9d339

Ensure rotation is successfully applied before starting the stress test
iterations, as this would previously lead to the first iteration of the
landscape test still being in portrait mode, and incorrectly passing the
assertions.

Test: atest DefaultImeVisibilityTest
Bug: 291742721
Change-Id: Iae068a92601d6dc632f10373ab6ab4bd41dd742d

cf811952

Re-submitting original CL as the issue has been fixed by setting the
correct (SHOW_EXPLICIT) flag for the InputMethodStressTest suite.

Original CL:

Fix SHOW_IMPLICIT and SHOW_EXPLICIT handling

This fixes a bug introduced in the refactor from [1], where
SHOW_IMPLICIT and SHOW_EXPLICIT requests would not be handled correctly,
as they represent the same underlying bit flag value.

IntDefs were added to help understand which set of flags to use
based on call site. Requests originating from InputMethodManager
(and a few from InputMethodService) must utilise InputMethodManager
flags (i.e SHOW_IMPLICIT). When reaching the ImeVisibilityStateComputer,
these are translated to InputMethodService flags (i.e. SHOW_EXPLICIT).

Additonally, this documents and tests that `ImeVisibilityStateComputer`
keeps the strongest state set until a hide request (i.e. an implicit
show request just after a forced / explicit show request, without
any hide requests in between, will still have the
forced / explicit state set).

[1]: Id1115ceb951e4bb0361a32b824d966cc70b7d132

Bug: 289188559
Test: atest DefaultImeVisibilityApplierTest
  DefaultImeVisibilityTest
  ImeVisibilityStateComputerTest
  com.android.inputmethodservice.InputMethodServiceTest

Change-Id: I2117053c5a45253b9537f903a1ac6b3c8bef69af

Test: atest
Bug: 238043427

Change-Id: I02933348d2be62cb31b9ee30177f7c4e47a59ef3

And app can call notifyColorsChanged() on a destroyed engine, which
would cause problems, given it doesn't have a surface anymore.

The same is true to visibility notification, where the engine can be
destroyed before it had the opportuinity of drawing its first frame (if
it had to load large assets for example)

Test: manually change wallpapers
Test: WallpaperServiceTest (both CTS and internal)
Fixes: 291053623
Change-Id: Iff83603695cff491f2045586d5b3f4658f7ae55a
(cherry picked from commit 650a7f8a)

Failure with the new model: expected:<30.0> but was:<24.353516>

Bug: 288354672
Test: atest MotionPredictorTest
Change-Id: Id02b0f7d132e30d2f2a20914ad7ce6377dd42f61

And app can call notifyColorsChanged() on a destroyed engine, which
would cause problems, given it doesn't have a surface anymore.

The same is true to visibility notification, where the engine can be
destroyed before it had the opportuinity of drawing its first frame (if
it had to load large assets for example)

Test: manually change wallpapers
Test: WallpaperServiceTest (both CTS and internal)
Fixes: 291053623
Change-Id: Iff83603695cff491f2045586d5b3f4658f7ae55a

Flicker test about transparent activities launch checking they
inherits bounds from the first opaque activity below.

Fix: 285851726
Test: Run `atest WMShellFlickerTestsOther:OpenTransparentActivityTest`

Change-Id: I09fba66f3b4e4654919385800006a0c76f099fac

TestableLooper.processMessages will block if the argument is less than
the number of available messages.

This adds a new method that will process the minimum of the argument or
available messages and return the number of messages processed.

Test: atest TestableLooperTest
Bug: 289042855
Change-Id: Ied9a3769a0ed2ed7723190853f9091721539df08

Test: atest
Bug: 290736037
Change-Id: I4e2914c5d99debeb11906cf9a880801e30c59c9d

Bug: 238043427
Test: atest

Change-Id: I6e24731fd99a9d751ee29703581afa2bae1ce4c3

When updateNotificationChannel is called for a channel, these changes are propagated to the conversation channels of which the one being updated is parent. This is done by applying the "diff" of the update to each child, only to fields that are not "locked" (i.e. previously set by the user).

Flag: PROPAGATE_CHANNEL_UPDATES_TO_CONVERSATIONS
Test: atest PreferenceHelperTest + manual
Bug: 285932635
Change-Id: I1cf2905ec861d82e68a0a7483838a9b8ca5fdb19

Bug: 289349543
Test: run atest FlickerServerTest and WMShellFlickerServiceTest and make sure files are available in artifacts
Change-Id: Ib389aa7f49b75f69cfc742efb3939bce7682c1cb

Bug: 289349543
Test: atest FlickerServiceTests:com.android.server.wm.flicker.service.notification.flicker
Change-Id: I04eadac724c9e436532d26da74f08b3ae70e6db3

Bug: 289349543
Test: atest FlickerServiceTest
Change-Id: I55e6be8afd3121e4d7bd758fd475c422bf61db9e

Bug: 289349543
Test: atest FlickerServiceTests
Change-Id: I69a3d21bde7d9b1459e4234c8e18028eaf663cc7

Bug: 289349543
Test: atest FlickerServiceTests
Change-Id: I1848ee30bfd8b13193a13e7fac0cd5f523888f6b

With CL[1], we can simply remove the typing logic in
EditTextTypeActivity and also revert CL[2] logic without worrying the
apk signing problem and permission check for injectInputEvent.

[1]: I443f67748dfd3db0deb4cd12ac068975fbebc2c3
[2]: Id3c3490d7ab98a17da4e07d8d62d048c98ff1ec4

Bug: 289210988
Test: atest UiBenchEditTextTypingMicrobenchmark
Test: pts-tradefed run commandAndExit pts-postsubmit-very-long -m PtsUiBench \
   --fastboot-command-preparer:disable  \
   --log-level-display verbose -l VERBOSE \
   --test-arg com.android.tradefed.testtype.AndroidJUnitTest:instrumentation-arg:iterations:=1 \
   --test-arg com.android.tradefed.testtype.AndroidJUnitTest:class:\
   com.android.uibench.microbenchmark.UiBenchEditTextTypingMicrobenchmark#testEditTextTyping

Change-Id: I9a3b6a2a3df101bbd4dba9880944e8b83eb14610

Bug: 289673579
Test: atest FlickerTestsIme
Change-Id: Ie5d36bbba1c858eff878c2497b8de4b2f5fd2780

Test: atest FlickerTestsOther
Bug: 286952194

Change-Id: I69e7a7411b5fc54581e45bbe74cef80f01472e3f

Bug: 288353930
Test: atest WMShellFlickerTestPip
Change-Id: I92ec51ea2a5e7e396ff4c618e03c6530f3257d1b

When the screen is off the nav bar doesn't appear

Test: atest OpenAppFromLockscreenNotificationWithOverlayAppTest
Fixes: 288591572
Bug: 209599395
Change-Id: Ied5d7abc503b22c61f815b7180281c85e6a60722

Currently all other packages are fetch, except for notification

Test: atest FlickerTestsNotification
Bug: 288342341
Change-Id: I107b1d5e16a0fb133787b581ae0c35067dec6cb8

Currently the tests run 2x

Test: atest OpenAppFromLockscreenNotificationWithOverlayAppTest
Bug: 288342341
Change-Id: I567d304350ed6dfabb7724220f9f669c4ef2c7cb

This layer may indeed appear for 1 entry, until the camera buffer loads

Test: atest OpenCameraOnDoubleClickPowerButton
Fixes: 278226203
Change-Id: Icdfa8debb82a771d1cb74154f2ee95b792fe89da

and cover B, ending in a split A|C.

Bug: 238043427
Test: atest
Change-Id: Ia643f9311854f0c1a737121d6d83cdcc714d29a7

The test collects expected APEX package names from listing /apex by a
shell command. The shell command also tries to remove the noise
(normally an APEX has two entires, see below).

$ ls -d /apex/*/
  /apex/com.android.adbd/
  /apex/com.android.adbd@340815002/
  ...
  /apex/com.google.mainline.primary.libs@340716000/
  /apex/sharedlibs/

The test used to deduplicate by filtering out '@'. But apparently an
(DLCA) APEX only has one entry with '@'.

With this change, the shell command removes '@\d+' then deduplicate the
strings.

Bug: 288551133
Test: BinaryTransparencyHostTest#testCollectAllApexInfo
Change-Id: I4bc3e8226dd7790aa276ac5dfad7371c60046384

Test: atest FlickerTests
Bug: 287971366
Change-Id: I3e34e79d2bb7c947390e462335ed72e523760e5b

And avoid androidx startup provider conflict

Test: atest FlickerLibTest
Bug: 269627537
Change-Id: Ibe9dd0fdc2a5ca639434e86d5e62ddc670e30eb2

Don't downgrade assertion to avoid losing coverage

Test: atest FlickerTestsAppClose
Bug: 288369951
Change-Id: I80df9fb5c6ec6995675dcb245dd7e53e49504b8b