|
|
||||
Re: Fix/Workaround for 2016 Issue
why does the .cab add a second entry
<characteristic type="HKLM\Software\Jataayu\Messaging\SMS"> <parm name="UseSystemTimeAsRecvTime" value="1" datatype="integer" /> ??? whats Jataayu? |
|
||||
Re: Fix/Workaround for 2016 Issue
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." |
|
||||
Re: Fix/Workaround for 2016 Issue
Quote:
Z |
|
||||
Re: Fix/Workaround for 2016 Issue
its interesting how confused our providers are when we try to alert them of the issue, their unwillingness to fix it also shows that they're in it for the $$$ and not customer satisfaction. desgraciados!
|
|
||||
Re: Fix/Workaround for 2016 Issue
The Sprint CSR I spoke with said she had a TON of phone calls about this issue today (they were closed yesterday when it began), and they have people working on the issue (no estimate on how long it will take to fix). I'm guessing not much will get done until the experts get back from the holidays. I understand the quality of CSR varies widely so you just had a less-informed one.
|
![]() |
|
Tags |
2016 y2k |
Thread Tools | |
Display Modes | |
|
|