text messages from the future Y2KX issue

[subzero1313]

Originally Posted by jsowder

if it only shows the time, I think that means the year is correct, if it were not correct the month/year would appear

Sounds right. So Im leaning towards HTC issue and LG people are liers

[moc426]

Mine shows only time for all messages in and out for today in threads. The older messages show the dates as I expect. All seems fine on mine.

Originally Posted by jsowder

if it only shows the time, I think that means the year is correct, if it were not correct the month/year would appear

[jsowder]

UPDATE: Im in the USA on Sprint

I have two phones: Touch Pro W/ Window Mobile 6.1 CE OS 5.2.19965 Build 19965.1.2.3 (Stock OS)
AND
Touch Pro 2 W/ Windows Mobile 6.5 CE OS 5.2.21887 Build 21887.5.0.86 (Mighty ROM WAR)

Touch Pro exhibits this behavior:
using windows text messaging, in the list of threaded messages (groups) all INCOMING messages display 2016. If I click on the threaded text which displays all messages in that group, each individual INCOMING text shows the correct date.

Touch Pro 2 exhibits this behavior:
using HTC text messaging, in the list of threaded messages (groups) the dates shows correctly, if I select a threaded message and look at each individual message in that group the date for INCOMING is 2016, outgoing is the correct date.

[doogie]

So to try and sum things up so far..

Your Windows Mobile 6.1/6.5 device may show SMS messages sent or received after 12:00am 1/1/2010 (local time) being sent or received in the year 2016, when the messages are viewed in Threaded mode. MMS messages seem unaffected.

No fix has been published yet, and although LG and HTC seem to be aware, no official statement has been made. Your carrier's Customer Support resources may not have complete information, and may give you inaccurate or anecdotal info until official word is out.

Devices, regions and carriers affected:
Seemingly any Windows Mobile 6.1 or 6.5 device, any carrier, any region..although it's not completely certain at this point. Positive repros on Touch Pro 2, Touch Pro and Mogul.

See http://www.howardforums.com/showthread.php?t=1606400, where some non-WinMo LG devices are exhibiting the problem.

Software affected:
Your choice of stock/custom ROM does not seem to change the problem. Mixed reports of SPB Shell and TouchFlo/Sense exhibiting the behavior. Native WinMo messaging software seems to consistently repro.

Reporting additional scenarios (positive or negative)..it's helpful to have specific software versions (OS, TouchFlo/Sense/SPB Shell), custom ROM name and version (if applicable), carrier, country you live in.

[keentech]

I love WinMo! Could be worse, it could have tweeked all of our calendars and really screwed some people up!

[slidebabyslide]

Originally Posted by journeyman846

Same problem here, verizon wireless using MightyRom.

Same problem as him

[Mazda Charles]

My brother says his AT&T Fuze doesn't have the problem. Maybe it's CDMA carriers?

[subzero1313]

Do the days and dates in 2016 match up with 2010?(Im lazy) If so, couldnt you change the time to 2016? Retarded "fix", but would it work?

[subzero1313]

Odd stretch here, but could it have anything to do with todays date being binary? 010110? which translates into.........16........Like I said, Looooooooong stretch, but hey...

[jsowder]

Originally Posted by subzero1313

Do the days and dates in 2016 match up with 2010?(Im lazy) If so, couldnt you change the time to 2016? Retarded "fix", but would it work?

Then your calendar is hosed