Kevo1110
22nd June 2009, 01:50 PM
Hi everyone!
I've been going through this ENTIRE forum, and countless others on top of dozens upon dozens of google searches, and I still haven't found a solution to my SMS timestamp error.
All the solutions offered up by people seem seriously promising, because they seem to help a lot of people, and that is what's kept me hopeful: that someone out there/in here can help me fix this problem.
Basically, I have an unlocked Fido Motorola Q9h, that is being used on the Rogers network. Never delved into flashing my device, cuz I was happy with WM6. Not to mention I'd got it tweaked to a very lovely point :)
Then a week ago, my phone locked up after I'd put my phone into airplane mode (I'd done this countless times before with no issue), and just would not let me turn the antenna back on. Nothing I tried worked, so of course I eventually caved and did a hard reset. That was when I figured I would give WM6.1 a try, seeing as how my device was gonna be starting from scratch anyway.
I flashed to an unlocked AT&T WM6.1 ROM, and went ahead with all the registry tweaks to remove all the bloatware. Phone is pretty damn clean if I do say so myself. I've got PHM on there, GPSID, CHome COnfigurator, and that's really about it.
After all that was said and done, and I got my first SMS, I realized the message was timestamped 4 hours behind. Every single SMS from every single contact shows timestamped 4 hours earlier. In the threaded SMS stream, my messages are timestamped correctly, but the other peoples' aren't.
Example:
Me (7:37): Send me a text to see if this timestamp issue's been fixed.
Steph (3:37): Okay =)
The strange thing is that MMS messages come in with the correct timestamp, and that is something that seriously boggles my mind.
Please, please, PLEASE. If anyone out there has some kind of suggestion, I would absolutely love to hear it. Here are the remedies I've tried that have had no effect:
-Installed DST cab from Microsoft.
-"TrustTimeZoneField" w/DWORD value of "0" minus quotations of course ;)
-"TrustTimeZoneField" wDWORD value of "1" to allow the device to trust the provider's time just in case my phone was screwing up.
-"RcvTimeStamp" w/DWORD value of "1"
-tweaked some "NetworkTimeSync" (or something along those lines) entry to a value of "1" instead of its current value of "0," but nothing.
I'm at the end of my rope here guys and girls, so please, anything you can suggest that I haven't already tried would be infinitely appreciated :)
Thanks in advance everybody :)
I've been going through this ENTIRE forum, and countless others on top of dozens upon dozens of google searches, and I still haven't found a solution to my SMS timestamp error.
All the solutions offered up by people seem seriously promising, because they seem to help a lot of people, and that is what's kept me hopeful: that someone out there/in here can help me fix this problem.
Basically, I have an unlocked Fido Motorola Q9h, that is being used on the Rogers network. Never delved into flashing my device, cuz I was happy with WM6. Not to mention I'd got it tweaked to a very lovely point :)
Then a week ago, my phone locked up after I'd put my phone into airplane mode (I'd done this countless times before with no issue), and just would not let me turn the antenna back on. Nothing I tried worked, so of course I eventually caved and did a hard reset. That was when I figured I would give WM6.1 a try, seeing as how my device was gonna be starting from scratch anyway.
I flashed to an unlocked AT&T WM6.1 ROM, and went ahead with all the registry tweaks to remove all the bloatware. Phone is pretty damn clean if I do say so myself. I've got PHM on there, GPSID, CHome COnfigurator, and that's really about it.
After all that was said and done, and I got my first SMS, I realized the message was timestamped 4 hours behind. Every single SMS from every single contact shows timestamped 4 hours earlier. In the threaded SMS stream, my messages are timestamped correctly, but the other peoples' aren't.
Example:
Me (7:37): Send me a text to see if this timestamp issue's been fixed.
Steph (3:37): Okay =)
The strange thing is that MMS messages come in with the correct timestamp, and that is something that seriously boggles my mind.
Please, please, PLEASE. If anyone out there has some kind of suggestion, I would absolutely love to hear it. Here are the remedies I've tried that have had no effect:
-Installed DST cab from Microsoft.
-"TrustTimeZoneField" w/DWORD value of "0" minus quotations of course ;)
-"TrustTimeZoneField" wDWORD value of "1" to allow the device to trust the provider's time just in case my phone was screwing up.
-"RcvTimeStamp" w/DWORD value of "1"
-tweaked some "NetworkTimeSync" (or something along those lines) entry to a value of "1" instead of its current value of "0," but nothing.
I'm at the end of my rope here guys and girls, so please, anything you can suggest that I haven't already tried would be infinitely appreciated :)
Thanks in advance everybody :)