Lines Matching refs:wake

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}
132 work, you can manage your wake lock through a
135 If your app doesn't follow that pattern, here is how you set a wake lock
144 <p>To release the wake lock, call
146 claim to the CPU. It's important to release a wake lock as soon as your app is finished
162 go back to sleep in the transition. If you don't hold a wake lock while transitioning
177 wake lock when the service starts. The intent that is passed with
179 holds an extra identifying the wake lock:</p>
195 to release the wake lock. The
212         // Release the wake lock provided by the WakefulBroadcastReceiver.