I need to send a text message to everyone on a phone. I have developed an Android application that sends a SMS to contacts, but I'm not sure how to do it for all contacts, especially since the phone I have to do it with doesn't have any mobile plan. Should I develop an Android application, or is there a better way of doing this? I have also tried putting all of the contacts in a group, but I can only send a message to ten people. Thanks for the help.
Related
I am trying to do Mobile Number Verification just like WhatsApp in my Android App. I'm able to send SMS from my Android app.
But I want to achieve these 2 things:
The Sender name in the receiver's Inbox should be a Custom Name decided by my App, like SMS from WhatsApp has sender name somewhat like WTAPP-5550. Currently its showing my Mobile Number.
Making sure that the SMS sent from User's phone doesn't show up in User's Sent Box. Currently SMS appears both as SENT and RECIEVED SMS. Like in d case of WhatsApp , no SENT Message is present only Recieved SMS is.
Thanks and Regards,
Rahul Soni
See Mr Rahul From your question what I understood is you are sending the sms to the mobile number through your app. That is not a good way to verify the mobile number. What you have to do is you have to send sms through the server. Whats app people will connect to their server and from server they will send sms to the entered mobile number. Thats why it will not appear in the sent box. And to set custom name to the sender number you have to use third party sms services.
I am developing chat application using xmpp smack my problem is how to send phone contact information to another users.I am struct here can any body help me.
you can just send a message stanza containing that contact info. AFAIK there is not any particular XEP present for contact sharing.
A phone contact specification is not currently available in XMPP. Your best bet would be to send the phone contact information in a standard message.
Consider putting some special tokens in place if you want to process these information in a different way than a standard message.
Is it possible to send SMS
confirmation (or any other content)
in your application other than by the
SMS gateway? I mean here to send
mass quantities of messages, and
the purchase of this package is
quite expensive. I know that Viber
uses something like that, and I
would like to implement it at home,
but I do not know if it's possible to
do without large costs. Talking
about Android. Please explain.
I was facing same problem. I am using an android app ezSMSgateway(www.ezsmsgateway.com/). it can change your android phone into a sms gateway, so the cost will be cheaper, but you still need to pay your sms fee to telco.
I can't think out a way to sent SMS without any cost yet...
Hi I am developing an android SMS app where I am fetching the SMS stored in the phone and displaying it on a list view. How can I update a SMS as read in the phone, upon reading an SMS in my app.
I refered the following link,
Android: how to mark sms as read in onReceive
This did not work. What can i use instead of this.
Please suggest. Thanks!
How can I update a SMS as read in the phone, upon reading an SMS in my app.
You can't, reliably. There are hundreds, perhaps thousands, of SMS clients on the Play Store. None of them have to expose some sort of API to allow third parties to somehow mark SMS messages as "read".
I built a messaging app that allows users to send and receive sms messages along with other types of messages. Right now I am storing all of the sent and received messages in Android's default databases that hold all sms messages. (content://sms/inbox and content://sms/sent) Is there any reason why this would be a bad idea? I know I could use my own database but unless there is a reason I should I like the simplicity of using the database that already exists on the users phone.
Also will all android devices from all manufacturers have their sms databases in the same place that I will be able to access or will their be issues across different devices and manufacturers?
It is perfectly ok to use existing databases. This is the way many existing messaging apps work.
I can't answer for all users, but I imagine a significant number of them (myself included) would object to having non-SMS messages stored in the same database as SMS messages.
If I used your app, and then opened up the stock SMS app and saw non-SMS messages there, I'd go on a rampage.