the event bitmask.
Comments on ag/24025770 suggest that the bit
shift will lead to undefined behavior for
event codes greater than 31.
Bug: 290318208
Test: atest VtsHalWifiNanIfaceTargetTest
# manually set some of the expected
# events codes to > 31 to verify that
# the bit shift works as expected
Change-Id: I09e11dac8acf90baf047e24cebe1d01970b1dc8a
to better handle overlapping events.
Reimplementation of aosp/2473685 for
the AIDL VTS tests.
Bug: 290318208
Test: atest VtsHalWifiNanIfaceTargetTest
Change-Id: I1a0e6ab8dd529c10fcec8f26424a7181e7d91568
For Panel TV devices, the vendor can implemented TV specific mDNS
offload instead of APF in U. If TV specific mDNS offload is implemented.
MdnsOffloadManagerService will exist in the system ext partition. The
APF vts will be skipped if MdnsOffloadManagerService exist.
Bug: 283038712
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: If55ec42507460b9a2c6eee683d85b8109f2af236
This includes:
- Adding a README to help users get started.
- Improving the test script to avoid issue where
device is not ready for the next ADB command
after 'adb root'.
Bug: 271914366
Test: Manual test
1. Reboot device.
2. ./runtests.sh
3. Tests are expected to execute.
Change-Id: I9f452384a7067708f617d1e932f06b2f5c7ab119
in the WifiChip constructor.
gTest suite currently cannot mock the legacy HAL
call for getSupportedIfaceConcurrencyMatrix.
If we set using_dynamic_iface_combination_ to true
in the unit tests, we can avoid making this call.
Bug: 271914366
Test: ./runtests.sh # gTest
Test: atest VtsHalWifiChipTargetTest # VTS
Change-Id: Ic43daab6ff5fdc5f78af614ad775f436fbbe8726
for the Wifi VTS tests.
Main method is getBridgedWifiApIface_1_6, which
allows us to configure the chip based on the
Bridged AP IfaceConcurrencyType, rather than
the AP IfaceType like in getBridgedWifiApIface_1_5.
Implementations were largely copied from
wifi_hidl_test_utils and wifi_hidl_test_utils_1_5.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
# tested on a Bluejay device that supports
# the AddAccessPointWithDualBandConfig test
Change-Id: I2571876149fc14c8de02e1cec9934dd052cada5c
APF is support is mandatory since VSR 14. Before that, the APF
requirement is optional. Vendors can opted into upgrading their
HAL to AIDL, so the VTS need to check if vendor API level on the device
and only mandate the APF capability check if the vendor API level is
greater or equal to 14.
Bug: 283181837
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: I21513187d4ca99d721d0e9dc5e243adad77ab8c6
supplicant_test_utils::initializeService() only stop Supplicant,
don't start it. refer Android T code, It should start Supplicant
when initializeService().
Bug: 279572212
Test: VtsHalWifiSupplicantP2pIfaceTargetTest pass
Change-Id: I9f4b3e21ee0865eb95d71f7f832b2eb405de9607
SetStrictConversativePeerMode HAL API is added in
AIDL version 2. So if the HAL interface version is
less than 2, skip the test.
Bug: 278169264
Bug: 277318919
Test: atest VtsHalWifiSupplicantStaNetworkTargetTest
Change-Id: I7f8ace88b0f37679ecaedd5370b47e220c437d50
VtsHalWifiHostapdV1_2TargetTest.
Test currently sets up a new interface
and uses that interface's name. On Pixel,
the new interface is wlan1, which does not
seem to support the OpenAccessPointWithoutAcs
configuration. However, the default SAP
interface wlan0 does support it.
The method to get the default interface name
is taken from this file before ag/19202002
was merged.
Bug: 270509029
Test: atest VtsHalWifiHostapdV1_2TargetTest
(on a Bramble device running rvc-qpr3-release)
Change-Id: Ic3c516f452dfb54f155246073a9bca20dbecaa0f
Update the aidl API documentation to describe how setDtimMultiplier API
is supposed to work, i.e. we can call this API to set a maximum DTIM
multiplier value to use in driver, any larger value must not be accepted
and meanwhile it allows to set a specific multiplier by OEMs. Try to
make the description clear and avoid the ambiguity.
Bug: 266256943
Test: m
Change-Id: Ic7d2284a25e32d1b0752cf2bc832c069f646fcea
dump method is called.
This should prevent a race condition
between stop() and dump().
stop() already acquires the global lock
when it calls validateAndCall().
Bug: 274641043
Test: adb shell dumpsys wifi # validates dump()
Change-Id: Ie2df0861308954cd2e399c9604d4ae0dcddf95fb
VTS test for IWifiChip#getFeatureSet.
Some implementations of the legacy HAL,
such as Goldfish, do not have any
supported features.
Bug: 273886122
Test: atest VtsHalWifiChipTargetTest
(tested on Cuttlefish)
Change-Id: I3ca22187cab0e77d36a28908e57ff4970535e4ae
Since Android U, VSR 5.3.12 mentioned the Android Packet Filtering must
be supported by CHIPSETs and DEVICEs launching on Android 14 or higher.
This VTS was added to check if APF is supported properly.
Given the limitation of the VTS testing environment, the first version
of the test case only checks: if the APF is supported by WiFi chips with
version 4 and more than 1024 bytes of usable memory.
Bug: 259309511
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: I3ee2a980a4440db232738a23c1633aaff3562d95
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
