Start the dream manager even if dreams are not supported.

The dreams manager also manages dozing.  It has a minimal footprint
so there is no real reason to disable the component (it just makes
debugging more difficult).

Improved the documentation of the config_dreamsSupported resource
to clarify exactly what it controls.

Bug: 12494706
Change-Id: I78244846f7c1ddfd11bc1605af59b0db91337971
This commit is contained in:
Jeff Brown
2014-02-24 13:57:53 -08:00
parent 2687550272
commit e0dd3ca81d
2 changed files with 11 additions and 4 deletions

View File

@@ -1077,8 +1077,16 @@
<!-- Name of the wimax state tracker clas -->
<string name="config_wimaxStateTrackerClassname" translatable="false"></string>
<!-- Is the dreams feature supported? -->
<!-- Specifies whether the dreams feature should be supported.
When true, the system will allow the user to configure dreams (screensavers)
to launch when a user activity timeout occurs or the system is told to nap.
When false, the dreams feature will be disabled (this does not affect dozing).
Consider setting this resource to false or disabling dreams by default when a
doze component is specified below since dreaming will supercede dozing and
will prevent the system from entering a low power state until the dream ends. -->
<bool name="config_dreamsSupported">true</bool>
<!-- If supported, are dreams enabled? (by default) -->
<bool name="config_dreamsEnabledByDefault">true</bool>
<!-- If supported and enabled, are dreams activated when docked? (by default) -->

View File

@@ -857,9 +857,8 @@ public final class SystemServer {
}
}
if (!disableNonCoreServices
&& context.getResources().getBoolean(R.bool.config_dreamsSupported)) {
// Dreams (interactive idle-time views, a/k/a screen savers)
if (!disableNonCoreServices) {
// Dreams (interactive idle-time views, a/k/a screen savers, and doze mode)
mSystemServiceManager.startService(DreamManagerService.class);
}