Clarify that limits include "=". This is particuarly critical for
the lower range value of 0 since in very close quarters measurements
will result in negative values which will be translated to a 0 - i.e.
must have >=0 for ranging to trigger discovery.
Bug: 65108607
Test: N/A
Change-Id: I443c2fff7fe8dad6133d66a82f645a8304787f4c
Clarify that this method is only available to device owner and
profile owner.
Change-Id: I2f77a16442a0403cc7895bdc3b8375cb22cb68a9
Fixes: 70038439
Test: builds
Responder to ANYONE was deprecated for API >= P. But the manager
code did not check for target API - i.e. even older apps would have
been rejected. Added the target API check to the manager code.
Bug: 72175022
Test: unit test + integration tests
Change-Id: I52e0c877e0af0756816b5b13e42f432504461e20
Legacy RTT APIs wrap around the new RTT API. The translation of
results from new to legacy APIs allocated the full number of
results - but only filled-in one of the results - the others
were left null.
Bug: 73884773
Test: RangeApSupporting11McTest:test_legacy_rtt_80211mc_supporting_aps
passes with multiple APs
Change-Id: Id5ec70de272868d92154bdca9eee1d398c3a1801
Update PeerHandle doc to relfect that while can be compared and hashed,
good practice will use an app level identifier.
Bug: 68931709
Test: 'make update-api' and reviewed generated doc
Change-Id: If6725e8854976d482ca18429a9b5352cff0baf93
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
API review mods: change ranging timestamp to milliseconds. Update
docs to clarify which time is being measured.
Bug: 73088768
Test: unit tests & integration tests
Change-Id: I8a81e92d1a3d264abd98a1695be6a5da6fa5f6a1
Changed from units of -0.5dB to units of +1dB (original is what comes
from the firmware).
Per API council feedback.
Bug: 73088768
Test: unit tests & integration tests
Change-Id: I77ccbf76f947f29b24a701626e0a1517dd85729e
Move LCI/LCR to a System API - unparsed:
- Punting parsing for future release
- Not widely available in APs for testing
- Usability/deployment unclear
Bug: 71643239
Bug: 73088768
Test: unit tests & sanity integration tests
Change-Id: Idd3bded55e887abbad6c51b00b31e75c859ba579
Legacy RTT API permitted access of results (e.g. distance) even
when the measurement failed - the new API throws an exception.
Add checks to the translation code (from new to legacy) so that
exceptions aren't thrown - results are simply 0.
Bug: 73297815
Test: builds, integration test is being developed
Change-Id: I8286e36afe5597cc372e65b75f03a382ca0cd2b3
Add an error code which will be used when the Responder does not
support IEEE 802.11mc - and by implication when such non-support
results in an error.
Note: @hide for now - will be unhidden in a subsequent CL.
Bug: 72975604
Test: unit tests, integration tests
Change-Id: I903abe6cfe19e771e4e4cdaadec48e82f009cbf3
Update documentation with references to (now) public API specifying
the ranging configuration of Aware devices.
Bug: 73088768
Test: builds
Change-Id: Iedb69550cfb249050bb9e92f3e698f8f7db2ff85
Remove the legacy RTT service. RTT requests are already directed to
the new API by a previous CL.
Bug: 65108579
Test: unit tests
Test: WifiRttManagerTest:test_regular_scan_then_rtt_ranging_stress
Change-Id: I436e8bcd2f4e2ba6056870d887eea141fbebae85
Set the default value of Randomized MAC address as 0:0:0:0:0:0 instead
of null.
Making this change to simplify storing randomized address to XML for
permanent storage. Without this change, will need to manually check if
the value is null during MacAddress<->XML conversion.
Bug: 72753415
Test: Unittest.
Change-Id: I6edf486360e267acec9f8a343386444be2ea99fa
ParcelableRttResults was unparceled incorrectly.
Bug: 70398564
Test: exploit provided in bug no longer works
Change-Id: Ifd6de547e9861bbebc399b43d0cc2899a8160813
Route legacy RttManager API on top of new WifiRttManager API - but
only support the legacy startRanging call. All others (including
Responder modes) are deprecated and throw an exception.
Note: the deprecation tags will be in a separate CL.
Bug: 65108579
Test: unit tests pass
Test: WifiRttManagerTest:test_regular_scan_then_rtt_ranging_stress
Change-Id: I63541fdcaac36f4bb40ed71660bbcfc507693ffc
