[Q] Weird Phone-Specific Issue with SMS App - Android Software Development

Hey, everyone!
So I am currently writing a small app for my friend which simply parses incoming text messages for a user-defined keyword and if it is present then it automatically sends back a corresponding text message with more information. It will essentially be used to get more information on events that may be going on.
The app works just fine on my phone (Droid X, rooted), however, my friend has the LG Optimus S (Sprint, unrooted) and the application doesn't work. It will receive the message and parse it correctly and it will say that it sent the text message to the right number, however, that message is never sent. Not only that, but once the app tries to send the text he is no longer able to send texts until he reboots his phone. He is able to receive texts fine but he just can't send any.
I tried running the app on another friends phone which is also on Sprint and unrooted and it works fine as well. All of the phones are on Froyo. Does anyone have any suggestions as to what the problem is?
Thanks!

Related

Native Text Message App - Sender Problem

I am coming from owning a Rogers HTC Magic running stock Rogers ROM (1.5) with 911 update.
Just picked up an N1 the other day and although it's a great unit, there are some minor annoyances that are starting to get to me.
One is the native text messaging app. Now, I am a real estate agent so I receive a lot of text messages from my office. With my Magic and any other phone for that matter, these text messages would appear as "7000" as the sender name/number for example as these messages are sent through a computer via the internet. It's very similar when you receive a text from your carrier wherein it's not coming from another phone, and it's typically shown as a number as indicated above.
The problem is that this number no longer appears as the sender name/number. Instead, the sender name/number shows up as the first word in the body of the text. This may seem trivial, however, what happens now is that all the text messages I am receiving from my office are no longer grouped under "7000" for example. Instead, text messages appear as a separate thread (sender).
For example....if my office were to send a fictitious text that reads "this is a test text message", this is how it should and used to look:
7000: this is a test text message
With my N1, this is how it appears now:
this: is a test text message
The only way it will display the proper name/number in the sender field is when the text comes from an actual cell phone.
I have tried another text messaging app like Handcent and the exact same thing happens. Brutal.
http://forum.xda-developers.com/showthread.php?t=629753
Wild shot, have you tried saving a contact with the phone number "7000"?
The first thing I did was try to make a contact with the name "7000" but that didnt work. For some reason the text app does not compute the sender name unless it's an actual phone number or contact.
supergodie thanks for the link....looks like im not the only one...too bad that thread was started back in February and still no fix. Hope it doesnt take too long as I would hate for such a small detail to be a deal breaker for me.
The other annoyance I have is that the native mail app does not have an option for signatures! It also does not allow you to copy text like my Magic did with a long press on the screen and a menu popping up asking to you select text. You would think such "small things" would be an afterthought and not something that should be missed or left out...such basic things...it boggles my mind.
btw supergodie, have you found any workaround for this?
handcent as I have reported does the same thing...I think its because the app works off the native mail app....whatever the case, the problem still exists with handcent.
perhaps another sms app that works?
Sorry, I have not found a solution, I used to it, wait an update by google.

[Q] Can't Send/Receive SMS text messages

I am very new to Android coming from Palm Pre and I purchased Droid Pro and activated it with Page Plus everything seems to work fine except I can't receive or can't send any plain text messages any kind. I haven't been able to receive or send any ever since I got this activated. I have tried everything I could.
I did activation multiple times and still no luck! I am very frustrated at this point and don't know what to do. I really love this phone and it works great including web data, calls but the stupid text messages will not work at all.
As soon as I send a text message I get an instant error message saying text message not sent and it does that for every message. This is just driving me insane since I text more than I talk.
I am getting close to my last resort is the reset this phone to factory which I don't know how to do. My brother uses Droid 2 Global and Fascinate on Page Plus Wireless with no problems. I tried calling multiple sources and no one is willing to help me.
Please help me if you can.
When this happened to me on Verizon, I would have to reboot my phone to get messages to send. I would suggest trying a 3rd party messaging app, such as HandCent, GOSMS or one of the other, reputable ones on the market.
There is a communication error in the Pro with the Verizon servers that will get 'backed up' from time to time and messages will not go through. Motorola is aware of this problem and is supposed to of sent out an update for this to help avoid this problem.
Being on Page Plus, I would hope that it's a similar issue.
Another thing I would suggest is to make sure Wifi is turned off on your phone. The Pro's have a different set of protocols for messaging when Wifi is active.
I hope that this helps you get your phone squared away ^.^

Weird MMS Problem

