Omnia showing incorrect times in SMS

[Guest Honam]

Hi there, I've been using my Omnia for about a week now, and I've noticed that the time in the SMS messages are incorrect. Does anybody know how to fix this? eg. through some setting or changes to the registry.

My system clock is set to GMT -8 Pacific US, and my visiting clock is GMT +8 Beijing, HK. The messages that I receive are off by approximately four hours. For example, if I had an incoming message at 1:00pm, the time would be shown as 9:00am.

Outgoing messages are fine, though; it's just incoming messages that are incorrect.

Thanks in advance.

Edit: Forgot to say, this problem persists even when I tried different roms.

Edited October 22, 2008 by Honam

[Guest Timsta]

Hi there, I've been using my Omnia for about a week now, and I've noticed that the time in the SMS messages are incorrect. Does anybody know how to fix this? eg. through some setting or changes to the registry.

My system clock is set to GMT -8 Pacific US, and my visiting clock is GMT +8 Beijing, HK. The messages that I receive are off by approximately four hours. For example, if I had an incoming message at 1:00pm, the time would be shown as 9:00am.

Outgoing messages are fine, though; it's just incoming messages that are incorrect.

Thanks in advance.

Edit: Forgot to say, this problem persists even when I tried different roms.

i have the same issue.. not sure what the work around is.

[Guest Massive Attack]

i had that issue, but for 2 or 3 sms only, then back to normal, will occur again then will be corrected again, i thought this is a problem with the network, not the phone.

[Guest Timsta]

i had that issue, but for 2 or 3 sms only, then back to normal, will occur again then will be corrected again, i thought this is a problem with the network, not the phone.

I thoguht it might be how the phone grabs info form the network. it probably is. i remember this happenign for japanese cellphones too. it doesn't sync properly with our networks at times.. could be old towers too..

[Guest hlay]

i have the same issue, i tried almost every fix i can find here and the other forums, none of those methods work for me. on my old Ipaq 6915, i changed something in the Regkey it worked

HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting\

Add a dword key "TrustTimeZoneField" and give it a dword value of 0

Have no issue on my Ipaq 614C and 914C but the Omnia

anyone know how to solve this?

Thanks

Edited October 24, 2008 by hlay

[Guest soondot]

i have the same issue, i tried almost every fix i can find here and the other forums, none of those methods work for me. on my old Ipaq 6915, i changed something in the Regkey it worked

HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting\

Add a dword key "TrustTimeZoneField" and give it a dword value of 0

Have no issue on my Ipaq 614C and 914C but the Omnia

anyone know how to solve this?

Thanks

hlay, did you find a fix? This is driving me nuts too. I can get in to the registry all the way to OEM. But past that, I can't find PhoneSetting, just MASD and VoiceCommand. Should I create dword entry for both?

Help please. I've looked at other forums and people don't seem to understand that this is a registry issue and not:

1) The SMS threading issue

2) Time Zone difference between sender and receiver

3) A Telco issue

[Guest momok]

I've got a somewhat weird related problem with my SMS.

It doesn't show the timestamp, only the date. this gets extremely frustrating! Anyone can help me?

[Guest phewie]

I've got a somewhat weird related problem with my SMS.

It doesn't show the timestamp, only the date. this gets extremely frustrating! Anyone can help me?

i'm also having this problem now ...

any solutions to it ?

[Guest St.James]

the wierdest thing is that SMS from my friend with an iPhone has the correct stamp. All others are off.

[Guest TheDrizzle]

This is happening on my i910 as well, but it seems to be for incoming texts only (if I am following a conversation in my sms screen, my side of the conversation will have the correct time, but my incoming messages will be waaaay off...). I'm definitely up for a solution....