Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
~John |
Re: text messages from the future Y2KX issue
Good news or maybe bad news, the same here in China, on China Telecom, seems to be a fault of HTC.
|
Re: text messages from the future Y2KX issue
I am from philippines and i am using SPRINT CDMA/GSM phone, i am on GLOBELINES telecom, my text messaging is OK, yes it is OK. everything reads fine, im using MM's war 3 rom and have the HTC messaging disabled.
|
Re: text messages from the future Y2KX issue
I am also experiencing this issue. At first I thought it could be just messages coming from rogers users. I am on Telus network using Mighty War rom.
|
Re: text messages from the future Y2KX issue
happy new years guys!!! i have the same problem just noticed it when i seen this thread. lol thats some funny stuff
|
Re: text messages from the future Y2KX issue
I am really late but I am running Mighty rom War on sprint and i have the same issue, but i didn't know until i read this thread and looked @ the date on my phone WoW
|
Re: text messages from the future Y2KX issue
looks like this is a bigger issue than just our smart phones.
http://www.howardforums.com/showthre...highlight=2016 |
Re: text messages from the future Y2KX issue
Quote:
This look like a huge problem...but an easy fix. |
Re: text messages from the future Y2KX issue
I saw it too at 12:10AM
|
Re: text messages from the future Y2KX issue
I have similiar issues, except in the WinMo Text Thread, it just shows 1/1 with no date. On the TouchFlo tab it does show 2016.
But all my texts are coming in out of order and doesn't show a timestamp. Weird ain't it? |
Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)
I woke up with the same issue this morning & the 1st thing I thought to do was check ppcgeeks to see if anyone else was having the same issue. Glad I'm not alone! |
Wirelessly posted (HTC Touch Pro 2: Opera/9.80 (Windows Mobile; WCE; Opera Mobi/WMD-50286; U; en) Presto/2.4.13 Version/10.00)
Quote:
|
Re: text messages from the future Y2KX issue
Quote:
|
Wirelessly posted (Opera/9.5(Microsoft Windows; PPC; Opera Mobi/16643; U; en) HTC_Touch_Pro2)
Quote:
|
Re: text messages from the future Y2KX issue
BOth of my TP2's and my TP have the problem. It has to be a WinMo issue. That isn' t stopping me from complaining to Sprint for carrying a phone with a serious defect lol. I'm going to give them a lot of guff this morning so they can yell at HTC.
|
Re: text messages from the future Y2KX issue
i dont think its a rom issue.. i am using MM's war 3 rom and everything is ok with me. no 2016 year, all 01/01/2010, i reside in the philippines. and i bought my phone in the us, using sprint CDMA/GSM phone.
|
Wirelessly posted (AdrianH85(TP2): Opera/9.5(Microsoft Windows; PPC; Opera Mobi/16643; U; en) HTC_Touch_Pro2)
i wonder what txtes we going to get in 2012 then |
Re: text messages from the future Y2KX issue
I noticed this also last night. I was running Mighty-Rom Sense 2.1 12/19/2009. I flashed over to 12/30 this morning and having the same issue.
|
Re: text messages from the future Y2KX issue
I got the same thing on Mightys Sense ROM. My coworker has a Snap, but everything is fine. SO maybe a WinMo Professional issue?
|
Re: text messages from the future Y2KX issue
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. |
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
Same problem, wouldn't mind it as much if it didn't disorganize everything.
|
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
|
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. |
Re: text messages from the future Y2KX issue
same, Sprint, Stock ROM, TP2
|
Re: text messages from the future Y2KX issue
Same here. Sprint TP2 with stock ROM.
|
Re: text messages from the future Y2KX issue
My wife and I are both having the problem on our Sprint Touch Pro 2s. Mine has the latest EnergyROM Leo and hers is stock.
|
Re: text messages from the future Y2KX issue
I'll just add I checked my brother's Sprint stock rom and he's having the same problem.
|
Re: text messages from the future Y2KX issue
lol. I just called verizon to see if they had received notice or other reports of people complaining about this (i know it isn't carrier specific, but i can dream that the device manufacturers send notice of problems to the carriers) and not only did i get the "no i'm sorry sir, we have heard nothing about this problem" i was also told that "it could be because we are in the northeast and it hasn't hit us yet" after i told her this problem has been reported world wide and also asked me if i had any other problems with my driod eris after i said "Windows Mobile devices" about 40 times in the course of the call...
sigh... I'm just gonna use my friends here at ppc geeks for any tech support problems I have, k? also, google searching hasn't found a fix yet. |
Re: text messages from the future Y2KX issue
This suuuucks, calling no2chem? Haha i was laying in my bed this morning when i noticed it (too drunk last night to either notice or care) and I was just thinking, I'm gonna go on PPCGeeks and this will be on the front page, i hope it's easy to fix. Now I'm bummed.
|
Re: text messages from the future Y2KX issue
Quote:
Same problem but I wouldn't mind having all my messages say its from 2016 |
Re: text messages from the future Y2KX issue
Quote:
My girlfriend's Snap is showing the issue.... In her messaging it just showing the date and month.... Normally the time would show from recieved and sent messages until the day passes then show the date and month.... All of her recieved messages show 1/01 but her sent messages show sent time.... |
Re: text messages from the future Y2KX issue
Having the same problem as everyone else. I don't care for the threaded messaging anyway. There is a .cab that disables threaded sms that I found at xda-developers called sms_mode_V31.cab (I cannot post links yet) that I'm thinking of trying. Obviously won't fix the 2016 thing, but at least it would make the out of order convo problem moot.
|
Re: text messages from the future Y2KX issue
instead of Y2kX (2010) wouldn't it be better to call it the Y2KXVI (2016) issue? if it was saying 2010 it wouldn't really be an issue would it?
or maybe MMXVI Issue or how about the Y2K4^2 issue? |
Re: text messages from the future Y2KX issue
Quote:
Hey I can't seem to find this reg entry. Wait a min... I see what you did there! :laughing6: |
Re: text messages from the future Y2KX issue
Quote:
|
Re: text messages from the future Y2KX issue
So no one has figured out a fix for this problem?
Im on MightyRom 12/30 and all my texts show 2016.. i guess were waiting for an official fix? Happy new year all! |
Re: text messages from the future Y2KX issue
Quote:
|
All times are GMT -4. The time now is 02:30 PM. |
Powered by vBulletin® ©2000 - 2024, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com