| 4b45f8da5e6c6be2b2d004421995885e9d872d3d |
|
04-May-2018 |
Etan Cohen <etancohen@google.com> |
[AWARE] Update docs for service discovery callbacks
Clarify that service discovery callbacks may be triggered multiple
times (and that therefore apps should deal correctly with it). These
may happen for several reasons (not documented since too low level):
- Peer went out-of-hearing-range and came back
- Peer went out of geofence range and came back
- Concurrency limitations caused discovery to switch from ranging-based
to non-ranging-based or back
Bug: 77925576
Test: N/A
Change-Id: I9fbb909e5bd57fb714aa82bcfeb2834361722149
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 647ee3aeff7c791bb97321c4db5c25e574eff252 |
|
14-Mar-2018 |
Etan Cohen <etancohen@google.com> |
[RTT][AWARE] Minor update to distance documentation
Clarify that measured distance may be negative.
Bug: 63446747
Test: builds
Change-Id: Iff73c1e22dcf98dfce6fc69b7c9d4cf8a05af8d7
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 8c4c5bf27503e0a68e199b9c293f2dac46c96e2f |
|
20-Feb-2018 |
Etan Cohen <etancohen@google.com> |
[AWARE] Update documentation to reflect Aware+Ranging best effort
Documentation update to reflect the "best effort" nature of Aware
discovery + Ranging configuration: if ranging is not enabled or
(temporarily) not available then normal discovery is performed.
Bug: 33821639
Test: builds
Change-Id: Ieb33f840809928f6025774bb9cd31dc1dd878518
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 6570644d02f9b0903bad770c945fef8b38259f62 |
|
07-Dec-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Uhide the RTT in context of Aware discovery API
New APIs to allow Aware discovery sessions to specify a ranging (RTT)
constraint.
Bug: 65108607
Test: unit test, integration tests
Change-Id: Ibbb123fc66676e0bd36b0803c8bac21136a801c0
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 88aa12b88a8aab9b748573796255faf3dd640290 |
|
08-Nov-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Add ranging API to discovery configuration
Add mechanism to enable ranging as a condition for discovery:
- Publisher: enable ranging
- Subscriber: specify min and/or max range (which implicitly
enables ranging)
Add range (distance) information to the discovery message.
Bug: 33821639
Test: unit tests and basic (non functioning integration tests)
Change-Id: Ic50fb72a4a94e56c608ea47ec669f2b59354456f
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| f7908cb6ec5f1df061fd2bcaa659e7961a4c5cd1 |
|
24-May-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Clarify semantics of service discovery parameters
On service discovery which happens on the subscriber we receive
some information about the peer (the publisher): it's id, some
arbitrary blob it's providing (ssi), and a "match filter". The
match filter is the matching criteria (aside from service name)
used to find a service. The semantics are clarified by this CL:
- Unsolicited publish/passive subscriber: the publisher is active
and broadcasting. We're getting the match filter which it
advertises. No change.
- Solicited publish/active subscriber: the publisher is silent
and will only respond if it matches what the subscriber provides.
In such a case we will never know it's exact criteria and
therefore cannot provide it to the app. We're simply providing
the local match criteria. This is a clarification/possible
change from initial understanding.
Bug: 36371061
Test: DiscoveryTest:test_positive_solicited_active_typical
Change-Id: I7d989cf0dc2383d15e4df18c9c0ea079f0486d80
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 8039e6d48d9f77e83f9aa3ccceed6315fd15ac0e |
|
21-Apr-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Add AutoCloseable interface/implementation
Make resource holding classes AutoCloseable. These are objects
which (already) require the client to call a destroy() method.
Note: the destroy() method was renamed to close() - no sense in
identical/duplicate methods.
(cherry-pick of commit 6a4572c89671d9320620eb0ef071dfe0a01de901)
Bug: 37514387
Test: unit tests and integration (sl4a) tests passing.
Change-Id: Ia14065ab9dcd92481412532bfdb198f2e8d9f83c
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 2cbaf22bba4da1b60c551112a97ccc7f2e7157fa |
|
20-Mar-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Remove Publish/Subscribe Count configuration
Simplify API: semantics of publish/subscribe count restrictions
aren't clear at the app level. They depend on DW configuration as
well as discovery session type - number of packets transmitted over
the air.
There's already an app-facing discovery session lifetime configuration -
the TTL. That has clearer semantics and is sufficient (for now).
Bug: 36446307
Test: unit tests and integration (sl4a) tests.
Change-Id: I9129975bd2e1a61b3d23a4b6acaae703b42216c7
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 7c9c4785fcade9f36fd0a30bcab0efe838592f23 |
|
24-Feb-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Remove (hide) sendMessage with retryCount API
Remove the sendMessage(..., retryCount) API (the version
without retryCount) remains. Baseline API already retries
transmissions (at the PHY/MAC layers) - no reason to add
framework-layer retries.
Bug: 35755823
Test: unit tests and integration (sl4a) tests
Change-Id: I49d8bd1e836c09d56f3a9343313f5647eac5c32d
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 6a4b323f08cea4eb538883127ff07302c3b10c46 |
|
10-Jan-2017 |
Etan Cohen <etancohen@google.com> |
[AWARE] Unhide Wi-Fi Aware API (baseline)
Baseline Wi-Fi Aware API providing discovery and connectivity (data-path).
Bug: 30983968
Test: unit tests + integration (sl4a) tests passing.
Change-Id: Idd7c6a625f168717b083d5f13e291ce916571933
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| b84ad8062dc7e7e0cbc87e6a6769741b66dd4568 |
|
24-Dec-2016 |
Etan Cohen <etancohen@google.com> |
[AWARE] Remove reason from discovery session terminate callback
Only valid reason is per request (destroy or timeout/count).
Bug: 32670068
Test: unit tests & integration tests (sl4a) passing
Change-Id: I85d417442e26a16d7f09d6d2d4cbb8ae7a9eba7e
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|
| 3de35a5e5573828838bfa6359a1ac1bf22b19303 |
|
20-Dec-2016 |
Etan Cohen <etancohen@google.com> |
[AWARE] Simplify Wi-Fi Aware API namespace
Simplify Wi-fi Aware API namespace. Rely on project and remove WifiAware
prefix from most classes.
(pure rename operation: no functional changes)
Bug: 31470256
Test: unit-tests + integration (sl4a) tests.
Change-Id: I38b8137c1730c8f40c482c6770caafcaeafd5c46
/frameworks/base/wifi/java/android/net/wifi/aware/DiscoverySessionCallback.java
|