- 28 Jan, 2015 1 commit
-
-
The Android Automerger authored
-
- 26 Jan, 2015 2 commits
-
-
The Android Automerger authored
-
The Android Automerger authored
-
- 22 Jan, 2015 1 commit
-
-
sample.lin authored
Bug: 18825290 from: https://partner-android-review.git.corp.google.com/#/c/192524/ Signed-off-by:
sample.lin <sample.lin@mediatek.com> Change-Id: I3c19e1df455e77f71354f5e45b6a4037cc366051
-
- 19 Jan, 2015 1 commit
-
-
The Android Automerger authored
-
- 16 Jan, 2015 2 commits
-
-
The Android Automerger authored
-
vandwalle authored
-
- 15 Jan, 2015 1 commit
-
-
The Android Automerger authored
-
- 14 Jan, 2015 2 commits
-
-
Vinit Deshpande authored
-
vandwalle authored
Bug:18917134 Change-Id: I0c4d0a2bd5383bac473a588af89589bf70f47c6c
-
- 13 Jan, 2015 3 commits
-
-
The Android Automerger authored
-
The Android Automerger authored
-
Erik Kline authored
-
- 12 Jan, 2015 1 commit
-
-
The Android Automerger authored
-
- 09 Jan, 2015 1 commit
-
-
Vinit Deshpande authored
Disabling an invalid configuration causes Wifi service to crash. This change gaurds against bad API call. Bug: 18904771 Change-Id: I8d853b754cbd4163c17f3d53bf81dc7625c95466
-
- 08 Jan, 2015 1 commit
-
-
Jeff Davidson authored
The lastUntrustedBSSID variable was being used as an SSID, not a BSSID, and was not cleared after the untrusted network was disconnected, causing stats not to increment on new connections if the last connection was to the same SSID. So, remove this unnecessary variable, and check the current WifiConfiguration to determine which network we're currently using, if any. Increment the connection count only when we are actually going to associate with the SSID. This only affects untrusted network flows and should have no impact when connecting to saved Wi-Fi networks. The only non-statistical change involves the boost given to the active network, which is controlled by the NetworkScorer and can be updated dynamically (outside of the framework). Bug: 18908655 Change-Id: I5b712a4ff613d8199d0591e568886be0d2419645
-
- 07 Jan, 2015 2 commits
-
-
The Android Automerger authored
-
Erik Kline authored
More specifically, the DHCP_FAILURE case is entered when a DHCPv4 RENEW fails. Even though we would connect to a network with no IPv4, when roaming to a "same network" and losing IPv4 it's probably better to disconnect and start afresh. Bug: 18867306 Change-Id: Ie667b4f0481ae0510d0dc00db819f4e5d43d98a9
-
- 06 Jan, 2015 3 commits
-
-
Jeff Davidson authored
This ensures that we see all requests for untrusted networks. Bug: 18815795 Change-Id: I9aaba6095b934fee27a27b20fa3adb2a10648e80
-
Jeff Davidson authored
-
The Android Automerger authored
-
- 03 Jan, 2015 1 commit
-
-
The Android Automerger authored
-
- 02 Jan, 2015 1 commit
-
-
The Android Automerger authored
-
- 29 Dec, 2014 1 commit
-
-
vandwalle authored
Bug:18865214 Change-Id: Iae9297cd50ebaf12217d12e4c5d55ae05316e917
-
- 22 Dec, 2014 4 commits
-
-
Jeff Davidson authored
This ensures that we see all requests for untrusted networks. Bug: 18815795 Change-Id: I9aaba6095b934fee27a27b20fa3adb2a10648e80
-
Jeff Davidson authored
This ensures that mConnectionRequests is managed exactly the same way as it is in standard builds, while still making sure that we see all requests for untrusted networks. Bug: 18815795 Change-Id: I9aaba6095b934fee27a27b20fa3adb2a10648e80
-
Jeff Davidson authored
-
The Android Automerger authored
-
- 20 Dec, 2014 1 commit
-
-
Jeff Davidson authored
This reverts commit 22fd791a. Change-Id: I695c9eeea66998845f3210af7d305a469899585e
-
- 18 Dec, 2014 4 commits
-
-
vandwalle authored
-
vandwalle authored
Merge "Disable legacy poor Network detection Bug:18723206 Legacy poor network detection was removed from L settings but can still be enabled during an upgrade if it had been manually enabled by user, now really disable it." into lmp-mr1-dev
-
Jeff Davidson authored
Should be reverted before launch, when a proper fix is in. Bug: 18637384 Change-Id: Id883cbc3c9379a7bad6237e9738a7b09fc5d3503
-
Jeff Davidson authored
Currently we only check whether the most recently seen BSSID has a score before deciding to disconnect an ephemeral network. This causes unnecessary flapping - if multiple BSSIDs are in visible range, and the scorer likes one of them but has no score for the other (or is still looking up the score), we will drop the connection. Instead, as long as we've recently seen a scored BSSID (in the last minute), we keep the connection alive. A scorer can still initiate an immediate disconnect from an unwanted network by nulling scores for all BSSIDs. The timeout (and whether we use this new behavior at all) is controlled by a Settings.Global flag. Bug: 18637384 Change-Id: I6bde3c9eef12caf2cc51c449abffc1c69f60c17f
-
- 17 Dec, 2014 2 commits
-
-
vandwalle authored
Bug:18706288 Change-Id: I27a86aeb650a63511b667244b0138afbc1bc059e
-
Jeff Davidson authored
Should be reverted before launch, when a proper fix is in. Bug: 18637384 Change-Id: Id883cbc3c9379a7bad6237e9738a7b09fc5d3503
-
- 16 Dec, 2014 3 commits
-
-
Jeff Davidson authored
Currently we only check whether the most recently seen BSSID has a score before deciding to disconnect an ephemeral network. This causes unnecessary flapping - if multiple BSSIDs are in visible range, and the scorer likes one of them but has no score for the other (or is still looking up the score), we will drop the connection. Instead, as long as we've recently seen a scored BSSID (in the last minute), we keep the connection alive. A scorer can still initiate an immediate disconnect from an unwanted network by nulling scores for all BSSIDs. The timeout (and whether we use this new behavior at all) is controlled by a Settings.Global flag. Bug: 18637384 Change-Id: I6bde3c9eef12caf2cc51c449abffc1c69f60c17f
-
vandwalle authored
Bug:18723206 Legacy poor network detection was removed from L settings but can still be enabled during an upgrade if it had been manually enabled by user, now really disable it. Change-Id: I661b326c6f5dfacfcc5582cea14dc52501740367
-
The Android Automerger authored
-
- 14 Dec, 2014 2 commits