Fix/Workaround for 2016 Issue

[ziggy471]

Originally Posted by psycho_maniac

thats what i wanna know. and i also would like to know if this is a work around or an actual fix? because the theory is that its on the server side. and i mean it worked 24 hours ago why would all of a sudden the date be wrong?

It's an actual fix, it's letting the phone put the time stamp on the SMS, and the phone's time is correct. I think the issue is with the client. I did give two different keys, but the first one DOES work with HTC MC 1.5.1922, at least it does for me.

If I feel up to it tomorrow, I'll look more into it, I'm just tired of looking at ARM Assembly for like 10 hours today trying to fix the Sprint Native HTC Messaging issue in 2.5.

BTW, I HATE ARM ASSEMBLY, sorry CMon, I know you love it. lol


Z

[psycho_maniac]

Originally Posted by NeroDan

Whoa! Yours shows the date too...is that a feature of 6.5.x?

i think so. i have 6.5 and it doesnt show the date. its nice.

Originally Posted by ziggy471

It's an actual fix, it's letting the phone put the time stamp on the SMS, and the phone's time is correct. I think the issue is with the client. I did give two different keys, but the first one DOES work with HTC MC 1.5.1922, at least it does for me.

If I feel up to it tomorrow, I'll look more into it, I'm just tired of looking at ARM Assembly for like 10 hours today trying to fix the Sprint Native HTC Messaging issue in 2.5.

BTW, I HATE ARM ASSEMBLY, sorry CMon, I know you love it. lol


Z

all im wondering is why did it normally work 24 hours ago but now it seems to be broken? what has changed in the new year? sorry im a very curious person lol

[ziggy471]

Originally Posted by psycho_maniac

i think so. i have 6.5 and it doesnt show the date. its nice.



all im wondering is why did it normally work 24 hours ago but now it seems to be broken? what has changed in the new year? sorry im a very curious person lol

Just wait until 2038 when the C TimeStruct runs out of seconds to count since 1/1/1970. It should be about as exciting as spending new years 2000 waiting for our systems to fail, thank god I lived in Colorado and we ran on Zulu (GMT), so I could actually enjoy the new year.

We did have fun at the media's expense though, we ran out of the building yelling and screaming about how we needed to get to the 'Mountain', but instead, left and went home.


Z

[OR78]

Wanna know something funny. All of my new years day text messages show 01/01/10. And I never installed this workaround. I consider this cab or reg edit a workaround not a fix. I think the network will fix itself.

[k0nkuzh0n]

yeah its deff a workaround, although its a fairly good one. Its quite possible that some people would prefer the timestamp method used in this workaround as opposed to using the date received with the text.

It really comes down to would you rather the timestamp be:
1. when the person actually sent it (which is the one that is off by 6 years right now)
or
2. when you actually received it

Its really just a personal preference that we were not given the option to change previously.

For 99% of your texts the time difference wont matter, but I'm pretty sure if you had your phone off, or there was a delay in receiving the text for some reason (which happens from time to time, not specific to the TP2, but can happen to any phone) the time will be different.

I use to have a phone that almost every text would be timestamped 3 or 4 minutes earlier then when I actually got it (which would mean it took me 3 or 4 minutes to get the text, or someone's clock is off).

[Speedy133]

because the theory is that its on the server side. and i mean it worked 24 hours ago why would all of a sudden the date be wrong?