1

I notice FCM needs an Android wake lock permission. Could I remove the wake lock permission using?

<uses-permission android:name="android.permission.WAKE_LOCK" tools:node="remove" />

or will it disrupt receiving the data/notification payload?

I was reviewing this topic and started wondering if its needed. I remember in GCM its mandatory.

The other question I have is since wake lock is not a dangerous permission, I think on and after API 23, users won't even see or know about this permission as it will be transparent. Even the Play Store will not show them that the app needs a wake lock, is that right?

Community
  • 1
  • 1
j2emanue
  • 60,549
  • 65
  • 286
  • 456

2 Answers2

2

Referring to the GCM docs, the WAKE_LOCK permission seems to have been only optional and not mandatory:

Optionally, the android.permission.WAKE_LOCK permission if the application needs to keep the processor from sleeping when a message is received.

And nothing is stated in the FCM docs that WAKE_LOCK is needed in some way.

And yes, the app will not show that it needs WAKE_LOCK. For permissions with Normal Protection levels (docs):

If an app declares that it needs a normal permission, the system automatically grants the permission to the app.

AL.
  • 36,815
  • 10
  • 142
  • 281
  • ok. and wat about on the google play store ? you know that dialog that usually comes up to show the user what permissions the app is requesting .... if an app needs a normal permission (and its api 23 or up) does it still show in that list ? – j2emanue Mar 01 '17 at 04:00
  • Nope. It's *automatically* granted. :) No point of including it in a prompt for asking permissions when it's already granted. – AL. Mar 01 '17 at 04:04
0

While AL's answer is correct, I would like to add that on the Play Store listing for the app, it shows the permission under the category "Other":

Under Play store permissions

I couldn't add the picture in a comment, so I was forced to create an answer.

Tash Pemhiwa
  • 7,590
  • 4
  • 45
  • 49