Unfortunately there is (currently) no way to implement a BroadcastReceiver because the standard sms application uses a SmsManger to send the messages but specifies concrete internal classes for the sent and delivered intents ( SmsReceiver. Class and MessageStatusReceiver. Class respectively).
Not that it is any consolation but you can find the following comment in the Sms application's source.
Unfortunately there is (currently) no way to implement a BroadcastReceiver because the standard sms application uses a SmsManger to send the messages but specifies concrete internal classes for the sent and delivered intents (SmsReceiver. Class and MessageStatusReceiver. Class respectively).
Not that it is any consolation but you can find the following comment in the Sms application's source: // TODO: Fix: It should not be necessary to // specify the class in this intent. Doing that // unnecessarily limits customizability. The best alternative seems to be polling content://sms/sent, potentially using a ContentObserver.
I can currently listen out for messages being sent via a content observer but I would like to stop the sms from being sent over the GSM/CDMA network and sent over a data connection instead. Would you have any insight into how to block an sms from sending over GSM/CDMA? – Donal Rafferty Mar 31 '10 at 11:45 1 No, unfortunately.
But I think blocking the message is going to be even trickier. I'll let you know if I think of something. Meanwhile, try asking a question on stackoverflow.
Com ;-) – Josef Apr 1 '10 at 12:17.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.