Not much I can say about this, but every time I view a received MMS, the phone locks up and a reboot is the only thing that will cure it.
Any ideas??
Related
When my phone is off, and someone send me a message, then I turn on the phone. The received time of the message is the time when I turn on the phone, not the time when it was sent.
I have tried OpenEclair 2.1 CM 1.6 rom. All of them have the same problem.
I think this is a big problem of the android system. Many other phones have no such problem.
This is a basic function of a phone...
I heared that the developers of Handcent maybe handle with this problem, It would be great.
original rom's have it working normally, that annoys me too
has anyone noticed that sms time stamps everything as received not when the message was actually sent. If i leave my phone off for example any text sent while it was off, will be time stamped when the phone is turned back on. my evo did not have this problem. i have tried other clients such a go sms and handcent but i get the same issue. any ideas?
tensux said:
has anyone noticed that sms time stamps everything as received not when the message was actually sent. If i leave my phone off for example any text sent while it was off, will be time stamped when the phone is turned back on. my evo did not have this problem. i have tried other clients such a go sms and handcent but i get the same issue. any ideas?
Click to expand...
Click to collapse
Hey there,
You are not alone, google this and you will get a huge search result back. This has been happening since the early days of windows mobile (pre android).
It can sometimes be carrier specific, ie the error is with them or it can be simple device setting errors.
Possible solutions:
1) Go to Settings>Date & Time and uncheck "Automatic" then confirm you time zone manually.
2) Install SMS Time Fix by Matthew Precious from Market.
Click to expand...
Click to collapse
This should help - http://forum.xda-developers.com/showpost.php?p=7933771?postcount=15
thanks i did see that but i wasn't sure if it was the same issue. i will try it.
Hi guys,
I've been having my text messages fail on me for no apparent reason. It just happens sporadically, and when it happens, it keeps happening for a while.
There's no issues with reception at the time it happens. I have no clue what could cause it, and I have never been able to pick up on a pattern either.
I've had it happen here and there before (i'd say 5%-10%) of my msg's but in the last week, it's been doing it for atleast 50% of my outgoing texts.
I just get a "message not sent" notification every time I try.
If it helps, I'm currently Undead's ICS Splashed v2.0
.. but I just dont think it's the rom itself, as I remember experiencing something similar with my Captivate, and if my memory serves correct, it also happened once in a while to my G1.
But over 50% of sms failing, is just absolutely terrible.
.. if anyone has any idea how I could resolve this issue, it be greatly appreciated.
Thanks
Its probably due to size. Over 160 characters and it will fail. Click the little error triangle, delete til its only on sms and resend.
First off, I have already found the SMSC help threads and verified my message center is the correct one for AT&T.
Sometimes, when I send SMS to certain people (random people?) the phone will say they are sent but the recipient will not get the message until 3-4 hours later. In the mean time I can text other people normally.
It gets weirder, I was thinking it was an inter-carrier issue, but if I reboot my phone, all of the missing messages will suddenly arrive at the recipient's phone. Its as if the phone tells me they are sent while they are in some backed up queue?
I was using Scott's regular build (several versions where I have this problem intermittently) and just upgraded to his beanstalk build and have the same issue.
I use GoSMS for my messaging.
Anyone heard of anything like this or can direct me to some help?
Much thanks!
And major props to Scott for his wonderful builds, my phone has never worked so well, minus whatever this issue is!
So, this is bit of a new issue, one I've not had before. I wish Hangouts/Messenger still had the Service Center ID in the settings in order to fix this, but, in the long/short run...
I unboxed my pixel and put my SIM in, started the phone. LTE/UMTS work perfect, locked right on, good signal/speeds, can place/receive calls, all is right in the world? I noticed after an hour I hadn't received any texts, and after feeling very unimportant, I sent a SMS to a friend, and got an immediate error. Out of curiosity, I went into the INFO settings (*#*#3646#*#*) and went into the SMSC settings. pressed refresh, which, populated an error. I manually typed mine, hit update, went back to hangouts, and voila!
The next day, I restarted the phone ( I like to do this often. I am also this user who actually turns their phone off from time to time ) and noticed upon restart, the problem resurfaced, like as if I never updated it to begin with.
Is this occurring with anyone else? I've yet to see a phone completely dump it. I'd prefer not to download another SMS application really, but, it's just inconvenient those few times I do restart it that I lose that SMSC number...
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
I'm having this same issue. I've contacted support about it, but haven't gotten a response yet (they said I would have an update yesterday).
If I manually put the SMSC in, and then Update, I can send texts briefly, but eventually I start getting an error 38 instead. A reboot and then manually entering the SMSC again allows me to send texts again.
vagosto said:
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
Click to expand...
Click to collapse
I'm curious if setting your mobile data to always-on would be a functional workaround to help until they can get this fixed for real. Have you tried that?