Initial Notes:
Using a rooted Verizon S5 with stock KitKat ROM (NK2), but this problem also persisted on a rooted Lollipop ROM (OA8).
This problem persists on the stock messaging app as well as all messaging apps I have downloaded from the Play Store so it seems to be an issue with the phone itself. I'm currently using Chomp.
------------------------------------------------------
Problem:
For the longest time, my MMS messages would come and go at what seemed to be the most random times, but I've finally come to notice that the only way I can get an MMS (including group texts) to send or receive is if I send more than 1 at a time.
For example, if I try to send my wife a single pic, it will hang indefinitely, literally for days sometimes. However, if I send another pic to ANYONE (including myself), the pic that was 'stuck' waiting to send to my wife will then finally send.
Also, if I long-press the stuck outgoing MMS, and choose 'resend' it will usually send, but then the recipient also gets 2 copies.
I've also noticed that when the stuck MMS finally does send, I frequently RECEIVE multiple pics or group messages from friends who sent them long ago. It's as if successfully sending an MMS from my phone has somehow unlocked a stuck setting somewhere in the network, which then allows all existing MMS to send/receive.
Also, I've noticed that if I attempt to send 3 pic messages, sometimes only 2 will actually go through. If I want to send the 3rd, I have to generate a 4th pic message also to any recipient. I've gotten to the point where I just decide in order to make MMS work, I have to do one of the following:
- Send 2 pics to the intended recipient
- Send 1 pic to recipient, and then forward that same message to myself.
- Send 1 pic to recipient, and then also forward it to someone else.
So I have come to learn that I do have a work-around of sorts, but it's incredibly inconvenient, and just flat-out weird to me. So it's obvious my MMS can work on this phone, but why do I have to send them in pairs?
Sent from my SM-G900V using XDA Free mobile app

Concatenated SMS

Hello,
I really like my G4 Play (Amazon edition) phone with one exception. I only receive a portion of Concatenated (greater than 160 characters) SMS messages that are sent from T-mobile Iphones to my phone (also on T-mobile). I will get some, but not all. I have used my SIM in other android phones and have another T-mobile SIM in my phone and I get the same issue. From iphones from other carriers I have no problems. From Androids on T-mobile, I also have no problems. I have no problem receiving single SMS messages nor MMS messages. I have contacted T-mobile and they have been no help. I have changed some APN settings, but with no success.
I have also restored my phone to factory settings and have tried Textra also. No changes.
My question: Has anyone had any issues with concatenated SMS messages?
I am thinking about getting a replacement phone, but don't want to if this happens on a replacement phone or if there is a known fix.
Thanks.
What sms did you recieve???
som1096 said:
What sms did you recieve???
Click to expand...
Click to collapse
I appreciate the response, but I'm not sure I understand your question.
I receive properly all SMS that are < 160 characters.
For SMS messages that are > 160 characters:
1) I will sometimes receive these and sometimes not receive these when they are from an iphone on the T-mobile network (I am also on the T-mobile network)
2) I will receive all of the the >160 SMS if:
a) they are on any other network regardless of the type of phone
b) they are on an android and on the T-mobile network​
Did that answer your question?
160+ character text messages are sent as mms. try sending/receiving a picture and see what happens.
hp420 said:
160+ character text messages are sent as mms. try sending/receiving a picture and see what happens.
Click to expand...
Click to collapse
MMS messages work just fine. When my wife puts in a subject field, the long messages are turned into a MMS and always get to me.
For long SMS info see: https://en.wikipedia.org/wiki/Concatenated_SMS
wrusry said:
MMS messages work just fine. When my wife puts in a subject field, the long messages are turned into a MMS and always get to me.
For long SMS info see: https://en.wikipedia.org/wiki/Concatenated_SMS
Click to expand...
Click to collapse
I have worked with T-mobile and Moto with no luck. Moto sent me a new phone (Amazon version of XT1607). I still have the same issue with not receiving long SMS messages (>160 characters) from iphones on T-mobile. These long SMS messages are concatenated SMS messages and are not MMS messages.
I'm sure that there is another Amazon G4 play person who is on Tmobile and has a Tmobile friend who can send them 5 long SMS messages to see how many get through to him/her. Can someone please try this? I have tried other SIM cards in it from my family and the same thing happens. It would be nice to see if someone else has the same issue!
I don't know what I can do but wait for the Nougat release in June. If I had know this would be an issue I wouldn't have bought the Amazon version and I could have installed another ROM.

VZW, can't send text message to one specific number

I switched to Verizon on my OP6T about 2 weeks ago. I've never had this issue before, but it is quite strange. About the device configuration:
Stock Rom
Magisk installed
Using Google Messages, but can re-create the issue in the stock Messaging app
There is one particular person that I cannot seem to send or receive text messages with. Note that initially, after moving to Verizon, I was able to. But then it just stopped working. Whenever I try to send a message, I just get an error message back saying "Not Sent. Tap to try again". Any new messages or retries fail immediately.
This is the only contact I have had issues with, and I can send and receive messages if they are in a group.
I have also tried clearing the cache and data for both Google Messages and the default Message app, as well as removing that message thread.
Any ideas about logs stored somewhere where I could get a better handle on what is causing this issue?
Are they blocking your text messages (in error or on purpose)? I would look there first. If you say no then we can go from there.
Never had this issue with Verizon. I had cricket for a while and both my old phone and the 6t could not send SMS to my brother, I could send mms and call and received everything fine. It was an intermittent issue where I would call support every couple weeks it would be fixed then randomly happen again. This was a contributing factor in my carrier switch lol.

Categories

Resources