bb280c7d67
This is a follow-up to https://github.com/phhusson/device_phh_treble/pull/163 which is about enabling `config_cellBroadcastAppLinks` for all devices, therefore making it unnecessary to specify it in a hardware overlay as well.
208 lines
12 KiB
XML
208 lines
12 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
/*
|
|
** Copyright 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.
|
|
*/
|
|
-->
|
|
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
|
|
<!-- List of regexpressions describing the interface (if any) that represent tetherable
|
|
USB interfaces. If the device doesn't want to support tethering 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>wigig0</item>
|
|
<item>wlan0</item>
|
|
</string-array>
|
|
<!-- Array of ConnectivityManager.TYPE_xxxx values allowable for tethering.
|
|
Common options are [1, 4] for TYPE_WIFI and TYPE_MOBILE_DUN or
|
|
[1,7,0] for TYPE_WIFI, TYPE_BLUETOOTH, and TYPE_MOBILE.
|
|
This list is also modified by code within the framework, including:
|
|
- TYPE_ETHERNET (9) is prepended to this list, and
|
|
- the return value of TelephonyManager.getTetherApnRequired()
|
|
determines how the array is further modified:
|
|
* DUN_REQUIRED
|
|
TYPE_MOBILE is removed (if present)
|
|
TYPE_MOBILE_HIPRI is removed (if present)
|
|
TYPE_MOBILE_DUN is appended (if not already present)
|
|
* DUN_NOT_REQUIRED
|
|
TYPE_MOBILE_DUN is removed (if present)
|
|
TYPE_MOBILE is appended (if not already present)
|
|
TYPE_MOBILE_HIPRI is appended (if not already present)
|
|
* DUN_UNSPECIFIED
|
|
if any of TYPE_MOBILE{,_DUN,_HIPRI} are present:
|
|
change nothing
|
|
else:
|
|
TYPE_MOBILE is appended
|
|
TYPE_MOBILE_HIPRI is appended
|
|
For other changes applied to this list, now and in the future, see
|
|
com.android.server.connectivity.tethering.TetheringConfiguration.
|
|
Note also: the order of this is important. The first upstream type
|
|
for which a satisfying network exists is used.
|
|
-->
|
|
<integer-array translatable="false" name="config_tether_upstream_types">
|
|
<item>0</item>
|
|
<item>1</item>
|
|
<item>5</item>
|
|
<item>7</item>
|
|
</integer-array>
|
|
<!-- Boolean indicating whether the wifi chipset supports background scanning mechanism.
|
|
This mechanism allows the host to remain in suspend state and the dongle to actively
|
|
scan and wake the host when a configured SSID is detected by the dongle. This chipset
|
|
capability can provide power savings when wifi needs to be always kept on. -->
|
|
<bool translatable="false" name="config_wifi_background_scan_support">true</bool>
|
|
<!-- Boolean indicating whether or not wifi firmware debugging is enabled -->
|
|
<bool translatable="false" name="config_wifi_enable_wifi_firmware_debugging">false</bool>
|
|
<!-- Wifi driver supports batched scan -->
|
|
<bool translatable="false" name="config_wifi_batched_scan_supported">true</bool>
|
|
<!-- Flag indicating whether the we should enable the automatic brightness in Settings.
|
|
Software implementation will be used if config_hardware_auto_brightness_available is not set -->
|
|
<bool name="config_automatic_brightness_available">true</bool>
|
|
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
|
|
in hardware. -->
|
|
<bool name="config_setColorTransformAccelerated">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>
|
|
<!-- Is the device capable of hot swapping an UICC Card -->
|
|
<bool name="config_hotswapCapable">true</bool>
|
|
<!-- Minimum screen brightness setting allowed by the power manager.
|
|
The user is forbidden from setting the brightness below this level. -->
|
|
<integer name="config_screenBrightnessSettingMinimum">1</integer>
|
|
<!-- 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>
|
|
<!-- Stability requirements in milliseconds for accepting a new brightness level. This is used
|
|
for debouncing the light sensor. Different constants are used to debounce the light sensor
|
|
when adapting to brighter or darker environments. This parameter controls how quickly
|
|
brightness changes occur in response to an observed change in light level that exceeds the
|
|
hysteresis threshold. -->
|
|
<integer name="config_autoBrightnessBrighteningLightDebounce">2000</integer>
|
|
<integer name="config_autoBrightnessDarkeningLightDebounce">4000</integer>
|
|
<!-- Screen brightness used to dim the screen when the user activity
|
|
timeout expires. May be less than the minimum allowed brightness setting
|
|
that can be set by the user. -->
|
|
<integer name="config_screenBrightnessDim">1</integer>
|
|
<!-- Array of light sensor LUX values to define our levels for auto backlight brightness support.
|
|
The N entries of this array define N + 1 control points as follows:
|
|
(1-based arrays)
|
|
Point 1: (0, value[1]): lux <= 0
|
|
Point 2: (level[1], value[2]): 0 < lux <= level[1]
|
|
Point 3: (level[2], value[3]): level[2] < lux <= level[3]
|
|
...
|
|
Point N+1: (level[N], value[N+1]): level[N] < lux
|
|
The control points must be strictly increasing. Each control point
|
|
corresponds to an entry in the brightness backlight values arrays.
|
|
For example, if LUX == level[1] (first element of the levels array)
|
|
then the brightness will be determined by value[2] (second element
|
|
of the brightness values array).
|
|
Spline interpolation is used to determine the auto-brightness
|
|
backlight values for LUX levels between these control points.
|
|
Must be overridden in platform specific overlays -->
|
|
<integer-array name="config_autoBrightnessLevels">
|
|
<item>100</item>
|
|
<item>200</item>
|
|
<item>400</item>
|
|
<item>600</item>
|
|
<item>2000</item>
|
|
<item>7000</item>
|
|
</integer-array>
|
|
<!-- Array of output values for LCD backlight corresponding to the LUX values
|
|
in the config_autoBrightnessLevels array. This array should have size one greater
|
|
than the size of the config_autoBrightnessLevels array.
|
|
The brightness values must be between 0 and 255 and be non-decreasing.
|
|
This must be overridden in platform specific overlays -->
|
|
<integer-array name="config_autoBrightnessLcdBacklightValues">
|
|
<item>1</item>
|
|
<item>60</item>
|
|
<item>65</item>
|
|
<item>75</item>
|
|
<item>85</item>
|
|
<item>145</item>
|
|
<item>255</item>
|
|
</integer-array>
|
|
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
|
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
|
<!-- Operating volatage for bluetooth controller. 0 by default-->
|
|
<integer translatable="false" name="config_bluetooth_operating_voltage_mv">3300</integer>
|
|
<!-- 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_dozeAfterScreenOff">true</bool>
|
|
<!-- 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:2097152,4194304,8388608,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>
|
|
<!-- 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>
|
|
<!-- 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>
|
|
<!-- 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>
|
|
<!-- Flag specifying whether VoLTE is available on device -->
|
|
<bool name="config_device_volte_available">true</bool>
|
|
<!-- Flag specifying whether VoLTE should be available for carrier: independent of
|
|
carrier provisioning. If false: hard disabled. If true: then depends on carrier
|
|
provisioning, availability etc -->
|
|
<bool name="config_carrier_volte_available">true</bool>
|
|
<!-- Flag specifying whether VT should be available for carrier: independent of
|
|
carrier provisioning. If false: hard disabled. If true: then depends on carrier
|
|
provisioning, availability etc -->
|
|
<bool name="config_device_vt_available">true</bool>
|
|
<!-- Flag specifying whether WFC over IMS is available on device -->
|
|
<bool name="config_device_wfc_ims_available">true</bool>
|
|
<!-- ImsService package name to bind to by default. If none is specified in an overlay, an
|
|
empty string is passed in -->
|
|
<string name="config_ims_package">org.codeaurora.ims</string>
|
|
<!-- Flag specifying whether or not IMS will use the dynamic ImsResolver -->
|
|
<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>
|
|
<!-- Whether device supports double tap to wake -->
|
|
<bool name="config_supportDoubleTapWake">true</bool>
|
|
</resources>
|