|
44 | 44 | import com.android.internal.policy.PolicyManager; |
45 | 45 |
|
46 | 46 | /** |
47 | | - * Extend this class to implement a custom Dream (displayed to the user as a "Sleep Mode"). |
| 47 | + * Extend this class to implement a custom dream (available to the user as a "Daydream"). |
48 | 48 | * |
49 | 49 | * <p>Dreams are interactive screensavers launched when a charging device is idle, or docked in a |
50 | 50 | * desk dock. Dreams provide another modality for apps to express themselves, tailored for |
51 | 51 | * an exhibition/lean-back experience.</p> |
52 | 52 | * |
53 | | - * <p>The Dream lifecycle is as follows:</p> |
| 53 | + * <p>The {@code DreamService} lifecycle is as follows:</p> |
54 | 54 | * <ol> |
55 | 55 | * <li>{@link #onAttachedToWindow} |
56 | 56 | * <p>Use this for initial setup, such as calling {@link #setContentView setContentView()}.</li> |
|
59 | 59 | * <li>{@link #onDreamingStopped} |
60 | 60 | * <p>Use this to stop the things you started in {@link #onDreamingStarted}.</li> |
61 | 61 | * <li>{@link #onDetachedFromWindow} |
62 | | - * <p>Use this to dismantle resources your dream set up. For example, detach from handlers |
63 | | - * and listeners.</li> |
| 62 | + * <p>Use this to dismantle resources (for example, detach from handlers |
| 63 | + * and listeners).</li> |
64 | 64 | * </ol> |
65 | 65 | * |
66 | 66 | * <p>In addition, onCreate and onDestroy (from the Service interface) will also be called, but |
67 | 67 | * initialization and teardown should be done by overriding the hooks above.</p> |
68 | 68 | * |
69 | | - * <p>To be available to the system, Dreams should be declared in the manifest as follows:</p> |
| 69 | + * <p>To be available to the system, your {@code DreamService} should be declared in the |
| 70 | + * manifest as follows:</p> |
70 | 71 | * <pre> |
71 | 72 | * <service |
72 | 73 | * android:name=".MyDream" |
|
0 commit comments