text messages from the future Y2KX issue - Page 27

Oryx · #**261** (**permalink**) 01-02-2010, 04:00 AM

Just a thought, perhaps this issue isn't a Windows Mobile issue nor an HTC issue, but instead related to the date/time value that is sent in an SMS over the Sprint CDMA network?

Think about it, the registry "fix" that is being shared here tells Windows Mobile to stamp the date/time from the clock when the message is received, when the value is removed, the date and time come from the SMS value for the date/time stamp.

I performed a test. I sent my phone's clock back to December 31, 2009 and sent myself a text message from another phone. The message was received with the date 1/1/16 and not 12/31/2009 showing that the date is part of the data received in the SMS message. When the registry value of RecvTimeStamp was set to 1, the date/time stamp set on the message was the current date/time of the phone.

Just a thought.. Give it a try for yourself.

Oryx

**BlackDynamite** · #**262** (**permalink**) 01-02-2010, 04:07 AM

Quote:

Originally Posted by Oryx

Just a thought, perhaps this issue isn't a Windows Mobile issue nor an HTC issue, but instead related to the date/time value that is sent in an SMS over the Sprint CDMA network?

Think about it, the registry "fix" that is being shared here tells Windows Mobile to stamp the date/time from the clock when the message is received, when the value is removed, the date and time come from the SMS value for the date/time stamp.

I performed a test. I sent my phone's clock back to December 31, 2009 and sent myself a text message from another phone. The message was received with the date 1/1/16 and not 12/31/2009 showing that the date is part of the data received in the SMS message. When the registry value of RecvTimeStamp was set to 1, the date/time stamp set on the message was the current date/time of the phone.

Just a thought.. Give it a try for yourself.

Oryx

Yes, this is already confirmed. Sprint is telling customers it is a network issue that they are aware of. Maybe the first post should be updated...

titaniumgiant · #**263** (**permalink**) 01-02-2010, 04:10 AM

check this out:

http://www.wmexperts.com/y2016-sms-bug

jdmtsx · #**264** (**permalink**) 01-02-2010, 04:48 AM

Here's a fix straight from wmexperts.com

**BlackDynamite** · #**265** (**permalink**) 01-02-2010, 05:16 AM

Quote:

Originally Posted by jdmtsx

Here's a fix straight from wmexperts.com

They got that fix from here. It's even posted in this very thread (and another on this forum).

sofarfromitall · #**266** (**permalink**) 01-02-2010, 08:49 AM

fix worked for me

Telek · #**267** (**permalink**) 01-02-2010, 09:32 AM

So still no confirmation on exactly why this is happening? Seems pretty clear that it's an SMS gateway issue? In which case it'll probably be silently fixed without any actual admission of guilt...

krid80 · #**268** (**permalink**) 01-02-2010, 10:01 AM

Quote:

Originally Posted by Telek

So still no confirmation on exactly why this is happening? Seems pretty clear that it's an SMS gateway issue? In which case it'll probably be silently fixed without any actual admission of guilt...

couldn't agree more. We'll never know why.