It's necessary to implement getDialogMetricsCategory to show
dialog in WifiSettings2.
Bug: 143328194
Test: make RunSettingsRoboTests -j ROBOTEST_FILTER=com.android.settings.wifi
Change-Id: I65ac4168ef922be981624e7916316f189ab590c2
Connect button becomes Disconnect button if the Wi-Fi AP
is connected.
Bug: 135891885
Test: make RunSettingsRoboTests -j ROBOTEST_FILTER=WifiDetailPreferenceController2Test
Change-Id: I0e0d485385294658170da3d37bc1cc1f8748468f
This commit makes fixes to the wifi tethering rototests.
These fixes are done by using the proper encoding for the AP bands.
Bug: 146767071
Test: Run robotest
Test: make RunSettingsRoboTests -j ROBOTEST_FILTER=com.android.settings.wifi
Change-Id: I4ddf6ea9328dabed09bc23d355efa188975316b6
Now there is no WifiDialog2 MODE_VIEW use case since
they are replaced by WifiNetworkDetailsFragment2.
Should think about removing MODE_VIEW in the future,
however, we should let it work before phase out it.
Bug: 146407136
Test: build
Change-Id: I7cd470c74cea846046975b8c65fd2604702cc136
- Add xml file to index "Saved network" and "Wifi data usage"
preferences.
- Disable the "Saved network" if the access points is empty.
- Disable the "Wifi data usage" if there is no wifi radio.
Fixes: 146823365
Test: manual
Change-Id: I049d0463fd58f186dae1d5f54dcc914f52031da7
To align with other advanced option behaviors in other Settings items, hide the Advanced Option button after the hidden advanced options are show, which also solve the a11y issue.
Bug: 146908469
Test: Add test case getVisibility_whenAdvancedOptionClicked_shouldBeGone
to verify View is Gone.
Change-Id: I11b2f9b250a7d50d32b8c05207498f4cf14feb41
This is a similar code merge of ag/575560 & ag/2588374
Bug: 143328194
Test: manual
Connect to a Wi-Fi network with wrong network.
Click the fail notification and launch Wi-Fi picker.
Check if the editor shows the specified Wi-Fi network.
Change-Id: I5bc8cd0ea51e7baf3d6d2d6d522a3973b74ef930
This is a similar code merge of ag/489459.
Bug: 143328194
Test: make RunSettingsRoboTests ROBOTEST_FILTER=WifiSettings2Test
Change-Id: I666b3293f00aa1822a6fdcc3760ae19d27019597
This change also implements context menu in WifiSettings2.
Bug: 70983952
Test: make RunSettingsRoboTests -j ROBOTEST_FILTER=WifiSettings2Test
Change-Id: I13b5a3724207f76e2b24fd0c1c49a236ee0c44f0
Update ACTION_PROCESS_WIFI_EASY_CONNECT_URI intent to include
additional information in case of a failure. The intent will
return an extra field with result code for R1 and R2 devices,
and additional details for R2 devices: SSID, channe list,
and band list.
Bug: 139381558
Test: Manual test
Change-Id: I6f1805f3b1ff72efc83961083c1311a24d6ebd3e
- remove duplicate index preference
- default set searchable = false when the preference has fragment
- make some fragments indexable
Bug: 143057584
Test: robotest & manual
Change-Id: I4d64f6106d2f92f0a45e8c7e26388677f593f412
For the R feature "Add saved networks to the
device for apps", need to handle the new intent case to update the content to be the specific networks in the new intent.
Bug: 146105504
Test: Add following unit test case to check if UI list had been updated:
getThreeNetworksNewIntent_shouldHaveThreeItemsInUiList.
Change-Id: Id043fabb16ba5a75aa81be8cacd403e62e5268b8
Added support for DPP R2 events that provide additional
details about the onboarding process of a remote enrollee.
Specifically, DPP R2 configurator waits for response from
the enrollee, which reports back the SSID, tried channels
and band support in case it cannot find the AP. When it
reports success, then it means that it is acutally connected.
Bug: 139381558
Test: Manual tests with DPP R1 and R2 enrollees
Test: atest DppManagerTest
Test: act.py -c ../WifiDppConfig.json -tc WifiDppTest
Change-Id: If19fc6906ec5abbdceef0742dc52b42c7d0acfe0
The Connect button in the Network Details Page should be synced to the
connected state of WifiEntry and should toggle between not visible,
"Connect", and "Connecting..." accordingly.
Bug: 70983952
Test: manual - connect to in-range saved network through Network Details
page
Change-Id: Id34a840dd81fb99c8e64ad219b0b7af73946c1bf
This change also remove redundant code of WifiNetworkDetailsFragment2
from WifiSettings.
Bug: 143326832
Test: Manual
Click connected Wi-Fi network and check the UI of
WifiNetworkDetailsFragment2
Change-Id: Id72c26116177f8e7063e433a6456557bd36c7927
There are still many methods not implemented in WifiEntry. This change has below workarounds:
1. Add WifiEntryShell to provide dummy WifiEntry methods.
2. Add @Ignore to WifiDetailPreferenceController2Test.
Must remove these workarounds after we have more constructed WifiEntry methods.
Bug: 143326832
Test: make RunSettingsRoboTests ROBOTEST_FILTER=com.android.settings.wifi.details2
make RunSettingsRoboTests ROBOTEST_FILTER=com.android.settings.wifi.savedaccesspoints2
make RunSettingsRoboTests ROBOTEST_FILTER=com.android.settings.wifi
Change-Id: Ic2edb424b9c645838558fe131991ccb9105dc64c
Use new metric, PANEL_ADD_WIFI_NETWORKS, for proto upload log use.
For R feature: Add a mechanism for apps to add saved networks to the
device, need to apply new metrics category.
Bug: 144891278
Test: Add following test case for testing metric:
getMetricsCategory_shouldReturnPanelAddWifiNetworks()
Change-Id: I7cde8057c5f2b01c951b1de4203ab1c1a2f0f40a
With the support of 6GHz in Android, BAND_ANY is no longer equivalent
to 2GHz+5GHz.
This commit makes the changes to adapt with this.
Bug: 139354972
Test: Manual
Change-Id: I29263573fb900a560494a84df5a16ac0e6948f59
As part of the support of the 6GHz band, the concept of dual-band is no
longer valid since we have more than 2 bands supported by Android and
can be checked on the device.
This commit replaces checks on dual-band support with an explicit check
on 5GHz band support.
Bug: 145936758
Bug: 139354972
Test: Manual
Change-Id: Ia118dedb573f61a148764146edf8091ae253a3e2
Handle adding multiple networks case, add UI components and process saving flow.
Bug: 136472483
Test: Add unit test cases to test filterSavedNetworks API.
Change-Id: I222e2f8294793796e293de49acdb96ecd6a57b0d
