Remove the old config_ims_package device config and configure the new MMTEL and RCS configurations in Telephony instead. Also, configure the RcsService to be the default RCS service. Bug: 111305845 Test: make checkbuild Change-Id: I0d709b8248f1c40f0a5b50ec799396706eeadd65
354 lines
18 KiB
XML
354 lines
18 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!-- Copyright (C) 2009 The Android Open Source Project
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
-->
|
|
|
|
<!-- These resources are around just to allow their values to be customized
|
|
for different hardware and product builds. Do not translate. -->
|
|
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
|
|
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
|
<bool name="config_unplugTurnsOnScreen">true</bool>
|
|
|
|
<!-- Boolean indicating if restoring network selection should be skipped -->
|
|
<!-- The restoring is handled by modem if it is true-->
|
|
<bool translatable="false" name="skip_restoring_network_selection">true</bool>
|
|
|
|
<!-- Set to true to add links to Cell Broadcast app from Settings and MMS app. -->
|
|
<bool name="config_cellBroadcastAppLinks">true</bool>
|
|
|
|
<!-- MMS user agent string -->
|
|
<string name="config_mms_user_agent" translatable="false">Android-Mms/2.0</string>
|
|
|
|
<!-- MMS user agent prolfile url -->
|
|
<string name="config_mms_user_agent_profile_url" translatable="false"
|
|
>http://www.google.com/oha/rdf/ua-profile-kila.xml</string>
|
|
|
|
<!-- List of regexpressions describing the interface (if any) that represent tetherable
|
|
USB interfaces. If the device doesn't want to support tething over USB this should
|
|
be empty. An example would be "usb.*" -->
|
|
<string-array translatable="false" name="config_tether_usb_regexs">
|
|
<item>"usb\\d"</item>
|
|
<item>"rndis\\d"</item>
|
|
</string-array>
|
|
|
|
<!-- List of regexpressions describing the interface (if any) that represent tetherable
|
|
Wifi interfaces. If the device doesn't want to support tethering over Wifi this
|
|
should be empty. An example would be "softap.*" -->
|
|
<string-array translatable="false" name="config_tether_wifi_regexs">
|
|
<item>"softap0"</item>
|
|
<item>"wigig0"</item>
|
|
<item>"wifi_br0"</item>
|
|
<item>"wlan0"</item>
|
|
<item>"wlan1"</item>
|
|
</string-array>
|
|
|
|
<!-- List of regexpressions describing the interface (if any) that represent tetherable
|
|
bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this
|
|
should be empty. -->
|
|
<string-array translatable="false" name="config_tether_bluetooth_regexs">
|
|
<item>"bnep\\d"</item>
|
|
<item>"bt-pan"</item>
|
|
</string-array>
|
|
|
|
<!-- When true, the tethering upstream network follows the current default
|
|
Internet network (except when the current default network is mobile,
|
|
in which case a DUN network will be used if required). -->
|
|
<bool translatable="false" name="config_tether_upstream_automatic">true</bool>
|
|
|
|
<!-- Dhcp range (min, max) to use for tethering purposes -->
|
|
<!-- USB is 192.168.42.1 and 255.255.255.0
|
|
Wifi is 192.168.43.1 and 255.255.255.0
|
|
BT is limited to max default of 5 connections. 192.168.44.1 to 192.168.48.1
|
|
with 255.255.255.0
|
|
P2P is 192.168.49.1 and 255.255.255.0
|
|
Wigig is 192.168.50.1 and 255.255.255.0
|
|
Wigig P2P is 192.168.51.1 and 255.255.255.0
|
|
-->
|
|
<string-array name="config_tether_dhcp_range">
|
|
<item>192.168.42.2</item>
|
|
<item>192.168.42.254</item>
|
|
<item>192.168.43.2</item>
|
|
<item>192.168.43.254</item>
|
|
<item>192.168.44.2</item>
|
|
<item>192.168.44.254</item>
|
|
<item>192.168.45.2</item>
|
|
<item>192.168.45.254</item>
|
|
<item>192.168.46.2</item>
|
|
<item>192.168.46.254</item>
|
|
<item>192.168.47.2</item>
|
|
<item>192.168.47.254</item>
|
|
<item>192.168.48.2</item>
|
|
<item>192.168.48.254</item>
|
|
<item>192.168.49.2</item>
|
|
<item>192.168.49.254</item>
|
|
<item>192.168.50.2</item>
|
|
<item>192.168.50.254</item>
|
|
<item>192.168.51.2</item>
|
|
<item>192.168.51.254</item>
|
|
</string-array>
|
|
|
|
<!-- This string array should be overridden by the device to present a list of network
|
|
attributes. This is used by the connectivity manager to decide which networks can coexist
|
|
based on the hardware -->
|
|
<!-- An Array of "[Connection name],[ConnectivityManager.TYPE_xxxx],
|
|
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
|
|
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
|
|
before automatically restore the default connection. Set -1 if the connection
|
|
does not require auto-restore. -->
|
|
<!-- the 6th element indicates boot-time dependency-met value. -->
|
|
<string-array translatable="false" name="networkAttributes">
|
|
<item>wifi,1,1,1,-1,true</item>
|
|
<item>mobile,0,0,0,-1,true</item>
|
|
<item>mobile_mms,2,0,4,60000,true</item>
|
|
<item>mobile_supl,3,0,2,60000,true</item>
|
|
<item>mobile_dun,4,0,2,60000,true</item>
|
|
<item>mobile_hipri,5,0,3,60000,true</item>
|
|
<item>mobile_fota,10,0,2,60000,true</item>
|
|
<item>mobile_ims,11,0,2,60000,true</item>
|
|
<item>mobile_cbs,12,0,2,60000,true</item>
|
|
<item>bluetooth,7,7,2,-1,true</item>
|
|
<item>mobile_emergency,15,0,5,-1,true</item>
|
|
</string-array>
|
|
|
|
<!-- This string array should be overridden by the device to present a list of radio
|
|
attributes. This is used by the connectivity manager to decide which networks can coexist
|
|
based on the hardware -->
|
|
<!-- An Array of "[ConnectivityManager connectionType],
|
|
[# simultaneous connection types]" -->
|
|
<string-array translatable="false" name="radioAttributes">
|
|
<item>"1,1"</item>
|
|
<item>"0,1"</item>
|
|
<item>"7,1"</item>
|
|
</string-array>
|
|
|
|
<!-- Whether WiFi display is supported by this device.
|
|
There are many prerequisites for this feature to work correctly.
|
|
Here are a few of them:
|
|
* The WiFi radio must support WiFi P2P.
|
|
* The WiFi radio must support concurrent connections to the WiFi display and
|
|
to an access point.
|
|
* The Audio Flinger audio_policy.conf file must specify a rule for the "r_submix"
|
|
remote submix module. This module is used to record and stream system
|
|
audio output to the WiFi display encoder in the media server.
|
|
* The remote submix module "audio.r_submix.default" must be installed on the device.
|
|
* The device must be provisioned with HDCP keys (for protected content).
|
|
-->
|
|
<bool name="config_enableWifiDisplay">true</bool>
|
|
|
|
<!-- Set to true if the wifi display supports compositing content stored
|
|
in gralloc protected buffers. For this to be true, there must exist
|
|
a protected hardware path for surface flinger to composite and send
|
|
protected buffers to the wifi display video encoder.
|
|
If this flag is false, we advise applications not to use protected
|
|
buffers (if possible) when presenting content to a wifi display because
|
|
the content may be blanked.
|
|
This flag controls whether the {@link Display#FLAG_SUPPORTS_PROTECTED_BUFFERS}
|
|
flag is set for wifi displays.
|
|
-->
|
|
<bool name="config_wifiDisplaySupportsProtectedBuffers">true</bool>
|
|
|
|
<!-- Boolean indicating whether the wifi chipset has dual frequency band support -->
|
|
<bool translatable="false" name="config_wifi_dual_band_support">true</bool>
|
|
|
|
<!-- Boolean indicating whether the wifi chipset has background scan support -->
|
|
<bool translatable="false" name="config_wifi_background_scan_support">true</bool>
|
|
|
|
<!-- Wifi driver supports batched scan -->
|
|
<bool translatable="false" name="config_wifi_batched_scan_supported">true</bool>
|
|
|
|
<!-- Indicates that connected MAC randomization is supported on this device -->
|
|
<bool translatable="false" name="config_wifi_connected_mac_randomization_supported">true</bool>
|
|
|
|
<!-- Configure wifi tcp buffersizes in the form:
|
|
rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max -->
|
|
<string name="config_wifi_tcp_buffers" translatable="false">524288,1048576,4194304,524288,1048576,4194304</string>
|
|
|
|
<!-- Indicate whether closing the lid causes the device to go to sleep and opening
|
|
it causes the device to wake up.
|
|
The default is false. -->
|
|
<bool name="config_lidControlsSleep">true</bool>
|
|
|
|
<!-- Indicate whether to allow the device to suspend when the screen is off
|
|
due to the proximity sensor. This resource should only be set to true
|
|
if the sensor HAL correctly handles the proximity sensor as a wake-up source.
|
|
Otherwise, the device may fail to wake out of suspend reliably.
|
|
The default is false. -->
|
|
<bool name="config_suspendWhenScreenOffDueToProximity">true</bool>
|
|
|
|
<!-- ComponentName of a dream to show whenever the system would otherwise have
|
|
gone to sleep. When the PowerManager is asked to go to sleep, it will instead
|
|
try to start this dream if possible. The dream should typically call startDozing()
|
|
to put the display into a low power state and allow the application processor
|
|
to be suspended. When the dream ends, the system will go to sleep as usual.
|
|
Specify the component name or an empty string if none.
|
|
|
|
Note that doze dreams are not subject to the same start conditions as ordinary dreams.
|
|
Doze dreams will run whenever the power manager is in a dozing state. -->
|
|
<string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
|
|
|
|
<!-- If true, the doze component is not started until after the screen has been
|
|
turned off and the screen off animation has been performed. -->
|
|
<bool name="config_dozeAfterScreenOffByDefault">true</bool>
|
|
|
|
<!-- Whether the always on display mode is available. -->
|
|
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
|
|
|
|
<!-- Control whether the always on display mode is enabled by default. This value will be used
|
|
during initialization when the setting is still null. -->
|
|
<bool name="config_dozeAlwaysOnEnabled">false</bool>
|
|
|
|
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
|
|
device from the display on/off state.
|
|
|
|
When false, autosuspend_disable() will be called before the display is turned on
|
|
and autosuspend_enable() will be called after the display is turned off.
|
|
This mode provides best compatibility for devices using legacy power management
|
|
features such as early suspend / late resume.
|
|
|
|
When true, autosuspend_display() and autosuspend_enable() will be called
|
|
independently of whether the display is being turned on or off. This mode
|
|
enables the power manager to suspend the application processor while the
|
|
display is on.
|
|
|
|
This resource should be set to "true" when a doze component has been specified
|
|
to maximize power savings but not all devices support it.
|
|
|
|
Refer to autosuspend.h for details.
|
|
-->
|
|
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
|
|
|
|
<!-- Screen brightness used to dim the screen while dozing in a very low power state.
|
|
May be less than the minimum allowed brightness setting
|
|
that can be set by the user. -->
|
|
<integer name="config_screenBrightnessDoze">17</integer>
|
|
|
|
<!-- Configure mobile tcp buffer sizes in the form:
|
|
rat-name:rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max
|
|
If no value is found for the rat-name in use, the system default will be applied.
|
|
-->
|
|
<string-array name="config_mobile_tcp_buffers">
|
|
<item>lte:2097152,4194304,8388608,262144,524288,1048576</item>
|
|
<item>lte_ca:4096,6291456,12582912,4096,1048576,2097152</item>
|
|
<item>umts:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hspa:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hsupa:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hsdpa:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hspap:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>edge:4093,26280,35040,4096,16384,35040</item>
|
|
<item>gprs:4092,8760,11680,4096,8760,11680</item>
|
|
<item>evdo:4094,87380,524288,4096,16384,262144</item>
|
|
</string-array>
|
|
|
|
<!-- Flag specifying whether VoLTE is available on device -->
|
|
<bool name="config_device_volte_available">true</bool>
|
|
|
|
<!-- Flag specifying whether WFC over IMS is available on device -->
|
|
<bool name="config_device_wfc_ims_available">true</bool>
|
|
|
|
<!-- IWLAN network service package name to bind to by default. If none is specified in an overlay, an
|
|
empty string is passed in -->
|
|
<string name="config_wlan_network_service_package">vendor.qti.iwlan</string>
|
|
|
|
<!-- Telephony qualified networks service package name to bind to by default. -->
|
|
<string name="config_qualified_networks_service_package">vendor.qti.iwlan</string>
|
|
|
|
<!-- Flag specifying whether or not IMS will use the ImsResolver dynamically -->
|
|
<bool name="config_dynamic_bind_ims">true</bool>
|
|
|
|
<!-- Config determines whether to update phone object when voice registration
|
|
state changes. Voice radio tech change will always trigger an update of
|
|
phone object irrespective of this config -->
|
|
<bool name="config_switch_phone_on_voice_reg_state_change">false</bool>
|
|
|
|
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
|
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
|
|
|
<!-- Flag indicating if the speed up audio on mt call code should be executed -->
|
|
<bool name="config_speed_up_audio_on_mt_calls">true</bool>
|
|
|
|
<!-- Shutdown if the battery temperature exceeds (this value * 0.1) Celsius. -->
|
|
<integer name="config_shutdownBatteryTemperature">680</integer>
|
|
|
|
<!-- Operating volatage for bluetooth controller. 0 by default-->
|
|
<integer name="config_bluetooth_operating_voltage_mv">3300</integer>
|
|
|
|
<!-- Vibrator pattern for feedback about a long screen/key press -->
|
|
<integer-array name="config_longPressVibePattern">
|
|
<item>0</item>
|
|
<item>10</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for feedback about touching a virtual key -->
|
|
<integer-array name="config_virtualKeyVibePattern">
|
|
<item>0</item>
|
|
<item>10</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
|
|
<integer-array name="config_keyboardTapVibePattern">
|
|
<item>10</item>
|
|
</integer-array>
|
|
|
|
<!-- Default list of files pinned by the Pinner Service -->
|
|
<string-array translatable="false" name="config_defaultPinnerServiceFiles">
|
|
<item>"/system/framework/arm64/boot-framework.oat"</item>
|
|
<item>"/system/framework/framework.jar"</item>
|
|
<item>"/system/framework/oat/arm64/services.odex"</item>
|
|
<item>"/system/framework/services.jar"</item>
|
|
<item>"/apex/com.android.art/javalib/core-oj.jar"</item>
|
|
<item>"/apex/com.android.art/javalib/core-libart.jar"</item>
|
|
<item>"/apex/com.android.media/javalib/updatable-media.jar"</item>
|
|
<item>"/system_ext/priv-app/SystemUI/SystemUI.apk"</item>
|
|
<item>"/system_ext/priv-app/SystemUI/oat/arm64/SystemUI.odex"</item>
|
|
<item>"/system/lib64/libsurfaceflinger.so"</item>
|
|
</string-array>
|
|
|
|
<!-- Should the pinner service pin the Camera application? -->
|
|
<bool name="config_pinnerCameraApp">true</bool>
|
|
|
|
<!-- Should the pinner service pin the Home application? -->
|
|
<bool name="config_pinnerHomeApp">true</bool>
|
|
|
|
<!-- List of files pinned by the Pinner Service with the JIT Zygote boot image b/119800099 -->
|
|
<string-array translatable="false" name="config_jitzygoteBootImagePinnerServiceFiles">
|
|
<item>"/system/framework/framework.jar"</item>
|
|
<item>"/system/framework/services.jar"</item>
|
|
<item>"/apex/com.android.art/javalib/core-oj.jar"</item>
|
|
<item>"/apex/com.android.art/javalib/core-libart.jar"</item>
|
|
<item>"/apex/com.android.media/javalib/updatable-media.jar"</item>
|
|
<item>"/system_ext/priv-app/SystemUI/SystemUI.apk"</item>
|
|
<item>"/system/lib64/libsurfaceflinger.so"</item>
|
|
</string-array>
|
|
|
|
<!-- Whether a software navigation bar should be shown. NOTE: in the future this may be
|
|
autodetected from the Configuration. -->
|
|
<bool name="config_showNavigationBar">true</bool>
|
|
|
|
<!-- When true use the linux /dev/input/event subsystem to detect the switch changes
|
|
on the headphone/microphone jack. When false use the older uevent framework. -->
|
|
<bool name="config_useDevInputEventForAudioJack">true</bool>
|
|
|
|
<!-- Is the device capable of hot swapping an ICC Card -->
|
|
<bool name="config_hotswapCapable">true</bool>
|
|
|
|
<!-- True if the device supports Sustained Performance Mode-->
|
|
<bool name="config_sustainedPerformanceModeSupported">true</bool>
|
|
|
|
<!-- Whether device supports double tap to wake -->
|
|
<bool name="config_supportDoubleTapWake">true</bool>
|
|
|
|
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
|
|
in hardware. -->
|
|
<bool name="config_setColorTransformAccelerated">true</bool>
|
|
</resources>
|