Fix/Workaround for 2016 Issue
 

First off, read the WHOLE post, there are things for n00b’s and HardCore users alike.

The Rilphone files posted here are for CDMA/GSM TouchPro2 only, use on any other phone may require a Hard Reset for your phone to work again.

1/27 - Added the 6.1 21052 Rilphone, since many users have been asking for it.
Also to clarify, the USC Rilphone cab is 6.5 21874.

1/16 - Just cabbed the USCC Rilphone for anyone using War or any ROM that uses the USCC OEMDrivers. This is from the Official HTC update posted last night for the USCC phones. If you want to fix the dates in existing messages, make sure to download and run the CorrectSMSDate also.
I tested it on War 12-30 and if Sci was around he would have said 'works like a champ'.

Here's the workaround for the 2016 bug, it's already been tested by many many users:

[HKEY_LOCAL_MACHINE\Software\OEM\SMS]
"RecvTimeStamp"=dword:00000001

You might also need this one, I didn't on MightROM War, but other 2.5 with Native HTC Messaging might:

[HKEY_LOCAL_MACHINE\Software\ Jataayu\Messaging\SMS]
“UseSystemTimeAsRecvTime”=dword:00000001

If you would rather not do registry edits by hand, there is a CAB attached.

For those that don't know how to install CAB files, here's a nice little video:
http://www.mobiletopsoft.com/board/2...pocket-pc.html


What this workaround does is that it tells the phone to date the incoming messages with the current time on the phone. This can be a problem if you have the phone turned off when the message was originally sent to you. When your phone is turned back on, it will receive all the messages sent to it while it was off, and date them at that time.

This is the default way that Verizon has their phones setup, so since I’ve been with them forever, and already had that key set, I didn’t notice the issue. Scientific had the issue, so I started looking through my ‘tweaks’ and found this key and had him try it. His response was ‘It works like a Champ’, so I posted it. I thought it originally was a Fix and not a workaround and posted it as such, again I’ve been with VZW forever, and thought this is how the SMS messages should be dated.

If you have a ROM build with the SSK Kitchen, Calkulin’s Kitchen or PPCKitchen.org BuildOS (with Verizon selected), this will not be an issue for you, since they already have the key in there. There are probably more ROM’s out there that set this in their Provisioning CABs, but I’m not going to download them all to check, I’m on MightROM War, and have no desire to change, been running MightyROM’s since 10-29 and LOVE THEM. Sorry to the other Chef’s I know you work hard on your ROM’s, I just plan on sticking with Mike for now.

With that said, I’m still looking into whether this can be fixed on the phone another way, read patch either SMS.dll or RILPHONE.dll, since RILPHONE.dll is the only one that I’ve found that reads the key.

The screen shots that I attached are from War 12-30 in Native HTC Messaging, in other words, it doesn’t show the year, but it does show that they were on the correct day.

If you already have messages dated from 2016, you’re options are to delete them or to do the following:
1.Backup your messages with PPCPimBackup
http://www.pocketpcfreeware.com/en/index.php?soft=1806
2.Uncheck the “Binary backup (faster)” option
3.Connect your phone, and select use as Disk Drive
4.Open Windows Explorer or My computer or hit “Windows Key”-E
5.Go to your PPC SD Card, the new Removable Disk that just appeared
6.I use 7-Zip for my compression program, so right click on the PIMBackup_YYYYMMDD.pib file, select 7-Zip->Open archive. If you need 7-Zip: http://www.7-zip.org/download.html
7.Extract the msgs_YYYYMMDD.csm file
8.Using Excel, import the file as a semi-colon delimted text file. Open file, select the delimiter as semi-colon.
9.Now press ‘Ctrl’-H, find and replace, in the ‘Find what’ field, enter ‘2016,01,01’ (It’s YYYY,MM,DD,HH,mm,SS), and in the ‘Replace with’ filed, enter ‘2010,01,01’. Change the day or leave it out, that’s your option.
10.Exit Excel, when asked if you want to keep it in Unicode Text format, select Yes.
11.Copy the msgs_YYYYMMDD.csm file back to your SD card, you should still have it connected as a Disk Drive. You ONLY need the ‘.csm’ file.
12.Disconnect your phone from the computer.
13.Open File Explorer on your phone.
14.Click on the msgs_YYYYMMDD.csm file, it should now open PPCPimBackup for you in restore mode.
15.Click ‘Next’ then ‘Next’. On the ‘Restore options’ page, leave it at the default, ‘Delete all existing messages from the Database’
16.Click Done, it will now restore your messages.
17.Soft reset for good measure.

Now here's a better way to fix your timestamps on SMS messages from the future. I just attached the CorrectSMSDate program from the Diamond and Touch Pro SMS fix cab file. Just extract the exe from the zip, copy to your phone and run.


Z

Re: Fix for 2016 Issue
 

so is this just a work around or really a fix? i still would like the date and time in my timestamps

Re: Fix for 2016 Issue
 

any confirmation if this actually works?

Re: Fix for 2016 Issue
 

Some further detail documentation as to what this change does please? This REG edit has been around for a long time and some confirmation is necessary please.

Re: Fix for 2016 Issue
 

Confirmed. Working for me.

