| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I28e268dd8b859a3a22c3d6f699216bbd7124af26
|
|
|
|
|
|
|
|
|
|
| |
In cases where networks are not properly configured, WiFi might tries to repeatdly switch from one network to a bad network, or might try to roam and renew DHCP which can fail. In KK, WiFi autojoin would try other networks (by cycling to network it sees) and end up associated to a "good" network. In L release even thought WiFi might pick a good network it will still repeatedly try to switch to what it thinks is a better network and fail, thus annoying the user whose connection becomes unstable. This CL tries to remember networks that have seen multiple DHCP or auth failure in the past and for those networks it disable roaming temporarily. That is, if wifi is not associated to any network, it will tries to join a network aggressively, however if wifi is currently associated to a network, it will not try to switch to a new network if that new network has seen multiple failure in the past. The maximum blacklist time is set to 2 days for now.
An example of such situation is:
- user has multiple SSID at home, one of which is incorrectly configured with a wrong password
- broken DHCP situation (potentially: multiple servers on home network, broken implementation incorrecting NAK'ing DHCP requests but properly serving DHCP offer...)
Bug:18792931
Change-Id: I332a9cebdc19be2e00b455205d386fcffcb70b29
|
|
|
|
|
|
| |
Bug:18706288
Change-Id: I59378faafbccfa58639d942c8b8e2e0e815261f4
|
|
|
|
|
|
| |
Bug:18703749
Change-Id: I8e35d602a80b341668d9607db2da3ca6fdb970ae
|
|
|
|
|
|
| |
Bug:18525241
Change-Id: I954c53c55c39f6c376b2bae3c7ac4d28246a7f5a
|
|
|
|
| |
Change-Id: Ia09dae3e334ef6fd11f2b468e78ad7c2c3cf55e9
|
|
|
|
|
|
|
|
|
| |
Since we don't support LABEL method in startWps, document
it explicitly.
Bug: 18298388
Change-Id: I5d4c2475a68f1b41e5fc449c911b7b01b3b82fc4
|
|
|
|
| |
Change-Id: Iadb4e0e1beeb9e582b944e003470815a5a865652
|
|
|
|
|
|
|
| |
This method will never return null. It may return "<unknown ssid>" if
no network is currently connected.
Change-Id: Iae09a6b2376e47c2d010f8d05750a16361510cca
|
|\
| |
| |
| | |
lmp-mr1-dev
|
| |
| |
| |
| |
| | |
Bug: 15892711
Change-Id: I4a027c99634a11d13bb3c8420ba959c201644689
|
|/
|
|
| |
Change-Id: I9d417c20c6b6721933a4eb943c1305845005facf
|
|
|
|
| |
Change-Id: I33d8672efd2747ed3f49dd8d5bcd5f47bf418053
|
|
|
|
|
| |
Bug: 17670914
Change-Id: Ibb2ea26ea28a38518caab7d1b45ae535a0eaf661
|
|
|
|
| |
Change-Id: Iba13db478ed69976c37bd4882f59bf0cae2212e6
|
|
|
|
|
| |
Bug: 14997906
Change-Id: Idfcf9ade905c7565cc1d59d15aa4362c1b597b72
|
|\
| |
| |
| | |
lmp-dev
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Phase2 isn't required for EAP_TLS networks, and it is possible
for a developer to miss it. We are requiring it for internal
book keeping - so this change just sets Phase2 to 'None' when
EAP_TLS is set on the configuration.
Bug: 17043082
Change-Id: I5a8e0a3a236d0dfd1295584de55d5b9a1b76b483
|
|/
|
|
| |
Change-Id: Ia2a4ac3e11f2b0c7412f33496a655c5d5297ea0c
|
|
|
|
|
|
|
|
| |
- allow for making use of more aggressive initial autojoin attempt rssi thresholds
- create a blacklist due to missing identiy reason
- make autojoin parameters configurable
Change-Id: I385db83aab1da7918ff6935eb59a209b253d42e6
|
|
|
|
|
|
| |
WifiConfiguration
Change-Id: I5052f6a76bcd1f980ef558bff54ce1b172319743
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This change implements access control for WifiScanner. It is now
available to only those apps that have CONNECTIVITY_INTERNAL permissions.
Bug: 15088601
Change-Id: I6acc13079b6dac6f190644b6d1a270c271cc679f
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This API allows finding channels by band, so scanning services
can find out which channels to use.
Bug: 16652660
Change-Id: I690825333988a336efa3fc8886297e5b8baf8e1d
|
|/
|
|
|
|
|
|
|
|
| |
- add the noInternetAccess field
- add stats about user triggered wifi state disabling requests
- Wifi SSID can change even though we don't loose connection, hence it must be looked at with each Network State Change
Bug:17348200
Change-Id: Ic956e11e7d61faf472a7332f84a46a746922455a
|
|\
| |
| |
| | |
these methods are called using reflection for location. Bug: 17371392 Change-Id: I6546f5b485415beff69164ba0d526757ee831f69" into lmp-dev
|
| |
| |
| |
| |
| |
| | |
-Currently these methods are called using reflection for location.
Bug: 17371392
Change-Id: I6546f5b485415beff69164ba0d526757ee831f69
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change addresses concerns from the API review. Things that
are fixed are -
1. WifiAdapter is removed, until we have 'real' support for it
2. All the methods from WifiAdapter are moved to WifiManager
3. Changed WPSListener API names to be onFailed/onSucceeded et al
4. Removed ActionListener from WPS APIs, they now take WpsListener
Bug: 16403303
Bug: 17115004
Change-Id: Ia721dd95041acb3e50d16690319e3320fe550ff5
|
| |
| |
| |
| |
| |
| |
| | |
settings to crash
Bug: 17293156
Change-Id: I5f7a8141adb21103e98913c9802d8364164eaba7
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
This CL is dependent on I3d2a230b0362520b9f1b2bc3792260116971e106
Change-Id: I1a0d655877d9368d833d62e231797af4b2560862
|
|/ /
| |
| |
| |
| | |
Bug:15563188
Change-Id: I3d2a230b0362520b9f1b2bc3792260116971e106
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 041bcc22bd21f84358e5b2102e3a919bcdd99b81.
Bug: 17134034
Change-Id: I1ebcdd9b4c56e5c93fd5667699c8971e8c6e5452
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 16823537
This CL is dependent on Iff32fae2cd67343e63046d58d75fa1e10d9775d0
Change-Id: Id9411c8097337b37ac1ce1a6ac8b28b4bda31ff3
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Valid dBm ranges should *not* be mentioned in the documentation.
Manufacturers should be able to produce devices which can detect
signal strengths with arbitrary sensitivity rather than being forced
to restrict strengths to a certain range.
Adds a reference to WifiManager.calculateSignalLevel(), an
often-useful method to convert these RSSI values into an absolute
signal level that can be displayed to a user as the signal strength.
Bug: 13731529
Change-Id: I0aae85a6d8bc48ffddd1927d816a1dfbf5230f7e
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | | |
This CL is dependend on Ic3ae7269f0ca11cec6b7aea5143499e88ecc7149
Change-Id: Ic533d1820c470bf2370a92452b37515ef7458f45
|
|\ \ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 17112931
Change-Id: I5980bc46bc1f16316caecd7fcc6cd771b8ca6cdf
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
LinkProperties can represent way more complicated configurations
than what we can actually apply to interfaces. This makes it
error-prone to use it to represent static configuration, both
when trying to apply configuration coming from LinkProperties
and when trying to save configuration from current
LinkProperties.
Instead, move static configuration (IPv4 only, since we don't
support static IPv6 configuration) into a separate
StaticIpConfiguration class.
Bug: 16114392
Bug: 16893413
Change-Id: Ib33f35c004e30b6067bb20235ffa43c247d174df
|
| |
| |
| |
| |
| |
| |
| |
| | |
settings"""""
This reverts commit c9249c69813c6fb889d71d84583c67ae2942e6de.
Change-Id: I5504fddaf7b18efb73cd6c76678b3b39ce9b0229
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
settings""""
This reverts commit 87efe74e092236c372d3b6909009641123aa416a.
This should be fine now with all the dependency CLs +2-ed
Change-Id: I96ad14ad5ff81e6b5391035cb6c5a62339c6cc40
|
| |
| |
| |
| |
| |
| | |
This reverts commit 19c8ce291e89a9ef1442a20e1feab421b11536d7.
Change-Id: Ie5a5571127311e0a29f314c0566e779cfe940b53
|
|/
|
|
|
|
| |
This reverts commit 0f0de0bdd021bad5f85fdb0399a4ea91a1611e25.
Change-Id: Ia3d0907e3d7c2ec42d64e45f60e3dfaffb932c3d
|
|
|
|
|
|
|
|
|
| |
MERGE]"
This reverts commit 41158d90a69cae2a9c4ced0e04f235e8cfef5259.
Bug: 16871063
Change-Id: I93623be92f2de41789b16827867f3f95bf0480c5
|
|\ |
|