| /frameworks/base/docs/html/training/scheduling/ |
| D | wakelock.jd | 30 However, there are times when an application needs to wake up the screen or the CPU
54 <p>The advantage of this approach is that unlike wake locks (discussed in <a href="#cpu">
89 <h2>Alternatives to using wake locks</h2>
112 wake locks. Wake locks allow your application to control the power state of the host device.</p>
114 <p>Creating and holding wake locks can have a dramatic impact on the host device's battery
115 life. Thus you should use wake locks only when strictly necessary
117 wake lock in an activity. As described above, if you want
122 <p>One legitimate case for using a wake lock might be a background service
123 that needs to grab a wake lock to keep the CPU running to do work while the screen is off.
126 <p>To use a wake lock, the first step is to add the {@link android.Manifest.permission#WAKE_LOCK}
[all …]
|
| D | alarms.jd | 78 <li>Don't wake up the device unnecessarily (this behavior is determined by the alarm type,
110 <p>Both types have a "wakeup" version, which says to wake up the device's CPU if the
129 on the amount of time since the device was booted, but doesn't wake up the device. The
137 at the specified time but does not wake up the device.</li>
|
| /frameworks/base/core/jni/ |
| D | android_os_MessageQueue.cpp | 42 void wake();
106 void NativeMessageQueue::wake() { in wake() function in android::NativeMessageQueue
107 mLooper->wake(); in wake()
141 return nativeMessageQueue->wake(); in android_os_MessageQueue_nativeWake()
|
| /frameworks/native/libs/gui/ |
| D | SensorEventQueue.cpp | 114 status_t SensorEventQueue::wake() const in wake() function in android::SensorEventQueue
117 looper->wake(); in wake()
|
| /frameworks/native/include/gui/ |
| D | SensorEventQueue.h | 67 status_t wake() const;
|
| /frameworks/base/native/android/ |
| D | looper.cpp | 67 static_cast<Looper*>(looper)->wake(); in ALooper_wake()
|
| /frameworks/base/services/input/ |
| D | EventHub.h | 251 virtual void wake() = 0;
313 virtual void wake();
|
| D | InputDispatcher.cpp | 2343 mLooper->wake(); in notifyConfigurationChanged()
2421 mLooper->wake(); in notifyKey()
2498 mLooper->wake(); in notifyMotion()
2535 mLooper->wake(); in notifyDeviceReset()
2655 mLooper->wake(); in injectInputEvent()
2885 mLooper->wake(); in setInputWindows()
2916 mLooper->wake(); in setFocusedApplication()
2951 mLooper->wake(); in setInputDispatchMode()
2972 mLooper->wake(); in setInputFilterEnabled()
3049 mLooper->wake(); in transferTouchFocus()
[all …]
|
| D | EventHub.cpp | 951 void EventHub::wake() { in wake() function in android::EventHub
|
| D | InputReader.cpp | 554 mEventHub->wake(); in requestTimeoutAtTimeLocked()
671 mEventHub->wake(); in requestRefreshConfiguration()
765 mEventHub->wake(); in monitor()
|
| /frameworks/base/docs/html/training/monitoring-device-state/ |
| D | manifest-receivers.jd | 35 <p>A side-effect of this approach is that your app will wake the device each time any of these
|
| /frameworks/base/services/java/com/android/server/ |
| D | EventLogTags.logtags | 29 # This is logged when the partial wake lock (keeping the device awake
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | mediaplayer.jd | 23 <li><a href="#wakelocks">Using wake locks</a></li>
344 <h3 id="wakelocks">Using wake locks</h3>
356 those conditions, you have to use "wake locks." A wake lock is a way to signal to
360 <p class="caution"><strong>Notice:</strong> You should always use wake locks sparingly and hold them
376 <p>However, the wake lock acquired in this example guarantees only that the CPU remains awake. If
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.0.jd | 320 …wake up the screen when it is displayed and show the window even if the screen is locked. This all…
|
| D | android-2.3.jd | 478 requests that result in wake locks or wifi locks according to
486 wake and wifi locks initiated by an application and adds it to the application's
|
| D | android-4.4.jd | 477 …wake the CPU to deliver your app the batched events. When the sensor eventually runs out of its me…
|
| /frameworks/base/docs/html/tools/help/ |
| D | MonkeyDevice.jd | 375 <a href="#touch">wake</a>
1147 <A NAME="wake"></A>
1153 <span class="sympad">wake</span>
|
| /frameworks/base/docs/html/training/basics/network-ops/ |
| D | managing.jd | 402 {@code <receiver>} in the manifest, it can wake up your app at any time,
|
| /frameworks/base/docs/html/guide/topics/appwidgets/ |
| D | index.jd | 227 wake up in order
234 perform updates based on an alarm that will not wake the device. To do
|
| /frameworks/base/docs/html/google/gcm/ |
| D | gcm.jd | 80 messages. The system will wake up the Android application via Intent broadcast when the message ar…
|
| /frameworks/base/docs/html/tools/help/uiautomator/ |
| D | UiDevice.jd | 3183 to allow the device time to wake up and accept input.</p></div>
|
| /frameworks/base/services/input/tests/ |
| D | InputReader_test.cpp | 700 virtual void wake() { in wake() function in android::FakeEventHub
|