|
||||
Re: text messages from the future Y2KX issue
Quote:
|
|
||||
Re: text messages from the future Y2KX issue
Quote:
I cannot confirm what you said about the native message viewer. The Windows messaging on my phone also displays the incorrect date 1/1/16 on top of TF3D. I do agree with you however that this is a Win Mo issue since this appears across different carriers, different brands (HTC, LG from what I've seen), and non windows mobile phones do not seem to be experiencing this issue. This doesn't sound good for us Sprint TP2 users since this resolution will probably get bundled into the WM6.5 release which could delay it even more... |
|
||||
Re: text messages from the future Y2KX issue
Happy 2016!!! Here's a reg edit to fix this issue: HKLM/SOFTWARE/FUTURE TEXTS/AM I DRUNK/OH WELL HAPPY NEW YEAR WHATEVER YEAR IT IS set value to 2010 LOL
|
This post has been thanked 5 times. |
|
||||
Re: text messages from the future Y2KX issue
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. |
![]() |
|
Tags |
2016 y2k |
|
|