Originally Posted by monkeyboy (Post 1458216)

are we *sure* this is a network issue, and not a WM bug (and a few other phones) misinterpreting the SMS timestamp year field as an 8-bit hex number rather than the two digits of BCD year that the specs call for?

Originally Posted by Analyzer52 (Post 1458274)

Cab works but editing in excel doesn't work eveything goes fine but pimbackup says "CSV File Error" when going to open it to start the restore. I have no idea why followed the directions exactly.

Any suggestions? Using windows 7 and office 2007

Originally Posted by ziggy471 (Post 1458305)

It doesn't appear to appear to be a network issue, at least if it only effects HTC, LG and a few Samsung devices, but I can't be sure. But from what others are posting, the carriers are saying that HTC and the others are working on a fix.



I've done it with 7 and 2010, and it worked fine. Double check the file to make sure no other changes were accidentally changed. Another issue I've had with PPCPimBackup is that if I don't have the files named with the date in them, it has issues, that one took forever to figure out.

Another option would be do use a regular text editor instead, I recommended Excel because it made things easier to read.


Edit: This worked but now the messages are not thread which defeated the purpose in doing it I hate how pim does this to messages when restoring them.


Z

Originally Posted by fjdollars2008 (Post 1458674)

Wanna hear something funny? So I called sprint tech support about the 2016 issue again this morning and they said they were aware of the issue and were unsure of how long it would be until network timestamps were working properly. They sent a link to my phone with the approved workaround and it's the exact same cab file ziggy created. lol intersting on their part

Originally Posted by scarydok (Post 1459452)

Ok, Hate to burst anyone's bubble on this, but has anyone really considered that this ISN'T a Windows Mobile bug? If you think about it, anyone that received a text on 1/2, 1/3, or even today, 1/4, THAT WOULD CHANGE THE BINARY CODING, AS IT WOULD BE 010210, 010310, OR 010410.
THIS APPEARS TO BE AN ISSUE WITH OUR CARRIERS, NOT OUR PHONES. IF THIS WAS JUST AN ISSUE WITH WINDOWS MOBILE, NON-WINDOWS PHONES WOULD NOT BE EXPERIENCING IT.

Originally Posted by BOO B) (Post 1459499)

Nonwindow phones are not experiencing this. I have 9 phones Sprint and Verizon. Only my 2 windows phones TP1 and a TP2 stock ROMS have this issue. not even my sons hero has this problem and thats HTC.

BOO B)