Any phone with the '2016 problem'?

[kangrk]

Hello to all of you and happy new year. (it is the new year there, right? I had my new year 13 hours ago.)



With the new years day, almost all of the Korean version of LG phones faced the 2016 problem. That is, in the txt inbox the received date of the message is shown as the year of 2016 instead of 2010.


LG is currently working on the problem and MASS amount of money is expected to be put into fixing the problem since there are too many phones with the problem.

It seems to be the problem on almost all of the phones that were launched on the market since 2005, with all carriers.



Wondering if North American/Asian/European version of LG phones have this problem too.


Inbox->Text. MMSes or Outbox txts don't have this problem.

[evolv]

I am having this same issue on a HTC Touch Pro 2 with a custom rom. Some of the other forums I am on, users are experiencing this exact same problem.

[WarRaven]

Just checked my new LG IQ, its working normally, shows the correct date.

ALmost sounds like a carrier issue then if a HTC has it.

WR

[wstaylor]

This seems to be an issue only in the Shell SMS Viewers on Windows Mobile Phones. Windows Mobile Messaging viewers are displaying the correct date because their format is m/d where the after market SMS threaded viewers are using the date format m/d/yy and that is where the issue is - either Microsoft is passing a bad variable to the SMS viewer or the SMS viewers themselves are sending bad display data.

Either way this is affecting Windows Mobile Phones across all carriers - appears to be only with SMS viewers that are non-native to Windows Mobile and is not localized to just the United States.

I have a Mighty ROM TP2, a Stock ROM Mogul with SPB Shell and both of those phones are being affected by the issue. I have an HTC Hero with Android that has no such issue.

Check your Windows Mobile native SMS viewer and see if the issue appears. I believe this is only with 3rd party SMS Viewers.

[wstaylor]

It is strange that the organization of the native Windows Messaging viewer is in order because it is relying on the date format d/m - so in the threaded messaging viewer in Windows Mobile it shows:



USER 1/1:

Happy New Year!

ME 12:01am:

You too!

USER 1/1:

My Windows Mobile Phone is FUBAR

ME 12:03am:

Mine is too!!!



But in the HTC Touch Flow Viewer it is showing in this format:

ME 12:01am:

You too!

ME 12:03am:

Mine is too!!!

USER 1/1/16:

Happy New Year!

USER 1/1/16:

My Windows Mobile Phone is FUBAR



So, my post earlier was premature - the organization of the threaded messages does not appear to rely on the year in Windows Mobile Messaging - but it does in the 3rd party Messaging Viewer.



This is INDEED a Microsoft issue.

[AzureeSoleil]

Have an HTC 6900 - with no SMS - yes on texting, on a CDMA North America network, mid-sized carrier in the Mid-Atlantic area - wmexperts (http://www.wmexperts.com/y2016-sms-bug) seem to have a work around and noticed these symptoms:

Here's what we know as of now:

•Messages received after 1/1/2010 may be dated as 2016
•Effects WM6.1, WM6.5 and even non-Windows Mobile phones
•It is ROM independent, meaning switching won't help
•All Some carriers seem to be experiencing this bug, but T-Mobile seems fine
•HTC and LG are aware, but no official response yet