Related
Sometimes at random the phone will stop allowing texts to be sent, on various contacts.
I think this isn't a problem with the phone but the Android software, i have signal and its connected to 3G, sometimes HSPA. However will repeatedly not send a text.
If i just reboot the phone it'll work fine. However can get this problem later on again. Its as if the software cant handle sending a certain amount of texts per 10 minutes or something?
Anyone else had this problem.
Rooted & CM Beta5, however done it OTB.
I've never had a problem sending or receiving txt.
I'm on stock rom though
I'm on the stock rom aswell and i've been having that problem lately too, i was hoping i wasnt the only one.
Seems a problem http://androidcommunity.com/forums/f10/text-messages-not-sending-4534/
I'd like to second this. I was trying to send a bunch of messages the other night and had to keep rebooting my N1 to get them to start sending again. Then it would stop sending, and I'd reboot again... worrying. I was using Handcent though.
I use the standard SMS application.
Stock ROM. Only fix is a reboot for me.
Same with me. Happens every once in awhile. Reboot is the only thing that fixes the problem for me. It has not happened since I rooted my phone and flashed cyanogen's rom
Fuse8499 said:
Same with me. Happens every once in awhile. Reboot is the only thing that fixes the problem for me. It has not happened since I rooted my phone and flashed cyanogen's rom
Click to expand...
Click to collapse
1 time, i gaveup and couldnt be bothered to reboot the phone. Went to sleep, wokeup an tried in the morning an it worked fine.
Maybe a buffer issue or something like its full due to sending a high ammount of messages very quickly?
Happened to me twice on CM 5.0.2.
TFJ4 said:
Happened to me twice on CM 5.0.2.
Click to expand...
Click to collapse
Ive had it over a dozen times, hence the thread
Ok,
So ive got the problem again! has occured at 2pm GMT. Have 4bars H signal.
Not going to reboot the phone just wait see how long it takes.
Surely more people are having this problem?
I'm using Enoms TheOfficial and I haven't ever had a problem. I text more than anybody I know too. [3k per month]
Maybe your local network or something. I'm in Dallas, Texas
~shrug~
dumbestcrayon said:
I'm using Enoms TheOfficial and I haven't ever had a problem. I text more than anybody I know too. [3k per month]
Maybe your local network or something. I'm in Dallas, Texas
~shrug~
Click to expand...
Click to collapse
It did it on STOCK Rom and Cyanogens Rom too. I send maybe the same ammount too!
Not the network as here in UK i am T-Mobile and other people on T-Mobile can text me when there stood 1ft away. My mates works and he has a Nexus on T-Mobile too.
We both own Sim-Free mobiles bought direct from Google and Delivered at the same time.
I say handcent is the problem
It's not handcent as it's happening with the stock messaging app also.
I also have the problem, usually around the same time, but i send anywhere from 7k to 10k a month... maybe tmobile is trying to limit my data?!?!
jn_vista said:
I also have the problem, usually around the same time, but i send anywhere from 7k to 10k a month... maybe tmobile is trying to limit my data?!?!
Click to expand...
Click to collapse
Mine still does it purhaps few times a week.
use a task killer (lately i have been favoring task panel), then restart your messaging app. you don't have to reboot.
I had an old sim card and had the same problem and got a replacement from tmobile and everything is fine now.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Is anyone having an issue where if they reply to someones text, the reply is listed chronologically before the previous message? I'm wondering if somehow the timestamps are getting messed up on my phone. It only happens sometimes, usually if I reply within 5-10 seconds.
Sent from my SPH-D700 using XDA App
I'm still experiencing this problem. Anyone else? </shameless_bump>
yes, here too, I see this today on 2 times, how can I fix this?!? please help!!!
It has happened to me also, however i noticed it is only with the default messaging app, so i use Handscent instead
this really annoys me
This has been happening to me ever since I had my Evo. I thought it would stop on the Epic, but it continues to happen. The only time I saw this problem dissipate was when I flashed a custom ROM to my evo. And it had the Stock SMS application on there.
Sprint really needs to fix this.
my theory is that if you reply to a message before the message registers as being "read," then the message will stay "unread" and remain the latest message while your response will go into the main list of messages.
if someone could edit how "unread" messages are checked and changed to "read," then this may solve our issue.
it only seems to happen to me when i reply within the same minute. if i get a text at 1:21 and reply at 1:22, im fine. if i get a text at 1:21 and reply and send it in the same minute, it seems to put my reply before their initial text. i dont think its reading the seconds on the time stamp.
Same here.
I can confirm that this happens on three epics
Sent from my SPH-D700 using Tapatalk
I went through 3 epics before i got one that is good for me, and let me tell you ALL of them had this issue.
I was having this issue... then I noticed it only happened while roaming.
I believe it may have to do with the sms time zone not being correctly handled by the roaming network.
i get perfect bars at my house (no roaming) and it happens to me there. i dont think it has to do with roaming.
I think the issue lies when texts are sent and received at the same minute, perhaps its not recording the seconds which is placing them out of order? It happenes to me when my friend with an epic sends me multiple texts in a row and it also happens to his phone as well.
Sent from my SPH-D700 using Tapatalk
It happens to me too. I was texting someone around 1pm today and the time stamp said 7:23 pm. I noticed it happened more frequently when I allowed my phone to roam too
Sent from my #epicwin using magic
bump..no fix for this?
Happens to me too. It use to happen on my BB too so i don't necessarily think it's the phone.
Hello to everyone!
I've been recently having some troubles with my evo 4g. I'm running fresh 3.5.0.1 and just updated my radios to 1.90_003 . Right before i upgraded (from fresh 3.4 or 3.3 not sure) I started to have problems with my text messages.
First i noticed that i got one from "the future" it was timestamped about 2 hours ahead of what time it was and i didn't recieve a notification for it. So i checked for some updates since it had been a while and upgraded everything i was suppose to (ota,radio,wimax,pri,etc). Now my messages seem to have the same problem if not more. I get alerted 5 or 10 minutes after i receive the message, while going through my conversations say i select a convo with my friend zack and convo from my friend kyle will come up, and i will have to go back and select it again.
So i'm wondering if this is a service provider problem or something with the apps for custom firmware i'm using. Could it be caused by an app like JuiceDefender?
The timestamp issue usually only happens when roaming, but can also be caused by network issues in general. My old flip phone, rumor, and instinct all had that issue from time to time.
The other issue with opening one text and getting someone else is an android issue, engadget reported on that today actually.
http://tinyurl.com/2eccmhw
Sent from my PC36100 using XDA App
Yeah I have been having time stamp issues also. And when someone replies, it puts them all above my txts sent that day, so I gotta constantly scroll up to read txts.
Anyone got any idea's on fixing this?
oOflyeyesOo said:
Yeah I have been having time stamp issues also. And when someone replies, it puts them all above my txts sent that day, so I gotta constantly scroll up to read txts.
Anyone got any idea's on fixing this?
Click to expand...
Click to collapse
^^That happens to me too^^ I thought my phone was just fcukin up. It does it when someone sends me a pic. Puts it at the top of the convo's for that day...
I got a "VERY" important text 20 mins late the other day too. 20 mins too late!!! Pissed me off!!!!
good to know that i'm not the only one experiencing this problem hopefully gets fixed soon. if i had to guess i think it's most likely a problem/conflict with sprint and android.
I searched the forums to see if anyone else noticed these issues. First I upgraded via the exe file from samsung and I even did a wipe of my sd card after backing it up...
I am on stock eb13 and not rooted..
My issue is this, sometimes when trying to send text messages they get stuck with sending and don't actually send... I am kinda assuming this is happening after receiving a picture or sending a picture, but I am not sure on this because I can't make it produce this problem on a constant basis.. the only thing that seems to fix this is rebooting the phone.. then the text messages that all had sending on them will send all at once..
Second issue is today I wanted to send a funny animated picture text I received to mutiple people and while typing the peoples names in I would get multiple force closes.. the only way it seemed to work was using the contacts then choosing the names that way... I didnt fully test this to see if that was the work around and was curious if anyone else were getting forces closes...
Overall my experience with the stock sms app has been very annoying. D118 worked far better for me in the sms category..
Thanks in advance for any help in this matter....
Sent from my SPH-D700 using Tapatalk
Regarding the stuck on Sending... this is a problem with 2.2 and there is no fix yet. It has been present since DK28 but is completely random on when it occurs; sometimes you go a month+ before it happens, other times hours.
When it happens, go to settings/applications/manage/running and FC the messaging app. When you reopen it, it should send. Only other option is reboot and it will send.
vooman said:
I searched the forums to see if anyone else noticed these issues. First I upgraded via the exe file from samsung and I even did a wipe of my sd card after backing it up...
I am on stock eb13 and not rooted..
My issue is this, sometimes when trying to send text messages they get stuck with sending and don't actually send... I am kinda assuming this is happening after receiving a picture or sending a picture, but I am not sure on this because I can't make it produce this problem on a constant basis.. the only thing that seems to fix this is rebooting the phone.. then the text messages that all had sending on them will send all at once..
Second issue is today I wanted to send a funny animated picture text I received to mutiple people and while typing the peoples names in I would get multiple force closes.. the only way it seemed to work was using the contacts then choosing the names that way... I didnt fully test this to see if that was the work around and was curious if anyone else were getting forces closes...
Overall my experience with the stock sms app has been very annoying. D118 worked far better for me in the sms category..
Thanks in advance for any help in this matter....
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
My Evo is known for getting stuck receiving the SMS messages. Never have been able to figure it out. very frustrating indeed so i feel your pain
Thanks for the replies.. much appreciated..
Sent from my SPH-D700 using Tapatalk
To tell you the truth I don't think I've ever ran into this problem myself...the only way I'm stuck on sending is if in a bad service area which is common, did you try to a hard reset possibly? I'm not much help on android development, but starting from scratch may help?
Sent from my SPH-D700 using XDA App
I have seen issues like this with sprint in general, not just on my Epic. Sometimes texts just won't send. Other times you get like 4 or 5 texts that get delivered late.
I know that your issue is probably software related though. I really don't like the 2.2 messaging app. The one on 2.1 worked great
I've also had this issue, back to when I had the Moment. Same fix for me, reboots and whatever I thought was already sent, finally sends. At least I have an excuse for when my gf wonders why I haven't responded to her texts lol
I've only had this problem since getting EB13. I've found that if you go into RAM manager via task manager and do a level 2 memory clear, it shuts down a critical SMS process and the phone will refuse to send any SMS until the the phone is rebooted.
By chance have you been clearing memory in RAM manager on the new EB13?
Atlienzz said:
I've only had this problem since getting EB13. I've found that if you go into RAM manager via task manager and do a level 2 memory clear, it shuts down a critical SMS process and the phone will refuse to send any SMS until the the phone is rebooted.
By chance have you been clearing memory in RAM manager on the new EB13?
Click to expand...
Click to collapse
I know that I do, I actually do this rather frequently when I want to make sure my music player or game or anything else isn't still running in background. Not going to do a memory clear the entire day and see if this error still comes up.
xxmastermindxx said:
I know that I do, I actually do this rather frequently when I want to make sure my music player or game or anything else isn't still running in background. Not going to do a memory clear the entire day and see if this error still comes up.
Click to expand...
Click to collapse
Let us know your results, I'm fairly certain this is the cause of my SMS issues. I haven't done a level 2 ram clear in a couple of days and have had zero SMS issues since.
Atlienzz said:
Let us know your results, I'm fairly certain this is the cause of my SMS issues. I haven't done a level 2 ram clear in a couple of days and have had zero SMS issues since.
Click to expand...
Click to collapse
No level 2 clears since I posted here last, zero SMS issues.
Sent from my SPH-D700 using XDA Premium App
xxmastermindxx said:
No level 2 clears since I posted here last, zero SMS issues.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I've been having the same issue too, and I can also confirm that I no longer have this problem by not using level 2 clears.
I'm having problems still and data problems..
Although I found out yesterday that Sprint put up a new tower in my area (south bend, in) and the problems won't be fixed for about a month :/
at least i know it's (most likely) not my phone
I am having similar issues. Just activated my phone, about an hour later I am using Syndicate 1.0.2
I can receive texts, but am getting "Failed" sent texts. Cleared my ram. Reboot. Still having issues.
I'm going to get to bed, and hope the problem is gone in the morning =P
EDIT: Well I figured out my issue. I tried to make a call this morning and got directed to SPRINT. Sprint apparently had to finish activating my phone... now texting works. hah! I feel kind of silly now for worrying about it.
I'm on AT&T running AOSPA 6.0.3. I've had an MMS group chat with 3 co-workers (4 including myself) going for several months with no issue until a few days ago. I know this dude has a Samsung/Android phone of some sort and is on Verizon. I can receive images from him, but not text. I have tried changing/resetting my APN but it doesn't seem to do anything. The other 2 people in the group receive his and my messages with no issue. Again, it's just MMS text I can't receive from one particular contact. We can SMS each other no problem. I thought maybe there could be some tower issues and it'd fix itself in a day or so, but now it's been nearly a week. This is by far the weirdest issue I've ever encountered.
I have this same issue. Did you ever figure out a solution?
I can send/receive texts/MMS (group texts and pictures) from everyone okay besides my sister who has a Samsung galaxy s6 edge. We are both on AT&T. The messenger app says there is a text waiting to download but won't let me download it. Any ideas? Maybe an issue with the Samsung phones?
Try to send one MMS in Safe mode. Once it sends it, then reboot the cell. It should work. My wife has a Nexus 6 and this happen for no apparent reason and this fixed it. Hope it helps.
Sorry, life got busy and can't say I really ever figured it out. The safe mode thing sounds interesting. I finally flashed a Nougat ROM a few days ago and so far everything seems to be back to normal. Maybe my phone just needed a reset?
Sent from my Nexus 6P using Tapatalk