Fix/Workaround for 2016 Issue - Page 18

**ziggy471** · #**171** (**permalink**) 01-03-2010, 07:42 PM

Quote:

Originally Posted by monkeyboy

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?

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.

Quote:

Originally Posted by Analyzer52

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

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.

Z

Analyzer52 · #**172** (**permalink**) 01-03-2010, 08:39 PM

Quote:

Originally Posted by ziggy471

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

I think I got it waiting on it to finish updating, I think something about how excel was saving it was the problem. I backed it up again extracted it with 7-zip changed the extension from csm to txt opened notepad did the find and replace saved it then changed the extension back to csm and now it appears to be working. Anyone with problems might want try that it worked for me.

piercer79 · #**173** (**permalink**) 01-03-2010, 08:59 PM

I've still got an Alltel htc ppc 6800 with WM6.1 Stock Rom here. This does NOT appear to work. Anyone have any ideas for this device?

fjdollars2008 · #**174** (**permalink**) 01-03-2010, 10:35 PM

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

**clueless25** · #**175** (**permalink**) 01-03-2010, 11:18 PM

I know why my SMS isnt available or showing up LMAO I'm on NRGZ's 28011 Dec 29th rom and there is no SMS Key under [HKEY_LOCAL_MACHINE\Software\OEM\SMS]. LOL Dang
Nor does this key show up [HKEY_LOCAL_MACHINE\Software\ Jataayu\Messaging\SMS]
“UseSystemTimeAsRecvTime”=dword:00000001

95FormulaTA · #**176** (**permalink**) 01-04-2010, 05:44 AM

Worked great on my Vogue running Sprints 6.1!

**ziggy471** · #**177** (**permalink**) 01-04-2010, 07:24 AM

Quote:

Originally Posted by fjdollars2008

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

Can you PM me that link please.

Z

scarydok · #**178** (**permalink**) 01-04-2010, 10:23 AM

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.

BOO B) · #**179** (**permalink**) 01-04-2010, 10:46 AM

Quote:

Originally Posted by scarydok

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.

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)

scarydok · #**180** (**permalink**) 01-04-2010, 10:50 AM

Quote:

Originally Posted by BOO B)

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)

Other users, not only on this forum, but also on other forums, have reported this bug on non-Windows phones.