aboutsummaryrefslogtreecommitdiff
path: root/overlay/frameworks
diff options
context:
space:
mode:
Diffstat (limited to 'overlay/frameworks')
-rw-r--r--overlay/frameworks/base/packages/SystemUI/res/values/config.xml16
1 files changed, 14 insertions, 2 deletions
diff --git a/overlay/frameworks/base/packages/SystemUI/res/values/config.xml b/overlay/frameworks/base/packages/SystemUI/res/values/config.xml
index 0f4f11c..b008822 100644
--- a/overlay/frameworks/base/packages/SystemUI/res/values/config.xml
+++ b/overlay/frameworks/base/packages/SystemUI/res/values/config.xml
@@ -28,11 +28,23 @@
<!-- Should "4G" be shown instead of "LTE" when the network is NETWORK_TYPE_LTE? -->
<bool name="config_show4GForLTE">true</bool>
+ <!-- Doze: should the pickup sensor be used as a pulse signal? -->
+ <bool name="doze_pulse_on_pick_up">true</bool>
+
<!-- Doze: does this device support STATE_DOZE and STATE_DOZE_SUSPEND? -->
<bool name="doze_display_state_supported">true</bool>
- <!-- Doze: should notifications be used as a pulse signal? -->
- <bool name="doze_pulse_on_notifications">false</bool>
+ <!-- Doze: when to pulse after a buzzworthy notification arrives -->
+ <string name="doze_pulse_schedule" translatable="false">10s,30s,60s,180s</string>
+
+ <!-- Doze: check proximity sensor before pulsing from intent? -->
+ <bool name="doze_proximity_check_before_pulse_intent">true</bool>
+
+ <!-- Doze: pulse parameter - how long does it take to fade in after an intent? -->
+ <integer name="doze_pulse_duration_in_intent">0</integer>
+
+ <!-- Doze: pulse parameter - delay to wait for the screen to wake up after an intent -->
+ <integer name="doze_pulse_delay_in_intent">0</integer>
</resources>