I agree with the frustration of having secret undocumented intents. Makes me wonder what else is available and how we would ever know. For example " put "android.provider.Telephony.SMS_RECEIVED"" ? There is not even an android.provider.Telephony" class in the API reference. If Google is going to use text strings for Intents actions, they should be documented. Does anyone have a list of intents actions beyond what the API provides? Ken
On Sunday, February 12, 2012 5:21:47 AM UTC-5, Raffaele Sgarro wrote: > Recently a question on SO ported this to my attention. Android doesn't > have a public API for listening to incoming SMS. There used to be an action > android.provider.Telephony.SMS_RECEIVED, but it has been removed from the > official API and even if it still works, it's obviously not future-proof. I > don't need this feature right now, but I may in the future, and I find it > very strange it's not available because: > > 1. Android has always encouraged the deep customization of every > little part of the system (think of tha launcher, the dialer, the contact > app) > 2. There are plenty of alternatives to the standard SMS app already in > the Market (not to mention the vendors' ones) > > Maybe I am missing something or maybe there's a technical reason - I admit > not know how SMS works > > Originally posted on StackOverflow<http://stackoverflow.com/q/9243059/315306> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
