diff options
| author | 2024-03-04 21:39:38 +0000 | |
|---|---|---|
| committer | 2024-03-04 21:39:44 +0000 | |
| commit | 66223039bc89f2600508066af4f8ba89dc21933a (patch) | |
| tree | 6421c93030fdbbed44a393823e1598e36a13d3ed | |
| parent | cd844c4adb68f6b76879df32dddfd03b62e01d93 (diff) | |
Revert "Add configuration for network capabilities that would be..."
Revert submission 26188732-satellite_internet_support
Reason for revert: Droid-monitored triggered revert due to b/328107058. Will be verifying through ABTD for confirmation and before submitting the revert.
Reverted changes: /q/submissionid:26188732-satellite_internet_support
Change-Id: Ie27eb2149aaabff97cf72a032265523a807a82fd
| -rw-r--r-- | core/res/res/values/config_telephony.xml | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/core/res/res/values/config_telephony.xml b/core/res/res/values/config_telephony.xml index 660e4c03320a..5e3e1b0bbb43 100644 --- a/core/res/res/values/config_telephony.xml +++ b/core/res/res/values/config_telephony.xml @@ -334,17 +334,4 @@ <bool name="config_enable_cellular_on_boot_default">true</bool> <java-symbol type="bool" name="config_enable_cellular_on_boot_default" /> - <!-- The network capabilities that would be forced marked as cellular transport regardless it's - on cellular or satellite--> - <string-array name="config_force_cellular_transport_capabilities"> - <!-- Added the following three capabilities for now. For the long term solution, the client - requests satellite network should really include TRANSPORT_SATELLITE in the network - request. With the following workaround, the clients can continue request network with - the following capabilities with TRANSPORT_CELLULAR. The network with one of the - following capabilities would also be marked as cellular. --> - <item>ims</item> - <item>eims</item> - <item>xcap</item> - </string-array> - <java-symbol type="array" name="config_force_cellular_transport_capabilities" /> </resources> |