Re: Fix for 2016 Issue
 

Since I didn't have this issue, I started looking at my reg files that I import from SDConfig for MM War. I noticed this one, don't remember why I set it, probably because I could, and since Scientific had the same issue, I had him test it, and it worked.

I did edit the first post with another key I found today while dis-assembling the HTC Messaging client trying to find a fix for the Sprint users. It should also work for anyone using native HTC Messaging on 2.5.1922, but I haven't tested that one.

NeroDan, thanks for the confirmation, now I can confirm three working.


Z

Re: Fix for 2016 Issue
 

how bout a confirmed screenshot?

Re: Fix for 2016 Issue
 

working on sprint tp2 energy phoenix, but didn't fix the msgs that were already messed up

thanks

Re: Fix for 2016 Issue
 

I tried the 2.5 fix. didn't work. Is there a space b/w the time? Also, I didn't have that entry. I had to create it?

Re: Fix for 2016 Issue
 

just did the first reg edit, worked for my MightyROM REV. 12/30. also checked my gf's TP1 that wasnt having the issue and she already had this entry.

Re: Fix for 2016 Issue
 

ok, i was able to do all of what was suggested but became lost with this part----->"RecvTimeStamp"=dword:00000001
where do i input this info?

Re: Fix for 2016 Issue
 

For all my friends who were flipping out, I told them I was messaging them from the future! It was kind of funny. =)

Re: Fix for 2016 Issue
 

Oh yeah! And it worked, thanks for that!

Re: Fix for 2016 Issue
 

Running stock USC Rom and dont have either entry

Re: Fix for 2016 Issue
 

Works perfect for MM Impact ROM :thumbleft:

Re: Fix for 2016 Issue
 

seriously? you cant just take our word that this fixed our issue? Just try it and see if it works, its not going to destroy your phone.

Re: Fix for 2016 Issue
 

You need to add the reg entry...

Re: Fix for 2016 Issue
 

I dont have the SMS string
Do I need to add it in?
Im running the Offical MightyROM 12/30

Re: Fix for 2016 Issue
 

Yeah you have to add a new string. I'm also running MightyRom 12/30 DWORD. Its pretty easy, you should be fine. :thumbleft:

Re: Fix for 2016 Issue
 

dude chill out! it was just a simple suggestion. you dont have to get all pissed over nothing.

Re: Fix for 2016 Issue
 

Can someone explain to me what the issue actually is?

Re: Fix for 2016 Issue
 

I can confirm this works (on my TP1)

It tells tmail.exe to use the received time stamp (calculated by the device) and not the sent time (received through the network)

Re: Fix for 2016 Issue
 

Re: Fix for 2016 Issue
 

There's a whole thread about the issue...ziggy posted a fix here in this thread.

http://forum.ppcgeeks.com/showthread...&highlight=WAR

Re: Fix for 2016 Issue
 

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?

Re: Fix for 2016 Issue
 

If no one beats me to it, I'll cab it up when I get home.

Re: Fix for 2016 Issue
 

Re: Fix for 2016 Issue
 

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

Re: Fix for 2016 Issue
 

not sure, but i like it :)

Re: Fix for 2016 Issue
 

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

Re: Fix for 2016 Issue
 

This has been tested with MightyROM WAR 12/30. WORKS!!

For all that can't find the reg here are instructions to add it.(Using Resco Registry)

1. Go to HKLM/SOFTWARE/OEM/
2. Add Key named "SMS"
3. Now open the SMS folder so you are at HKLM/SOFTWARE/OEM/SMS
4. Add Dword value and name it RecvTimeStamp
5. Place 00000001 into value and select Hex
6. Soft Reset

Hope this helps anyone wary of reg edits, and big ups to the solution finder.

Re: Fix for 2016 Issue
 

the screens in the first post don't show the date, only time

Re: Fix for 2016 Issue
 

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

Re: Fix for 2016 Issue
 

Check first post, just did it, took like 1 minute. Much faster than re-installing Mobiler to take the screen shots.


Z

Re: Fix for 2016 Issue
 

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

Re: Fix for 2016 Issue
 

maybe this is offtopic? what else is in the SMS folder? I actually had to add the SMS folder because that wasnt even in my registry which i thought was odd. running MR 12.27.09

Re: Fix for 2016 Issue
 

i had to create a new key so there was nothing

Re: Fix for 2016 Issue
 

Hmm - my only problem with this is that I frequently lose my signal at work, and it is nice to know when someone SENT me a text message that I receive at 5:30pm when I go home. With this fix it will just say 5:30pm, right? I guess we just have to wait for Sprint to fix it on their end then - tech support is completely closed today for the holiday so I'm hoping that's the only reason it hasn't been fixed already.

Re: Fix for 2016 Issue
 

I am on MightyROM LOVE3 [winmo6.5.5 (28014.5.5.0) manila 2.1 (2.1.19202217.5)] 12/27 release and the first fix seems to work fine for me.

Re: Fix for 2016 Issue
 

Now i see why they call them smart phones u have to be smart to operate one lol Just got the phone couple days ago now this im still learning the basic features let alone how to edit the REG.

SO far your post seems the most understandable if I only knew how to get to step 1?? Anyone??