> I think you may have missed my point. Let's say I want to create a new > SMS app that has this obfuscating feature. But I don't really want to > invent the wheel since there are so many good SMS apps already out > there. Is there a way for an app to catch the event that indicates the > message is going out so that it can tap into it?
Look at the SMS_RECEIVED intent and sample code scattered about on stack overflow. Create a broadcast receiver, give it a priority higher than the built in app, catch the broadcast about the SMS, either muddle with its data elements and let it go, or do all your obfuscating and stick it in the SMS inbox through the content provider and don't let anybody else see it. The content provider is probably easier to mess with but has the downside of being a content provider, which means it's not required to work (or even be implemented by an OEM, despite being in the AOSP) to pass the android certification process. -- 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
