Quote:
Originally Posted by willysp
Your title says "fix/workaround" - what's the "fix" in the 3rd party SMS Gateway?
TIA!
|
Quote:
Originally Posted by psycho_maniac
if this is the only fix we will be getting that is gonna suck. i wanna know when the personn sent it not when i got it.
|
Quote:
Originally Posted by almatic
I didn't read all the posts, but some of my texts are dated this year and some are not. Can that be explained?
I had always thought that the reason texts are dated 2, 3 or even more hours later when I am roaming had to do with the tower that relayed the text imprinting it's own time stamp. But perhaps I was incorrect in my guess.
I'm not doing the fix as it's not that important to me, I am more interested in the root cause of it.
|
The root cause, at least what I can tell is in the assembly code I already posted in
#193. It is in RILPHONE.dll, it's converting the date improperly from Binary Coded Decimal. It's just that I haven't worked in assembly in longer than I'd care to say, but it was on an IBM CS1, if anyone even knows what that is, and if you do, you probably know me.
The only reason I still have 'Fix' in the thread title, is that for some, this would be considered a fix. VZW has this set as default, until 1 Jan while sitting in IRC and Sci mentioning this, I didn't even realize that you could find out when a SMS was actually sent.
I'm not sure if this is of help to anyone, but I looked at the VZW MR1 release yesterday, and RILPHONE.dll has changed a little in the functions that convert the dates. I'm not sure if any of the Chef's plan on using the OEM's from it to build any newer releases to see if it fixes the issue. I really have no desire to go back to 2.1, so I haven't flashed MR1, but anyone else that wants to, go ahead. Once flashed, change the key to 0, since VZW sets it to 1, and see if it works.
Z