aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordavidevinavil <davidevinavil@gmail.com>2017-01-13 02:13:58 +0100
committerdavidevinavil <davidevinavil@gmail.com>2017-01-14 15:53:24 +0100
commitf0eafbab5cb9a6da0be43bd07e0f5a3ab9850d30 (patch)
tree61c7f8cb5463445091b47e7e4fe71ca0b39d37b6
parent02c461848ab1be4cd1439953c13850a76d60df98 (diff)
z2_plus: Delete overlay for button backlight
Change-Id: If5b75812f16b95714ca3c0a1f31533ddb3dabe37
-rw-r--r--overlay/frameworks/base/core/res/res/values/config.xml13
1 files changed, 0 insertions, 13 deletions
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index abb2ea8..5f1af24 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -66,14 +66,6 @@
<item>255</item>
</integer-array>
- <!-- Array of output values for button 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_autoBrightnessButtonBacklightValues">
- </integer-array>
-
<!-- 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. -->
@@ -196,7 +188,6 @@
should be empty. An example would be "softap.*" -->
<string-array translatable="false" name="config_tether_wifi_regexs">
<item>"wlan0"</item>
- <item>"wigig0"</item>
</string-array>
<!-- List of regexpressions describing the interface (if any) that represent tetherable
@@ -390,19 +381,15 @@
<!-- 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>