remove doze characteristic
This commit is contained in:
parent
9b37d7deab
commit
c49b8cd845
|
@ -44,79 +44,10 @@
|
||||||
|
|
||||||
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
||||||
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
||||||
|
|
||||||
<!-- ComponentName of a dream to show whenever the system would otherwise have
|
|
||||||
gone to sleep. When the PowerManager is asked to go to sleep, it will instead
|
|
||||||
try to start this dream if possible. The dream should typically call startDozing()
|
|
||||||
to put the display into a low power state and allow the application processor
|
|
||||||
to be suspended. When the dream ends, the system will go to sleep as usual.
|
|
||||||
Specify the component name or an empty string if none.
|
|
||||||
Note that doze dreams are not subject to the same start conditions as ordinary dreams.
|
|
||||||
Doze dreams will run whenever the power manager is in a dozing state. -->
|
|
||||||
<string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
|
|
||||||
|
|
||||||
<!-- 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>
|
|
||||||
<!-- 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">1</integer>-->
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<integer name="config_autoBrightnessLightSensorRate">300</integer>
|
<integer name="config_autoBrightnessLightSensorRate">300</integer>
|
||||||
<bool name="config_automatic_brightness_available">true</bool>
|
<bool name="config_automatic_brightness_available">true</bool>
|
||||||
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>
|
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>
|
||||||
<bool name="config_cellBroadcastAppLinks">true</bool>
|
|
||||||
<bool name="config_device_volte_available">true</bool>
|
<bool name="config_device_volte_available">true</bool>
|
||||||
<bool name="config_device_vt_available">true</bool>
|
<bool name="config_device_vt_available">true</bool>
|
||||||
<bool name="config_device_wfc_ims_available">true</bool>
|
<bool name="config_device_wfc_ims_available">true</bool>
|
||||||
|
|
Loading…
Reference in a new issue