I'm having reliability issues when it comes to SMS. The phone often freezes when a text arrives, requiring a reboot. Once rebooted, the new text is gone and never re-appears. This can be kind of a big deal, as you might imagine, because people assume I got a text that I never actually got to read...
I am running Fireburned's WM6.5 v3.1 ROM. I usually have SMSBubbles running, but it has happened when disabled as well.
If this is not a particularly known problem with some sort of fix available, is there, perhaps, some software that will more robustly save an incoming text? Thank you!
have you tried reflashing the rom? I've had a few softwares problems, and they've always been fixed by a reflash
I'm also facing the same problem.. tried re-flashing but still the problem exists??????? Some body help!!!
So I've got a few problems that seemed to have cropped up with my HTC Dream (hence the vague title!)
I'm running Android 1.5, Rogers Post-E911 firmware - I'd imagine that in itself is a problem, but whatever!
The main problem I'm having currently is that my phone keeps losing connection to the network. It says I have perfect connection/full bars, but any outbound calls just bounce me back to the home screen, any outgoing texts get the "Could not be sent" error, and anyone trying to contact me gets a message saying my phone is unavailable. I've factory reset my phone several times but this keeps happening.
The second problem I'm having is that a lot of the time when I start my phone, I get an error saying "Android.Process.Acore is not responding". Forcing it to close leaves me with a blank screen (background image with no icons). Telling it to wait just sends me to my regular home screen, and nothing appears to be wrong after that.
Both of these issues have been ongoing since about a month after purchasing the phone (Pre-E911) but have increased in frequency since the update.
Now I realize that the Dream is nowhere near the cream of the crop these days, but it's my only phone currently, so hopefully the geniuses on XDA Forums can solve my problem =D
Nobody? ~bump~
I flashed the Energy.RHODCDMA.23673.Sense2.5.Cookie.Jul.17.7z rom onto my touch pro 2(sprint on boost mobile). Ever since then I get random text from 9067 thats just filled with random characters. I thought at first it was the boost message getting messed up but after I actually got a message from boost that eliminated that theory. I also blocked it using the 9999 block 9067 text. I got a confirmation text that it was blocked and still I get them. Now the phone doesnt even have an active service on it I they still come in. WTF help me.
i noticed that too on my phune, mostly in the morning
i guess noone else has or has any solutions?
bump noone else really has this problem or a solution?
I figured out it happens when there is a change to my gmail account that is linked into the email on the touch sense. Anyway to remedy this?
Anyone else experiencing their text threads being out of order? For instance, i can send a text that shows that it was sent at the right time, however if someone texts me, the time is a couple of minutes off. Thus, throwing the chronological order off.
If im reading and thinking of ur problem rite it may be the same as mine was. When i first send text sometimes it would fail and wouldnt resend till i reopen text. So it would have wrong time at least i thought it did.
chvybeatsford said:
If im reading and thinking of ur problem rite it may be the same as mine was. When i first send text sometimes it would fail and wouldnt resend till i reopen text. So it would have wrong time at least i thought it did.
Click to expand...
Click to collapse
No, my texts don't fail. When I send them, they show the same time as my clock. However, if someone sends me a text, it shows they sent it about a minute or two ahead of my actual time.
I'll try to give an example: 6:45PM- actual times that these text are sent.
Me (6:45PM)- aaaaaaaaaaaaaaaaaaa
Me (6:45PM)- ccccccccccccccccccc
Someone Else (6:46PM)- bbbbbbbbbbbbbbbbb
See, how it places the incoming texts at 6:46, even though it is really 6:45 still, throws the order off on my reply. It makes it seems like both of my texts were sent before I even received a response.
Very frustrating......
Are you having this problem in the stock messaging app? I noticed it every once in a while, but haven't had the problem yet with Handcent.
If you're using the stock app, try downloading Handcent or ChompSMS or something, and see if it goes away
i have this same issue, its made me switch to handcent because the problem hasnt occured using that. Plus it lets me have vibrate functionality ONLY in the vibrate setting and retain only audio notification in a sound profile
60HertzJig said:
Are you having this problem in the stock messaging app? I noticed it every once in a while, but haven't had the problem yet with Handcent.
If you're using the stock app, try downloading Handcent or ChompSMS or something, and see if it goes away
Click to expand...
Click to collapse
Yeah, I'm using the stock messaging app. I'll try Handcent, apparently a lot of people like it. I'll update ASAP
i'm still using my fuze and i have the same problem. i wonder if it has something to do with the time on att , the other persons phone and/or other carriers servers
Handcent all the way! It corrects the out-of-order issue and is way more customizable, including assigning ringtones for each contact. Just remember to turn off the notifications on the stock messaging app, otherwise you'll receive double notifications on each message received.
Im having the same problem on my Captivate...But my N1 gets it right. Im getting replys before I even send a text...according to the time stamps.
Sorry to report that, although ive only experienced it once, i have seen the same problem with Handcent SMS
All these little issues on this thing are starting to pile up :/
Intervenient said:
All these little issues on this thing are starting to pile up :/
Click to expand...
Click to collapse
But this is true, at least for me, for every device.
soul4rent said:
i'm still using my fuze and i have the same problem. i wonder if it has something to do with the time on att , the other persons phone and/or other carriers servers
Click to expand...
Click to collapse
No cuz my iPhone worked just fine...
This problem happens to me if I reply back really quickly... It'll put my text above the one I replied to.
Intervenient said:
All these little issues on this thing are starting to pile up :/
Click to expand...
Click to collapse
Beauty is there's ways around it (other apps) and we don't have to rely on anyone to fix it.
My wife and I both have Captivates. Her phone has the text messages out of order, while mine does not. Something we noticed is that when we do an auto sync of the date/time, her phone is consistently 4 minutes behind mine. For example, my time will be 6:06, and her phone says 6:02. I believe this is what is causing the text app to "re-arrange" the messages. The text app just looks at the time stamp of the message, and not the actual order of the send/receive process.
I am not sure how to correct this other than manually setting her phone forward by 4 minutes.
tikicult said:
The text app just looks at the time stamp of the message, and not the actual order of the send/receive process.
Click to expand...
Click to collapse
This is exactly the problem.
If I get a text at 9:01... And I reply at 9:01... It puts mine as having been sent before the one I received.
just use handcent people.
Yeah, but like I said, Ive reproduced the problem once, even with Handcent. On a side note, does anyone know how or where to get more skins for Handcent?
domin8 said:
just use handcent people.
Click to expand...
Click to collapse
That does not solve the root problem... Some phones are getting the wrong time from the network when set to auto-config.
tikicult said:
My wife and I both have Captivates. Her phone has the text messages out of order, while mine does not. Something we noticed is that when we do an auto sync of the date/time, her phone is consistently 4 minutes behind mine. For example, my time will be 6:06, and her phone says 6:02. I believe this is what is causing the text app to "re-arrange" the messages. The text app just looks at the time stamp of the message, and not the actual order of the send/receive process.
I am not sure how to correct this other than manually setting her phone forward by 4 minutes.
Click to expand...
Click to collapse
tikicult, somone else reported that their phone was off by 4 minutes. Solved it by getting a new SIM Card.
Guess I'm a new user so I can't post a link to the forum thread, but here is the url:
forum.xda-developers.com/showthread.php?p=7280990#post7280990
TexUs said:
This is exactly the problem.
If I get a text at 9:01... And I reply at 9:01... It puts mine as having been sent before the one I received.
Click to expand...
Click to collapse
I've been having this problem as well.
I went to the AT&T store today to try and get a new SIM, as per one of the suggestions in this thread. Problem still occurred. Tried it on a fresh straight out of the box Captivate. Problem still occurred. Sales guy threw his SIM from his iPhone in a demo Captivate. Problem still occurred on both Captivates.
Later I tried adjusting the time manually up by a minute or 2. Problem still occurred after a text with a response approx. 20-30 seconds later. Still showed the text coming in at 1:23, and my response which was 30 seconds later as being sent at 1:22.
Seems like a Samsung software issue.
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!