Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 6877c6fd authored by Jack Yu's avatar Jack Yu Committed by Cherrypicker Worker
Browse files

Add configuration for network capabilities that would be forced marked as cellular transport 

Bug: 326972202
Test: atest FrameworksTelephonyTests, CtsTelephonyTestCases,
Test: Device test at b/324536098
Test: Basic telephony functionality tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0fe76a0999b3f46098de9d025804950273540152)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:8e0436299cd89495bd2b59f88394524d51341c28)
Merged-In: Iffd705d7f380713ea340c1048a87cbee5f9dcf43
Change-Id: Iffd705d7f380713ea340c1048a87cbee5f9dcf43
parent 9860e4e2

core/res/res/values/config_telephony.xml

+14 −0
Original line number Diff line number Diff line
@@ -334,4 +334,18 @@ 
    <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>