Develop Bugs

FIXED: SMS Timestamp Issue

UPDATE: I've found a fix for this issue - AWESOME!
Just go to the Android Market and install the SMS Time Fix app by Matt Precious.
http://www.androlib.com/android.application.com-mattprecious-smsfix-pAFq.aspx
It works perfectly, and updates the time stamp on all messages to relfect PHONE time and not network time. HINT: Make sure the "Last Resort" option is checked in the settings and offset is set to zero. This little app now makes the Evo Messages app usable. Finally...
Hope this is helpful info
So, I've been reading and experiencing several issues with SMS timestamps on the Evo 4G.
It seems there are three distinct issues with SMS timestamps on the the Evo and I believe they all have the same root cause.
Issue 1: When roaming texts are received with the wrong time stamp, offset by several hours (typically 4 or 5 hours off). This causes them to not be threaded in the conversation correctly. Very annoying.
Issue 2: When receiving SMS messages on any network (Sprint or Roaming), the time stamp is off by an hour. The result is the same as Issue 1, but a less extreme example.
Issue 3: When texting back and forth in quick succession, SMS messages are not logged in the order in which they are received, and received text messages ALWAYS appear before sent text messages if they are sent during the same minute, regardless of which one was actually sent first. This is also very annoying.
I believe the root cause is that the native Sense UI messaging app is using the timestamp of the tower of each SMS rather than using the time stored on the phone. To prove this, if you use Handcent and set it to use "phone time" and ignore the tower time, it works perfectly. The thing is that I don't want to use Handcent and I want to use the native app. Is there a setting that can be tweaked to fix this? Has anyone talked to HTC or Sprint about the issue and is a fix in the works?
For such a major problem, I am surprised more people haven't come forward. It's a pretty significant bug...
Thanks,
Matt_TX.
Click to expand...
Click to collapse

I agree and its getting really annoying since it causes me to miss texts.

NM, too easy

Has anyone talked to Sprint or HTC about it? I am sure there HAS to be a fix in the works. The good news is that the native Froyo messaging app does not do this (as far as I can tell). I used a Nexus One on T-mobile and it doesn't occur. It appears to be using the phone's timestamp, as it should...
As long as HTC don't apply their "logic" (or lack thereof) over Froyo, it should be fixed soon.
I also can't believe that Sense UI stops the user from having more than one Exchange account. Android 2.1 (Eclair) does this by default. Why on earth would they remove it?
Anyway, back on topic... Please please post with your thoughts and discoveries around the SMS timestamp issue.
Thanks!

How is this related to development?

tkrechel said:
NM, too easy
Click to expand...
Click to collapse
I'm not sure what you mean by "NM, too easy". Can you explain or provide any insight. Please help if you can. For those of us with this issue, it's REALLY annoying. I apologize if the question is dumb and there is an easy fix.
I realize that some of you may not feel that it is related to development, but I disagree. For those geniuses out there that make ROM's, maybe there is some way to fix this with a setting or minor change in the Sense UI messaging app...
Additionally, there is no need to berate someone that's genuinely asking for help. It's obvious that this forum gets the most traffic, and it's obvious that the smartest "Evo User" minds are located here. I don't think there is any harm in reaching out for help, isn't that the purpose behind these forums

The samething was happening to me last night.
Sent From My HTC EVO 4G

nebenezer said:
How is this related to development?
Click to expand...
Click to collapse
Agreed. If its not happening with Handcent nor the AOSP apk, then its a direct HTC issue.
General Discussion. Also, probably not really that urgent.

