Changed class to send a pings for 1.5 seconds to see if conn problems are
resolving after time. Turning RD flag on for now
Change-Id: I05bcf208bda3ea8fb98bd7aec8f0109523d64583
The hostapd daemon can bring down an interface, followed by immediately bringing it up
and this results in us turning off tethering completely.
Wait for the right notification to enter tethered state after brining up hostapd.
Bug: 5135245
Change-Id: I95c8c0c4c2c99c03fce2d18c014eaff37ed4e762
- Turn off watchdog by default on wifi-only devices, b/5073657
- Do not disable wifi networks if connectivity manager reports
no mobile connection.
Change-Id: I835e753624fc5e447081cde473039011721112c6
Hostapd start can block and state machine can be slow to respond.
Refactor wifi state machine to handle this behavior.
Bug: 5079498
Change-Id: Id7707bf2b0e1cb46a1f1374598ec4d7f6403ae1a
In one use case, I see that if we go straight from
wifi client mode to tethering operation, the interface change notifications
are reported in an order that causes to enter tethered state
without actually tethering through connectivity service.
It is because an interface down notification (from wifi going down) comes after
we have started soft ap and we think we have tethered after calling startTethering
and switch to Tethered state
Instead, we should make sure tethering has started before going to Tethered state.
Change-Id: Iba7e8fab0feeb5637d40938862a8638871df8b02
First stage. Get the bones in right now even though
we are not ready on the native side.
Once, we have things underneath working - we will further update the
framework
Change-Id: I4a7dab5cd4267373dc5f8989ae4122f91c384ed5
The set config will only update hostapd config file right now and we need to restart after that happens.
Also, softap interface is changed to be the regular interface
Bug: 5069108
Change-Id: Ibe80129b58e5339f06f186870bcd8f37569c6db3
Also moved customizable settings into Settings.Secure and
added listeners for setting changes into the state machine.
Change-Id: Ia6859c71f7edae13062685867959adc423af4643
Adding a parsable wifiinfo object in Connected broadcast, public api.
The connected broadcast only occurs on successful setup on the wifi
interface, so in normal use is very infrequent (once if the wifi
sleeps, or once at new hotspots, etc...)
WifiInfo objects are small, <10 ints, <5 short strings, and contain info
that could be useful to listeners, such as SSID.
The alternative is to the poll the Wifi Manager, using getConnectionInfo.
Because the Wifi Manager can update state in its own thread, polling the
Wifi Manager might result in an info object that's out of sync from the
received broadcast.
Change-Id: Iafcec77f45dd094ea84e6022b7a40e8952ae8137
We used to bring down the interface on network disconnect
which would in turn clean up all the IP addresses.
The interface bringup/shutdown is now handled by wpa_supplicant.
Add netd interface for clearing all IP addresses
Bug: 4676254
Change-Id: I7e24c0ab2e4a412b8d61e9c33ce028966913aaf6
Change I242cda97 introduced a regression where network state
was being modified on any supplicant state change.
Revert the old behavior of only changeing network detailed state
based on supplicant state change in a disconnected state
Bug: 4690073
Change-Id: I927cc5fa36b862cc54661b033939f543cd15d31f
If you do it before you have a race condition and some apps will
manage to reconnect on the dieing network before it goes and then
get no notification when it goes.
bug: 3408025
Change-Id: I5386ff313c759b3f687bc38731454ab43dbe76b8
The driver start and stop events will be removed as they are now
redundant (and incorrect)
Move to using supplicant INTERFACE_DISABLED indication for deciding
if driver has started or stopped
When driver start is given, the supplicant will first switch to
INTERFACE_DISABLED state and then out of it to start connecting.
We should use this indication to find out driver has started
When driver stop is given, the supplicant will just switch to
INTERFACE_DISABLED state and this indicates driver has stopped
Bug: 4550125
Change-Id: I242cda97951a733c8707c8d99cdfcc9a33b75c2d
Latest supplicant introduces the INTERFACE_DISABLED state. This
is entered when the interface is brought down (which is effectively
done by us and tracked already through the driver stop operation)
Also, added is a state for tracking authentication when supplicant acts as
the SME
Change-Id: I76090068d0ebba6df76f16707da559fcbd7512c5
Add DhcpStateMachine for interation with dhcpcd
- Supports wakeup and renewal on dhcp
- Supports multiple controllers to use the state machine
simultaneously
- Optionally, a controller can request a notification prior
to DHCP request/renewal being sent
Change-Id: I5324814b19ff19863aa6fa89f1e3f0a202930c98
