View Single Post
  #93 (permalink)  
Old 01-02-2010, 02:39 AM
ziggy471's Avatar
ziggy471
Geek with a Gun
Offline
Threadstarter
Location: NoVA
 
Join Date: Oct 2009
Posts: 744
Reputation: 6575
ziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Fix/Workaround for 2016 Issue

Quote:
Originally Posted by Mylt1 View Post
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
Reply With Quote