Geek Answers Handbook

Why does my BroadcastReceive fail READ_PRIVILEGED_PHONE_STATE on M?

I have a broadcast receiver that is defined as follows:

<receiver android:name="stuff.BroadcastReceiver"> <intent-filter> <action android:name="android.intent.action.PHONE_STATE"/> <action android:name="android.net.conn.CONNECTIVITY_CHANGE" /> <action android:name="android.intent.action.BOOT_COMPLETED"/> </intent-filter> </receiver>

When the application starts on M, even though the application has received permission from the Phone group, I very rarely see this in the logs when there is an incoming call or device is loading.

  W/BroadcastQueue﹕ Permission Denial: receiving Intent { act=android.intent.action.PHONE_STATE flg=0x10 (has extras) } to stuff/stuff.BroadcastReceiver requires android.permission.READ_PRIVILEGED_PHONE_STATE due to sender android (uid 1000) 10-20 12:59:28.014 10946-10946/stuff V/BroadcastReceiver﹕ onReceive()

Although the receiver performs.

+7
android android-6.0-marshmallow android-permissions
source share

No one has answered this question yet.

See related questions:

3295
Why is the Android emulator so slow? How can we speed up Android emulator development?
8
Broadcast Rejection Resolution
8
Android: Incoming call listener without permission
3
BroadcastReceiver and PHONE_STATE not working
2
Android service has stopped working
one
W / BroadcastQueue: Appop Rejection: Broadcast Intent {act = android.intent.action.BOOT_COMPLETED
one
W / BroadcastQueue: permission denied: W / BroadcastQueue: permission denied: intent broadcast {act = com.moca.push.ACTION_PUSH_RECEIVE
0
ITelephony interface method answerRingingCall () does not work
0
Broadcast receiver does not receive intent in Redmi 1s when receiving message
-one
Failure Resolution: Broadcast Intent act = android.provider.Telephony.SMS_RECEIVED

More articles:


All Articles