Develop Reference

Prevent sms show after sms sending

I'm developing a business application. When user register in app, app will send his coordinates by using active internet connection. But if connection is not avaliable coordinates will be sended by sms.
Using SmsManager in app to send sms:
sendSMSButton.Click += (s, e) =>
{
var phone = "999999";
var message = UserLocation;
var piSent = PendingIntent.GetBroadcast(this, 0, new Intent("SMS_SENT"), 0);
var piDelivered = PendingIntent.GetBroadcast(this, 0, new Intent("SMS_DELIVERED"), 0);
_smsManager.SendTextMessage(phone, null, message, piSent, piDelivered);
};
My problem is that the message that was sent is displayed in user's phone, and he can see coordinates and phone number. So he can edit this data and send again.
How I can prevent showing messages that was sent by smsmanager in outgoing sms of user's phone ?

Doesn't seem like you can, sendTextMessageWithoutPersisting has only been added in API 28 and is intended for internal carrier use only. You won't be able to use it since this method requires the Manifest.permission.MODIFY_PHONE_STATE permission. You can read more here in the docs.

Push messages to send data?

my app need's to send data to another android device so far its sending it through sms messages that gets blocked in the other android device ... but since the kitkat version i cant block them anymore.. is there anyway of sending push messages in the background to another user and receiving them back ? and if so... I would love to see any example ( I don't prefer GCM i think its way too complicated.. ) .
this is the code i am using to send the SMS message :
SmsManager sm = SmsManager.getDefault();
ArrayList<String> parts =sm.divideMessage(String.valueOf(points));
int numParts = parts.size();
ArrayList<PendingIntent> sentIntents = new ArrayList<PendingIntent>();
ArrayList<PendingIntent> deliveryIntents = new ArrayList<PendingIntent>();
for (int i = 0; i < numParts; i++) {
sentIntents.add(PendingIntent.getBroadcast(getBaseContext(), 0, getIntent(), 0));
// deliveryIntents.add(PendingIntent.getBroadcast(getBaseContext(), 0, data, 0));
}
sm.sendMultipartTextMessage(number,null, parts, sentIntents, deliveryIntents);
SmsManager.getDefault().sendTextMessage(number, null, String.valueOf(points), null, null);
}
Looking for something similar just for the push messages.

You could send a data SMS. They operate differently than a regular SMS because they use a port upon sending, and so you specify that same port on the receivers handset. This avoids the problem of competing intent filter priority on the SMS receiver.
This allows direct sending from one android to another.
See here for an example

Google Cloud Messaging is what your are after:
http://developer.android.com/google/gcm/index.html
One disadvantage over your current method is that you will probably need a server to act as a broker, as a GCM message can only have a relatively small payload

SMS sending to multiple numbers not being sent

I am sending an SMS to multiple numbers. When I choose only one, it works, and the message is being sent immediately. But when I use multiple (3 for example) SMS Intent is opened, but after I click Send button I see "Sending..." message all the time, SMS is not sent.
Intent sms = new Intent(Intent.ACTION_VIEW);
sms.setType("vnd.android-dir/mms-sms");
sms.putExtra("address", getSMSNumbers);
sms.putExtra("sms_body", "Help!!!");
startActivity(sms);
And getSMSNumbers String looks like this: 512991220;505202222;606123456.
What is wrong? Why isn't the message being sent and it's "sending" all the time?
Also I see when I have more than 1 number, it's being converted to MMS - why?

Maybe you could loop through the numbers and send messages one by one, like this
android.telephony.SmsManager.getDefault().
sendTextMessage("00112233", null, "Message body text", null, null);

I managed to do this - needed to turn off "Group Messaging" in AVD Settings. App was trying to send MMS and that's why it wasn't being sent.

Sending long (concatenated) SMS in Japan

Is there anyone from Japan ? I have a question about Japan mobile network operators (Docomo, AU) and their phones: are they able to send/receive a long SMS (longer than 160 latin characters / 70 japanese characters)? or they are splitting the SMS in two fragments sent separately?
In my app, I want to send a long SMS using SMSManager's sendMultiPartTextMessage and I want to know if I can use it or send multiple SMS fragments using just sendTextMessage.
Thank you!

As per documentation, that's how you can send multi-parts message:
final String phoneNumber = "1111111111";
final String message = "this is text body for multi part sms...bla bla bla...";
SmsManager sms = SmsManager.getDefault();
ArrayList<String> parts = sms.divideMessage(message);
sms.sendMultipartTextMessage(phoneNumber, null, parts, null, null);

Unable to send text messages on some Android Phones using SmsManager

My mobile app occasionally is sending text messages, everything works great on most phones but i am starting to receive emails from some users stating the messages aren't going out. Here is the code i am using:
SmsManager sms = SmsManager.getDefault();
sms.sendTextMessage("+12223334444", null, "test sms", null, null);
I've read somewhere that I should use the PendingIntent, so i tried it as follows:
PendingIntent sentPI = PendingIntent.getBroadcast(context, 0, new Intent("SMS_SENT"), 0);
PendingIntent deliveredPI = PendingIntent.getBroadcast(context, 0, new Intent("SMS_DELIVERED"), 0);
SmsManager sm = SmsManager.getDefault();
sm.sendTextMessage(number, null, message, sentPI, deliveredPI);
So far I have gotten emails from users of Samsung Galaxy S II, Sprint Evo Shift, Samsung Sidekick phones.
Please keep in mind it's not phone specific, i have tested the app on two of these phones (my friends) and the text message was sent normally

The problem here is that you aren't handling retries at all. It is possible for the SMS to fail to send in a variety of colourful ways. You can listen for these events using the sent PendingIntent using something like:
public void onReceive(Context context, Intent intent) {
if (getResultCode() != Activity.RESULT_OK) {
// failed to send the sms, see SmsManager.ERROR_<description> for more info on why
}
}
What I suspect is happening is that users have no signal at the time you send the message, so it fails and never retries. This would also explain why it isn't device specific.