In this change list, the old WifiAutojoin module is
refactored initially. The old WifiAutojoinController is
replaced with a new WifiQualifiedNetworkSelector.
WifiConfiguration, WifiConfigureStore and
WifiStateMachine have been modified accordingly. The new
network selection logic is refactored with a more clear
and deterministci one. To refer to thedescribed in
details, in "Quality Network Selection and Connectivity
Scan Management in N". The link of the document is:
https://docs.google.com/document/d
/1JPTa2NEk-PgjCJ16fIrR6ohV-kDKveDlYDOeiMCB2_c
cherry-picked from 8d106780b6a638552749e54e169fc72537d4bccc
and make changes on WiFiConfigurationSerializer.java since
it is not on mm-wireless-dev
Bug:26012244
Change-Id: I44e454544b630b891c9a58a18b5a028edcce580f
In this change list, the old WifiAutojoin module is
refactored initially. The old WifiAutojoinController is
replaced with a new WifiQualifiedNetworkSelector.
WifiConfiguration, WifiConfigureStore and
WifiStateMachine have been modified accordingly. The new
network selection logic is refactored with a more clear
and deterministci one. To refer to thedescribed in
details, in "Quality Network Selection and Connectivity
Scan Management in N". The link of the document is:
https://docs.google.com/document/d
/1JPTa2NEk-PgjCJ16fIrR6ohV-kDKveDlYDOeiMCB2_c
Bug:26012244
Change-Id: I3df124c110e458e3b6bc29466b9046748d79582a
Remove the battery saver notification and instead create a detail
panel within QS that allows it to be turned on and off.
Change-Id: I54654d26183586fa171fda04877a840701f8ef33
Add a parser that will parse an XML of the suggestion categories
and ordering and query those categories into Tiles.
Change-Id: I3154c94e176108358163bbe36feb48e889fe00d1
It is not valid for the user to choose a disabled WebView implementation
so if the user does that we prompt them to enable the chosen package. In
this patch we add a string resource for the message prompting the user
to do this.
Bug: 26400585
Change-Id: I112783135c453c324f9178dcdac6bacdd73d33b1
When hidden PackageManager methods take a userId argument, they
should be named explicitly with the "AsUser" suffix. This fixes
several lagging examples so that we can pave the way to safely
start passing flags to new methods without scary overloading.
Also fix spacing issues in various logging statements.
Change-Id: I1e42f7f66427410275df713bea04f6e0445fba28
Avoid the libcore.icu.TimeZoneNames cache for time zone
settings by using ICU4J: it will not use timezone names
that were cached and can be missing / incorrect if the
clock was incorrect at zygote start. Instead, the devices
current time will be used when generating the names.
This change values correctness over performance. ICU does
perform its caching of names so I don't expect any
degredation to be noticeable.
Bug: 20879084
Bug: 26158280
Bug: 21015187
Bug: 26182881
Change-Id: I9f68e3e5232434949468305bbdaf7e697e58da1e
Make it possible to change WebView provider (through a Developer
setting) and kill all apps using the old provider.
This includes checking the signatures of the WebView providers to make
sure they are valid.
Now that we can change WebView provider through a setting it is possible
to change provider while some provider is being updated. Because of this
we now keep track of which provider should be in use in
WebViewUpdateService to make sure we use the correct provider at all
times.
We now also read WebView package meta data (name, package name, and
signature) from a separate xml file.
Main bug: crbug.com/546185
Bug: 25338573
Change-Id: I660fd1a40a5388f6569a06a7f0d029e8ff65945a
Try to avoid too many calls to the PM and cache the info we get
from it to avoid too much stuff during settings launch.
Change-Id: I64132cbe47cf8eac6080c8c82583b0b5eeb75a28
Currently, both the wifi detail view in Quick Settings and the
wifi settings screen show "connected, no internet" for a few
seconds after a network connects. This makes it seem that
network validation is slow, even though usually it only takes
tens or hundreds of milliseconds.
Fix this by updating the access point list when we receive an
onCapabilitiesChanged NetworkCallback for the current wifi
connection.
This also allows us to stop listening to the RSSI_CHANGED_ACTION
broadcast, because:
1. WifiStateMachine only ever sends out that broadcast just after
calling updateCapabilities, which causes an
onCapabilitiesChanged callback to be received.
2. We don't use any of the extras in the RSSI_CHANGED_ACTION
broadcast, only call updateNetworkInfo, which we do on
every onCapabilitiesChanged callback anyway.
While I'm at it, move a variable assignment around to improve
clarity.
Change-Id: I57d3a13754ba4d8c6d58c566713d3f07d0ed2476
