View Single Post
  #168 (permalink)  
Old 01-03-2010, 06:34 PM
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 scarydok View Post
Ok, I have manually edited the registry and it's now showing received time. But like most people on here, I want to know sent time, not received time.

Also, prior to searching for this fix, I had called the sprint idiots, and of course, this "tech" apparently has had his head in his @$$ and just told me to do a soft reset and that should take care of the issue.

I'll be the first to admit I know little about phones and cell networks, but I wonder how little sprint pays to have such underqualified people working for them? Seriously, these people don't know the first thing about real troubleshooting. "If doing a soft reset doesn't fix it, call us back." That was just his way of saying "I don't know what I'm doing, so I'm going to try to pawn this off on someone else."
Without a patch to one of the DLLs, you can only have the receive time right now, that's why this is a workaround for the time being. If your on Verizon, this is how they have it configured by default, so I didn't even know there was an issue until I was chatting with Scientific and he mentioned it.


Z
Reply With Quote