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
Merged-In: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
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
With MLO, WiFi 7 supports establishing multiple links between the
Station and Access Point. Each of the link has its own stats.
To maintain backward compatibility, if multi link stats is not supported
by vendor, always fallback to single link layer stats.
Bug: 246988155
Test: hardware/interfaces/wifi/aidl/default/tests/runtests.sh
Change-Id: Iede8ce771f0e58975222808b1870e5e2e179384c
Due to the introduction of multi links, StaLinkLayerStats carries stats
for multiple links as a vector. For LegacyLinkLayerStats, only single
link will be available. So convertLegacyLinkLayerStatsToAidl() push the
stats for single link as the first element of the link vector.Fix the
unit test to index the first link.
Bug: 246988155
Test: hardware/interfaces/wifi/aidl/default/tests/runtests.sh
Change-Id: I8c9a8beca6bda6cf894edb616cdfe54f09d029f7
Currently framework gets the connected AP frequency
information by checking the scan cache & through signal
poll command. But these mechanisms doesn't work if framework
scan cache is not updated with the connected AP information
(For example in case of roaming and force connection without scan).
To fix this modified supplicant state change interface
and included the frequency of the connected channel in the
state change event.
Bug: 240299862
Test: atest vts
Test: Manual - Tested STA - AP connection and verfied the data
from debug logs.
Change-Id: I936bd3256420de38cdfee740e43972bc262ec4b8
Added a new field in chip capabilities to get the
maximum number of concurrent TDLS sessions supported
by the chip
Bug: 240247868
Test: Manual - STA connect/disconnect
Change-Id: I62fcd2d4a562b088cdeb4b04f72cfe55ed61241c
Added a new field in chip capabilities to get the
maximum number of concurrent TDLS sessions supported
by the chip
Bug: 240247868
Test: Manual - STA connect/disconnect
Test: m android.hardware.wifi-update-api
Change-Id: Ie2a4129241f40fc9eba28105b8ea3c06b27a8492
Define a new AIDL API to get capabilities from the vendor chip.
Bug: 231497844
Test: m android.hardware.wifi-update-api
Change-Id: I3c1cfce4df2101125a628f230b938b3be0f80311
Added a new StaIfaceCallback method to indicate that
the operating frequency of the BSS is changed
due to channel switch announcement from the AP.
Bug: 195617184
Test: Manually triggered channel switch through peer AP hostapd command
and verified the new frequency in STA logs.
Change-Id: I9dd59d7c5d4ddc5f3443f8b6786cfea9beec4f3c
Create a snapshot of hardware_legacy for legacy HIDL, to avoid any build breakage due to new hardware_legacy for the new AIDL. Should be removed with the HIDL when we finish the switch
Bug: 205044134
Test: build and CtsWifiTest
Change-Id: Ib1068112f6c90f2a41b68e20027d959c95798120
Supplicant and Hostapd tests have a dependency on
the Vendor HAL in order to do setup/cleanup,
such as bringing up an interface.
This change will make the tests compatible with either
the HIDL or AIDL Vendor HAL, depending on which
is available.
Bug: 205044134
Test: atest VtsHalHostapdTargetTest
atest VtsHalWifiSupplicantStaIfaceTargetTest \
VtsHalWifiSupplicantStaNetworkTargetTest \
VtsHalWifiSupplicantP2pIfaceTargetTest
Tests were run using both the HIDL and AIDL
Vendor HALs.
Change-Id: I1f6b15016414a0bf614703315b47b5b47d3a1e50
This change is for Enrollee to send the DPP connection status
result frame to configurator. The changes includes,
1. Modified the existing onDppSuccessConfigReceived callback function
to indicate that configurator has requested for the connection status
result frame.
2. New callback function to indicate that the connection status result
frame is sent.
3. Defined connection status code.
Bug: 235844564
Test: m android.hardware.wifi.supplicant-update-api
Test: Manual - Ran DPP tests and confirmed that
connection status frame is processed correctly
Change-Id: I45866707971c874c9270e7316a7b86fe0953d95a
Add a callback to notify MLO link status changes due to
- Multi-Link Reconfiguration (AP Removal)
- TID to link mapping updates
Bug: 247119055
Bug: 248289182
Test: mm -j
Change-Id: I1010cfb3ef608466a46d54e1ef2ae4e665504210
TID-to-link mapping, which is introduced in IEEE 802.11be standard
allows an Access Point and a Station to determine how uplink and
downlink QoS traffic corresponding to TID values between 0 and 7 will be
assigned to the setup multi links.
This commit adds an interface to TID-to-link mapping in existing MloLink
AIDL.
BUG: 247119055
Test: mm -j
Change-Id: I3ef6e37d9857606020a8e0580c82ca8ab1b8bf82
The GO interface MAC address would be used to calculate the link-local
IPv6 address of the GO in the GC side.
Test: m
Bug: 233912758
Change-Id: I8cdae90a2703d446dafbdfba8f99c191b751f552
ASan is not meant to be enabled in production binaries, and the fuzzer
"sanitizer" is only intended to be used with fuzz targets. So disable
both of them.
Change-Id: Ice7d8d3fd6621077d485b430d9e06fb3ba240e87
When device supports two AP interfaces (i.e. {AP, 2}. not a bridged case),
the AP interface name might be observed from the getPredefinedApIfaceNames.
Check if the interface name is used or not when creating a new interface.
Bug: 244387442
Test: Manual test by commands
adb shell cmd wifi start-softap tetheredAp open -b 2
adb shell cmd wifi start-lohs lohs open -b 5
Change-Id: I59b3796895ee09452a9650c4dc138ad9e143282e
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Merged-In: I5353ab1561622eae12e2dff87eb0f17b47c3773d
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
(cherry picked from commit 3ab5c90104)
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Merged-In: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
(cherry picked from commit c4ac3355a6)
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
