Stop an SMS from being sent from default SMS client.

by Gulfam » Thu, 19 Nov 2009 15:56:34 GMT


Sponsored Links
 Hi All,

 I also want to achieve the same goal as said by Mr Aftab.

The Goal I want to achieve:
(As you have seen many apps in market like "Truephone" those
intercepts outgoing calls and
abortBroadcast(); and take user decision to call via GSM or via their
apps.)

So i want to achieve this goal with "out going sms" as with "out going
calls". I want to take user decision on "out going sms" that he want
to "send sms"  Via operator or via my application.

but I don't know how to achieve it. Any solution or any other way to
achieve it so please let share with us.
I am waiting for your response?????

Thanks in advance.
Gulfam Hassan







--



Other Threads

1. Android cursor lifetime

I have the following piece of code, which is behaving in a very
strange manner.

1. When I run this code, the Cursor always carries 0 rows.
2. I know this sounds stupid, but when I debug the code, it carries
all the rows in my table.
3. Alternatively, when I do not close the database and run through it,
it carries all the rows.

Is this a timing issue of some sort? Has it anything to do with the
cursor's lifetime? Will the cursor be invalid if I close the database
and the openlitehelper? Why in that case do I get valid data if I
debug through the code.

//Open the database
openForRead();

StringBuilder query = new StringBuilder("SELECT ");

//Append the projection columns
SQLiteQueryBuilder.appendColumns(query, projection);

//Force append the _ID column
SQLiteQueryBuilder.appendColumns(query, new String[]{", " +
_IDColumnName + " AS " + BaseColumns._ID});

//From tablename
query.append("FROM " + tableName);

//Query the database and return the cursor
C = database.rawQuery(query.toString(), null);

//Close the database
close();

return C;

-- 

2. App Widget Lifecycle?

Hey guys,

I am bit puzzled by an app widget's lifecyle.

When I create a widget my own configuration activity is launched,
some data is entered, I store this data some place and call finish on
my config activity like this:

Intent resultValue = new Intent();
resultValue.putExtra(AppWidgetManager.EXTRA_APPWIDGET_ID, appWidgetId);
setResult(RESULT_OK, resultValue);
finish();

Now I would expect to see something like that in my log:

I/System.out( 312): onReceive...=android.appwidget.action.APPWIDGET_ENABLED
I/System.out( 312): onReceive...=android.appwidget.action.APPWIDGET_UPDATE

But as a matter of fact those log entries from above are created when
the configuration activity is *started*. Is that right? Am I doing
something wrong here?
Should I invent some artificial limbo/default state for the widget
that can be displayed when it is in its configuration mode?

Cheers,
Mariano

-- 

3. Space internal hh di dream

4. Project idea

5. Port based sms in android

6. How to develop faster without the emulator?

7. BB Gaul-nya Isa