text messages from the future Y2KX issue

[BlackDynamite]

Originally Posted by cptok

Here's my take on this. The "issue" seems to be with the SMS gateways putting an incorrect sent time stamp on the SMS (relatively well confirmed at this point). Just like email - where you can decide if you want the "received" column to be when it was sent by sender or received on your server - SMS clients do the same thing.

It's my bet that in fact, with the possible exception of T-Mo, ALL SMS messages actually have the bad time stamp from the gateways for the "sent time", but that it is the SMS clients use of received time rather than sent time making the difference as to whether it is an "affected device".

So it comes down to what the client does. Verizon stock ROM's appear to have default of using received timestamp - so no problem. Same for other devices and OS's. Cooked ROM's like Mighty do not have that reg entry and so were using sent time, and nobody paid much attention to this little difference - until all hell broke loose on 1/1/16!

It is a valid and healthy debate as to whether it is more valuable to use received time or sent time. In the email world, this has been debated a lot - and yet few people actually know which one they are using. In Outlook Express - the default is "Received" - i.e. the time it hit your server inbound. But "Sent" is a non-default option you can put in there and display if you wish by customizing the columns.

Personally - I don't care much which one is displayed. Although, at the moment, I wildly prefer to display "Received" time!! Once the carriers fix whatever gateway bug was malforming the sent date, we will then have that choice to keep the reg entry, or delete it and go back to sent time. In the meantime - I don't see this as a Windows issue as such - but rather a nice feature that windows actually allows configuring the display of either the sent time or the received time.

I might be wrong on this one - but I'll test tonight with a non-windows phone. Turn off the device so that it delays the SMS message a few minutes. Then turn on and see what time displays. I'm betting on Symbian it's the received time..... Possibly so on Android as well. In which case, those devices would not display the problem - although the sent time field may still be just as wrong on those "unaffected" devices.

So I very much agree that the current "reg fix" is not a fix for the real problem. That will be the gateway providers fixing the sent timestamp. But then... once the carriers really do fix this - look at what we've figured out! We now know that we can configure our incoming timestamps on SMS just the way we choose via a simple reg setting.

I would bet that you are absolutely correct. I mean, I highly doubt sprint would be telling everyon eit's a known network issue if it was really a problem with Windows Mobile. And they've told me it's a known network issue like 5 times now, so...

[psycho_maniac]

friend has a blackberry storm and she does not have the problem.

[BlackDynamite]

All of you people saying so and so doesn't have the problem, please also post whether their SMS shows with a time stamp that they received it or with a time stamp from when it was sent.

You can test this by having them turn their phone off, sending them a text message, having them wait 5 minutes and then turning their phone on and getting the message. does it say the time you sent it or the time they actually received it?

Just saying it works on so and so's phone doesn't really tell us anything at this point. Heck, it works on our phones too if we set it to use the phone's "received" time stamp instead of the network's "sent" time stamp (which is all this "fix" does)...

[cptok]

Right on Salt. That was the whole point of my post, but I think it might have been too long for people to read! LOL!

[wstaylor]

This is interesting.... smh.com.au/business/businesses-stung-by-boq-computer-bug-20100103-lmys.htm

[mikejones13]

Originally Posted by wstaylor

This is interesting.... smh.com.au/business/businesses-stung-by-boq-computer-bug-20100103-lmys.htm

bro, you might want to fix your link

[BlackDynamite]

Originally Posted by mikejones13

bro, you might want to fix your link

Here it is, I searched the site and found the story for him:
http://www.smh.com.au/business/busin...0103-lmys.html

[mikel81]

We're not the only ones. nice!

http://www.cairns.com.au/article/201...ness-news.html

As the rest of Australia welcomed 2010, Bank of Queensland computers skipped six years ahead to January 1, 2016.

[jude_b23]

Dang i just hard reset-ted and theres a cab to fix this??? thanks ppcgeeks!

[Rugby Enforcer]

Hi. I have a Treo Pro, and I tried this fix. I ran the PIM backup, but I am unable to open the .pib file at all. It doesn't even give me an option to open. Please help thanks.