text messages from the future Y2KX issue

[MightyMike]

threads merged.

[meatgel]

Sprint TP2, running ROM from Calkulin's kitchen with no manila ... and no 2016 issue. My threaded messaging is in order and all from 2010.

[bkrodgers]

Originally Posted by MightyMike

threads merged.

Good, you survived new year's eve! But I'm afraid you partied so hard that you passed out for 6 years! It's now 2016!!!!

[MightyMike]

Originally Posted by bkrodgers

Good, you survived new year's eve! But I'm afraid you partied so hard that you passed out for 6 years! It's now 2016!!!!

*looks at his phone.. holy moly!*

MightyROM still reigns supreme in 2016!!!!

[lipidfats]

I have the bug on sprint tp1 and tp2. has this been confirmed for other WinMo devices, not just HTC? What about other platforms?

[cptok]

Originally Posted by ScooterG

Phone: Touch Pro2
Carrier: T-Mobile
Location: Orange County, CA
Rom: EnergyROM "Leo" 28011, Dec 31, Sense 2.5
Have this bug: No

More annecdotal evidence this may be an SMS-C issue (SMS gateways). T-Mobile users don't seem to have the issue - but sprint, verizon etc. do. Same type of evidence by country as well.

Sticking by my earlier prediction that the carriers will own up to this sooner or later.

[psycho_maniac]

Originally Posted by MightyMike

*looks at his phone.. holy moly!*

MightyROM still reigns supreme in 2016!!!!

must be REALLY GOOD if im running the 12.27.09 rom still in 2016! HAHA

[MightyMike]

Originally Posted by psycho_maniac

must be REALLY GOOD if im running the 12.27.09 rom still in 2016! HAHA

lol, if my phone looks like this in the year 2016, I'm going to be one super pissed mouse!

HTC Innovation my ass

[laxman12786]

Originally Posted by cptok

More annecdotal evidence this may be an SMS-C issue (SMS gateways). T-Mobile users don't seem to have the issue - but sprint, verizon etc. do. Same type of evidence by country as well.

Sticking by my earlier prediction that the carriers will own up to this sooner or later.

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.

[krid80]

Originally Posted by MightyMike

threads merged.

welcome aboard the Y2KX train, MM. 2010 starts out with this EPIC FAIL