GoSMS has the SMS_RECEIVED priority set to 2147483647. Android docs state that it should be less than 1000 (http://developer.android.com/ reference/android/content/IntentFilter.html#SYSTEM_HIGH_PRIORITY). Priorities set too high will have unpredictable results, just as apps with the same priority level will execute in an arbitrary order (the Stackoverflow thread says that it is in installation order, and even though that seems to be the usual order, I have seen it execute in what seems to be random order).
GoSMS has this wrong (and many other apps) and it interferes with other apps, as indicated in your logcat. -Jim On Jul 12, 5:26 am, Mark Murphy <[email protected]> wrote: > On Mon, Jul 11, 2011 at 11:08 PM, rich friedel <[email protected]> wrote: > > Yeah... Go SMS Pro really screws with things... the only thing I can figure > > is they are absorbing the incoming broadcast and somehow not letting it > > through so that other receivers can do what they need to do. > > The OP had originally posted on StackOverflow -- here's the analysis: > > http://stackoverflow.com/questions/6600266/suppress-block-broastrecei... > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Warescription: Three Android Books, Plus Updates, One Low Price! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
