Note that there are some explanatory texts on larger screens.

plurals
  1. POFacebook's "Messenger" has a SMS Broadcast Receiver that takes highest priority after reboot
    primarykey
    data
    text
    <p>Facebook's Messenger, has a priority of <code>2147483647</code>, for their <code>android.provider.Telephony.SMS_RECEIVED</code> broadcast receiver, declared in their manifest. </p> <p>(It's sad we are forced to not follow the documentation's standards of max priority being 1000 because other apps make their own rules)</p> <p>I understand that if my priority is also set to the ridiculously high level of <code>2147483647</code> that I'd have to have my app installed first to take precedence over any "ties". No problem, I made a screen to alert users what apps would probably need to be uninstalled then re-installed after my app to function properly.</p> <p>But, here's the problem - Everything works fine, but as soon as the phone reboots, "Messenger" starts getting precedence over my app. I've looked all over the place to see how they could do this black magic. <strong>How do they do this? How do I get priority after reboot, when my app is installed first?</strong></p> <p>The only thing that has come to mind so far, is package names being ordered alphabetically on boot when registering broadcast receivers.</p> <p>com. <strong>f</strong> acebook > com. <strong>s</strong> trikeforcezero</p> <p>I was about to attempt to register my broadcast receiver on <code>android.intent.action.BOOT_COMPLETED</code> but I have a feeling this won't work.</p> <p>Messenger also has another "low priory broadcast receiver" for <code>android.provider.Telephony.SMS_RECEIVED</code> set to <code>-1</code></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload