Last I saw, it appeared that OTA Marshmallow 6.0 on Moto X Pure Edition had voice call problems with VoLTE enabled, on T-Mobile.
The workaround was to disable VoLTE (Disable "Enhanced LTE"), to maintain good voice calls quality.
Can anyone offer info on whether this is still a problem with OTA MM, T-Mobile, and VoLTE?
I'm staying with 5.1.1 until I see this resolved, either on T-Mobile end, MM, or maybe with a fix to some offending component or app.
TIA...
Please everyone let Motorola know about this bug so that they will fix it.
https://forums.lenovo.com/t5/Moto-X...l-audio-after-MM-upgrade-w-VoLTE/td-p/3239629
I read that thread a while back. My conclusion was there was insufficient resources when the screen off when on VoLTE. I'd think using a kernel manager with a custom kernel would let you set a higher cpu speed with the screen off, or maybe enable more cores to be available.
There still no fix for VolTE voice calls bug on this phone?
No fix. Motorola/Lenovo is basically ignoring us. You can see this in the long running Motorola support forum thread. Kernel change does not help as it has been tried already. Moto sucks.
That's a bummer. I think I'm going to return it before I loose the window. My last phone was an LG G2 and the VoltE worked flawlessly. It is sad that a newer/better specs phone is worse in that area than a 2013 phone.
Sent from my XT1575 using Tapatalk
If I downgrade to KitKat the bug will still be there? Or maybe use another modem/radio?
hachuelo said:
If I downgrade to KitKat the bug will still be there? Or maybe use another modem/radio?
Click to expand...
Click to collapse
KitKat does not exist for this device. Lollipop does not have the VOLTE bug. But you will loose band 12 LTE.
I don't think this is a Lenovo issue. I'm on AT&T and pretty much they only support VoLTE on their branded phones. Blame your carrier, not the phone. VOLTE does work on Verizon as I know two other people with this phone on VZ and once they got MM update, it worked.
Sent from my awesome phone!
aybarrap1 said:
I don't think this is a Lenovo issue. I'm on AT&T and pretty much they only support VoLTE on their branded phones. Blame your carrier, not the phone. VOLTE does work on Verizon as I know two other people with this phone on VZ and once they got MM update, it worked.
Sent from my awesome phone!
Click to expand...
Click to collapse
That could be true. T-Mobile tells me they are aware of it.
kevev said:
That could be true. T-Mobile tells me they are aware of it.
Click to expand...
Click to collapse
I don't want to jinx myself but I have had my XT1575 (US) since October but recently switched to T-Mobile from VZ. Although my bootloader is still unlocked, I am running stock 6.0 (24.201.3 - Feb Security Update) and have had zero VoLTE issues (even on VZ it worked fine once enabled on my account)... Still no Wifi-Calling (on either carrier) with my XT1575, but HD Voice works great when calling another T-Mobile VoLTE phone (HD icon appears and voice quality/audio range is noticeably improved).
Not to state the obvious, but have those of you with VoLTE issues go into the hidden "testing" menu and made sure the VoLTE Provisioning Flag was set to "ON"? Access the Testing menu by entering these keys from the dialpad: *#*#4636#*#* and go under Phone Information then scroll down...
Also, make sure you have the T-Mobile LTE APN (Access Point Name) configured and enabled (should be auto-provisioned as "T-Mobile US 260 LTE" but if not the APN is "fast.t-mobile.com" and there are instructions for manually configuring their APN on their website).
Hope this helps.
ech1253 said:
I don't want to jinx myself but I have had my XT1575 (US) since October but recently switched to T-Mobile from VZ. Although my bootloader is still unlocked, I am running stock 6.0 (24.201.3 - Feb Security Update) and have had zero VoLTE issues (even on VZ it worked fine once enabled on my account)... Still no Wifi-Calling (on either carrier) with my XT1575, but HD Voice works great when calling another T-Mobile VoLTE phone (HD icon appears and voice quality/audio range is noticeably improved).
Not to state the obvious, but have those of you with VoLTE issues go into the hidden "testing" menu and made sure the VoLTE Provisioning Flag was set to "ON"? Access the Testing menu by entering these keys from the dialpad: *#*#4636#*#* and go under Phone Information then scroll down...
Also, make sure you have the T-Mobile LTE APN (Access Point Name) configured and enabled (should be auto-provisioned as "T-Mobile US 260 LTE" but if not the APN is "fast.t-mobile.com" and there are instructions for manually configuring their APN on their website).
Hope this helps.
Click to expand...
Click to collapse
VOLTE Provisioned flag is set. APN is correct.
Tinkerer_ said:
Last I saw, it appeared that OTA Marshmallow 6.0 on Moto X Pure Edition had voice call problems with VoLTE enabled, on T-Mobile.
The workaround was to disable VoLTE (Disable "Enhanced LTE"), to maintain good voice calls quality.
Can anyone offer info on whether this is still a problem with OTA MM, T-Mobile, and VoLTE?
I'm staying with 5.1.1 until I see this resolved, either on T-Mobile end, MM, or maybe with a fix to some offending component or app.
TIA...
Click to expand...
Click to collapse
It really doesn't matter if you upgrade the phone from Lollipop because VoLTE didn't exist on the phone until the Marshmallow upgrade. If you have problems with calls you can turn VoLTE off which is what you have now.
heap1 said:
It really doesn't matter if you upgrade the phone from Lollipop because VoLTE didn't exist on the phone until the Marshmallow upgrade. If you have problems with calls you can turn VoLTE off which is what you have now.
Click to expand...
Click to collapse
It does if we want to make calls on LTE band 12 as this band only supports VOLTE for voice.
kevev said:
It does if we want to make calls on LTE band 12 as this band only supports VOLTE for voice.
Click to expand...
Click to collapse
I think you misunderstood what I said. VoLTE was not added to the phone until the Marshmallow upgrade. If you are still using Lollipop VoLTE doesn't exist.
ech1253 said:
I don't want to jinx myself but I have had my XT1575 (US) since October but recently switched to T-Mobile from VZ. Although my bootloader is still unlocked, I am running stock 6.0 (24.201.3 - Feb Security Update) and have had zero VoLTE issues (even on VZ it worked fine once enabled on my account)... Still no Wifi-Calling (on either carrier) with my XT1575, but HD Voice works great when calling another T-Mobile VoLTE phone (HD icon appears and voice quality/audio range is noticeably improved).
Not to state the obvious, but have those of you with VoLTE issues go into the hidden "testing" menu and made sure the VoLTE Provisioning Flag was set to "ON"? Access the Testing menu by entering these keys from the dialpad: *#*#4636#*#* and go under Phone Information then scroll down...
Also, make sure you have the T-Mobile LTE APN (Access Point Name) configured and enabled (should be auto-provisioned as "T-Mobile US 260 LTE" but if not the APN is "fast.t-mobile.com" and there are instructions for manually configuring their APN on their website).
Hope this helps.
Click to expand...
Click to collapse
Your move from VZ to T-Mobile may support it is a carrier thing. Perhaps because your phone was already provisioned to with VOLTE on VZ, it carried over. I know the phone supports it, but let's face it, U.S. Carriers seem to hate not having control (especially AT&T). Any means to keep features limited unless you use their branded devices is one more control they have.
Sent from my XT1575 using XDA-Developers mobile app
heap1 said:
I think you misunderstood what I said. VoLTE was not added to the phone until the Marshmallow upgrade. If you are still using Lollipop VoLTE doesn't exist.
Click to expand...
Click to collapse
I understood what you said. But band 12 opens up a larger coverage area. Without VOLTE calls do not work on band 12.
One thing to note is that if the screen is kept on the jitter goes away. So it may also be a power management issue. We have already tried disabling power management on call services. But it did not help.
kevev said:
I understood what you said. But band 12 opens up a larger coverage area. Without VOLTE calls do not work on band 12.
One thing to note is that if the screen is kept on the jitter goes away. So it may also be a power management issue. We have already tried disabling power management on call services. But it did not help.
Click to expand...
Click to collapse
I am not disputing the fact that you need VoLTE to make calls over Band 12. Fortunately where I live in the Boston area T-Mobile pretty much operates exclusively on Band 4. So if I start having call problems with VoLTE enabled I can just turn it off. However, if I was still on Lollipop and in areas of the Country that use Band 12 exclusively I would not be able to make any cell calls using T-Mobile, since VoLTE was not enabled on the phone until the Marshmallow upgrade.
I would like to be able to blame T-Mobile for the problem but unfortunately this doesn't seem to be the case. Other third party phones like the recent Nexus phones, the Axon Pro, and the iPhone 6s and 6s plus all seem to have no problems making voice calls with VoLTE enabled. In my case I have noticed that the static problem does not occur with every call. It seems to come and go on an intermittent basis.
heap1 said:
I am not disputing the fact that you need VoLTE to make calls over Band 12. Fortunately where I live in the Boston area T-Mobile pretty much operates exclusively on Band 4. So if I start having call problems with VoLTE enabled I can just turn it off. However, if I was still on Lollipop and in areas of the Country that use Band 12 exclusively I would not be able to make any cell calls using T-Mobile, since VoLTE was not enabled on the phone until the Marshmallow upgrade.
I would like to be able to blame T-Mobile for the problem but unfortunately this doesn't seem to be the case. Other third party phones like the recent Nexus phones, the Axon Pro, and the iPhone 6s and 6s plus all seem to have no problems making voice calls with VoLTE enabled. In my case I have noticed that the static problem does not occur with every call. It seems to come and go on an intermittent basis.
Click to expand...
Click to collapse
I agree that it seems to be device specific. It sucks that Moto is ignoring the issue.
Sent from my XT1575 using XDA-Developers mobile app
kevev said:
I agree that it seems to be device specific. It sucks that Moto is ignoring the issue.
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think we all agree that Moto ignoring the issue is the worst part of the situation. I don't think they have even acknowledged it as a problem yet. There are a lot of things about the phone I like. However, at this point I would never buy another phone from Motorola. All phones have minor bugs. However, this is a major problem.
Hey, I'm assuming there's at least a handful of you on BOOM! Mobile (Verizon)? They recently rolled out VoLTE on the Verizon network, but I'm having trouble getting it to work.
First off; I had an issue getting them to activate my Moto X Pure on their network (apparently mine is still on Verizon's "blacklist" like many were when this phone was first released). After much strife with their customer support, I just ordered one of their cheapo phones to activate the SIM, then popped it into my Moto X. No problem. They called later because the different IMEI apparently threw a red flag, but updated the info in their system and all was well.
So to get back to VoLTE, I had to fill out a form in order for them to activate the feature on my account, but got a confirmation email that it had been activated. I still didn't get the "advanced LTE" option in the cellular network settings on my phone, so I used the secret phone menu to "turn on VOLTE provisioned flag". This made the option appear, already enabled. However when trying to place a call, I immediately get "Server error. Try again later". Radio restarts, sets the VoLTE flag to off, and I can place calls as before.
So has anyone had better luck with VoLTE on Boom? I understand it works on Verizon, correct? It did work when I was on TMO. I'm completely stock 6.0 unrooted/locked. I suspect it may have to do with Verizon thinking my device is "incompatible"?
Anyone out there using unlocked AT&T V35 on Cricket wireless? Does VoLTE and WiFi calling work?
Since I figured out the answers, I will post them for others benefit.
With AT&T firmware, both WoWiFi and VoLTE appear to work with Cricket. However, there is no indication VoLTE is working since there isn't a different icon.
With Google Fi firmware, VoWiFi is disabled on Cricket by default. There is not even an option to turn it on. The only way to fix this is to root the phone then edit vo_config.xml file. VoLTE, however, does seem to work but again, no special icon.
I have an H910A that I'm currently running with Lineage OS 17.1 on Cricket Wireless.
I wanted to try out Mint Mobile (which is TMobile MVNO), so i picked up one of their little $2 7-day trial SIM cards. I wasn't aware that TMobile\Mint already implemented the VOLTE requirement in January 2021 (vs 2022 for AT&T), so I'm not able to make voice calls when using the Mint-Mobile SIM card in my phone.
If i were to go back to a stock-based ROM, supposedly this would fix VOLTE for AT&T/Cricket, but my question is will it also make it work with TMobile's VOLTE?
I get band 12 LTE where I'm at on my phone on the TMobile/Mint network and texts, data work on the phone, just no voice calls.
I have a dual-SIM international Moto G7 (XT1962-6) running LineageOS that I was happily using on AT&T until the 3G sunset (and VoLTE whitelist) became a thing.
I was hoping that I could move the phone over to T-Mobile, but testing with a family member's Google Fi SIM has shown that VoLTE doesn't work. (I don't have a T-Mobile SIM handy to test, but I assume that results would be similar.) Calls immediately fail if I disable 3G.
The behavior is exactly as described here - https://gitlab.com/LineageOS/issues/android/-/issues/2178
That post refers to missing "binary blobs," but it never really got resolved, as the user was able to get his phone working by back to the stock firmware, and then back to LineageOS. Unfortunately, I'm guessing that this won't work for me, because the phone is an international model, so even the stock firmware won't have the "magic bits" required to make it work with a U.S. carrier.
Can anyone think of any way to make this work?