It has an effect on following case:
If STA firstly connected with 6ghz channel AP and Application create p2p group without config, wpa_supplicant also tried to select STA-associated channel(in this case, i.e. 6ghz ch).
Bug: 281733591
Test: atest android.net.wifi.cts.ConcurrencyTest#testPersistentGroupOperation
Change-Id: Iff6aa55439c08c9e31cef04a1681967fb1278658
The correct path should be under /data,
or it is not writable.
wpa_supplicant now support p2p overlay configuration, a unified
wpa_supplicant init entry can be used.
Bug: 238601241
Test: create a group and check this group is persisted
after reboot
Change-Id: If34d3173bba6d3fe2296d3dd63b05d99221faf42
In previoues mechanism, p2p channel only can raise on same channel
while STA connected to 2.4GHz band. However, if device support DBS
mode, we should allow p2p to raise on 5GHz band for 230423673 higher
performance.
Bug: 230423673
Test: connect STA to 2.4GHz and verified that p2p is able to come up in
5GHz DBS mode.
Change-Id: I9eb836be753a33923d4769cf395c292fb84e942a
Include necessary definition, service for wlan function.
Bug: 228913716
Test: WiFi can be enabled with "adb shell cmd wifi set-wifi-enabled enabled"
Test: WiFi can scan with "adb shell cmd wifi start-scan"
Test: WiFi can get scan result with "adb shell cmd wifi list-scan-results"
Test: WiFi can connect to an AP with "adb shell cmd wifi connect-network GoogleGuest open"
Test: WiFi can ping with "adb shell ping www.google.com"
Change-Id: I8798cc1662191f72d672d6b40f92d1ce62b84c74