./agree on all poins with OP.
I posted in Q&A about this same issues, with no replies 8(.
Anyway, I thought it was related to the modified prl that I installed. However it would do it even when I was on the stock prl.
Long story short, I called sprint and said I was having the issue. They said they were going to refresh something on their side, to wait 20 mins then power cycle the phone.
Did that and to my surprise it worked! Then yesterday I re-flashed a custom rom and the sms timestaps went all wonky. /sigh

suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.

this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.

davebu said:
suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.
Click to expand...
Click to collapse
look at this guy.
handcent didn't work on my froyo rom, not sure about chomp, didn't try it.
at work i always have this problem, texts are recieved 5 hours into the future, whereas the ones i send are the correct time. occasionally ones they send are the correct time so i have to scroll up and down and it is very annoying.
not a fan of handcents pop up notifications, i guess i could turn em off.
guess i'll just 'suck it up'

regulator207 said:
this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.
Click to expand...
Click to collapse
yup, had the same problem on my old HTC Diamond with Sense/TF3d on it.

Updated First Post...

[BUG]Android firing a message to the wrong person!

Have you read this terrible notice from engadget.com?
Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed
By Chris Ziegler posted Dec 31st 2010 1:12PM
Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremely serious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.
More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.
This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.
Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
Click to expand...
Click to collapse
Contribute yourself to convince GoogleGuys to fix it!

Never had any issue with this...

Maybe, it happens only on the default Google sms app not the HTC one.

I've often sent 2 - 3000 text messeges a month with two diffrent devices over the last 18 months and never had this problem. on the otherhand engadget are known for chatting sensationalist rubbish, only to have to apologise later in an editorial.

Fightspit said:
Maybe, it happens only on the default Google sms app not the HTC one.
Click to expand...
Click to collapse
I have experienced this with the HTC messaging one. When I individually texted "Happy new year!!" to everyone, the bug happened twice and it actually sent to someone else.

AndroHero said:
I've often sent 2 - 3000 text messeges a month with two diffrent devices over the last 18 months and never had this problem. on the otherhand engadget are known for chatting sensationalist rubbish, only to have to apologise later in an editorial.
Click to expand...
Click to collapse
is not sensationalism, is an actual big ugly bug.

crapula512 said:
is not sensationalism, is an actual big ugly bug.
Click to expand...
Click to collapse
If it's a bug, then why have I not encountered it since owning this phone for 7 months?
It could be a stock Android problem as already mentioned (HTC Sense ROMs have a different messaging application).

I found a post in the discuss thread where a guy explain how to reproduce this *bug*:
killerbee3 said:
If anyone is interested, evidently "Darth Mo" has been able to replicate it - found in ACentral Forums - entire post follows;
"It's not user error, or at least it's a combination of user technique and a possible design. It has to do with how the stock messaging app interacts with the Android system notification.
I recreated it this way. Open a text, but only from the notification bar. You will be taken directly to the conversation from that contact. Now, just hit the home button to get back to the home screen. Repeat this four times to let the open conversations build up. We'll call the earliest contact 1, the next 2, etc. for this example. Let's say you converse with these contacts over some time so that messages occur in this chronological order (opened from the notification menu if possible) : 1, you, 2, you, 3, you, 4, you, 1, 3, you, 3.
Now, you've read the message from contact 3, but quickly hit the back button because you need to send a message to contact 4. So you're back at the conversation list and select conversation 4. You compose and send your message and off you go. But, what can actually happen is that your message went to contact 1 because there is a bug that when you use the back button, it will take you to the conversation screen and when you select one, it will take you to the conversation with the last "unreplied" message received before the last conversation you didn't reply to, regardless of the one you actually select from the list. It's easy to miss that it took you to the wrong conversation as the on screen info can take a beat to update and it looks like you've select the right conversation. The kicker is the conversation list does highlight the one you meant to select, but will take you to that other conversation. It's as if it's saying, "Hey, I know you want to go to that one, but you opened this message and jumped out of it without replying. Maybe you didn't see it."
It's pretty easy for people to not have seen this for a few reasons:
1. You open messages directly from the messaging app
2. You close out every conversation using the back button and don't let them build up on top of each other
3. Messages can come in such a sequence that the conditions are never correct
4. It has actually happened, only the last "unreplied" message was from the conversation you actually intended to enter
I was able to create reliably using my Google voice number to send myself text and watched it bounce around conversations seemingly randomly. It was only when I looked at the times of each message with no replies that I saw what it was doing actually had order to it.
About 30 minutes of experimentation to figure it out, but I had to know how this was happening as I could see it leading to an egregious error later. Now to explain it to HTC..."
Click to expand...
Click to collapse

i've never had this either - i use handcent

Since a few minutes ago, the issue is considered critical instead of of medium:
http://code.google.com/p/android/issues/detail?id=9392#c794

Are kiddin me?
I dont send any sms for a while , this is a very big issue !
It never happened to me but , this is a realy really big bug!

Mekrel said:
If it's a bug, then why have I not encountered it since owning this phone for 7 months?
It could be a stock Android problem as already mentioned (HTC Sense ROMs have a different messaging application).
Click to expand...
Click to collapse
why havent you encountered it? i have no frikking clue and i dont care.
fortunately now it is a critical bug.
btw, i just care about android stock problems, im not using that sense stuff.

I quite often get messages which are meant for other people from someone who has a samsung galaxy (seems that's it's a copy of the message, rather than it being sent to the wrong sender).
I don't text as much, so less prone to the error.

happened to me on stock Android. Never on HTC Sense or mod

I have actually had this bug... but it reported the message had gone to the wrong person, but the correct person replied so I assumed it was reporting it wrong.... only happened twice.
on stock rom unrooted desire

I'm using a stock ROM & native SMS. I get this bug quite a few times.
I'm working in a very loud environment, so I send & receive lots & lots of text messages.
I notice that when i have lots of threaded messages, the SMS starts to slow down & sooner or later the bug will cause me send a text to the wrong recipient.
I'm quite careful of what I'm sending now.
HTC & they told me to reset the phone.
It hasn't been fun for me since I have to reset the phone once a month because my threaded sms buildup very quickly...
I'll update to 2.29.405.5 to see if this fixes anything.

Guys,
Is the 'wrong' person who receives the message someone in your phonebook or a total stranger. If it'd someone you don't know... how does your phone pick that number up? Randomly?
I had my Desire since April, and never had this issue. I open texts from notification bar and have sent them frequently.

I've had a G1, Magic, Milestone and now a Desire and I've never experienced this at all.

I don't think this bug is very common... I've never experienced it myself and none of my android friends have either...
Just some evil forces trying to make the Android OS look bad. Not our fault they couldn't resist taking a bite of that apple so screw them!

Overblown sensationalism AKA typical journalism. It's a bug but seldom a problem encountered by users, or XDA-Dev would've been flooded with such problem threads long before such publicity sites noticed. Just me personally having switched between over a dozen ROMs/kernels and their versions since March with over 60 average text out per day since and not one occurrence means it isn't anything but rare. I rely on SMS very much daily.
------------------------------
- Sent via HTC Desire -

Text message threads

Hello all,
I'm several months into owning my first Android phone coming from a Palm Pre and I've already taken the measures to root and load Calkulin's rom onto my phone. I however am now growing fairly annoyed with how my phone keeps my text message threads and was just wondering if it was me.
For some contacts I have at most two separate threads running for the same individual and for the same conversation even though I only have one number for them. I was wondering if it was possible to merge these threads together or how to just get one thread going for my text messages.
Any help would be advice or tips would be appreciated. Thank you guys.

iamkt said:
Hello all,
I'm several months into owning my first Android phone coming from a Palm Pre and I've already taken the measures to root and load Calkulin's rom onto my phone. I however am now growing fairly annoyed with how my phone keeps my text message threads and was just wondering if it was me.
For some contacts I have at most two separate threads running for the same individual and for the same conversation even though I only have one number for them. I was wondering if it was possible to merge these threads together or how to just get one thread going for my text messages.
Any help would be advice or tips would be appreciated. Thank you guys.
Click to expand...
Click to collapse
Could it be something like Facebook causing the problem with their email/phone syncing? Go into contacts go through them and merge all duplicates?
Sent from my oh-so-sexy Samsung!

Yeah I thought about that and I went through all my contacts and set the google # as the default and then I thought better and went through and deleted all the facebook numbers out of my contacts so I only have the phone number associated with google in my phonebook. Haha am I the only one that has this problem? That sucks lol.
Yeah I'll have a thread with a person with like over 1000 msgs and another thread in the several hundred but with the same person but itll be the same conversion. Oh well I guess I'll just have to endure haha

[Q] Not receiving some texts (sms)?

Desire HD with Lord C's 5.5 ICS Rom.
I've had a few problems with the rom so am doing a full wipe and upgrading to 6.1, with as few titanium backup restores as possible this time.
I've had a few texts not appear on my phone? They show up as sent on other people's phones but I don't get them? Happened twice in two days, with two different people (one from an iphone 3gs and another from an android, not sure what phone). I have hundreds of texts with these people and didn't ever experience this on gingerbread roms (I used ARHD and CM7 for about 6 months each).
Any idea what might cause it? I'm using stock sms app, and I'm about to do a full wipe and upgrade from 5.5 to 6.1.
I opened go SMS and didn't see them; they aren't on my phone and I don't receive notifications of them.
Thanks

I see you're on Orange. I would say that is your problem.
Nowadays it only happens every now and again. You should get the messages in a few days.
Sent from The App that Time Forgot.

I'm not convinced; there was one that was sent on the 9th march that I haven't ever received, and I've only had the issues since ICS.

Tamen said:
I'm not convinced; there was one that was sent on the 9th march that I haven't ever received, and I've only had the issues since ICS.
Click to expand...
Click to collapse
dropped texts are a very common problem across any network and phone. Lord knows how many fights ive had because of a text that said "do you miss me?" that i never got lmao. Anyways, what specific data are you restoring from backup with tibu? I'm sure the answer is no, but were these texts sent to you during your upgrade process of flashing the phone?

In the UK texts are actually really reliable; obviously you don't always know when they haven't delivered (orange charge like 3p per delivery report, no thank you to an extra £30.00 a month!) but I've never had anyone mention "oh, didn't you get my text" or feel that someone had ignored me pre-ics upgrade. I assumed that their phone was the problem, but after it happened several times I've decided it was me
No they weren't send/received during flash; I tend to flash a rom and then (as long as it's stable) stick with it. The last time I flashed a rom was a couple of weeks ago, and only as an upgrade.
TiBu is just restoring small things like wifi netwrosk and fruit ninja scores haha
Having full-wiped and restored SMS, call-log, re-setup accounts and got the majority of my apps all sorted, the phone seems quite stable. Had 2 reboots during the first hour or so but I think that's probably down to everything running for the first time, it seems rather stable now.
I've got alogcat running & saving logs to sd card so we can see what's causing any reboots if they occur too!

Text alerts for *sent* messages as well as received since update

Apologies if I am posting this in the wrong spot. I have a Pixel 2 XL(obviously) and had been on the Android beta program for some time now. The android p beta had been running really solid for me with no issues. So when they pushed it out officially last week i of course went for it. However, all of a sudden now, when *sending* texts, it gives me a notification sound (same as incoming notification). Anyone run into this? I searched the forums briefly but didnt see anyone with the issue although I couldve missed it.
Note- I'm using the Google Messages(I believe thats the official name) app, I just prefer it to Hangouts. I did check the settings, and disabled the setting for outbound notification sounds- but it persists.
Here's the kicker- it cant be isolated to just me, as my mom has the same phone -she messaged me last week and asked if she should update (I'm typically the guinea pig) and I said yep, been rock solid for me.. now she's getting the exact same behavior. So barring it being the messages app itself which i suppose is possible, I dont know.
Thoughts? Suggestions? I havent tried a different messenger app yet, suppose I could(textra maybe), I'm just partial to this one for whatever reason.
Thanks in advance!

Disregard. I guess its specific to Android Messages app. Installed another text app and the issue went no longer occurs.

I have the same issue with my Android Messages app