text messages from the future Y2KX issue

[krid80]

Originally Posted by i4get75

http://search.twitter.com/search?q=1%2F1%2F16

Seems it's more widespread. Just saw someone with a Palm Treo with the problem also. Check this Twitter search, people having the same problem

LOL awesome. And I freaking love that "Y2KX" showed up in a couple of tweets. Kinda fun to know I coined the term.

[OR78]

Not to burst your bubble but this was discussed in a Sprint forum and it was rumored that a "Y2KX" problem was in some phones. Someone beat ya to it bud.

[krid80]

eh, no big deal. seems nothing is ever original anymore with all them internets these days

[rube77]

Verizon stock here, and no show of the "y2kx" bug in any messages so far! Im using the threaded messages and have looked at all the times and they only state "today" and the time ...no dates except from ones received yesterday which state 12/31/09....so hopefull this tp2 is one of the lucky ones.

[fceeviper]

[pastert33]

Originally Posted by rube77

Verizon stock here, and no show of the "y2kx" bug in any messages so far! Im using the threaded messages and have looked at all the times and they only state "today" and the time ...no dates except from ones received yesterday which state 12/31/09....so hopefull this tp2 is one of the lucky ones.

Are you using touchflo?

[cptok]

I'll going to go out on a limb here and predict that this is an SMS gateway issue - not WimMo or HTC. All the evidence so far seems to point to that... and I'm betting that most carriers (maybe except T-Mo?) are using the same SMS gateway infrastructure.

[revolver_ocelot911]

i'm using a uscc touch pro with psyki final and all of the texts that i have recieved today also say 1/1/16

[Malatesta]

Adam Lein (pocketnow) confirmed with me his TMo TP2 is unaffected; same with Phil's Moto Droid on Verizon.

Strange.

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

[demonizator]

I don't experience this issue on my TP (running Gen.Y R1)