text messages from the future Y2KX issue

[ajac]

Originally Posted by dOOfus

same issue here, energy 2.1, applies only to incoming sms

same here custom rom 6.5.3 and getting messages from 2016. Man I wish they would tell me how 2016 is give me some lottery ticket numbers

[psycho_maniac]

Originally Posted by laxman12786

I'm pretty new to all of this, but if that were the case wouldn't it be ALL Sprint and Verizon phones (or at least all of the TP2's) that would be affected?

Seems more likely to me that it's an issue with either a variable type or the way the date variable is passed. If its a hex variable and gets a "10" passed to it, it would be interpreted as 16.

Hence, "09" = 09 ---> 2009
"10" = 16 ---> 2016.

i like this theory. seems like an easy fix also seems like a fix on the server side right? not on the phone side? should we call in and complain? would they even understand what were are talking about when we mentioned this? there solution is to do a hard reset or send in the phone to get a different one.

[rorytmeadows]

Phone: Touch Pro2
Carrier: T-Mobile USA
Location: Spencerport, NY
Rom: Stock
Have this bug: No

[OR78]

Originally Posted by psycho_maniac

i like this theory. seems like an easy fix also seems like a fix on the server side right? not on the phone side? should we call in and complain? would they even understand what were are talking about when we mentioned this? there solution is to do a hard reset or send in the phone to get a different one.

So is it safe to say our phones are now dumbphones given they can't understand binary code?

[themuffinman]

Originally Posted by psycho_maniac

i like this theory. seems like an easy fix also seems like a fix on the server side right? not on the phone side? should we call in and complain? would they even understand what were are talking about when we mentioned this? there solution is to do a hard reset or send in the phone to get a different one.

Its definitely on the server side. I used my tmobile sim today and I haven't had the issue at all but once I switch back to sprint its doing it.

[brownhornet]

This shlt is annoying as hell when you're texting in a threaded conversation

[mikejones13]

Originally Posted by psycho_maniac

i like this theory. seems like an easy fix also seems like a fix on the server side right? not on the phone side? should we call in and complain? would they even understand what were are talking about when we mentioned this? there solution is to do a hard reset or send in the phone to get a different one.

LOL, I called North America HTC support this morning as soon as I woke up. And the guy "Bill" had no clue about this bug. I explained to him it wasn't just one carrier but several. He said HTC is currently looking into it and they don't know when it will be fixed, since it was the first time he had heard of it. What really sux is that I am still getting paid the same as I was in 2009, maybe its time to find a new job.

[lipidfats]

that'd be cool if they cant fix it... then i can use it as an excuse to convince sprint to give me my upgrade price early for the next best phone that comes out this year j/k

[kabuk1]

I honestly don't see this as that big a deal. We all know what year it is, I doubt anyone's gonna mistakenly think it's 2016 based on a text message.

I like the hex theory too though. Makes sense.

[NeroDan]

Originally Posted by kabuk1

I honestly don't see this as that big a deal. We all know what year it is, I doubt anyone's gonna mistakenly think it's 2016 based on a text message.

I like the hex theory too though. Makes sense.

I think the problem is more that since it puts times for outgoing and just a date for incoming, threaded messaging gets all sorts of out of order.