Age | Commit message (Collapse) | Author |
|
|
|
Relnote: Now only support to play with Lut on the image. We provide the
pre-defined Lut, and users can check the button to see the results.
Bug: 391680040
Test: play with SilkFX
Flag: EXEMPT demo app development
Change-Id: I0f82126c1fd7cbb474e6c619709de641dfa636b5
|
|
|
|
main
|
|
java.net.SocketException is the parent exception of java.net.ConnectException. Given that java.net.SocketException is sometimes also thrown instead of java.net.ConnectException when the trace processor crashes, we need to expect this class instead.
Bug: 400513449
Flag: TEST_ONLY
Change-Id: Ida197016bf1f36e82bc2c6f6e9ba39bb663aa293
|
|
Behavior for ALL_APPS and ACCESSIBILITY_ALL_APPS is exactly
the same so reducing the enum conflict.
Test: atest InputTests
Bug: 245989146
Flag: EXEMPT refactor
Change-Id: I729362351e7384f7119f1588f3f3be80e12df5fe
|
|
This is now handled by SysfsNodeMonitor.
Bug: 397208968
Test: Presubmit
Flag: EXEMPT bug fix
Change-Id: Ic7c1ed8575a1f332011aa35a207e00c2e0c59133
|
|
|
|
|
|
|
|
|
|
Remove code associated with foreground power key capture for system
apps, including the system API (reverts ag/30871623 and ag/30152916).
The decision was made to abandon this change for 25Q2 as Wallet does not
plan to use this feature with the system app limitation.
The flag is already rolled back in Gantry: see https://gantry.corp.google.com/changes/0a61p0a000001?build_unique_id=ComAndroidHardwareInputOverridePowerKeyBehaviorInFocusedWindowLaunch-platform&apply_default_filter=true&enable_workflow_timeline=false
Context: b/357144512#comment55
Test: atest PowerKeyGestureTests && atest GestureLauncherServicetest &&
atest WindowManagerServiceTests
Test: manually ensuring power button shortcuts remain same as before.
Bug: 357144512
Flag: com.android.hardware.input.override_power_key_behavior_in_focused_window
Change-Id: Ifd533b7e28745dd78be8ff53bd0cc465f248dda4
|
|
Bug: 400513449
Test: atest TracingTests
Flag: TEST_ONLY
Change-Id: I9428ec336017783c177af4a205faaafc4442f3b0
|
|
This change cleans up some duplicate code by moving it to a utility
class.
Bug: 404877363
Test: atest CoreAppJanktestCases
Flag: EXEMPT bugfix/refactor.
Change-Id: Ie8d3ef8369dfc0619f930ed22e18d5ee32ed9b75
|
|
This will help input team ensure that their code is formatted without
doing it manually and dealing with it in code reviews.
Also, run the formatter on the existing files.
Bug: 245989146
Test: repo upload
Flag: TEST_ONLY
Change-Id: I38df2dfa1f76ffe702864c88083a3d579a873442
|
|
When JankTracking is first enabled the JankTracker object is passed the
apps UID. When stats are being reported from non platform libraries we
need to confirm the UID in the reported AppJankStat matches what was
passed in when JankTracking was first enabled. This makes sure that all
metrics and frames are associated to the app correctly.
Bug: 383586335
Test: atest CoreAppJankTestCases
Flag: EXEMPT bugfix
Change-Id: I12c827bcfc06e4e4d3de08fce0b65e5c93574c47
|
|
|
|
Upstream Mockito has deleted the deprecated matchers. Migrates usage to replacements
to unblock upgrade.
Test: m checkbuild
Flag: TEST_ONLY
Bug: 310268946
Change-Id: I7a44a6b5acb32044613358899f13b6fe355a6ebd
|
|
Fixes a bug in where kcm fallbacks with search based modifiers could
not activate since PhoneWindowManager would consume all search events.
This prevented the InputDispatcher from generating the fallback.
This change modifies the behavior so that when a search-based
fallback is detected, the key event will be directly sent to
InputDispatcher to handle the fallback. This will NOT send the
original event to applications.
Bug: 384113980
Test: atest PhoneWindowManagerTest
Test: atest InputTests:InputManagerServiceTests
Flag: com.android.hardware.input.fix_search_modifier_fallbacks
Change-Id: Iacecf945ea6be9841b6009d5f30bcf83f68309ef
|
|
|
|
|
|
On some devices, error dialogs aren't supposed. Skip the 'wait for the
app' test on those devices. Also skip looking for ANR dialog on the
'close app' test.
Also, increase the timeout for waiting for the activity to launch and
bind. When run on auto_md cf remote target, this is taking > 5 seconds
to launch and connect. So it used to fail with the following message
when the timeout was equal to 5 seconds:
STACKTRACE:
junit.framework.AssertionFailedError: UnresponsiveGestureMonitorActivity failed to call 'provideActivityInfo'
at junit.framework.Assert.fail(Assert.java:50)
at android.testing.PollingCheck.check(PollingCheck.java:73)
at com.android.test.input.AnrTest.startUnresponsiveActivity(AnrTest.kt:235)
at com.android.test.input.AnrTest.setUp(AnrTest.kt:132)
And even with the multiplied timeout, the test used to fail, so increase
the timeout to 10 seconds at the same time.
When the ANR dialog is skipped, we need to ensure that we wait for "exit
reasons" for a long time, because we are no longer waiting for the ANR
dialog to appear.
To run the test on auto cf md:
$ lunch cf_x86_64_only_auto_md-trunk_staging-userdebug
$ acloud create --local-image --boot-timeout 1000
$ atest AnrTest
Flag: TEST_ONLY
Bug: 339924248
Test: atest AnrTest
Change-Id: I031361e48c8bcdeac7489555d1c12df1a956a982
|
|
|
|
into main am: 8fbdf7c842 am: 915abab4fd
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3534300
Change-Id: I311b004f13f559730846576e52cfe82ab48c76b1
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into main
|
|
Test: 'atest FsVerityTest' on devices with 4K, 16K,
and "simulated" 16K page size
Bug: 397562534
Flag: TEST_ONLY
Change-Id: I53662a16415a2471a7ac27559123a0e42f6ea762
|
|
handleKeyGestureEvent() is synchronous API that makes system server
dependent on handler and can cause ANR if handlers misbehave.
As a replacement, handlers should provide list of gesture they want
to listen to. For consistency, we only allow single handler per
gesture.
Test: atest InputTests
Test: atest WmTests
Test: Presubmit
Bug: 358569822
Bug: 383602794
Flag: EXEMPT refactor
Change-Id: Iea0f6ba3360ed241e19f0265d6ab28fd7889aafa
|
|
Upstream Mockito has deleted the deprecated matchers
in the latest version. Migrate usage to replacements
to unblock upgrade.
Test: m checkbuild
Flag: TEST_ONLY
Bug: 310268946
Change-Id: I79cef17cbbe442d03194ca165151ee5e615767b0
|
|
|
|
Since the fsverity_api flag was launched, FsVerityTest can now assume
that it is enabled.
Bug: 285185747
Test: atest FsVerityTest
Flag: TEST_ONLY
Change-Id: I3f75490a6fa94391c63d1d24ab374f4ffbf82179
|
|
into main
|
|
Bug: 396782079
Test: v2/mainline-engprod/apct/mainline/tethering/R/device-all-gce
test skipped
Test: preubmit
Flag: EXEMPT; test code
Change-Id: I0fb4cfb8ba300bb3d361536377fda5f9f0f8c3d9
|
|
|
|
The method has been replaced by verifyNo(More)Interactions
in later Mockito versions.
Test: m checkbuild
Flag: TEST_ONLY
Bug: 310268946
Change-Id: I57faa43a5f158bb131f64c19d93de99e04f257ca
|
|
|
|
This would make these test start running as mts for coverage
Bug: 354112511
Test: atest PackageWatchdogTest
Flag: EXEMPT moving test
Change-Id: If4ea7d54e2f9eaddeb3eb5bb355acc9300202e07
|
|
|
|
|
|
Some tests need it, and it's harmless.
Bug: 379472827
Flag: EXEMPT test-only
Change-Id: Ic7ee829a5d5663d63d3dd486c353107c6bcdcab5
|
|
Bug: 400865401
Test: atest PointerIconLoadingTest
Flag: TEST_ONLY
Change-Id: I9e97e2db2bd409f1a6121f43baf596e343ddff0f
|
|
|
|
"vaibhav_isKeygestureSupported_refactor" into main
* changes:
(3/n) Remove usage of isKeyGestureSupported() from KeyGestureController
(2/n) Remove usage of isKeyGestureSupported() from KeyGestureController
|
|
Flag: EXEMPT test-only code
Bug: 379472827
Change-Id: Idf4fb68eba9b50a798455e8e32bede20b34fabdf
|
|
Flag: EXEMPT test-only code
Bug: 379472827
Change-Id: I25ee7d044452c67b24132850ae39776914da168a
|
|
|
|
It interferes with the test by showing a dialog. It was already disabled for other test suites
Flag: TEST_ONLY
Test: atest FlickerTests WMShellFlickerTests
Fixes: 400664547
Change-Id: Iad6bd28a790a1a9fed418d537dfdbfcc18282eb2
|
|
* changes:
BatteryControllerTests: create TestableContext as a @Rule
TouchpadDebugView tests: Use TestableContext as a @Rule
|
|
This is the way that TestableContext's JavaDoc recommends, to let it
clean up after itself once the test finishes, so we should do it anyway.
However, it won't fix b/339924248 on its own.
Bug: 339924248
Test: $ atest InputTests:com.android.server.input.BatteryControllerTests
Flag: TEST_ONLY
Change-Id: I53b40671286530a7c411cfff6bc08239f5baf13b
|
|
This is the way that TestableContext's JavaDoc recommends, to let it
clean up after itself once the test finishes, so we should do it anyway.
However, unfortunately, it doesn't fix b/339924248, where
com.android.test.input.AnrTest fails if it's run after the touchpad
debug view tests.
Bug: 339924248
Test: $ atest \
InputTests:com.android.server.input.debug.TouchpadDebugViewTest \
InputTests:com.android.server.input.debug.TouchpadDebugViewControllerTests
Flag: TEST_ONLY
Change-Id: Ia5a480ccbdc05491c7e0bab8c269aa5bd55a205c
|
|
Test: m checkbuild
Flag: TEST_ONLY
Bug: 310268946
Change-Id: Id68adb5ab554a8031f8d03f6158c0e9ffa03604c
|