Adding the extra key that will be used to
propagate RAT information for each call via
call extras. The key is used in IMS Service.
Bug: 20144385
Change-Id: Ia7ca81d661afb579fd25315036c43489b1dca50d
Allow the API to specify if the selection should be persisted across reboots.
This also has the side affect of not notifying the user when signal is lost.
Necessary becasue the API might be used transparent to the user and the
notifications will be bizarre.
Bug: 23971948
Change-Id: Ibb15144fb8a61f63a9c967d875d9ce8c70520ff0
Two arrays are passed from caller (in this case IMS service
implementation) to listener (in this case client of ImsManager).
Listener is not modifying arrays and caller is not expecting
data to be returned back.
Bug: 23749309
Change-Id: I6231cfd16852acfca88ee43e8538b2440058d774
+ Add new API for handling DB query and Resources object per subscription.
+ Add constants for column name of DB storing subscription info.
+ Add a common settings file for multi-tab
Bug: 22360525
Change-Id: Icf6d35bdbe31618e2a95df450aee12b99d3aea7a
Legacy API should not need new permissions.
Also found some more hidden/system that should have permissions.
bug:22379438
bug:19257083
Change-Id: I24be0a90dffcffe03d25982a9b02eedcf03fbd59
Hooks the ConnectivityManager.TYPE_MOBILE_EMERGENCY,
PhoneConstants.APN_TYPE_EMERGENCY, and NetworkCapabilities.NET_CAPABILITY_EIMS
together so carrier apps can request connections to this APN.
bug:21785357
Change-Id: Id92a5e28d19407cc7a8f8b5478b23457f2f7f89d
1. IMS MWI Feature
- Add new API to update waiting
voice message count, for UI
propagation based on RFC 3842
2. phantom call support
Supplementary services
3. IMS : Incoming Call Barring
- Modified existing API to support
request like registration,activation,
deactivation,erasure,interogation.
4.Unsol supplementary service notification
- send unsol supplementary notification to UI
- add call history info
Miscellaneous
5. Ims: Originate conference call in DIALING state
6. IMS: Addition of Extras to ImsCallProfile
- Add EXTRA string definitions to ImsCallProfile
7. IMS: Definition of error code
- answered elsewhere
- FDN call failure
8.
- Propagate IMS supplementary services to telephony framework
- Introduce call forwarding history info.
Bug: 21725750
Squash of 2 earlier CLs:
Change-Id: I52a64e9a5df3479189f62921a01655a50fb386fc
Change-Id: Idc3a433785e84a3d683cbcfc7fb90f0b89dced12
Change-Id: I428ce3c6a043e43b86dea41622e0a828d8b45e53
Renamed API to use consistent semantics: available refers to the current
state of the service rather then whether feature is enabled by device/carrier/
user.
Added VT API to match VoLTE/WFC.
Change-Id: Ifb31f123db77e731e75a982b8594168f59a289e7
Current code does not map pay phone and unknown
presentation with OIR.
Add code to map pay phone and unknown presentation
with OIR correctly.
Bug: 22123243
Change-Id: I7610db8547a0f0f5529c2627879047dd9a45cf9f
TM.getCellNetworkScanResults: Performs a radio scan for networks and returns
a list of OperatorInfo.
Tm.setNetworkSelectionModeManual: Manually selects a network and returns the
status of the selection.
Bug: 21563489
Change-Id: If64f30d6f1ed373c1d90433688389307f3dfee8c
- Cleanup javadoc to make it more explicit how to use STATE_AUDIO_ONLY.
- Use VideoProfile.isAudioOnly() instead of doing == comparison.
Bug: 21645094
Change-Id: I5a67290a996f8f338aebab72a4d3cb57f1b1993b
Part of this API involves persisting config bundles to avoid binding to
apps at critical moments (like boot). Regular bundles should not be
written to disk because they support object types that can lose their
meaning while the data is at rest.
In order to use PersistableBundle, we must either start with one or
filter unwanted types out of Bundle objects. Since the carrier config
API has no use for unsupported types, we chose to use PersistableBundle
everywhere.
Bug: 20268926
Change-Id: I17989ce840014c2a0ed3679c1bca5a8498082c7f
Move CameraCapabilities into VideoProfile
Make PhoneAccount and PhoneAccountHandle final
Bug: 21040387
Bug: 21066505
Change-Id: I72453c89ae3765f9b9cf263938fce96d5978d2e0
Including a fromProfile in addition to the requestedProfile.
- Changed VideoCallImpl to generate the fromVideoProfile based on the
call's current videoState. This ensures the InCall UI only needs to
pass in the new video profile; the VideoCall Impl already has enough
knowledge to generate the fromProfile.
- Changed VideoCallImpl to track the current videoQuality, which forms
a part of the fromVideoProfile.
Bug: 20704229
Change-Id: I89f293f03a2b13fc8c1dcfd8a07ab8640d3950e0