If STA and NAN share the same iface wlan0, Wi-Fi vendor HAL service
sends eventDisabled to NAN framework when STA setMacAddress to wlan0.
This disables NAN when STA is turned on.
Since NAN always uses its own random MAC instead of using MAC of STA,
this action is not necessary and gets NAN kicked off for no benefits.
We add a build time configuration to optionally disable this behavior.
Bug: 273426515
Test: manually test
Change-Id: Ifc71b7e8d09eac1b66b9e18c70e0e6d202683ff6
Use a new structure to passdown:
- AFC information queried based on frequency
- AFC information queried based on channel number
- expiration time
This change is per chip vendor request. Based on AFC server support,
either frequency based information or channel based information may be
empty. If both are empty, then it indicate the driver should not allow
any standard power transmission on 6Ghz.
Bug: 262791660
Test: compile
Test: Manually verified information is passed down with local framework
change
Change-Id: Id1d014a6113f6863b98ef8239a5a52d3863aa758
explain why the linter is disabled.
If the linter were enabled, we would run into a
build failure because fixed-size arrays are not
supported on SDK Level < 33. The interface indicates
min_sdk_version 30 due to mainline requirements,
but the interface will only be accessed by devices
running Android U.
Bug: 267819850
Test: m
Change-Id: Ifed2223d1c5f4bf46329ed72fa622b730e99cde1
* changes:
Rename getCapabilities to getFeatureSet in the Vendor HAL implementation.
Rename getCapabilities to getFeatureSet in IWifiChip and IWifiStaIface.
NewApi was recently updated to support linting methods in
the system, module_lib, and system_server sdks, and was
demoted to a warning due to the new issues it finds.
Baseline all the new issues that NewApi can be made an error
again.
These cls were generated automatically by a script that
copied the NewApi issues from the reference baselines.
Bug: 268261262
Test: m lint-check
Change-Id: I22f3b3575b6ea00d72d143019d9eed028aa98b56
in IWifiChip and IWifiStaIface.
Main purpose is to distinguish between
the 2 capability methods in IWifiChip:
- getCapabilities (renamed here)
- getWifiChipCapabilities
Bug: 267819850
Test: atest VtsHalWifiChipTargetTest \
VtsHalWifiStaIfaceTargetTest
Change-Id: I03c15d652d02aef99b219c2d630b69acb4d9e43c
we changed to store event information in bitmap format
so that overlapping events can be handled.
Bug: 270650316
Test: startPublishRequest_1_6
Change-Id: I6f3cb8026d54dfa692bfd6eb64b24005ba663a1f
Signed-off-by: dheda.shin <dheda.shin@samsung.com>
Re-assign the value according to the Wifi Aware R4.0 section 9.5.21.1
Also correct several comments.
Bug: 269440402
Test: build
Change-Id: Ib3dd6365b2a28f871ec6ae3775ee8b9e9481475f
types in the Vendor HAL interface.
Specs should be included in the
relevant places.
Bug: 267819850
Test: m
Change-Id: I1f213774ebf5dc297225a5cabb757d2956d67bf4
* changes:
Update usages of WifiRadioCombinationMatrix in the Vendor HAL service.
Remove the WifiRadioCombinationsMatrix type from the Vendor HAL interface.
Vendor HAL interface.
We can return a list of WifiRadioCombinations instead.
Bug: 267819850
Test: atest VtsHalWifiChipTargetTest
Change-Id: I0f57df6262d36917dfd8cc3e27d6781e9b7c8dbf
After adding ag/21179155, auto join flag is
not set for every p2p connect command. The tests
are passing an unknown peer MAC address to connect(). To
pass the tests, the connect should trigger a scan and
try to find this unknown mac address. So set join flag
to true to run the same scan logic.
Bug: 268236829
Bug: 218608010
Test: atest VtsHalWifiSupplicantP2pIfaceTargetTest
Change-Id: Id5baa0f599d11a3563780aae15ff3cea0407060c
XML parsing logic.
Fixes a minor memory leak that results from
not freeing that buffer.
Bug: 269520490
Test: Manual test
1. Create several XML files under
/vendor/etc/wifi/vendor_hals
2. Modify the codepath to run the
initVendorHalsDescriptorList method
(does not run by default on Pixel).
3. Check that the XML parsing logic is
working as intended.
Change-Id: I42944169b70c759998d94e8523d2aa55d0366ffd
Interface combinations in legacy-hal is predefined with
'WIFI_HAL_INTERFACE_COMBINATIONS' build flag. This change
allows the WiFi HAL to request all the possible interface
concurrency combinations via vendor HAL API,
wifi_get_supported_iface_concurrency_matrix(). Thus build time
dependency can be removed by querying the combination at runtime.
Bug: 249351396
Change-Id: I3bc85ac013490949aab71a00f60028bf5daee68c
Merged-In: I3bc85ac013490949aab71a00f60028bf5daee68c
Test: Build successfully
Signed-off-by: Purushottam Kushwaha <quic_pkushwah@quicinc.com>
(cherry picked from commit f68b9a2709)
Add capability fields for TID-to-Link mapping negotiation support for
both station and access point.
Bug: 268219346
Test: atest VtsHalWifiSupplicantStaIfaceTargetTest
Change-Id: Iaf82cdb8a0c3e57135487c95750f53ab1d6fc187
- Add an event to know the device is suspended
- More status code
- Add pub_sub_id in the datapath request to build the relationship
Bug: 247913151
Test: build
Change-Id: I77733c1bca821b77fdab7ed1ed03c1e54c9373b2
Maximum MLO association link count can be an input for MLO scoring
logic. If the candidate AP has less number of links to associate,
scroring logic can give a weightage to an AP with matching links as
station Assumption here is when the environment becomes better, the
AP with less score now can be a better choice.
Bug: 269336948
Test: m android.hardware.wifi-update-api
Change-Id: Iac0c82203c9e1a23637c757f5b92f5b213bb5da6
Deprecated onPmkCacheAdded() callback function and
added a new onPmkSaCacheAdded() callback function to
include the connected AP BSSID. This will help framework
to include BSSID information as a key to store PMKSA.
Bug: 260042356
Test: atest vts
Test: Manual - Tested WPA3 STA - AP connection multiple times and
confirmed that PMKSA cache is added and supplicant is using
the PMKSA cache entries for open authentication.
Change-Id: I9fc7da7f4ba60e45ddeee9a41654c74f128fe3d6
Multi-link llstat parsing codes in wifi legacy hal, specifically
'copyLinkStat' and 'copyPeerInfo', pass the output container parameter
'std::vector<>' by value instead of by reference. The result is the
copied 'LinkStats' list and 'WifiPeerInfo' list are discarded when
'copyLinkStat' and 'copyPeerInfo' return. The empty links list are
passed to framework and fails validity check in Wi-Fi framework and
leads to system server crash.
Fix this issue by passing 'stats' and 'peers' by reference.
Bug: 269049672
Test: Manual Test with multi-link llstat implementation integrated
Change-Id: If8c366213af2ffcb9f7b3c904e1541ed0ac2fea4
in the Vendor HAL service.
Bug: 266521428
Test: Vendor HAL gTest suite
(see the modified test case)
Change-Id: I86e0c465b9f9d2f31413d75727e36b42c2b6b88a
Also update the IWifiChip VTS test to reflect
this change.
Bug: 266521428
Test: atest VtsHalWifiChipTargetTest
Change-Id: I537588c405d8a01091a6818020084acbe2679e14
Framework populates MLO link information from scan cache. In roaming
use cases, framework may not have the scan result for the roamed AP.
So, always get the MLO link parameters from the supplicant. Add static
parameters apMldMacAddress, apLinkMacAddress and frequency of the
link. Dynamic parameters like RSSI, link speed..etc. are queried from
signal poll.
Bug: 268230307
Test: m android.hardware.wifi.supplicant-update-api
Change-Id: I7ffb23a8ead63a385cd00d26969529e2943fcff1
Skip P2P tests if P2P is not supported.
Bug: 200064365
Test: run vts -m VtsHalWifiSupplicantP2pV1_4TargetTest
Change-Id: I6ba23bb27f24700980cab28d1ff806e5efc65ec9
(cherry picked from commit b676061cd5)
(cherry picked from commit 4d81b6562dca69a3334bcb87756539fbdaedcd2d)
Implementation of Wi-Fi P2P Technical Specification v1.7 - Section 4.2.8
"IP Address Allocation in EAPOL-Key Frames (4-Way Handshake)".
Changes includes,
1. API to configure the IP addresses in supplicant for P2P GO to
provide the IP address to client in EAPOL handshake.
2. Send the received IP address information to framework via
p2p group started event.
Bug: 170056953
Test: Manual - Establish P2P connection & confirmed from sniffer logs
and logcat logs that IP addresse is allocated via EAPOL exchange.
Ping works after connection.
Change-Id: I2662fde9ca645aa5e34b21678d1a47cbf26ef3d3
The maximum number of Simultaneous Transmit Receive (STR) links used in
Multi-Link Operation can be different from the maximum radios supported
by the chip.Explicitly mention the max links as max STR links. Update
the description and usage of the capability field.
Bug: 267963579
Test: m android.hardware.wifi-update-api
Change-Id: I5691fcc44c60821766fe41e67624e458ba051059
Unlike the default constructor, create() populates
the weak_ptr_this_ variable, which is needed for
callbacks from the legacy hal.
Bug: 265857332
Test: Manual test - connect to an AP and walk away
from it. Check that the RSSI callback is
triggered in the framework.
Change-Id: I1a10a75c07ea59a3e01b9bb68d9d393bbd20d29d
The AOSP-version of wifi hal apex now contains the VINTF fragment in it.
Bug: 247018693
Bug: 266885060
Test: atest CtsWifiTestCases
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
NAN is not supported by Cuttlefish, so check
for Aware support before running any related
tests.
Also fix the incorrect function call in
CreateP2pIface.
Bug: 263762326
Test: atest VtsHalWifiChipTargetTest
(tested on Cuttlefish and Bluejay)
Change-Id: I3ec52fcc18aedad157dbc17d19078dde216261fb
HAL API support for setting max permissible power on a range of
frequencies. Unspecified frequencies will get reverted to their
respective default values.
Also add capability flag for this new API.
Bug: 242917176
Test: make -j128
Test: Manually verified the framework can call the HAL API
Change-Id: I14ac494124b51ca0b85c394eefe6332c4b382d19
In the API, we can enable/disalbe STA-connected indoor or DFS channels for WFA GO, SAP and Wi-Fi Aware.
Bug: 207669954
Test: m android.hardware.wifi-update-api
Change-Id: I8513bc265fe8fc4f43d9e4b508d8c361f3455fd7
When convert byte to uint16, if the byte represent a negative number,
the high 8 bit of the uint16 will be all 1, which causes a mismatch.
Same as HIDL, convert byte to unit8 then fill into the uint16
Bug: 263690436
Test: cts SingleDeviceTest
Change-Id: Id9462dce48d2a2558c6b5c104866da66ce951b0e
Added the check for TLSV1.3 feature support in
SetMinimumTlsVersionEapPhase1Param test
Bug: 261922145
Test: atest SupplicantStaNetworkAidlTest
Change-Id: I26e7796d4d83e72e0098d5aa6ee520824bda23b1
