I don't want to use TMo's app. I'm sure it'll just have ads or do data collection or just otherwise be bad -- it only has 3.5 stars in the play store and looks to be filled with bugs. You guys suck for dropping support of the built in android voicemail feature which worked just fine.
Ugh. Stuff like this, my terrible reception at home, and the sprint merger make me think more and more about switching -- and I've been a t-mo customer for 15 years!
+12
magenta9400132 wrote:
It's easier to blame t-mobile in this case because:
a) I have two identical devices. It works on one and not the other.
b) someone else in this thread had it working, then it stopped, then they switched carriers and it worked again.
c) other people in other forums on the internet had the same problem with different carriers. They called the carrier, the carrier fixed a setup issue, and then it worked.
Again - why are you in this thread? You don't have an issue - congrats. A lot of us do and are still waiting for an explanation.
a) Then it shows T-Mobile isn't trying to charge people for VVM. It just isn't working correctly. I pointed this out, but people keep pushing the conspiracy they got a text stating they were going to start charging for it.
b) Carriers don't have the same requirements or systems for VVM so it may worrk for one and not the other.
c) Yes and if you read those forums other people may still have problems even after calling it. Things don't always work 100% of the time.
As I mentioned earlier people with the stock app have been having problems as well. It may be a problem with 5G roll out as well as IMS(Universal Profile/RCS) being worked on.
I don't care why it's not working. I care that it's not working, many signs point to a t-mo problem, and they are ignoring it. I'm not a developer. I'm not paid for the hours I've wasted trying to troubleshoot the issue.
Why are you in this thread? Are you a t-mo employee? You have added zero to the discussion and have only confused the issue.
+12
magenta9400132 wrote:
Why are you in this thread? Are you a t-mo employee? You have added zero to the discussion and have only confused the issue.
I didn't confuse the issue. Someone brought up conspiracy theories not me. No I am not an employee. They've already said multiple times. If there is a problem with 3rd party apps they can't help you because they did not develop the app in question. It works for some and not for others doesn't mean it points to it being a T-Mobile issue. As with software as I pointed out before may work for some and not for others. You will find the same thing on customer boards. It's one thing for it not working with first party apps but another with 3rd party apps.
tidbits wrote:
magenta9400132 wrote:
Why are you in this thread? Are you a t-mo employee? You have added zero to the discussion and have only confused the issue.
I didn't confuse the issue. Someone brought up conspiracy theories not me. No I am not an employee. They've already said multiple times. If there is a problem with 3rd party apps they can't help you because they did not develop the app in question. It works for some and not for others doesn't mean it points to it being a T-Mobile issue. As with software as I pointed out before may work for some and not for others. You will find the same thing on customer boards. It's one thing for it not working with first party apps but another with 3rd party apps.
Yes, it is clearly and demonstrably a TMo issue.
Logs have been provided in this and other threads from affected devices showing that the device is asking the carrier for configuration and the carrier is not providing it. It is called provisioning.
Your boneheaded denial is just as dumb but much louder and exacerbating than the few conspiracy theory voices. Just be thankful and pray that your devices are still not affected.
tidbits wrote:
magenta6790580 wrote:
VVM was never free or if you want to spit hairs, included in the service we pay for? I've always understood the transcribing to be extra but not regular VVM. What most here are talking about is not transcribing but native VVM in the stock android dialer. It's broke or has been removed from certain devices.
I think most people here have no idea why it's not working and are looking for answers. It also seems like you think people are making this up. I'm referring to the standard VVM that has worked fine for years on certain devices with or without transcribing now doesn't. I don't care if transcribing works or not and I'm fine if T-Mobile wants to charge extra for it, just want to know why regular VVM is now broke.
I am saying that text for a charge is advertisement for VVM to text. As you stated earlier you got a text saying something about a charge, and I said it was for VVM to text as I have gotten that multiple times on multiple times. Google h as updated their dialer app at least 14 times(beta included) in the past 2 months. Google simply could have broken it and has nothing to do with T-Mobile. It's always easier to blame T-Mobile because Google can do no wrong(evil) seems to be the norm.
My response earlier in this thread was to vcolombo about what someone (T-Mobile?) told him. Sounded like they were trying to get more money with a better experience from VVM.
I never stated I got a text saying something about a charge. I might have mentioned (in this thread or another) a text that I received that, to me, seemed to be the magic trigger for my devices to have native VVM stop working. As I l clearly stated previously I don't care if T-Mobile wants to charge extra for transcribing, don't have to pay for it and I won't.
Yes, it's been updated many times but that doesn't explain why the same version on a Pixel 3 works and doesn't on the PH-1 or a Pixel 2. That would make sense for another OEM's dialer though. I'm not blaming anyone, I have no idea who to blame. Not blaming here but this situation seems to be a T-Mobile issue, since it works just fine on another carrier (Fi). It also seems T-Mobile can do no wrong.
+12
user401 wrote:
tidbits wrote:
magenta9400132 wrote:
Why are you in this thread? Are you a t-mo employee? You have added zero to the discussion and have only confused the issue.
I didn't confuse the issue. Someone brought up conspiracy theories not me. No I am not an employee. They've already said multiple times. If there is a problem with 3rd party apps they can't help you because they did not develop the app in question. It works for some and not for others doesn't mean it points to it being a T-Mobile issue. As with software as I pointed out before may work for some and not for others. You will find the same thing on customer boards. It's one thing for it not working with first party apps but another with 3rd party apps.
Yes, it is clearly and demonstrably a TMo issue.
Logs have been provided in this and other threads from affected devices showing that the device is asking the carrier for configuration and the carrier is not providing it. It is called provisioning.
Your boneheaded denial is just as dumb but much louder and exacerbating than the few conspiracy theory voices. Just be thankful and pray that your devices are still not affected.
show these logs please I would love to see it.
First off, the native dialer is built into the Android OS it's not a 3rd party app. Secondly; my payment amount per month hasn't changed in 8yrs. Third; I'm on a postpaid plan and this feature still no longer works. So your other "postpaid" point ain't true tidbits.
J. Davis on Android
On Wed, Aug 14, 2019 at 7:47 PM, tidbits<no-reply@t-mobile.com> wrote:
#yiv9991906968 * #yiv9991906968 a #yiv9991906968 body {font-family:Helvetica, Arial, sans-serif;}#yiv9991906968 #yiv9991906968 h1, #yiv9991906968 h2, #yiv9991906968 h3, #yiv9991906968 h4, #yiv9991906968 h5, #yiv9991906968 h6, #yiv9991906968 p, #yiv9991906968 hr {}#yiv9991906968 .yiv9991906968button td {}
|
T-Mobile Support |
|
|
It sucks TMo is disabling android native visual voicemail
reply from tidbits in Android products - View the full discussion
+12
Yes it's a 3rd party app... It isn't designed by T-Mobile or any other carrier for their network. Google wrote it so it's a 3rd party app. Do you understand and why T-Mobile doesn't guarantee it will work with their network and services as they didn't write the software.
You want to see faster results put it in here and have it elevated to the point Google can't ignore it and watch how fast it get fixed. 😊
By that logic, if t-mobile changes their service such that my android phone can't make calls, send texts, or receive internet data that ain't t-mobile's fault and I should take it up with the 3rd party dev.
+12
magenta9400132 wrote:
By that logic, if t-mobile changes their service such that my android phone can't make calls, send texts, or receive internet data that ain't t-mobile's fault and I should take it up with the 3rd party dev.
If T-Mobile changed their service then it would be broken for EVERYONE except T-Mobile's own app. That's why there is provisioning in the event T-Mobile changes something, and provisioning always get updated first to reflect old and new before T-Mobile switches over(or any carrier for that matter).
+15
If it works on some devices but not others. It isn't the service. It's the device and or app.
Okay now riddle me this; if both of my phone's are using the exact same Google phone app stock dialer that was already pre-installed on them from the OEM, how come VVM from that dialer only works for one of my devices and not both like it used to? It's strange how this feature still works on my 2016 phone but not my 2017. So, I'm going to tell you the same thing that I told "tidbits"; let's agree to disagree.
J. Davis on Android
On Fri, Aug 16, 2019 at 9:43 AM, syaoran<no-reply@t-mobile.com> wrote:
#yiv7971564660 * #yiv7971564660 a #yiv7971564660 body {font-family:Helvetica, Arial, sans-serif;}#yiv7971564660 #yiv7971564660 h1, #yiv7971564660 h2, #yiv7971564660 h3, #yiv7971564660 h4, #yiv7971564660 h5, #yiv7971564660 h6, #yiv7971564660 p, #yiv7971564660 hr {}#yiv7971564660 .yiv7971564660button td {}
|
T-Mobile Support |
|
|
It sucks TMo is disabling android native visual voicemail
reply from syaoran in Android products - View the full discussion
Visual Voicemail is a provider side feature. There might be apps included with the OS that do support the feature, but the feature itself is tied to your phone number, not your device. What an app supports, does not support, and how that support changes over time is almost always a result of something changing in the app.
If you actually think T-Mobile's VVM system is so comex, that it will play favorites with devices. I am going to say, that is silly. That would be asking for issues that would arise with every device update and app that supports VVM access. The system is simple. It works like your APN. If the settings are correct, it works! If those settings are not correct, it doesn't work.
Reply to this message by replying to this email, or go to the message on T-Mobile Support |
Start a new discussion in Android products by email or at T-Mobile Support |
Following It sucks TMo is disabling android native visual voicemail in these streams: Inbox |
This email was sent by T-Mobile Support because you are a registered user.
You may unsubscribe instantly from T-Mobile Support, or adjust email frequency in your email preferences
|
Only if they changed it for everyone. All the evidence in this VVM case points to a change at an account level. Once the change is made, there's no going back. So if they made a similar change for voice/text/data, you'd be in the thread defending them for for some unknown reason. You're acting as if you're being paid to defend them. You aren't affected by the change, you're adding nothing to the solution, you at some point weren't even referring to the correct issue, and you're defending them in spite of overwhelming evidence that they caused the change. For the 4th time: why are you in this thread?
If I have two identical devices and versions of the app, and it works on one and not the other, it's the service. Not the device or app. If it stops working on one person's device, and they switch carriers and it starts working again, it's the service, not the device or app.
+12
magenta5733023 wrote:
Okay now riddle me this; if both of my phone's are using the exact same Google phone app stock dialer that was already pre-installed on them from the OEM, how come VVM from that dialer only works for one of my devices and not both like it used to? It's strange how this feature still works on my 2016 phone but not my 2017. So, I'm going to tell you the same thing that I told "tidbits"; let's agree to disagree.
J. Davis on Android
Not all devices are the same. They may look the same they may have the same name, but they are not the same. Like with the original Pixel for example. Some people lost their mics. They were all produced from the same plants as all the other ones, and all from different batches. A difference of a solder location before off by a micon changes things(even if it is within tolerance). These things can affect software and makes it hard to pinpoint problems looking at it at face value. As I mention before send logs to Google and let them figure it out. If it gets elevated fast enough watch how fast the problem is fixed.
Also, if the t-mo twitter account tells someone in this thread that they changed their service, it's the service.
+12
magenta9400132 wrote:
Only if they changed it for everyone. All the evidence in this VVM case points to a change at an account level. Once the change is made, there's no going back. So if they made a similar change for voice/text/data, you'd be in the thread defending them for for some unknown reason. You're acting as if you're being paid to defend them. You aren't affected by the change, you're adding nothing to the solution, you at some point weren't even referring to the correct issue, and you're defending them in spite of overwhelming evidence that they caused the change. For the 4th time: why are you in this thread?
They wouldn't change it for some of them. So we are going to change VVM for some users because we can... We are not going to change it for everyone because that would be easier to do. You understand? When working with a system that does all or nothing for the most basic services you have to write a lot of code to change something to affect a single person. VVM is a basic service built into the base plans like calls, texts, and such. If it wasn't then it would be an addon like VVM to text which has a core cost. So you are telling me T-Mobile is willing to spend a few millions of dollars to take people off VVM?
If we go post it on a Google forum, are you going to troll that thread too and tell us it's a carrier problem? Because right now there's a ton of evidence that it's a carrier problem and none that it's an OS problem, other than your hopes and wishes.
Lolololol you know exactly how they roll out features and run their business. As if no business has ever changed features for some customers and not others. Hahahaha
You're a gigantic troll, a paid employee, or an absolute moron. For the 5th time, why are you in this thread?
+12
magenta9400132 wrote:
If we go post it on a Google forum, are you going to troll that thread too and tell us it's a carrier problem? Because right now there's a ton of evidence that it's a carrier problem and none that it's an OS problem, other than your hopes and wishes.
Actually I provide source code for changes and I help log information and submit them to Google. No I do not work for Google, but I like Android as a platform. I even help on linux boards as well. I have helped out more people on this board more than you care to imagine. I am showing you right now one of the fastest way to get something fixed, but you treat it as trolling because you are hearing something you don't like to hear. You don't want to do legwork to fix your problem. Can't help someone who is unwilling to help themselves.
I would like to see this evidence. You have failed to provide evidence. Everything so far is anecdote.
Your "postpaid" point about this feature is still invalid. And like I stated before, how come it works on one of my devices and not both like it used to?
+12
magenta9400132 wrote:
Lolololol you know exactly how they roll out features and run their business. As if no business has ever changed features for some customers and not others. Hahahaha
You're a gigantic troll, a paid employee, or an absolute moron. For the 5th time, why are you in this thread?
Yes I know how a network works. I used to work for a large network for the DoD. Network management has never changed much over the years. Any advancements to networks has always come from Military complex needs for information. So yah have fun with that. Show me a business that has rewritten software just to removed a small handful of people off a service they provided that is bundled in all their plans?
+12
magenta5733023 wrote:
Your "postpaid" point about this feature is still invalid. And like I stated before, how come it works on one of my devices and not both like it used to?
It contradicts your whole argument you are working. If they are kicking people OFF the stock dialer for VVM then both shouldn't work for both devices. Remember it is supposed to be tied to the account and there's a switch that is supposed to block it remember? So what now?
"You don't want to do legwork to fix your problem. Can't help someone who is unwilling to help themselves.
I would like to see this evidence. You have failed to provide evidence. Everything so far is anecdote."
I don't want to do the legwork? I've spent hours searching for solutions, including over an hour with a clueless rep trying 5 different guesses for fixes.
I've provided the evidence. It's been provided in this thread ad nauseum. You're choosing to ignore it. Why would I waste my time posting it again? If I post a quote from John Legere saying they broke VVM you'll still say it's a Google problem. I've lost count, is this the 5th or 6th time I've asked: why are you in this thread?
o
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
