| 0c4a9266264d37e724f7372ef7ef932cf60c505c |
|
10-Jun-2017 |
Eugene Susla <eugenesusla@google.com> |
Support associating with an already-paired device
This is required for migration scenario, where device(s) are already
paired(and thus no longer discoverable) but didn't go through companion
flow.
This also fixes a bug with filtering by mac address, which is also relevant to
the use-case of associating a specific device
Test: Pair with a device first, and call associate with a filter with its MAC
address and single device requested. Ensure the device is found.
Ensure only that device is ever returned when filtering by MAC address.
Bug: 62487084
Change-Id: Ic7cc6affc0648ad85b15620e8c3aba4b9fc91aa1
/frameworks/base/core/java/com/android/internal/util/CollectionUtils.java
|
| cf00adebec29d4cdbec5bc0f004b26a09327c236 |
|
10-Apr-2017 |
Eugene Susla <eugenesusla@google.com> |
API for notification listener for Companioon apps
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
/frameworks/base/core/java/com/android/internal/util/CollectionUtils.java
|
| 4df89bcb31cde334dc317cce705a75b0ff036a8a |
|
29-Mar-2017 |
Eugene Susla <eugenesusla@google.com> |
[DO NOT MERGE] Fix associations serialization optimization bug
There mas a missing defensive copy causing false positive detections of
"associations not changed" case, leading to xml file not being updated once
at least one record is present
Bug: 30932767
Test: Associate at least two different devices and ensure the xml has both.
Change-Id: Ic0dc615dd2b847e137555c1084c616831b4dde83
/frameworks/base/core/java/com/android/internal/util/CollectionUtils.java
|
| 6a7006a9683ba5a79ca338050c7c50b346b04de0 |
|
13-Mar-2017 |
Eugene Susla <eugenesusla@google.com> |
Register PackageMonitor for CompanionDeviceManagerService
1. On package removed -> remove all its associations
2. On package updated -> if had associations, update special access permission
in accordance with (potentially changed) permission entries in manifest
Bug: 30932767
Test: 1. Remove app, and ensure xml entries for it got removed.
2. adb install new version of app without special permissions in manifest, and
ensure whitelist removal method got called
Change-Id: I87261c05ddcf40a18332d160b44ee2f8284df5e4
/frameworks/base/core/java/com/android/internal/util/CollectionUtils.java
|