SMS timestamps are off - Desire General

Strangest thing - since I upgraded to newest CyanogenMod a month ago, all my incoming text messages have timestamp one hour behind my telephone time (and timestamp on my sent messages).
What is this?

Your phone time is off. The timestamp is based on carrier time. Change your time to a few minutes or so off to get it back right. At least, that's what I did.

I am not using carrier's time. I am using software that syncs it with atomic clock every 12 hours. I don't see how this could cause a problem.
And it didn't on previous version of CyanoGenMod.

impactor said:
Strangest thing - since I upgraded to newest CyanogenMod a month ago, all my incoming text messages have timestamp one hour behind my telephone time (and timestamp on my sent messages).
What is this?
Click to expand...
Click to collapse
Are you in the UK? It's not something to do with BST is it? I'm just thinking that if your time zone isn't taking this into account, there'd be a spare hour somewhere...

Yes, I am in the UK.
The strange thing is, that my own messages have correct time. It's only the incoming ones that are behind.

Hmm, it looks like it's not that uncommon - there's an app in the market called "SMS Time Fix" which addresses your exact problem. Unfortunately, it doesn't say why it happens, but apparently it fixes it. Half a solution I know, but maybe better than none?

Thanks for the tip. Hope it works.

Related

Text messages not accounting for daylight savings time?

Since DST ended my text messages show that they were received an hour ahead of the actual time. I'm using vp3g's WM6 ROM. Any ideas on a fix?
Anyone have an idea?
I just started having this problem today (i think anyway). It's only the incoming texts. Even my sent ones reflect the correct time. Is there a fix? :hsugh:
I'm using the Official ATT ROM, by the way.
i take it you have checked that your regional settings are correct on the phone?
superfuji57 said:
I just started having this problem today (i think anyway). It's only the incoming texts. Even my sent ones reflect the correct time. Is there a fix? :hsugh:
Click to expand...
Click to collapse
:hsughno: LOL

FIXED: Evo 4G 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
Trying updating your Profile and PRL.
if that doesn't fix it, dial #2
I also have noticed issue #1. I even called Sprint to ask about it and they referred me to a 3rd party app in the marketplace to fix the timestamp.
I have been using Handcent ever since to get around the issue.
Updated First Post...
trying updating your Profile and PRL.
agix said:
I also have noticed issue #1. I even called Sprint to ask about it and they referred me to a 3rd party app in the marketplace to fix the timestamp.
I have been using Handcent ever since to get around the issue.
Click to expand...
Click to collapse
Its the tower issue mentioned at the top of this topic. Updating your PRL, (Preferred Roaming Location), is usually helpful when you are traveling and lose signal, this will help catch another carriers tower or at least one a bit closer, also, updating your Profile, (Data profile), only will refresh from your device the settings matching your NAI (ID address) with your carrier and refresh your data settings...ie > HCM/SPS>OMA, these tactics are unnecessary, and you can do both with a quick power cycle. The best thing for timestamp correction is to use your phone time as the stamps source & to make sure only to use for future time dated messages. As for dialing *2 or #2 as in this thread, it will get you no where with the issue, they will only refresh your device in their system, in this case meaning Sprint, you can do the same, unless, of course you are running specific roms which clear Carrier IQ, you may then run in to some trouble with those device self updaters, but as mentioned earlier a power cycle will do the same all at once.
The Time Stamp Fix, from the Market works just fine
Does this fix work for when you have your phone off or in Airplane mode? I hate getting my text messages when I turn my phone back on are they are all timestamped to when I turned my phone back on not to when they were actually sent.
thank god i saw this, i have a vzw prl and my timestamp is always 4 hours in the future. works great.
Oddly my sms timestamp is fine on aosp roms, just on sense it is off...

FIXED: SMS Timestamp Issue in HTC Sense Froyo

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
Does anyone know if this issue has been fixed in the HTC Sense Froyo Update?
Matt_TX said:
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...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
no it has not, ive been having problems with this, ALOT.
Updated First Post...

[Q] SMS / Text Message Timestamp Incorrect

