Re: text messages from the future Y2KX issue
I just got off the phone with Sprint Business Support and the Rep I spoke to indicated that it is a HTC issue and are attempting to reach them in an effort to work this issue out.
|
Re: text messages from the future Y2KX issue
mine just show the time as usual, stock rom verizon.
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
There are threads on various forums about this. It's a Windows Mobile issue, not specifically HTC. Someone posted about an LG WM device with the problem, and people on various carriers have reported it. I guess we'll just have to deal with it until someone can find a solution. Hopefully it doesn't take too long.
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
my text messages are not sayng that but is saying 1/1 from those im recieving a text from then mine say the time,
|
Re: text messages from the future Y2KX issue
I guess I fail to understand how this would be a hardware-specific issue? Or was the assertion that it's somehow related to HTC-produced software code (Sense)?
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
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. Looks like a HTC/Windows 6.x comination issue. I dont see any posts showing issues with other phones running winmo 6.x (may be wrong though) |
Re: text messages from the future Y2KX issue
I'm 100% stock, just activated my phone two days ago and it's got the 2016 issue. It certainly isn't life threatening but it is a bit annoying. Hope the fix comes soon.
|
Re: text messages from the future Y2KX issue
pretty sure my stores Samsung Intrepid is doing it as well, Ill check
|
Re: text messages from the future Y2KX issue
Well I am not using touch flo, I use spb shell and I have it use the default messaging client.
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
The microsoft viewer is using whatever settings you have set in regional settings to display the date/time, as does HTC. Interestingly enough mine only started showing 2016 after 2:00am EST - prior to that I got messages in fine with the correct 10/01/01 date. After 2am they started displaying with 16/01/01! Also my GF's S720 may also have the problem - incoming messages are displaying (1/1) instead of their usual time. She's running WM6.1 stock Telus ROM. |
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
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.
Quote:
|
Re: text messages from the future Y2KX issue
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. |
Re: text messages from the future Y2KX issue
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. |
Re: text messages from the future Y2KX issue
I love WinMo! Could be worse, it could have tweeked all of our calendars and really screwed some people up!
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
My brother says his AT&T Fuze doesn't have the problem. Maybe it's CDMA carriers?
|
Re: text messages from the future Y2KX issue
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?
|
Re: text messages from the future Y2KX issue
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...
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
*holy crap! 12 pages!* |
Re: text messages from the future Y2KX issue
Quote:
http://forum.ppcgeeks.com/picture.ph...&pictureid=483 |
Re: text messages from the future Y2KX issue
But that isn't 16 in binary ...
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
in Hex it is... |
Re: text messages from the future Y2KX issue
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 |
All times are GMT -4. The time now is 04:57 AM. |
Powered by vBulletin® ©2000 - 2024, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com