Fix/Workaround for 2016 Issue - Page 17

fsped69 · #**161** (**permalink**) 01-03-2010, 01:40 PM

I have an HTC Touch with Sprint with stock OS. I tried the patch file with no luck. Hopefully KevinC2021 is correct. I will wait...

ShowYouHow · #**162** (**permalink**) 01-03-2010, 01:45 PM

Quote:

Originally Posted by fsped69

I have an HTC Touch with Sprint with stock OS. I tried the patch file with no luck. Hopefully KevinC2021 is correct. I will wait...

Hmm... I dunno about the Touch, but my TP2 Sprint Stock OS was fixed by it (using Ziggy's cab and my SKTools fix for old messages)
Did you manually edit the registry or use the cab?
Did you soft reset afterward?

Either way, good luck!

a3rdeye · #**163** (**permalink**) 01-03-2010, 03:05 PM

Going to review what has been posted since yesterday but I spoke with Sprint today and this problem is a nationwide issue affecting HTC, LG, and some Samsung phones. Supposible the issue should be corrected by the upcoming week. Thanx for being a much better source than the phone answering carriers PPC

jac187 · #**164** (**permalink**) 01-03-2010, 04:17 PM

manually fixed the registry and soft reset..working good so far. thanks!!

fsped69 · #**165** (**permalink**) 01-03-2010, 05:11 PM

I used the cab file and then went into the registry to confirm the changes, Everything matched the first page. I didn't care about old messages so I didn't run the SKTools fix. I did soft reset. Held the power down, confirmed shutting down. Then I powered up. Sent a text, it showed the time (no date) then when I recieved a text it show the 2016 date.

My friend has the same phone with Verizon The white HTC Touch, he has had no issue at all.

This is odd though. Some are from 2010 some from 2016 and 1 with just the time. Odd.. any thoughts?

villagephotos.com /utils/image.aspx?u=2003-6\249532\untitled.PNG.jpg

Lane03 · #**166** (**permalink**) 01-03-2010, 05:40 PM

Quote:

Originally Posted by vb3

oops. sorry. so do you think it will be alright if i delete that entry if i'm running on a treo pro?

You can delete it and if it undoes the workaround, then just reinsert the key. Keep in mind the treo pro was made by HTC.

scarydok · #**167** (**permalink**) 01-03-2010, 06:25 PM

Ok, I have manually edited the registry and it's now showing received time. But like most people on here, I want to know sent time, not received time.

Also, prior to searching for this fix, I had called the sprint idiots, and of course, this "tech" apparently has had his head in his @$$ and just told me to do a soft reset and that should take care of the issue.

I'll be the first to admit I know little about phones and cell networks, but I wonder how little sprint pays to have such underqualified people working for them? Seriously, these people don't know the first thing about real troubleshooting. "If doing a soft reset doesn't fix it, call us back." That was just his way of saying "I don't know what I'm doing, so I'm going to try to pawn this off on someone else."

**ziggy471** · #**168** (**permalink**) 01-03-2010, 06:34 PM

Quote:

Originally Posted by scarydok

Ok, I have manually edited the registry and it's now showing received time. But like most people on here, I want to know sent time, not received time.

Also, prior to searching for this fix, I had called the sprint idiots, and of course, this "tech" apparently has had his head in his @$$ and just told me to do a soft reset and that should take care of the issue.

I'll be the first to admit I know little about phones and cell networks, but I wonder how little sprint pays to have such underqualified people working for them? Seriously, these people don't know the first thing about real troubleshooting. "If doing a soft reset doesn't fix it, call us back." That was just his way of saying "I don't know what I'm doing, so I'm going to try to pawn this off on someone else."

Without a patch to one of the DLLs, you can only have the receive time right now, that's why this is a workaround for the time being. If your on Verizon, this is how they have it configured by default, so I didn't even know there was an issue until I was chatting with Scientific and he mentioned it.

Z

monkeyboy · #**169** (**permalink**) 01-03-2010, 06:58 PM

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?

Analyzer52 · #**170** (**permalink**) 01-03-2010, 07:26 PM

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