Hi Guys - i've posted this in the HD7 specific forum too - please let me know if multiple posts is frowned upon and i'll delete it.
Anyway...
I've been searching and searching and I cant find anyone with the same problem as me, on WP7 or HD7. Basically the times are completely wack on the text messages i receive. The could be a few hours behind, or usually entire days behind, and my personal favorite, from the future.
No idea what's going on. Everything seems fine in the settings - been over them 100 times. I've seen it as being a common issue with some older phones, but nothing on the latest ones.
Has anyone had this? Or even better, does anyone know how to fix it? The text messages that I send are stamped correctly, so it's just the ones i receive. It looks like the phone is using the time sent from the carrier, and then applying some wacky timezone to it based off my timezone (which is Auckland, New Zealand).
Help!
I have this exact same problem.
My outgoing texts display the time correctly but incomg is off by something like 5 hours. I've searched the forums and google and haven't found anything myself.
Answer from Microsoft:
Time stamps for Text messages are encoded and sent from the carriers MMSC message system. If the time stamp is showing up wrong, that is because it is being encoded wrong from the carriers network. Unfortunately there is nothing that can be done device side, you'll want to focus your attention on Rogers in this case.
I suppose other phones possibly counter this by just making the receive time the timestamp as well.
http://social.answers.microsoft.com...7/thread/bf92da2a-5bcc-4af9-bb6a-79ce98d74406
I've never had such an extreme case with a five hour time difference, but it does happen with some incoming texts.
I remember I sent my sis a text at 1:43pm and she replied and the timestamp said 1:38pm. So maybe it depends on the person your texting and how their time is set up?
Well that's a pain. I read that reply from Microsoft too, but it's pretty unhelpful. To be honest using the date stamp from the carrier seems like a poor decision, or at least not having the option to chose, as far as the user is concerned the only date / time they care about is the one on their device.
I guess i'll have to wait and see if someone comes up with a way to change this on the phones, I see there is a way to do it on the WP6 phones.

Disappearing text messages

I've noticed an issue on my Galaxy Nexus (Stock Rooted 4.0.4, VZW) where randomly a text message will disappear.
I don't have any idea what is causing it and its so sporadic, it happens maybe once every 1,000 texts.
The only way I know I'm even missing a text is if I see it appear in the notification bar but not be there when I go into the messaging app (Using stock messaging) or, because I have mightytext installed, I'll see the message forwarded to my browser but I'll notice its gone from my phone.
I was able to pull a logcat after it happened most recently, so if someone thinks they would be able to decipher some information from it, let me know.
I'm posting because I'm wondering if I'm the only one seeing this issue or if others are in the same boat.
Thanks in advance and let me know if anyone would like some more info...I've been trying to nail this thing down for months now.
You're welcome to put it up on pastebin or something and post it, but I would first eliminate MightyText as the first possible problem. Uninstall it and see if it still happens.
I had the same problem when still on 4.0.2 stock, unrooted. Only ever used the stock messaging app. It happened very sporadic, with the same symptoms you described.
Messages popped up in notification bar but could be nowhere to be found in messages app.
Since upgrading to 4.0.4 it never happened again, or at least I didn't notice.
As you are on 4.0.4 already, that's probably not comforting.
Sent from my Galaxy Nexus using Tapatalk 2
Yeah, it happens so infrequently that I'm not surprised you haven't noticed it since updating, but nice to know someone else has the same issue.
Do you have mighytext installed or can we rule that out as a culprit?
Do you have any SMS Backup applications installed?
If not, I recommend the "SMS Backup +" by Jan Berkel.
Works amazing on my ICS.
Does backups of SMS, MMS and Call Logs (if you want.)
Yes, I do have that installed, but thats not really relevant to the issue I described here.
Thanks.
gbenj said:
Yes, I do have that installed, but thats not really relevant to the issue I described here.
Thanks.
Click to expand...
Click to collapse
Sorry - I realized I never finished my train of thought. Got "distracted" as someone walked into my office.
To continue, when your texts disappear from your phone, do they also disappear from your Gmail SMS label?
As per every 1000 texts - I assume you get a TON of texts per day?
I ask - because my cousin who is a promoter also gets/sends 1000's of text messages a week, and he made a funny comment yesterday about how some of his incoming texts "vanished."
He doesn't have SMS Backup+, so I couldn't verify it for him at the time. I'm wondering if you and him have the same problems?
Regards,
var
I also have SMS Backup + installed, but not Mighty text. When a disappearing text arrived, it never even had a time to kick in, even though I'm on wifi and it's said to backup upon arrival. The text is just gone, right after the notification vanishes.
But hard to investigate as it happens really very sporadic... And yup, I get hundreds of messages each day in a developing country, where sometimes also sms are not delivered, so everybody knows and it's not that big of a problem.
Sent from my Galaxy Nexus using Tapatalk 2

Categories

Resources