Re: Fix/Workaround for 2016 Issue
 

Working just fine on my VZW TP2 running MM War 12-30 with HTC Messaging 1.5.19222911.0.


Z

Re: Fix/Workaround for 2016 Issue
 

I'm on sprint and wish i could report the same, also on mightyrom WAR 12/30. Any ideas?

EDIT: It just started working! Thanks for the quick fix!

Re: Fix/Workaround for 2016 Issue
 

I wish it were a true fix, it just a workaround for now. The 'fix' just tells the phone to use the received time instead of the sent time. I'm currently on a short break from looking at the files to see if it can be patched to provide a better fix. The only real fix I can think of, that's if it's not an issue with WinMo or HTC, is that the providers need to fix their servers.


Z

Re: Fix/Workaround for 2016 Issue
 

i appreciate that bro,thanks for taking time to look into this.unfortunately im not experienced enough yet to know how to help.

Re: Fix/Workaround for 2016 Issue
 

its a shame that someone was able to find and create a fix for this problem before microsoft, desgraciados!!

Re: Fix/Workaround for 2016 Issue
 

It's just a workaround for now. The real issue is that the SMSMessage->LastModified (Date/Time sent) is off by 0x6B9B1FF124000 (6 years in FILETIME format, 100-nanoseconds since Jan 1 1601).

This should be able to be fixed slightly better by using an IMailRuleClient, checking the PR_LAST_MODIFICATION_TIME and if it's 6 years off, subtract six years. It sounds easy enough, but it's time to get a little sleep, been up for 25 hours now and I NEED SLEEP or caffeine.


Z

Re: Fix/Workaround for 2016 Issue
 

ROTFL, that's what God invented caffiene for (or Meth-Amphetamine) ;-)

~John

Re: Fix/Workaround for 2016 Issue
 

Did the reg edit and it seems to not list 01/02/16, but the time on my texts....Thanks.

Re: Fix/Workaround for 2016 Issue
 

Hi, does anyone know how to un-install this fix?

Re: Fix/Workaround for 2016 Issue
 

Either delete the reg key if you did it manually or uninstall the cab.


Z