IMS connection capabilities were not getting
propagated to the upper layers whenever a
capability was added or removed. Adding the
same.
Change-Id: Ic67d76df05c8b2a1b8abaf27f266fe9693764e52
Support multiple CA certificates as trust anchors for server certs
when connecting to EAP networks. For the full feature, also requries
wpa_supplicant support, Wifi stack change to set up certificates and
aliases, and Wifi Setting UI tweak.
Bug: 22547958
Change-Id: I3c9f0e184632b79044a9e623ce0e7d9aaddd2ae3
This reverts commit 831e401c055391745691a58d0c87c48b49139f50.
Not needed now since tests create HandlerThread
BUG=25691379
Change-Id: Ic0ac3e3ef3c717fd31acb5fc8d6d81cc9995a2f7
Moved retry manager from DataConnection to ApnContext. Moved the
configuration from system properties to carrier config.
bug: 22208242
Change-Id: I224d4b0fd0115b964e85a07e2c1b5061726ca91b
* Add boolean WifiConfiguration.shared, which indicates whether a network
is shared (visible to and usable by all users) or private (visible to
and usable only by the user who created it)
* Extend WifiConfiguration.configKey(...) so that when two users create
private configurations for the same network, their configurationKeys
will be different.
* Make AccessPoint.matches(...) take into account the shared flag
BUG=25600871
Change-Id: I4a4335fa3b4b4f850e16748583a29ab66992ddc8
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
- Added acceptRingingCall API which accepts a videostate to complement the
existing API.
Bug: 20159300
Change-Id: I2a9d53fd4dbbb0be49d95416f7e26d3ec61774cd
Used the correct CDMA bitmask to determine if the bearer services
are based on 3GPP2 radio technologies.
bug: 26318528
Change-Id: Ic30c25aa7b67372898a041dd1f3a08a3abede394
Correct the comments for exponential back off scan. Only binary
exponential back off scan is supported.
Updated the API doc. A couple of un-related fields which were
not updated get updated as well.
Bug: 26236392
Change-Id: I5668092f393b564aa40904ed609a51aa16890614
Added new PhoneAccount capability used to indicate whether the dialer
should use the presence bit in the contacts provider to determine when
the video call icon is shown or not.
Bug: 20257833
Change-Id: Ifb3cc5b7ff1090d539dfb925dce9f6327de15c46
Current usage of NetworkSpecifier: network factory will match a request
if the request has either a (1) empty network specifier, or (2) a
network specifier which is identical to that of the network factory.
Note: 'matching' w.r.t. network specifier - all other matching rules
are still in effect.
Change: add rule (3) or the network specifier of the network factory
is the special string (which is defined as "*" and which user-facing
network requests aren't allowed to use).
Rationale: allows on-demand network creation.
Example:
- Can specify a Wi-Fi NetworkRequest with NetworkSpecifier="ssid"
- It will match a Wi-Fi network factory specifying NetworkSpecifier="*"
- That network factory will bring up a Wi-Fi network, connecting to the
specified SSID.
- Once the network is created it will create a NetworkAgent which will
now have a NetworkSpecifier matching that of the request (not the
match-all special string!)
That final step of making sure that the NetworkAgent matches the request
and not the match-all is critical to delivering any subsequent callbacks
correctly. I.e. your network will only get callbacks which match it.
Bug: 26192833
Change-Id: I49e3b492e0bb48a3f6e9a34e3f94f0e1cf89741f
If a direct listener alarm attempts to match a regular
PendingIntent alarm, it will attempt to fetch the binder of the
regular alarm's direct listener, which is null, and crash the
system with an NPE.
Cherry-picked from 9b43ce0c98ce9f865d6db547529d098c8982cc
Bug: 25823676
Change-Id: I85fb98b43436930a2513274dc5ab408f7d41d97f