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

Commit 0fe76a09 authored by Jack Yu's avatar Jack Yu
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
Change-Id: Iffd705d7f380713ea340c1048a87cbee5f9dcf43
parent 20faed1b

core/res/res/values/config_telephony.xml

+13 −0
Original line number Diff line number Diff line
@@ -339,4 +339,17 @@ 
    <integer name="config_metrics_pull_cooldown_millis">82800000</integer>

    <java-symbol type="integer" name="config_metrics_pull_cooldown_millis" />



    <!-- 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>