Lines Matching full:your
33 <p>The approach you take depends on the needs of your app. However, a general rule of thumb
34 is that you should use the most lightweight approach possible for your app, to minimize your
36 where the device's default sleep behavior is incompatible with the requirements of your app.</p>
43 in your activity (and only in an activity, never in a service or
56 manages the user moving between applications, without your app needing to worry about
59 <p>Another way to implement this is in your application's layout XML file, by using the
71 You can use whichever approach is best for your app. The advantage of setting the flag
72 programmatically in your activity is that it gives you the option of programmatically
78 stay on in your running application (for example, if you want the screen to time out
93 <li>If your app is performing long-running HTTP downloads, consider using
96 <li>If your app is synchronizing data from an external server, consider creating a
100 <li>If your app relies on background services, consider using
112 wake locks. Wake locks allow your application to control the power state of the host device.</p>
118 to keep the screen on in your activity, use
127 permission to your application's manifest file:</p>
131 <p>If your app includes a broadcast receiver that uses a service to do some
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
145 {@link android.os.PowerManager.WakeLock#release wakelock.release()}. This releases your
146 claim to the CPU. It's important to release a wake lock as soon as your app is finished
157 {@link android.os.PowerManager#PARTIAL_WAKE_LOCK} for your app. A
168 {@link android.support.v4.content.WakefulBroadcastReceiver} is to add it to your
210 // Do the work that requires your app to keep the CPU running.
