Fix/Workaround for 2016 Issue

[Mylt1]

i believe it is the same across the board. i was one of the people that figured out this string so we knew when we actually received text. im a paid fire fighter and get text notifications from our 911 center and wanted to know what time calls come out instead of just knowing there was a call last night.

[fusion]

Wirelessly posted (Opera/9.5(Microsoft Windows; PPC; Opera Mobi/16643; U; en) HTC_Touch_Pro2)

Originally Posted by NeroDan

I don't use manila...it happens in the native sms client. Everytime I softreset, I have to open each convo and let it lock up and do it's thing for awhile. I also just leave the sms/mms prog running in the backround. I keep hoping new builds will fix it. It never happened in 6.1 with over 10,000 messages, in 6.5 it becomes noticable after about 50 messages from one person. Blah.

i was having the same issue with sms hanging forever.. i flashed back to stock rom, did a clear storage and then flashed back to mightyrom 12.30 and things r good now

[ziggy471]

Originally Posted by Mylt1

i believe it is the same across the board. i was one of the people that figured out this string so we knew when we actually received text. im a paid fire fighter and get text notifications from our 911 center and wanted to know what time calls come out instead of just knowing there was a call last night.

Until about an hour ago, I thought this was how it was supposed to work, at least all my phones I've had on VZW have worked this way. I understand why you definitely need the correct time, but not everyone does. I just hope that the carriers fix the problem in their servers, or one of us writes a program to intercept the text message, check the year, and correct just the year.

I'm reading up on the MessageInterceptor Class right now to see if it can be easily done.


Z

[xxceenotexx]

Originally Posted by ziggy471

All,

Here's the fix for the 2016 bug, it's already been tested by Sci.



Z

thank u sir!

[Mylt1]

there was actually a LOT of people that wanted the actual sent time when the TP first came out. of course im sure there are a lot of people that dont turn there phones off at night as well. i like my sleep and wanted a work around so several of us in the TP forum searched till we found that string and worked on it till we had it figured out. then someone actually make it into a cab to save time. but as you said, the original 1 was set so the time received was what was posted instead of the time sent. not sure why this was done because every other phone i had before posted the sent time and not received. i figured thats how it would have been for the TPII but i guess they just left it alone.

[Tim Smith]

I'm using MightyROM Void on Verizon and the cab posted to fix this fixed it for me.

[madjokeer]

wow finally a fix to this issue, i been having this after mighty rom started to make the project roms.. thank you sir for this!!!!!!!!!!!!!!!!

Special Thanks To Ziggy!!!

I have to say that this is the quickest response to a sudden issue such as this. Didn't realize it could be solved that easily and within the same day. Nice touch putting this in a .cab format for those who aren't comfortable editing regristy files. Thanks again man. A.K.A. f50ferori from XDA-Developers

[ziggy471]

Alright, to explain what is happening with the RecvTimeStamp flag. If you read the SMSMessage Class for Windows Mobile, there are two fields representing the date, LastModified (when it was sent) and Received. My guess is that RecvTimeStamp forces the phone to use receive time instead of sent time. Now just to figure out how to get it to read LastModified correctly.



Z

[HTCotta]

Wait has anyone gotten this fix to work for HTC Messaging Client? I'm still receiving texts from the future...