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