When and why is PARTIAL_WAKE_LOCK required?

All other trace locks make sense, for example. the developer wants the screen to not disappear when doing something. But in the partial blocking of the trace, the documentation says that:

If you perform partial tracking locks, the processor will continue to run, regardless of the display timeouts or screen status, and even after the user presses the power button. In all other tracking locks, the CPU will start, but the user can still turn off the device using the power button.

Does this mean that during some operations the CPU may disappear? Do I need to set a tracking lock on a service?

+4
source share
1 answer

Does this mean that during some operations the CPU may disappear? Do I need to set a tracking lock on a service?

(and here - for the power off button)! Everything is more complicated if you try to start the service while the device is sleeping. Most likely, you will not do it. Take a look at the Commonsware WakefulIntentService - it is suggested that with the emergency manager receiver (which contains the lock after waking up) you should get a (static) wakelock while still in onReceive()order not to sleep.

+1
source

All Articles