tmo_maxwell wrote:
Glad you're staying on top of everything, keep us updated opwog!
Let me know when to expect my paycheck for doing your job because it is actually t-mobile people who should be following up on this and keeping the rest of us updated, not the other way around.
So to follow up on my previous post, of course I never got that call back, so when I called in I spoke to a new rep who said that it was still open as a "master" or "global" ticket, but that they had no ETA for when it may get fixed. Also, "global" for T-mobile doesn't mean all over the world, but means that the known issue affects several functions of the device (as the terminology was explained to me). I think that this is limited to the devices that have received and keep receiving the update that they are obviously still pushing out, but the initial "unable to connect" errors and subsequent wifi calling errors happen to smaller numbers of people within those groups. I couldn't get any estimate of how many people that this is affecting in various negative ways, so it is tough to get an idea what kind of priority this is getting on the programmers end to get fixed. The rep said that the master ticket for this was opened on February 3 (a month already) and and he said that he sees master tickets sometimes take several months to fix, but pointed out that the oldest one that he could see open in the system was from October of 2012 and still wasn't fixed.
Obviously, none of this is good to hear as a customer.
So instead of waiting for somebody like me to keep the issue updated, how about you or one of teh other t-mobile team on these forums, now goes and researches this from the inside to see what kind of priority that you can get this issue to get fixed and then report back to us. They are obviously still pushing out this car wreck of an update, as there are still new people coming on here and posting that they are now getting these issues: