Lines Matching refs:dreams

142 to the full suite of input events. Your dreams run in your app’s process and have full access to
147 android.service.dreams.DreamService}. The {@link android.service.dreams.DreamService} APIs are
150 android.service.dreams.DreamService#setContentView setContentView()} at any point after you have
151 a window, such as from the {@link android.service.dreams.DreamService#onAttachedToWindow()}
154 <p>The {@link android.service.dreams.DreamService} class provides other important lifecycle callback
156 android.service.dreams.DreamService#onDreamingStarted()}, {@link
157 android.service.dreams.DreamService#onDreamingStopped()}, and {@link
158 android.service.dreams.DreamService#onDetachedFromWindow()}.
159 You cannot initiate a {@link android.service.dreams.DreamService} from your
164 android.service.dreams.DreamService#finish()} to end the dream so the user can see the
168 android.service.dreams.DreamService} with a <a
171 "android.service.dreams.DreamService"}. For example:</p>
177         &lt;action android:name="android.service.dreams.DreamService" /&gt;
183 <p>There are some other useful methods in {@link android.service.dreams.DreamService}
187   <li>{@link android.service.dreams.DreamService#setInteractive(boolean)} controls whether
190 {@link android.service.dreams.DreamService#finish()} to stop the dream.</li>
192 android.service.dreams.DreamService#setFullscreen
195 is approaching. Calling {@link android.service.dreams.DreamService#setScreenBright
199 <p>For more information, see the {@link android.service.dreams.DreamService} documentation.</p>