| || |
Re: Application permissions
Apps that use the WAKE_LOCK permission don't necessarily drain the battery, but apps that misuse it will. Certain apps require this permission to operate properly. For instance the music app I'm beta testing now requires it to ensure the app can continue to playback music without interruption. So while music is playing, it uses a "partial wake lock" which allows the CPU to keep running even if the device's display is powered off. Otherwise, music would stop playing once the device went to sleep.
Apps that use WAKE_LOCK need to be very careful to only acquire a wake lock for the shortest amount of time necessary and to release it immediately when it's no longer required. Also they should use partial wake locks instead of full wake locks if possible.
So basically if you're using an app that would have a legitimate reason to run in the background (like a music app), you shouldn't be worried about the WAKE_LOCK permission (assuming the developer is using it properly). But if an app doesn't seem like it has a legitimate reason to use it, it may be a good idea to not use the app, or at least ask the developer why they're using that permission.
When I release my app in the Play Store I plan on having a section at the bottom of the app description describing what each permission is used for. I really wish Google would have a built-in way for developers to add notes to each requested permission. I get nervous when I see an app asking for a weird permission (like sending SMS's, etc.), so it would be nice if developers specified why they needed the permission.