For the purpose of exposing the class as a storage for Wps
info with p2p, it is better to just call it Wps
Bug: 5247957
Change-Id: Iaebef958dd8f08fdbeb4b9d7fa5ad5527400710d
- Update the WifiP2pGroup class
- Add reason code response for all failures
- Fix display of self in peer list
- Retain p2p group when explicitly created by API and fix join behavior
Bug: 5247957
Change-Id: Ibd9b163887db1c8a9dd8213253fda20c436a49e3
First part of documentation and cleanup before we can unhide
the p2p API for review by API council.
Bug: 5247957
Change-Id: Idb52f0b699d23e22aa829f60cfac2c98451d2e22
Useful for checking if on a wifi-only device.
Similar to asking for NetworkInfo for a network type and checking for
null, though here the intent is explicit.
bug:5087537
Change-Id: Ia3ddd09b6b735b8b3ceb7a347891e015fd96b218
Until we figure out a good way to do it from both group owner
and client, remove persistent behavior
Bug: 5241839
Change-Id: I31bda672edaa17e6a500f185b6b879dcfdbd069d
When we first ported wpa_supplicant 0.8, we had a work around
to fix the supplicant state change behavior from the driver.
Remove the work around since the driver behavior is fixed.
Bug: 5195278
Change-Id: I320f21ab01704931a3def6214b0cc40f214a688e
And fix associated changes from the settings.
With p2p_reconnect setting turned on, it means the p2p group can be
started without a group negotiation. Hence, handle p2p group started in
the P2pEnabledState
Also, reinvocation results in supplicant not reporting device address correctly.
Handle that until supplicant fix is fixed.
Bug: 5002384
Change-Id: I335f6e854acd6839f54da9b460b17ad7505b1098
- Space was truncated on 'disabled' notification
- Disable reason was getting wiped out on subsequent disabled
- disable reason was not propogating to WifiSettings
Change-Id: I2e57ee33d285aad39aabe1b048e7436d364b02f3
- Simplify the API with minimal needed functionality
- Fix responses for all async messages from the framework
- Fix state machine handling of connection setup and supplicant communication
Change-Id: I2724c83760b2aaa2068f9cd81ca0754753f83220
Add policy controls to NetworkStateTracker which are combined with
other user preference and internal flags to decide if data connection
should be established. Better locking around enabled flags.
When data network would be over limit, proactively disable data on
that network. Enable when policy is snoozed or when cycle resets.
Track and dismiss notifications from now-stale policies.
Bug: 4587023, 5178147
Change-Id: Ibfcc9f73cda7c369209af701b46eddd3d1943f2d
After a p2p group is formed, STA connect and disconnects come over
interface address. Figure out device address from interface address
and fix the device comparison
Bug: 5002384
Change-Id: I7d3aa4f0616e000550cd2b057adbac71cfd2adb4
- ConnectivityService interaction and support for running dhcp server
and client
- State machine enhancements for connectivity interaction
Change-Id: Iba3beb8c87554ffd67a7b7e852bbb4dd8666a4f5
Now that the driver is built into the kernel, a runtime crash
followed by a driver unload and reload does not reset the interface.
Ensure interface is down before bringing up supplicant
Bug: 5032635
Change-Id: Ib8f3d47617e587139a8a91a82146ee3a2f329700
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
