aboutsummaryrefslogtreecommitdiff
path: root/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
diff options
context:
space:
mode:
Diffstat (limited to 'rro_overlays/FrameworksResOverlayVeux/res/values/config.xml')
-rw-r--r--rro_overlays/FrameworksResOverlayVeux/res/values/config.xml16
1 files changed, 16 insertions, 0 deletions
diff --git a/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml b/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
index 2f92c89..a805d18 100644
--- a/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
+++ b/rro_overlays/FrameworksResOverlayVeux/res/values/config.xml
@@ -553,6 +553,22 @@
turned off and the screen off animation has been performed. -->
<bool name="config_dozeAfterScreenOffByDefault">true</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>
+
<!-- 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