| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
MMS is not charged as data on Verizon network, roaming
or not roaming.
Test: Manual tested with Vzw SIM. Confirmed sending MMS
will not increase the data usage in Settings->Data Usage
->Cellular data usage.
bug: 31233558
Change-Id: Iaa44ce5385e845a99ce8149be8353e4bf6fad293
|
|
|
|
|
|
|
| |
Fields marked uneditable are: type, protocol, bearer, carrier_enabled
Bug: 30457714
Change-Id: I0d3f1af25e52d48c25ebedfffa37b708dd23fcf5
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
For VZW, turn on option to notify the user when a video call hands over
from wifi to LTE.
Change-Id: Id5097b5308d08e2d2e560e999dc69fde73421982
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Adds a CNAP filtering String array to 311480 in order to filter out
CNAP caller id information that is not helpful.
Bug: 30142293
Change-Id: Ic3f81afb571b335bfc82949772d418360a70fcf0
|
|/
|
|
|
| |
Bug: 30702393
Change-Id: I36e415465c00150830566fa239531ed07ab690eb
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 30793629
Change-Id: I0ad29427b6db1797b45575a93e55f6e4b7edaf19
|
| |
| |
| |
| |
| | |
Bug: 30474919
Change-Id: I0f0dbda86fb441d2b8c10a2934650b9ecec63e19
|
|/
|
|
|
| |
Bug: 30697460
Change-Id: I73e7aa86d283b869c1cea0663699cba64b528d5b
|
|
|
|
|
|
|
|
| |
Adding what should be the final remapping for disconnect causes for
multi-endpoint. These are based on observations in testing.
Bug: 28813047
Change-Id: I19c78671458258e6030ea59297807ab1f85eeb4b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds a key for not supporting hold during incoming and outgoing IMS
calls. This removes the CAPABILITY_HOLD and CAPABILITY_SUPPORT_HOLD
capabilities from the Connection.
Bug: 30195356
Change-Id: I572aa7cdb80d3b4fdb42ea83f828edac5c75ecd9
|
| |
| |
| |
| |
| |
| | |
b/29558615
Change-Id: Ibd49b7e5e3021541007170dc2cf7d98256f4b4c7
|
|\ \
| | |
| | |
| | | |
into nyc-mr1-dev
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before when extreme alert is disabled, severe alert will be disabled
by default because we assume users won't be interested in severe
alert if he is even not interested in extreme (higher level) alert.
Now we turn this feature off for Verizon to fullfill their test
requirement CMAS TC4.
bug: 29369591
Change-Id: I4d9a6839066601e2d398c88a78a8decc12d8ae7a
|
|/
|
|
|
| |
Bug: 30013801
Change-Id: I7990b6ec3a0881d87da8a6a153a75e54970a5202
|
|
|
|
| |
Change-Id: Id9b0e9301f87d2545dfe33219a21b41ec8f561ce
|
|
|
|
| |
Change-Id: I95035c8dc113e0a984fa57d3c9aebe6117481ec2
|
|
|
|
|
|
|
|
| |
Per Verizon spec, adding IMS reason code and message remappings.
These are in support of multi-endpoint.
Bug: 29999290
Change-Id: If87c3b8eef6be7519d1b9df2879e6edbf562c1b2
|
|
|
|
|
|
|
|
|
| |
Enabling carrier config option that suggests the user should enable
wifi calling if they cannot make a call, wfc is off, but they're connected
to a wifi network.
Bug: 27970317
Change-Id: Ibf854cd66d9afc9b3c34d7829200396cff597731
|
|
|
|
|
|
| |
Bug: 29047863
Change-Id: I5c9ed52f97565a4092fac2228963ee9e85747399
|
|
|
|
|
| |
Bug: 29059073
Change-Id: I167f21f2d08c814da5cc04a5cf956dd4c826c849
|
|
|
|
|
|
|
| |
b/28989849: The default WiFi calling preference for Verizon should be
cellular preferred per Carrier Requirements.
Change-Id: Ief9c01e2fee918942580296c2fa3159ce2a7f8a3
|
|
|
|
|
| |
Bug: 29275420
Change-Id: Ie7f562257a48c5af737b7072e73acb963fba9b6c
|
|
|
|
|
| |
Bug: 29045653
Change-Id: I5f6cc9e6e1eecd749422a08ea30a3d5215fca422
|
|
|
|
|
|
|
| |
b/28384577: The default WiFi calling preference for Verizon should be
cellular preferred per Carrier Requirements.
Change-Id: I29a9b2424afb936b7c6d80b6d1a4091a03321b35
|
|
|
|
|
|
|
|
| |
Used Carrier Config to load correct ERI configuration file since
there are MCC/MNC shared by different carriers.
bug: 23887558
Change-Id: I6431b76a79a59bf5d573231d8833fdb0befd1a70
|
|
|
|
|
| |
Bug: 24147407
Change-Id: I0d971a2579443563ffbd665f85664386d162f2a9
|
|
|
|
|
|
| |
Bug: 24519879
Bug: 24681288
Change-Id: Ifdf1899931449b27844bf54a246f0416b9b1033c
|
|
|
|
|
| |
Bug: 22787515
Change-Id: Icb640e63091670e2869988dbbba381cb44911e1c
|
|
|
|
|
| |
Bug: b/21878236
Change-Id: I00eb434c350eeb3df85c8e323845cd3422b06b77
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The variable disable_cdma_activation_code_bool is overridden on shamu
for three specific VZW networks, but the overrides have been moved to
vendor/moto/shamu. They can be deleted from here.
Note: 310304 was supposed to be 310004 (corrected in vendor/moto/shamu)
and 20404 was only supposed to apply for a specific gid1.
Bug: 22229196
Bug: 21618018
Change-Id: I7b4e78480d054daf595f856dab3ffa18979f8f54
|
|
|
|
|
| |
Bug: 22093601
Change-Id: I187da9a992ae7571cfd27a2d3cf7b6ca4c2f9dbc
|
|
|
|
|
| |
Bug: b/21878236
Change-Id: I5c71be5496602da61357a1868bbe72f10f4333f3
|
|
Make DefaultCarrierConfigService easier to maintain by moving the values
for each network into XML files. It's important to note that this uses
assets and not resources. The file for a particular network may depend
on more than just the MCC+MNC in the future.
Note on the XML document format. This is set by
PersistableBundle.restoreFromXml, so there is no option to change it in
this CL.
Bug: 21618018
Change-Id: Iecfe7009c2aa0f7a9d5814d1f355dfe4190ce912
|