Not Get Sms Even When Set The Highest Priority And Installed First
Solution 1:
I have faced the same problem.
As per the documentation by Android, Highest priority must be 1000 http://developer.android.com/reference/android/content/IntentFilter.html#SYSTEM_HIGH_PRIORITY
But this application is using a higher priority evading the guidelines.
http://forum.avast.com/offline/forum.theftaware.com/viewtopic5dcd.html
Don't Be Evil You better follow the guidelines.
Cheers
Solution 2:
As the question you are linking to explains, once the GO SMS app's receiver gets called, they can call abortBroadcast()
. Assuming they are using the highest priority possible (=2147483647), I would assume that the following snippet from the docs would apply:
The order receivers run in can be controlled with the android:priority attribute of the matching intent-filter; receivers with the same priority will be run in an arbitrary order.
However, since they always happen to intercept SMS before your app, I would assume that the magic is somewhere else. Among their permissions, they have the following:
- "android.permission.PERSISTENT_ACTIVITY"
- "android.permission.WRITE_SMS"
- "android.permission.READ_SMS"
Do you mind trying a combination of these, to see if it affects the ordering of intent resolution?
Post a Comment for "Not Get Sms Even When Set The Highest Priority And Installed First"