Fix/Workaround for 2016 Issue

[ziggy471]

Originally Posted by psycho_maniac

told me he is going to let his supervisor know also so maybe this can be a national thing also. im still on the phone lol.
verizon ticket number: 00000 339 5874

lets get the word out, sprint has a fix soon so should we

Sprint's fix should also work on VZW, since it will most likely be a patched DLL. It appears from what I've been reading, that the issue is that the date is BCD, Binary Coded Decimal, but the phone is interpreting it as standard Hex. In BCD, 10 is represented as 0x10, which is the same thing as 16 if just interpreted as raw Hex. Once it's released, I'd bet it's a modified SMS.dll or RILPHONE.dll, since RILPHONE is the only DLL that I could find that queries that key.


Z

[dumpringz]

Wirelessly posted (HTC Touch Pro 2 (Sprint): Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

i got the correct date now just not timestamp for when text was received. i dont know if any1 else mentioned the half fix but im at work n dont have time to search. in any event at least its gotten somewhere

edit- scratch that ... only 1 text was right the rest that just came in 100mph all are screwy again.

[ziggy471]

I've found the function that's causing the issue, or at least I think I have. The subroutine in RILPHONE.dll that accesses the reg key is at 0x100722C8, and it is only called by 2 other routines, 0x10075080+1C8 and 0x10076A40+45C. Both of those functions read the SystemTime, then run the folowing code starting at loc_10075270:

CMP R0, #1
BNE loc_10075270
ADD R0, SP, #0x34+SystemTime ; lpSystemTime
BL GetSystemTime
ADD R1, SP, #0x34+SystemTime ; void *
MOV R2, #0x10 ; size_t
ADD R0, R5, #0x54 ; void *
BL memcpy
B loc_10075280

loc_10075270

R3, R7, #0x400
ADD R0, R3, #0xD9
ADD R1, R5, #0x54
BL sub_100744C8
LDR R3, [R4,#4]
ORR R3, R3, #0x40
STR R3, [R4,#4]

loc_1007528C ; CODE XREF: sub_10075080+1B0j

ADD SP, SP, #0x10
LDMFD SP!, {R4-R11,LR}
BX LR

sub_100744C8 is dealing with TimeZoneInformation and FileTimes and converting SystemTime to FileTime. Filetime is how MAPI stores it's datetime.

Well, at least we know where the issue is now, maybe someone at HTC has found the same thing and patched it.



Z

[Scientific]

Originally Posted by ziggy471

I've found the function that's causing the issue, or at least I think I have. The subroutine in RILPHONE.dll that accesses the reg key is at 0x100722C8, and it is only called by 2 other routines, 0x10075080+1C8 and 0x10076A40+45C. Both of those functions read the SystemTime, then run the folowing code starting at loc_10075270:

CMP R0, #1
BNE loc_10075270
ADD R0, SP, #0x34+SystemTime ; lpSystemTime
BL GetSystemTime
ADD R1, SP, #0x34+SystemTime ; void *
MOV R2, #0x10 ; size_t
ADD R0, R5, #0x54 ; void *
BL memcpy
B loc_10075280

loc_10075270

R3, R7, #0x400
ADD R0, R3, #0xD9
ADD R1, R5, #0x54
BL sub_100744C8
LDR R3, [R4,#4]
ORR R3, R3, #0x40
STR R3, [R4,#4]

loc_1007528C ; CODE XREF: sub_10075080+1B0j

ADD SP, SP, #0x10
LDMFD SP!, {R4-R11,LR}
BX LR

sub_100744C8 is dealing with TimeZoneInformation and FileTimes and converting SystemTime to FileTime.

Well, at least we know where the issue is now, maybe someone at HTC has found the same thing and patched it.



Z

You're spending WAY too much time on this issue Zig! lol

[ziggy471]

Originally Posted by Scientific

You're spending WAY too much time on this issue Zig! lol

I got really bored imaging laptops today, sorry.......

Remember what I said in IRC, I Can't let the machines win. Hey maybe I should rename myself to John Conner.



Z

[Bradleyj44]

Worked for me thanks again!!!

[Mr.Gas]

Just to let everyone know. I am using stock Sprint rom with Sprint tp2 tweaks and the first reg entry fixed it for me. Thanks again everyone for your dedication!

[trailmix]

Just to be clear, without the registry edit, Sprint continues to have the 2016 problem.

[Mayonesa]

IN THE YEAR 20166666666

[OR78]

THUNDER BEADS IN 2016!!!!!! WOW...