For a connected network, keep status as CURRENT. For a network,
that is disconnected it should be ENABLED. A disabled network
will have the status as DISABLED
Also, add a unit test to ensure there is only one CURRENT network
that is connected
Change-Id: Iaa4a7124a0c372a8f6df3d846ae8c15d9b29cf13
- Add delayed disk write in WifiConfigStore
- Remove synchronization and keep all access to config store
throught the state machine thread
Change-Id: I53768a17895e48da7b99542ac95c6c2fddbcb021
At some point the system UI switched to using 5 rssi levels
while the framework only broadcasts a change for 4 levels.
Hence RSSI change can be slow to be displayed on the UI, fix this
Bug: 5732700
Change-Id: I21700f96ba7a8dd678fb2ccfff8ef59f9b696666
- Add device name on SSID for legacy devices to discover a given
group and join
- Do not remove a group for a device lost event which only indicates
discovery is stopped
Change-Id: Id431c29da371986e694ab230d72d32061b209ebe
= Provision Discovery:Is an optional discovery technique for figuring out
if a peer supports the specific WPS option. For compatibility reasons,
we will now always use it during connection but at the same time support
devices that request to support connection without it
= State machine and UI redesign around the new interaction
= Specify config methods explicitly for compatibility
Bug: 5599949
Change-Id: Ib79435dda472c43cc0746f56bf79ea896b2e33a4
- Use the right interface for untether
- Wait till tethering service confirms that untether() is successful before
shutting down soft Ap. This helps to make sure interface does not go away
before clean up is done.
Bug: 5659166
Change-Id: Iff9d4a67ff40664c2114e766590d6a83b7739738
Causes problems on our wext driver and potentially on cfg
based driver as well.
NLP can trigger very quick acquire and release within seconds
leading to driver switching between start and stop state.
We now keep driver up for atleast couple of minutes after a start
Bug: 5478196
Change-Id: I1b261578252c5fb9a65446241b51e5686d4d9cc3
Now that we also handle supplicant state change to identify that
a network is disconnected (in case CTRL-EVENT-DISCONNECTED goes missing),
it is dangerous to defer all supplicant state change messages
while in DisconnectingState.
It may happen that the CTRL-EVENT-DISCONNECTED goes missing while in
DisconnectingState resulting in a supplicant state change of 0 (disconnect)
getting deferred.
Eventually after a connection completes, the supplicant state change events
get handled and the state machine goes into DisconnectedState.
Fix by having state machine switch out of DisconnectingState once we
do not immediately see a CTRL-EVENT-DISCONNECTED state.
Bug: 5490789
Change-Id: Ia2263795e53c51da0a2bfeefecfeb6256d6c5267
This allows a carrier app to authenticate before we notify the user.
For future, we will provide an API that allows app to disable
the walled garden check.
Bug:5398921
Change-Id: Iff98ddaaa9fa38def4f43b1995f4b2c36f93a919
Handle a supplicant state change indicating disconnection
even if we have missed the CTRL-EVENT-DISCONNECTED notice
Bug: 5437924
Change-Id: I28e314f47f17359926c091b2015cd1fb7422fb22
Reconnecting to a bad network can be expensive (network down time wise and for the device as well).
Add a minimum threshold.
Bug: 5234206
Change-Id: I5ef1fe06038db73c29a3e95b6229506555f36c77
WEXT on crespo has an issue where the interface up/down events
can happen in an unexpected fashion.
At a driver start, we can go from interface disabled to interface enabled,
back to interface disabled and then eventually into an interface enabled state.
Earlier, we were just expecting a single interface enable event that would trigger
driver specific commands. Now, we just handle these events as individual driver
stop and driver start situations so that we do appropriate things eventually
Bug: 5239853
Change-Id: I6bd5d844edf9fadfdca4e8eb753c2ba738aa6ad5
- The pings are delayed async messages that were getting handled
after a disconnect as well
- Increase poll time to 200 ms, so we block on a receive for 1ms every 200ms for a
sent packet
Bug: 5361564
Change-Id: I1931a1c4146e78a87407d541d8c3934ff8232604
When framework fails to get a notice of supplicant shut down,
timeout and proceed with a forced terminate
Also, avoid killing supplicant immediate upon stop and use the
timeout for recovery
Bug: 5337272
Change-Id: Id8971c673dc3082a5f15a6d5cef907bebe1e0fa0
