Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

Phone: Touch Pro2
Carrier: Sprint CDMA
Location: NC
Rom: Stock
Have this bug: Yes

Phone: HERO
Carrier: Sprint CDMA
Location: NC
Rom: Stock
Have this bug: nope...

I just text to my HERO, hero seems fine, so I think its WM problem..

anyway, Happy New Year 201? Everyone :)

Re: text messages from the future Y2KX issue
 

Re: text messages from the future Y2KX issue
 

I must have had a good new years if I didn't make it here until 22 pages in.

And yes, Mighty 6 Alltel TP on V; 2016 here also. Time to read these two hundred some odd posts and see if there is a fix.

:P

Re: text messages from the future Y2KX issue
 

Tried this on my TP1 on Sprint ROM and it had no effect - the problem still persists.

Re: text messages from the future Y2KX issue
 

Yup. Same Here. VZW TP2 running WAR. Also for some reason my text msgs are in the begining of the conversation and the persons are at he bottom if that makes any sense. Even tho its the threaded view. The txt messages are out of order.... weird......

Re: text messages from the future Y2KX issue
 

Just tried that on Sprint, sent myself a text, and it was dated 1/1/16. I'm still texting myself from the future. (I should have texted myself the 2010 Superbowl winner)

Re: text messages from the future Y2KX issue
 

Actually, "technically" they are in order. Because the ones you are RECIEVING (being dated 1/1/2016) are being read by the program as coming after the ones you are SENDING (being dated 1/1/2010).

...if that makes sense.

Re: text messages from the future Y2KX issue
 

ok well mine just went back to 2016... it worked for 4 msgs and is now back saying its 1/1/2016

Re: text messages from the future Y2KX issue
 

Phone: Touch Pro 2
Carrier: Sprint
Location: Orlando, Fl
Rom: ENERGYRom LEO
Have this bug: Yes

Re: text messages from the future Y2KX issue
 

Yea, I thought of that before I fully understood the issue. Since the problem is only limited to incoming texts and thus associated with data coming along with the text, changing the time locally wouldn't have any bearing.

I'm still interested in knowing if the problem will be fixed when tomorrow comes (1/2/10).