Support OWE in transition mode for devices with OWE support
and devices without OWE support. Scan results will return a
new type of network for OWE in transition networks on devices
that support OWE, and Open for devices that don't support OWE.
Handle the case where Open network is manually added to a device
that supports OWE.
Bug: 132139642
Test: Device with OWE: Connect to Open, OWE-Transition, OWE networks
Test: Device without OWE: Connect to Open, OWE-Transition
Test: Manually create Open network, connect to OWE-Transition
Change-Id: I29e69eaae2672562420ee7c6393bf2cc4d7f1b91
Add FT/SAE AKM to InformationElementUtil class and parse it correctly so
that the phone would be able to associate with APs advertising it.
Added additional unit tests that were missing.
Bug: 132378498
Test: atest InformationElementUtilTest
Change-Id: I470e4e071de36dfe8f79475477c6077ed8bef3cb
With change ag/7340724, the device's P2P MAC adress will only be
available to callers holding the LOCAL_MAC_ADDRESS permission, and will
be anonymized otherwise. This CL updates the documentation in
WifiP2pManager to reflect that.
Bug: 132055766
Test: atest tests/src/android/net/wifi/
Change-Id: I9c2b5ce2cb2c2d2d6766fd34f3451ad4f22a5698
wpa_supplicant accepts a semicolon delimited list of domain suffixes.
Update the javadoc to reflect this.
Bug: 130664269
Test: No code changes
Change-Id: I93dbabeddb8854112b413dbb27d094d9d187a73c
The package information of caller is needed to check the SDK version in
WifiService layer.
Bug: 124301934
Test: ./frameworks/base/wifi/tests/runtests.sh
Change-Id: I07020da22f044bdd32d376787fc14690bf926513
Signed-off-by: Ecco Park <eccopark@google.com>
This code is mostly a NO-OP for most apps & OEM's. The pinner only takes
effect if the app's target SDK < Android L. But, there might
be some OEM's who may want to enable this for all apps.
Bug: 129906426
Test: Compiles
Change-Id: Iccf67ba0d4ea8d9c5d3561a128908611636b420e
There were a number of Javadoc style problems in the
WifiNetworkSuggestion.Builder.build() docs, which caused some formatting
problems.
One specific problem worth noting: A {{ causes trouble at publish time,
because it looks like the start of a Django directive. But escaping the
{ -- e.g. { -- doesn't work, because the Javadoc compiler helpfully
escapes the *ampersand*, so the HTML output is "&#123", which
renders on the page as "{" instead of "{". So putting a space
between the two braces seems like the simplest solution.
No code changes here, just Javadoc comment fixes.
Tested by building the docs and staging to:
http://go/dac-stage/reference/android/net/wifi/WifiNetworkSuggestion.Builder#build
Screenshots (in case the stage gets overwritten):
https://screenshot.googleplex.com/o4p7efFGCbJ.png (1)
https://screenshot.googleplex.com/nkhEqU54LNb.png (2)
Bug: 128536865
Test: make ds-docs (then build & stage)
Change-Id: Ie04bc4dc517443a6899aba989beeb38b9299826e
For apps targeting older SDK (<Q), preserve the old behavior for
setWifiEnabled.
Bug: 129549163
Test: Compiles
Change-Id: I4a2e89cfa1c1ac612a679ecab6a2d526a987f7c0
This reverts commit 506a9b9517.
Bug: 126503889
Reason for revert: UI changes was punted to R. No rationale in making this API changing behavior now.
Change-Id: Ia8ccacc383cdb6db7520657a46d77bc1154f8569
Based on discussion with IEEE 802.11 WG these are not necessary for RTT.
Bug: 111439464
Test: All unit tests pass; end-to-end tests pass.
Change-Id: I78adc0257cf65cfad9698f3d43342d5404d790e5
Rename getIsSameRegisteredCell() to isSameRegisteredCell().
Bug: 128919394
Test: wifi unit test with frameworks/base/wifi/tests/runtests.sh
Change-Id: I3549d9abbaba87971ea3c0a9edf4351289731912
Initialize Suite-B ciphers correctly based on the CA cert type. Read the
cert type from key store, parse it and get the signature algorithm.
Enforce SHA384, and initialize AllowedSuiteBCiphers based on the
certificate type: RSA or ECSDA.
Bug: 128861164
Test: Verify Suite-B initialized correctly with RSA and ECDSA certs.
Test: Associate to SUITE_B_192 AP.
Test: atest WifiNetworkSuggestionTest
Change-Id: Ia9b8460caa586f695ed7aab3507ddeb4ecb8c3f3
The current ordering of priority is hard to handle inside the wifi
stack because "-1" was unassigned priority and 0 is considered the
higheest priority level.
Reverse the polarity so it's much easier to compare network
suggestions with different priorities such that
priority1 > priority2 is always true. unassigned priority will always
be lesser than any assigned priority value.
Bug: 127644378
Test: Compiles
Change-Id: I74dacdb85838250c242257a80ebbe6046cef752f
API council feedback:
- Move required builder methods to the constructor
- Add IntRange to port and transport protocol APIs
Bug: 128904106
Test: atest android.net.wifi.aware
Test: atest com.android.server.wifi.aware
Test: CtsVerifier Aware tests
Change-Id: I9bc978732caeada792e997bdd6263a53efdf7071
One of the code samples in a Javadoc comment contains a {{ ;
this gets interpreted as a Django directive by our docs publish tool
(go/devsite2cmd), which results in a syntax error. We verified
(http://cl/238522152 ) that escaping one of the {s resolves the
issue.
Tested by building the docs and staging to:
http://go/mivi-stage/reference/android/net/wifi/WifiNetworkSuggestion.Builder
Bug: 128536865
Test: make ds-docs
Change-Id: I70a3e0481ad195665c878c72d0ec6b1ccbbf958f
Exempt-From-Owner-Approval: Doc-only change
Deleting EAP Wi-Fi configuration deletes shared credentials used by other
configs. To resolve this issue the following changes were implemented:
1. When manually adding Wi-Fi certs from storage, Wi-Fi will not attempt
to delete them when network is removed.
2. When apps use WifiEnterpriseConfig#setClientKeyEntry to add certs,
they will be deleted if the network is removed.
3. Allow the user to delete Wi-Fi certs the same way that allows the
user to add them. Make the "Remove" option available, and implement key
store removal in settings.
Bug: 30248175
Test: atest WifiEnterpriseConfigTest
Test: Load certs, remove certs from credentials menu
Test: Load cert, create 2 EAP networks that use it, forget one network
Change-Id: I5bb1a1e02437b4db4a9c0a289acc074c30a786ab
Also, added a constant to indicate the start of the permanent
blacklist reasons.
Bug: 126503889
Test: Compiles
Change-Id: I4ba1dc5377bffe34a9f236c0698c36cbf34969a9
Modified builder methods to:
a) Add boolean input for all boolean setters.
b) Add a public value for unassigned priority and added IntRange
annotation.
Bug: 128317241
Bug: 128317186
Test: Compiles
Test: ./frameworks/base/wifi/tests/runtest.sh
Change-Id: Iaf9d26ed857fe9337d3e4006c9c894efbcfa32dd
This commit provides an update to the WifiLock types API documentation.
It adds the condition of the device to be connected to an access point
for lock to be active. This applies to both high perf and low latency
locks.
Bug: 127884567
Test: None
Change-Id: If65681939058a5d6508cf0a970517fa856cc04b3
Note: API only change - no functional changes
Move the Builder class and method which generates WifiAwareNetworkSpecifier
to the class it actually builds and have it return that type.
Per API council feedback to match standard builder patterns.
Bug: 126700127
Test: builds + make docs
Test: atest com.android.server.wifi.aware
Test: atest android.net.wifi.aware
Test: atest SingleDeviceTest (CTS)
Change-Id: If4d58e96b4a268df7afe58bc3d883b6c54ec889d
Add annotations to ParcelablePeerHandle per API council feedback.
Bug: 126375748
Bug: 126701031
Test: atest android.net.wifi.aware
Change-Id: I60471659dd9dd267b10507d5fb5e7639b3c964c2
