When configuring Aware discovery with ranging validate that the RTT
feature is present on the device.
Bug: 63906015
Test: unit tests, integration tests
Change-Id: Ie12feaf84f17c075f0e60bdacfc14af3703124c3
Change to a sensible name which doesn't conflict with legacy RTT
service.
Bug: 65108607
Test: unit test, integration test
Change-Id: I54855635061c09e8d4bd2e97bac049f2893de123
MacAddress class is being added as a public API. Convert ad-hoc
byte[] represetations to new class.
Bug: 65108607
Test: unit tests and integration tests
Change-Id: I4bf3b7c47f37d4ef4dd5af0dcdeb7d57f2f94368
Responder was using the new MacAddress before its finalization.
Fix reference to a (now removed) constructor.
Bug: 65014962
Test: unit tests & integration tests
Change-Id: I4d0fd32454c1362129e03deada2d6e6a253e2590
Direct Aware Responder configuration set to the basic rates (discovery
channel 6, 20MHz bandwidth). It is expected that these will be ignored
and that (with a Ranging enabled Responder Publisher) enabled on the peer
a high accuracy RTT will be negotiated.
Bug: 67678464
Test: unit test & integration test (non-functional at this point)
Change-Id: I240cfef91a968cd1eb75a71b5ead96ae4eccb32d
Add public equals()/hash() methods to PeerHandle. Allows the handle to
be used across multiple calls/sessions.
Bug: 68931709
Test: builds, unit test, integration test
Change-Id: Idc59269d4275181ed6d9a793213c681dc4e98134
Add a generic Responder mode which is the common configuration for
any peer (which any peer configuration can be translated to).
Bug: 65014962
Test: unit tests and integration tests
Change-Id: If2f6abc217508792d319d7d5e54aa3f7385b0ec5
When emitting a method or field, verify that we're able to reference
all mentioned types. This ensures that we don't accidentally
reference undefined classes/interfaces.
Test: manual inspection of API files
Bug: 69791141
Change-Id: I84e0c87fe83daa118661f61dbdf17b58ea5282d4
Passpoint Provisioning status and failure codes to be used by callback
API to provide information to the caller about the provisioning flow
Bug: 67914151
Test: Unit test
Change-Id: If1bf28ac8e2e0b7d8141d1b9cb12e3a6e46cb126
Created a new hidden API to be called for starting subscription
provisioning with a certain provider. Create a callback interface and a
callback object to be used by the caller to get provisioning status
updates.
Bug: 67645546
Test: Unit tests
Change-Id: I9592222cfe79c5859c455c5a658956120558059f
Since the packet rate fields of WifiInfo now have sane units (pps),
remove the getters.
Bug: 68204362
Test: Unit tests
Change-Id: Ib699cef91a8e10aaca05994ba1617ac5556d110f
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
Useful for dev, should now be off by default.
Bug: 65108607
Test: builds, unit tests, integration tests
Change-Id: I3090d804073e1ecaf7fcbddcac9f36b577add6bc
Add System API to manage ranging operations. Use WorkSource to specify
the actual source of the operation. Add cancel API (using WorkSource)
to allow cleaning-up (proxying binder death).
Bug: 65015291
Test: unit tests and integration tests
Change-Id: I98f762df8b1d262d1f386963e7e2ff3569b001d5
The getSSID() method used to return a string with no quotes before
Android J, so add documentation mentioning when this was changed.
Bug: 12957620
Test: Compiles & verified that the docs are updated (make
doc-comment-check-docs).
Change-Id: I5d3713303c8f8c5c09d74ad1c5b8398107847b87
Add a broadcast + availability API allowing apps to keep track of when
Wi-Fi RTT is available.
Bug: 65014694
Test: unit tests and integration tests
Change-Id: I06f4f022c3fc6200be2308931b1fc886ae0ba37e
Bug: 67967771
Test: Ran make ds-docs.
We don't actually document how to do a Wi-Fi scan anywhere on DAC;
at the moment, this seems like the place where it makes the most sense
to provide that guidance.
The forcing function for doing this is that a new doc explicitly
recommends that devs do Wi-Fi scans in certain cases, but doesn't
have a place to link to that tells them how to do so. That doc
plans to send readers here.
Change-Id: Ic35fb77d323e825e5bd5b4eec2716730f0d531e1
Delete the @removed setWifiApEnabled call along with any remaining
callers.
Bug: 66917593
Bug: 26753849
Test: frameworks/base/wifi/tests/runtests.sh
Change-Id: Ieefc59e01d801d9f5a943830c66c86e9e624158c
Now that the WifiManager.setWifiApEnabled call is deprecated and
removed, delete the underlying code.
Bug: 66917593
Test: frameworks/opt/net/wifi/tests/wifitests/runtests.sh
Test: frameworks/base/wifi/tests/runtests.sh
Change-Id: If68ddd3e2301b0ba9efc3914e2a0f0e17436ccf0
Change the units (and name) of the ranging result from CM to MM.
Bug: 65108607
Test: unit tests & integration tests
Change-Id: Id4d3d25e508d6a743c0fe13c9829c0a2ba4196c3
API council feedback:
- Ap -> AccessPoint
- Timestamp -> add us unit
Bug: 65108607
Test: unit tests & integration test suite
Change-Id: I733ab9e07e7ced2fa15144eea2c395fe267ce974
Add API to specify RTT requests to Wi-FI Aware peers specified either
using their MAC address (out-of-band discovery) or their PeerHandle
(in-band discovery).
Bug: 65015034
Test: unit tests + integration tests
Change-Id: I1cb8e90cab7c1acc621576703c9d0c6f4f5ac8d4
Using enforce instead of silently ignoring calls with insufficient
permissions to let apps know that the operation failed.
Bug: 67008628
Test: Toggle verbose logging successfully from Settings.
Change-Id: I322e870212a7dbbd2e864635b1d0ccb3df613555
Add API which returns all Wi-Fi configurations corresponding to
Passpoint configurations installed on the device AND usable on
the specified AP (ScanResult).
Bug: 67891871
Test: unit tests
Change-Id: Ie9e6abea23f4376f78c75d09b3a2e25e58a416b0
