1. 13 Jan, 2015 2 commits
  2. 12 Jan, 2015 1 commit
  3. 08 Jan, 2015 1 commit
    • Jeff Davidson's avatar
      Fix incorrect tracking of ephemeral network statistics. · 2c9b6297
      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
      2c9b6297
  4. 07 Jan, 2015 1 commit
    • Erik Kline's avatar
      Disconnect if we had IPv4 and lost it. · ac966790
      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
      ac966790
  5. 06 Jan, 2015 3 commits
  6. 29 Dec, 2014 1 commit
  7. 22 Dec, 2014 2 commits
  8. 18 Dec, 2014 2 commits
  9. 17 Dec, 2014 1 commit
  10. 16 Dec, 2014 2 commits
    • Jeff Davidson's avatar
      Stabilize ephemeral connections in the face of new BSSIDs. · 16fdf070
      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
      16fdf070
    • vandwalle's avatar
      Disable legacy poor Network detection · 82f9342c
      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
      82f9342c
  11. 14 Dec, 2014 9 commits
  12. 12 Dec, 2014 4 commits
  13. 11 Dec, 2014 3 commits
  14. 10 Dec, 2014 1 commit
  15. 09 Dec, 2014 2 commits
  16. 08 Dec, 2014 2 commits
  17. 06 Dec, 2014 3 commits