1a280b0979
The `config_dozeComponent` property is already [set via
device_phh_treble][1] and all overlays overwriting it just did so with
its default value. As this doesn't add any value, this commit removes
the definition of `config_dozeComponent` from all overlays which set it.
It also removes `config_dozeComponent` from `knownKeys` with the
intention that somebody wanting to overwrite it in future should justify
why it should get added back to `knownKeys` again.
[1]: 04583fa95a/overlay/frameworks/base/core/res/res/values/config.xml (L32)
223 lines
11 KiB
XML
223 lines
11 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.
|
|
*/
|
|
-->
|
|
|
|
<!-- These resources are around just to allow their values to be customized
|
|
for different hardware and product builds. Do not translate.
|
|
|
|
NOTE: The naming convention is "config_camelCaseValue". Some legacy
|
|
entries do not follow the convention, but all new entries should. -->
|
|
|
|
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
|
|
<!-- 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>1</item>
|
|
<item>40</item>
|
|
<item>100</item>
|
|
<item>325</item>
|
|
<item>600</item>
|
|
<item>1250</item>
|
|
<item>2200</item>
|
|
<item>4000</item>
|
|
<item>10000</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>11</item> <!-- 0-1 -->
|
|
<item>22</item> <!-- 1-40 -->
|
|
<item>47</item> <!-- 40-100 -->
|
|
<item>61</item> <!-- 100-325 -->
|
|
<item>84</item> <!-- 325-600 -->
|
|
<item>107</item> <!-- 600-1250 -->
|
|
<item>154</item> <!-- 1250-2200 -->
|
|
<item>212</item> <!-- 2200-4000 -->
|
|
<item>245</item> <!-- 4000-10000 -->
|
|
<item>255</item> <!-- 10000+ -->
|
|
</integer-array>
|
|
|
|
<!-- Minimum screen brightness allowed by the power manager. -->
|
|
<integer name="config_screenBrightnessDim">6</integer>
|
|
|
|
<!-- 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 if current platform supports BLE peripheral mode -->
|
|
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Set this to true to enable the platform's auto-power-save modes like doze and
|
|
app standby. These are not enabled by default because they require a standard
|
|
cloud-to-device messaging service for apps to interact correctly with the modes
|
|
(such as to be able to deliver an instant message to the device even when it is
|
|
dozing). This should be enabled if you have such services and expect apps to
|
|
correctly use them when installed on your device. Otherwise, keep this disabled
|
|
so that applications can still use their own mechanisms. -->
|
|
<bool name="config_enableAutoPowerModes">true</bool>
|
|
|
|
<!-- Maximum number of supported users -->
|
|
<integer name="config_multiuserMaximumUsers">5</integer>
|
|
|
|
<!-- Whether UI for multi user should be shown -->
|
|
<bool name="config_enableMultiUserUI">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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Power Management: Specifies whether to decouple the interactive state of the
|
|
device from the display on/off state.
|
|
When false, setInteractive(..., true) will be called before the display is turned on
|
|
and setInteractive(..., false) will be called after the display is turned off.
|
|
This mode provides best compatibility for devices that expect the interactive
|
|
state to be tied to the display state.
|
|
When true, setInteractive(...) will be called independently of whether the display
|
|
is being turned on or off. This mode enables the power manager to reduce
|
|
clocks and disable the touch controller 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 power.h for details.
|
|
-->
|
|
<bool name="config_powerDecoupleInteractiveModeFromDisplay">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>
|
|
|
|
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
|
|
<bool name="config_intrusiveNotificationLed">true</bool>
|
|
|
|
<!-- 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>"wlan0"</item>
|
|
<item>"softap.*"</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>"bt-pan"</item>
|
|
</string-array>
|
|
|
|
<!-- Array of allowable ConnectivityManager network types for tethering -->
|
|
<!-- Common options are [1, 4] for TYPE_WIFI and TYPE_MOBILE_DUN or
|
|
[0,1,5,7] for TYPE_MOBILE, TYPE_WIFI, TYPE_MOBILE_HIPRI and TYPE_BLUETOOTH -->
|
|
<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 has dual frequency band support -->
|
|
<bool translatable="false" name="config_wifi_dual_band_support">true</bool>
|
|
|
|
<!-- Is the device capable of hot swapping an UICC Card -->
|
|
<bool name="config_hotswapCapable">true</bool>
|
|
|
|
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
|
|
in hardware. -->
|
|
<bool name="config_setColorTransformAccelerated">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 WFC over IMS is available on device -->
|
|
<bool name="config_device_wfc_ims_available">true</bool>
|
|
|
|
<!-- Flag specifying whether WFC over IMS 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_wfc_ims_available">true</bool>
|
|
|
|
<!-- 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 name="config_wifi_background_scan_support">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. -->
|
|
|
|
|
|
</resources>
|