Use TimeUtils to format the time display fields which hold wall clock
time.
Also, use |elapsedRealTime| to calculate the time durations for the
fields which are populated using elapsedRealTime.
Bug: 77224338
Test: Unit tests
Test: 'adb shell dumpsys wifi'
Change-Id: I850ebdc3ba1f7bfb7d5137382d2feed7e551c311
The api for setWifiApConfiguration allows for config saves to return
false, but the implementation always returns true (if there wasn't an
exception thrown). This CL allows the API to actually return false and
adds unittests.
Bug: 67601382
Test: frameworks/base/wifi/tests/runtests.sh
Test: frameworks/opt/net/wifi/tests/wifitests/runtests.sh
Test: manually update ap config in settings and verify save
Test: wifi integration tests
Change-Id: I038ab68f5fc4bf22df5b61d329077eacda547338
Some call sites using explicit TRANSPORT types want to know about the
raw underlying transport, and they don't want to know about VPNs
that are going over that transport.
For example, SettingsLib always wants to know about the actual
Wi-Fi network, so it uses NOT_VPN to avoid being confused by VPN
networks that are backed by a TRANSPORT_WIFI network.
GnssLocationProvider wants to know about any validated internet
access, regardless of the underlying transport.
Test: atest com.android.settingslib.wifi
Bug: 68499889
Change-Id: Ib5897946d856444d9ff3b54c4aeace6baa42f8bf
The RTT distance and standard deviation are calculated based on a set
of N measurements. Of those M (M<=N) may be successful.
The quality of the provided results can be assessed by 2 measures:
1. The standard deviation of the results
The standard deviation is only valid if the number of successful
measurements is >1 otherwise a 0 is returned. A value of 0 cannot be
differentiated from a legitimate 0 standard deviation.
In one case (number of samples > 1) a standard deviation of 0 indicates
high confidence in the result. In the other case (number of samples = 0)
no confidence information can be derived.
2. The ratio of successful to total attempted measurements
Add API which provides the number of attempted measurements and number
of successful measurements used to calculate the final results.
Bug: 76445930
Test: N/A (unhide CL only, code verified earlier)
Change-Id: Ia7322b3abc28e83c29d0b0ae79db30fd99bb7fe1
Add information about the number of attemped and successful measurements
used to calculate the final results (especially critical for standard
deviation).
Bug: 76445930
Test: unit tests & integration tests
Change-Id: I906b6e8a4d74799447ab7c2e55965fdd448dc470
Since we are using "02:00:00:00:00:00" as the default/invalid MAC
address in the Wifi Framework, we should make it invalid for Connected
MAC Randomization for consistency.
Updated the configuration to use "02:00:00:00:00:00" as the default
invalid MAC and attempt multiple time to generate valid random MAC.
Bug: 74436465
Bug: 74446723
Test: Unittest
Change-Id: Ia5ac806d478191d7e8fad247d5c3a1b97d16498f
This is needed for client mode operations for configuring WPA_PSK
networks. There is no alternative public value for WPA_PSK.
The intention was to deprecate usage of this value for AP
mode, but since we share the same object across client & AP mode
operations, we cannot mark this field deprecated.
Bug: 72332080
Test: make update-api
Change-Id: I75f675b630080d853422f945d7cbc37c5f205fde
This is an internal cleanup patch
Bug: 68388459
Test: compile, unit tests
Test: manual test that wifi scan still works
Change-Id: I30ee0b342a04fe55fc8da8142600ccc4d34b30c1
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
This change sets LOCAL_SDK_VERSION for all packages where
this is possible without breaking the build, and
LOCAL_PRIVATE_PLATFORM_APIS := true otherwise.
Setting one of these two will be made required soon, and this
is a change in preparation for that. Not setting LOCAL_SDK_VERSION
makes the app implicitly depend on the bootclasspath, which is
often not required. This change effectively makes depending on
private apis opt-in rather than opt-out.
Test: make relevant packages
Bug: 73535841
Exempt-From-Owner-Approval: Global cleanup
Change-Id: I26458e41ecb84de91ac9a356a5d4bafb44f463c1
Clarify that this method is only available to device owner and
profile owner.
Change-Id: I2f77a16442a0403cc7895bdc3b8375cb22cb68a9
Fixes: 70038439
Test: builds
Removing @hide class that's not being used.
Bug: 74019502
Test: compile, run ./frameworks/base/wifi/tests/runtests.sh
This is CP from master fbce0f15544edc80b1ae49061f6fee365e3a2fea
Change-Id: I8b364bfa09f6fe6a585fbec01e5ff94b8b745bca
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
