Have a different set of strings, since we cannot mention mobile data for
a wifi-only device.
Bug: 3487952
Change-Id: I486315da40f15807f75d85d2a077a6b234a1e3d7
- revise xml for new layout
- introduce padding View objects for resizing screen when
software keyboard is shown.
- We now don't show the detailed status of Wi-Fi module anymore
in SetupWizard flow (like "disconnected", "connecting", etc.)
- remove Forget button and relevant code.
Bug: 3347865
Change-Id: Ieab3246f06ee73af59e247b3f9f31c7570efc71f
- add onAuthenticationFailure() method to prepare
appropriate UIs.
- set "edit" boolean to true so that users can modify
password when re-seleting a network.
- keep mStatusText shown for simplicity. It has been hidden
during "editing" phase, but we don't need to do that any more
- modify Connect button handling so that the button
hides/appears at appropriate time
- manage visibility state of some fields so that
we can "reset" the status when authentication failed
- show keyboard again when password field re-appears
Bug: 3330109
Change-Id: I1cdf0573280ab46882117e21501a43a447e50b40
When wifi network state is disconnected, supplicant
state changes provide more fine grained information to display.
When network is connected, the UI should ignore supplicant
state changes.
Change-Id: I46aa8c2ba80303aae5c74415825102a13cc41380
The Comparator with TreeList that was added during
wifi set up changes does not work well since
access point can change later.
Restore the old compareTo behavior.
Change-Id: I75681fea616792e9fd134c0d71762b4e0d46ffd6
Major:
- move SetupWizard-related codes to WifiSettingsForSetupWizardXL as
much as possible
- stop using Preference for configurinig wifi network. We use
WifiConfigUiForSetupWizardXL instead, which is base on a bare View.
Minor:
- change button handling code expecting better readability.
- hide Detail button.
- modify strings a bit.
- add logs
Bug: 3175016
Change-Id: I5b29917af73aac6a82e13ba846a9d5085f9bd523
We don't want to show every configurations in default, while
we also don't want to complicate basic wifi logics. In order to
achive both goals, we first introduce tweaked xml file
(wifi_config_preference2.xml). It does contain all the
config components but almost all of them are in "gone" visibility.
Those components are still able to act as data storage, but never
be seen as actual UI components.
Change-Id: I4ad3c1b4cbbe77ca2b628b0be25e2b3eb9d645aa
The WPS available option is shown
for networks in scan results. Upon
selecting a network, the user has
the option of manually entering passwords
or choosing WPS for connection
Bug: 2277571
Change-Id: Ia12eb1742f1bf17128d51fa09e56dc4c3f067fa5
Current UI shows nothing when there's no connection available, even when
the device is finding some. So user cannot know whether the static
"Not connected" screen means: the device is finding right now, or
actually no network is available.
Change-Id: Ia8ea1c66956e8de819f6a98362bcc9086bda172c
* Add WifiSettingsForSetupWizardXL as a new Activity
The activity has WifiSettings fragment in it. It also contains
several buttons, texts around the fragment.
* Making configuration UI part of Preference list.
In Wifi Setup for Setup Wizard XL, WifiSettings fragment lets
a UI for configuring access points shown inside a
PregerenceCategory object, while it has been shown as Dialog.
To achieve this action, WifiDialog is decomposed into two parts:
- WifiConfigUiBase (Mainly UI part)
- WifiConfigController (Mainly Wifi controller part)
All codes for wifi configuration in WifiDialog is now in
WifiConfigController, which is reused from
WifiConfigPreference.
* Misc stuff
- Remove AccessPoint#compareTo(). Instead,
AccessPoint.AccessPointComparater should be used when needed.
Change-Id: I520d690d3301837d32f91dad54a973a379ce1989
- Add button bar feature toward SettingsPreferenceFragment,
which has existed in PreferenceActivity and has been used
(probably) only by Settings app.
- super.onActivityCreated() is not called at the beggining of
WifiSettings#onActivityCreated(), the parent method assumes
the child should have prepared PreferenceScreen, while
WifiSettings cannot do until the parent Activity is ready.
- Call SetHasOptionMenu() should be called AFTER the parent
Activity is ready. It is not documented, so it would be better
to file another bug.
- Add exception to proguard...
Change-Id: Iebd27f0cb0abdbee9b4b1cc9b00f4bf127f7815d
When scan fails for 3 times, we show a
failure toast and continue to scan.
In one case this caused infinite toasts,
until the user stopped wifi.
Its not clear what can cause this kind of
a state since wifi disable broadcast should
stop the scans. This fix will stop scans
after 3 continuous failures. Any wifi state
change will restart scan.
Bug: 2601937
Change-Id: I68733394cb3c9b76ffb15f7579e7af6c1f54d39c