There is currently a bug that is affecting some devices out there including Windows Mobile Phones. Apparently, text messages sent after 1/1/2010 are showing up with a date of 2016. The problem has not been identified yet but some are speculating that it has to do with how computers store information.
To make it simple the hex value of 10 ie the 10 int 2010 has a decimal value of 16 hence the 2016 issue. There is not confirmation from Microsoft but this is a valid theory. Computer weekly stated Some IT bloggers said the problems have arisen because programmers in the build up to Y2K did quick fixes which effectively made any two-digit date less than 10 a date in the 2000s, while anything greater than 10 was pushed back into the 1900s. They also mentioned that Dow Jones reported that Deutsche Sparkassen und Girovemad (DSGV) Bank where hit with a 2010 software error that affected chip and pin cards. We will see if that turns out to be the case. However my speculation is that this is on the carrier side not the Phone, because the dates are stamped through the network. A work around as been posted by the guys at WMEXPERTS. The workaround modifies the registry to use the date and time on the phone instead of the Network.
Here are the instruction we found at Pocketpc-live.com
Just grab a free Registry editor and modify the following
[HKEY_LOCAL_MACHINE\Software\OEM\SMS]
“RecvTimeStamp”=dword:00000001
Or you can grab this patch here.
I can already see the Windows Mobile Haters dancing naked around a bond fire in celebration, but allow me to rain on your parade. iPhone users, let’s not forget the SMS bug that allowed someone to take over your phone only 6 months ago . I think I would rather have a wrong date then have someone sober, drunk dialing my contacts.
Blackberry users, need I say more about the constant outages impacting ALL customers?
And for the Android users are you sure we can type reboot in a text message without rebooting the phone or how about clearing the frequently called list on the DROID, OOF!!
