| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Bug: https://issuetracker.google.com/issues/139695999
Test: A11y unit tests (I did't find a way to reproduce the bug)
Change-Id: I0aa8f417b157ca3d96b61b8d9356dd65df360dae
Signed-off-by: wangmingming1 <wangmingming1@xiaomi.com>
|
| |
|
|
|
|
|
|
| |
Test: 1. Trigger the confitrmation dialog.
Ensure it looks exactly like the one from settings.
2. Call an API without associating the appa first
Ensure exception is thrown with a message mentioning the need to associate 1st
Change-Id: I94d4116e1988db869ed445ae3fd018c50590e3f4
|
| |
|
|
|
|
|
|
|
|
|
| |
The first item in such lists was improperly generated and
included type information.
Bug: 35209951
Test: Looked at enabled_accessibility_services after performing
accessibility shortcut
Change-Id: I715ea6276a23e421e4c0611a4b66af5566db90bc
|
|
|
This introduces an API for apps that support companion devices to provide a
more streamlined flow for pairing and setting up the device
Bug: 30932767
Test: Using a toy app, invoke the newly introduced API (CompanionDeviceManager),
and go through the flow. Ensure filtering works, and device is returned to
the calling app. Ensure the calling app can pair to the selected device.
Change-Id: I0aeb653afd65e4adead13ea9c7248ec20971b04a
|