Related
What the heck? I had at least 600+ txt messages from all different people, and now they're all gone?!?! I sent a txt message (stock, not rooted, using google's Messaging app), put my phone into sleep mode, woke up my phone a few minutes later to send another msg, and was greeted by an empty thread (with a bud's phone number there but none of the prev. messages), and there were no messages/threads anymore
The exact same thing has happened to me twice so far...
Yep. This happens ALL THE TIME with me. I've been having MyBackup Pro run nightly backups so I don't lose important information. This is a serious bug for me and it's cost me some info that could not be recovered before that I really needed.
I've never had a smartphone that has done this but the Nexus does it about once a week. Now I only lose a few messages when it happens since I back up every night, but the fact the issue is there at all and it just happens randomly is really disheartening. Rooting and using a custom ROM has not helped.
Have all of you tried disabling auto delete?
Yeah, that's not related to this issue. You can have auto-purge off and it will still happen after a while. Just randomly erases everything.
That's odd, this is the first time im hearing of this. I've never had my phone delete anything i didn't want it to.
Maybe it's something to do with the ROM you're using or some tweaks you've done.
Try using a stock rom for a while or something and see if the problem persists
I've heard this happening many times now, and every time it was when using the built in messaging app. So I've used hand cent from day 1.
interesting. this happened to me also. only one time though so far..*knocks on wood.
never had it happen to me (knock on wood) thats a very weird problem :\
This has happened top me once on my Nexus in three months.
It's on the buglist here - http://code.google.com/p/android/issues/detail?id=5669 where they are asking for logs to help identify the issue.
There are already a couple of threads about this. It's not just the Nexus - it seems to be 2.x
see here
http://forum.xda-developers.com/showthread.php?t=667800
PhantomRampage said:
Maybe it's something to do with the ROM you're using or some tweaks you've done.
Try using a stock rom for a while or something and see if the problem persists
Click to expand...
Click to collapse
For the record, while it only happened to me once, it did happen to me and I've never rooted or installed any custom ROMs (I even waited for the official OTA for update 1 to hit me in due order).
Luckily I had a 2-week old backup of SMS to restore and I've since set a nightly backup schedule for SMS/MMS and call log via MyBackupPro.
One thing that may contribute is that I am a pack rat and so have every message that I've gotten since I got my G1 in 10/08 (ignoring that one purge due to this bug and the time when I forgot to turn off auto-deletes and didn't notice until a couple of weeks later). I have threads with several hundred messages in them for the friends I text most...
It does seem to happen to us pack rats, and not very often to those who don't hoard messages. I read somewhere that it was suspected to be an overflow error of some sort, and that people had managed to prevent it by keeping the auto-delete function active.
I am not prepared to do that however. I don't want to deliberately delete my messages that I have worked so hard to collect. I would rather google fixed it.
Hopefully froyo will bring a solution to our problem.
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.
Hi guys.
An issue I noted was that my messages would appear above my friend's messages even though he messaged me first.
Does anyone else have this problem? A reboot seems to temporarily fix it, but I can't seem to pinpoint what exactly causes this. Thanks!
That is a problem that has existed for quite some time. It is something about gtalk displaying messages ordered by received time, but incomming messages use a different time than system time, or something like that. You can check that the messages are sorted by time, but incomming messages have wrong timestamps. It happened to my GFs phone once and the fix was checking (or unchecking) "automatic" in Settings>Date & Time settings. Very weird, I know...
See also https://code.google.com/p/android/issues/detail?id=6434
PS: I don't have a Nexus10 yet, I'm waiting for mine, and never had this problem myself, but I know about this problem on many other phones as you can see in the link above.
garciaw said:
That is a problem that has existed for quite some time. It is something about gtalk displaying messages ordered by received time, but incomming messages use a different time than system time, or something like that. You can check that the messages are sorted by time, but incomming messages have wrong timestamps. It happened to my GFs phone once and the fix was checking (or unchecking) "automatic" in Settings>Date & Time settings. Very weird, I know...
See also https://code.google.com/p/android/issues/detail?id=6434
PS: I don't have a Nexus10 yet, I'm waiting for mine, and never had this problem myself, but I know about this problem on many other phones as you can see in the link above.
Click to expand...
Click to collapse
Never had this problem on my gnex but I thank you.
Had this problem occasionally on my other device as well.
[sent from my nexus 10]