Having the AP and STA set the same MAC address in tests could cause
unintended failures when WifiApIfaceHidlTest and WifiStaIfaceHidlTest
are executed back to back.
Bug: 172528120
Test: atest VtsHalWifiApV1_4TargetTest VtsHalWifiV1_2TargetTest
Change-Id: I336d21cd896c46b064f16ecfa184a26dab67deaa
1. Add new 1.3::IfaceParams to support AP+AP.
2. Fix vts to match use the 1.3::IfaceParams
But the test on dual APs mode needs to add after vendor Hal ready to
create two interfaces.
AP+AP Part 1 includes:
1. HIDL: Hostapd support dual bands/channels configuration
2. Framework: HostapdHal support only
3. Hostapd deamon:
a. Support briged interface query
b. Support config dual bands/channel
c. Callback use bridge interface in dual APs mode.
Bug: 162686273
Test: atest -c VtsHalWifiHostapdV1_3TargetTest
Test: atest -c VtsHalWifiHostapdV1_2TargetTest
Test: atest -c VtsHalWifiHostapdV1_1TargetTest
Test: atest -c VtsHalWifiHostapdV1_0TargetTest
Change-Id: I621b303c1e1f36996ca9b7720242f134bbe5fd75
Add SupplicantStaIfaceCallback v1.4 with support for the new
Passpoint T&C notification callback.
Bug: 171928337
Test: atest VtsHalWifiSupplicantV1_4TargetTest
Change-Id: I14f88427a6112b6a097d168c00ece3e36a7bd82f
Before R, those two calls are not going to work with fake values.
After enabling auto-join, it will success always.
Bug: 169890122
Test: atest VtsHalWifiSupplicantP2pV1_0TargetTest
Change-Id: I7d94e797e140520a5df33bba854d5cb2b015eacf
Fix VtsHalWifiSupplicantP2pV1_0TargetTest to skip tests
in such a way that VTS reports the module as complete on
devices that don't support Wifi Direct.
Bug: 170326147
Test: run vts -m VtsHalWifiSupplicantP2pV1_0TargetTest
Change-Id: Ia418c4bb72f4772422d724636453395c4ba9fb2d
We don't need to test supplicant in the presence of vendor HAL & without
it. For a given device, this behavior is fixed.
Bug: 161951052
Test: atest VtsHalWifiSupplicantV1_1TargetTest
Merged-In: I71097c3afef1765ca514abf2c350c423e3999020
Change-Id: I71097c3afef1765ca514abf2c350c423e3999020
(cherry picked from commit 984b6e0607)
We don't need to test supplicant in the presence of vendor HAL & without
it. For a given device, this behavior is fixed.
Bug: 161951052
Test: atest VtsHalWifiSupplicantV1_1TargetTest
Merged-In: I71097c3afef1765ca514abf2c350c423e3999020
Change-Id: I71097c3afef1765ca514abf2c350c423e3999020
This reverts commit 1c50a59eae.
Reason for revert: This was not needed. Does not fix the issue at hand.
Bug: 161951052
Merged-In: I872a1b3e87f17a43eb3c22c930e916c7e5e2d2a6
Change-Id: I872a1b3e87f17a43eb3c22c930e916c7e5e2d2a6
aosp/1427815 add invoke terminate function in teardown function.
It will cause Create Test case fail since Create killed global hostapd_
service to re-generate the local one.
Use global hostapd_ to replace local variable to make teardown function
work normally.
Bug: 169248773
Test: atest -c VtsHalWifiHostapdV1_2TargetTest
Test: atest -c VtsHalWifiHostapdV1_1TargetTest
Test: atest -c VtsHalWifiHostapdV1_0TargetTest
Change-Id: I6300a626db76e68873bbc34c489a9a8ee2d55e7a
The access network type can be used to indicate network metered state.
Add access network type support when create access point.
Test: Manual Test, check client scan IE to show correct interworking
value. see: b/137879206#comment14
Test: atest VtsHalWifiHostapdV1_0TargetTest
Test: atest VtsHalWifiHostapdV1_1TargetTest
Test: atest VtsHalWifiHostapdV1_2TargetTest
Bug: 137879206
Change-Id: I74213bd763f865f26781313b00e1b1cfeee93086
