Yes, I have that problem with Handcent... :-| But your suggestion won't work because there is no priority anymore in 4.4.. The documenation I found says the following..:
"Note that—beginning with Android 4.4—any attempt by your app to abort the SMS_RECEIVED_ACTION broadcast will be ignored so all apps interested have the chance to receive it." And according to the same documentation, non-default app can not do write operations agains the SMS provider, ala delete, etc... :-| This is starting to remind me of the iOS API, sigh.............. BTJ On Sunday, November 10, 2013 5:28:59 PM UTC+1, Steve Gabrilowitz wrote: > > I totally agree with you on this one but its not for us to say and we > probably can't do anything about it besides trying to devise workarounds. > I don't know about deleting messages from the SMS provider but maybe you > can prevent them from being stored in the first place: give your receiver > a ridiculously high priority to try and get it first in line to get the > broadcast message, then call abort_broadcast() to keep the default SMS app > from ever getting it! Granted this approach won't work with certain SMS > apps such as Handcent but I suspect you already have that issue anyhow! > On Nov 10, 2013 5:55 AM, "BTJ" <[email protected] <javascript:>> wrote: > >> I have several app on Play that is specialized SMS apps, i.e. they use >> SMS services provided by others.. >> Like I have one app that uses the SMS services provided by banks to ask >> for current amount on an account, transfer money between accounts, etc... >> All this is done sending SMS and parsing SMS response... And this app is >> very user friendly and does all the needed SMS handling.. >> But now with the new 4.4 API, the app no longer can operate without >> cluttering up the Inbox and Sent box of the SMS application... >> Why on earth would a user need to save the sent messages for such an >> app?? And also, before I could stop the response from being written to the >> inbox, this is no longer possible.. >> And in the text from Google about this API change it says: "....this will >> create a better user experience...." How on earth is this going to be a >> better user experience for my users!!??? >> Now my users have to manually open the default SMS app and delete all the >> messages that should not have been written to the SMS provider... >> >> Question: Can my app delete messages that have been written to the SMS >> provider without being the default SMS app? >> >> >> Regards, >> >> BTJ >> >> -- >> 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]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
