text messages from the future Y2KX issue

[Brian.G]

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.

My Samsung SGH-Z140 has always shown the time the SMS was sent (as has every phone I've ever owned) and when I put my SIM in it just now there were no SMS problem. SMSs show correctly as sent on 2010.

I wonder if this could be a problem with the radio part of Windows phone ROMs?

[CaliforniaPlaya]

Don't know if this is known, I'm not reading through all 31 pages of this. I just talked to a friend who works for Sprint Tech Support. He looked at the trouble ticket for this and said it is a lot of WinMo devices. Sprint is aware and they are waiting for a fix from Microsoft. Also said it should be an ota fix, but isn't positive on that. Unknown eta when I talked to him.

[psycho_maniac]

if its a new rom for this little fix iim gonna be totally p!$$3D, but im sure we could find somebody who could extract the one file we need. as i understand from ziggy

[Rugby Enforcer]

I have used the cab file from Ziggy and that worked fine. However, when I tried to back up my texts it didn't work on several attempts. So now I am trying to just delete the threads, but after a soft reset the messages reappear. They will not go away. Someone please help.

[Telek]

Any update on this?

[Rose4uKY]

So will ther ebe a fix or do I need to install the cab file? I know it mentioned doing stuff to the registry but I wasn't sure if I needed to do that or just install the Ziggy fix cab only? I didn't even notice the 16 until I read it on the Sprint Forums and then came here.. Rose

[ivwonka]

Originally Posted by Rose4uKY

So will ther ebe a fix or do I need to install the cab file? I know it mentioned doing stuff to the registry but I wasn't sure if I needed to do that or just install the Ziggy fix cab only? I didn't even notice the 16 until I read it on the Sprint Forums and then came here.. Rose

the cab does the registry fixes for you. just do one or the other, whichever you prefer. all of your messages with 2016 in them will stay there though. you have to delete them if you want everything to threat normally from here on out. but, yes, eventually microsoft, htc, or your cell provider will fix it but why wait for that?

[m3xicanprid3]

this been post already keep lookng on the list n ull find the rite answer

[m3xicanprid3]

this the the cab to fix the problem Ziggy 2016 Fix.cab

[psycho_maniac]

i think they are asking for a real fix. not a work around. anybody get a reply back from HTC or Microsoft? telling them about this horrible flaw