Related
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
RoyJ said:
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
Click to expand...
Click to collapse
Sorry forget to mention I knew that was normal for the drop to H+, but yes the signal drop is not. Well it started out of the blue. IS there a thread on here with what should be the correct APN settings? Also my old nexus 5 started to do this before I returned it under warranty for refurbished, then I had a moto G lte for a month worked fine, got a refurbished (due to warranty) and started again.
Here is a graph of my network coverage to show that the signal just drops.
Sent from my Nexus 7 using XDA Free mobile app
same problem
jgr208 said:
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Click to expand...
Click to collapse
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
raptir said:
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Click to expand...
Click to collapse
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
cell radio fix
jgr208 said:
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
Click to expand...
Click to collapse
I found it here (just take away the spaces after .com and after 02/): ianmarmour.com /2014/02/02/ google-nexus-5-fixing-modemcellular-issues-on-34g-networks
It's an older post from February, but seems to have the best details and fixes. If you simply search nexus 5 cellular radio issues or nexus 5 4.4.4 call drops, you should find a lot of these recalls from lots of N5 users. I'm tempted to try it, but don't really feel like sorting all my files in case i brick my device. I'm also not sure if ota update will work if i tinker with cell radios. Otherwise that's the page containing all the details you'd need including links and step by step guides. And hey if it works for you, let me know, maybe I'll try it out if it goes well for you.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
Exactly, i know that's totally possible, but i wouldn't want a smartphone that has no lte and/or hspa+ service at this point in time. This seems to happen wherever lte isn't as strong or available but hspa+ is. I think the modem responsible for switching between lte and hspa+ causes calls to drop. I took note of it a couple hours ago when i attempted to make a few phone calls resulting in instant call drops. Seems to do it while switching from lte to hspa+ network. I just wish Google would stop burying their heads from the outside world like an ostrich, and get in top of this. I mean this is their flagship device until N6 goes on sale. They should seriously fix this issue or at least stop denying that they've never heard of any complaints with their N4 and N5 customers. I love this device, but a simple fix like this not being addressed by Google is not very professional, especially because it's primary function is to call people. I'm really tempted to flash those radios, but really want to see if Google addresses this issue with an official ota lollipop update.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Factor resetting it won't help, I've tried it already.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
simms22 said:
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
Click to expand...
Click to collapse
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
simms22 said:
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
Click to expand...
Click to collapse
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
anactoraaron said:
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
Click to expand...
Click to collapse
Def wasn't gonna try hardware and only software and great to hear! Did you try out lollipop yet?
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
simms22 said:
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
Click to expand...
Click to collapse
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
well, try the lollipop preview, it was working for the other guy, see if itll work for you. if it does, great.
I am starting this thread, since there seems to be a lot of confusion around "newer" LTE bands, like Band 12 on T-Mobile, which apparently require a fully functioning and "approved" VoLTE phone to get reception.
There are various threads in device-specific forums, but they are not getting a lot of attention, and this is a significant enough problem that it should be more visible.
T-Mobile at this point has pretty fantastic coverage via the 700MHz Band 12 LTE network.
The only problem is that Band 12 requires the phone to be VoLTE "certified". The rumor was that phones could still connect to this band/LTE-network and send/receive data, but that they would fall back to alternative bands, even 3G or 2G, for phone calls. For a lot of people that would be "good enough" if not ideal.
Based on some recent testing, this is NOT CORRECT:
While phones may "sometimes" connect to Band 12 for data, the much more common scenario is apparently that the phone will disconnect from Band 12 almost immediately, or will refuse to connect to Band 12, and will instead default to an alternative LTE, 4G, 3G, or 2G connection.
In other words: even if you have perfect LTE Band 12 coverage (5/5 bars, or 100%), your "Band 12 capable" phone may instead try to connect to a really ****ty GPRS or EDGE tower that has barely any reception for the phone.
I recently encountered this with my Xperia X Compact while travelling: My phone would barely be able to connect to a T-Mobile tower with a GPRS data connection, while my wife's Moto G4 would get 5/5 or 100% LTE reception. Swapping SIM cards had the same result, so we know the problem rests with the phone.
Searching for "Available Mobile Networks" on my "band 12 capable" phone would show various T-Mobile 4G networks, but the phone would be unable to connect to them.
Talking to other Xperia X Compact owners, they have the same problem: the phone will sporadically connect to Band 12, but it is not a reliable connection (if the phone even connects) and it will (more likely) prefer other networks/bands/frequencies.
Based on the phone having the proper frequencies, I would assume that T-Mobile has some mechanism on some (or the majority of) towers where they disconnect non-VoLTE certified devices.
Anecdotally, I also had a similar issue with my previous phone - a Nexus 5x. The phone is even VoLTE certified, but when using Cyanogenmod/LineageOS, it would have really terrible reception, despite the location having almost perfect Band 12 coverage - LineageOS/CM does not (or had no) VoLTE support.
I have also tried "hacking" the X Compact to enable VoLTE support by adding the relevant lines to the build.prop and enabling the option under Settings and (*#*#4636#*#*) but this does not appear to make any difference.
A list of T-Mobile "VoLTE certified" phones can be found here:
http://www.spectrumgateway.com/compatible-phones
Would be great if anyone has any suggestions how to resolve this, or force the phone to prioritize Band 12, but it would otherwise appear that the only solution is to get the phone certified by T-Mobile (so much for net neutrality and open access).
I'm using an Xperia X Compact and my home market only has band 12 lte and I can't connect to it. Which means I'm always in 3g or roaming and rarely have data in buildings. It's maddening because I will only buy Sony. I think they are the only manufacturer making attractive handsets and the build quality is light years beyond well marketed, poorly constructed brands like Samsung and LG. But regardless of anyone's choice of manufacturer, a device with a functioning 700 mhz lte radio should function just fine on the corresponding network regardless of where it was purchased.
Would certifying this device and enabling VOLTE be particularly costly to Sony? Correct me if I'm wrong but based on internal components this device should be capable of this ja?
I think it wouldn't hurt to send petitions to both the manufacturer and T-mobile USA. This certainly doesn't help Sony in a market they are seriously struggling in. It also isn't very uncarrier to favor certain devices over others.
The only reason I switched from Verizon was the ability to choose my device. That and the things John Legere was doing to change the industry. I believed in what he was saying. But right now it isn't working for me and likely many others. He should know. I can say firsthand that the guy answers his emails. I think we need to show both parties that this is worth their attention.
---------- Post added at 01:09 AM ---------- Previous post was at 12:14 AM ----------
I should mention that after multiple calls to T-mobile tech support I received a cryptic call very late at night from someone high up in tech support.
Long story short he at least admitted that even though it wasn't a t mobile device and even though it didn't support VoLTE, it should still connect to band 12 just fine. He also said that they were having problems with this sort of thing in my area and that it should be resolved in a month. He also said my IMEI was logged and I would be given priority in the matter. Whatever that means.
I should also mention that was a month ago and he didn't have an email to give me. He did however give me a phone number (probably just the department) that I need to dig up.
Could just be a bunch of fluff because they are afraid to lose customers. Then again he was from tech support not customer retention. And as I said t mobile does listen to its customers.
POMF2K said:
I'm using an Xperia X Compact and my home market only has band 12 lte and I can't connect to it. Which means I'm always in 3g or roaming and rarely have data in buildings. It's maddening because I will only buy Sony. I think they are the only manufacturer making attractive handsets and the build quality is light years beyond well marketed, poorly constructed brands like Samsung and LG. But regardless of anyone's choice of manufacturer, a device with a functioning 700 mhz lte radio should function just fine on the corresponding network regardless of where it was purchased.
Would certifying this device and enabling VOLTE be particularly costly to Sony? Correct me if I'm wrong but based on internal components this device should be capable of this ja?
I think it wouldn't hurt to send petitions to both the manufacturer and T-mobile USA. This certainly doesn't help Sony in a market they are seriously struggling in. It also isn't very uncarrier to favor certain devices over others.
The only reason I switched from Verizon was the ability to choose my device. That and the things John Legere was doing to change the industry. I believed in what he was saying. But right now it isn't working for me and likely many others. He should know. I can say firsthand that the guy answers his emails. I think we need to show both parties that this is worth their attention.
---------- Post added at 01:09 AM ---------- Previous post was at 12:14 AM ----------
I should mention that after multiple calls to T-mobile tech support I received a cryptic call very late at night from someone high up in tech support.
Long story short he at least admitted that even though it wasn't a t mobile device and even though it didn't support VoLTE, it should still connect to band 12 just fine. He also said that they were having problems with this sort of thing in my area and that it should be resolved in a month. He also said my IMEI was logged and I would be given priority in the matter. Whatever that means.
I should also mention that was a month ago and he didn't have an email to give me. He did however give me a phone number (probably just the department) that I need to dig up.
Could just be a bunch of fluff because they are afraid to lose customers. Then again he was from tech support not customer retention. And as I said t mobile does listen to its customers.
Click to expand...
Click to collapse
Since I did encounter this also on my Nexus 5x with LineageOS, I doubt that what T-Mobile told you is true. They must be actively blocking these non-certified handsets, since the phone should just attempt connecting.
So who do we need to appeal to? T mobile or Sony.?
POMF2K said:
So who do we need to appeal to? T mobile or Sony.?
Click to expand...
Click to collapse
Both. Maybe also complain to the FCC - I thought that carriers needed to provide open access to their network. Verizon got into hot water for not doing so ...
Does your compact ever connect to lte for a few seconds after a reboot?
I might try to force LTE and restart and see if that has any effect.
I just flashed the UK. T mobile networks work just fine. Well except lte/4g but that was expected.
POMF2K said:
Does your compact ever connect to lte for a few seconds after a reboot?
I might try to force LTE and restart and see if that has any effect.
I just flashed the UK. T mobile networks work just fine. Well except lte/4g but that was expected.
Click to expand...
Click to collapse
It does connect sometimes but it then usually kicks down to Band 4 or a GSM band (HSDPA, UMTS, EDGE, or even GPRS).
I cannot find any info how to prioritize LTE bands, so I assume this is T-Mobile's band 12 cell tower's kicking the phone off when they notice that it is not VoLTE approved.
Interesting discussion on Howard forums....
http://www.howardforums.com/showthr...rtphones-with-band-12-LTE-w-o-VoLTE-now/page2
POMF2K said:
Interesting discussion on Howard forums....
http://www.howardforums.com/showthr...rtphones-with-band-12-LTE-w-o-VoLTE-now/page2
Click to expand...
Click to collapse
Interesting discussion though nothing new.
Yes, we know that Band 12 phones should be able to get a data connection, yet T-Mobile apparently actively disconnects them (or bars them from connecting), especially in areas where Band 12 would give you great coverage but there is no other coverage.
F Sony and F T-Mobile for this!
BTW: here is an article about the follow up model: https://arstechnica.com/gadgets/2017/08/sony-xperia-xz1-compact/
Please leave comments about Sony not getting their phones approved for VoLTE with T-Mobile and the phone therefore NOT REALLY WORKING with the carrier.
It would seem to me that the only solution to this problem would be either T-Mobile accepting a standard spec for VoLTE, they open source their code for VoLTE, or someone figures out how to implement VoLTE and trick T-Mobile to think it is an approved "whitelisted" phone.
Given that the T-Mobile network is getting worse and worse every day without Band 12 coverage, I find it really surprising that most people just don't seem to care. Does nobody use their phone outside of WiFi?
andTab said:
It would seem to me that the only solution to this problem would be either T-Mobile accepting a standard spec for VoLTE, they open source their code for VoLTE, or someone figures out how to implement VoLTE and trick T-Mobile to think it is an approved "whitelisted" phone.
Given that the T-Mobile network is getting worse and worse every day without Band 12 coverage, I find it really surprising that most people just don't seem to care. Does nobody use their phone outside of WiFi?
Click to expand...
Click to collapse
There is a standard spec, the problem is the certification. It requires a certificate from T-mobile to be used by the phone, which is gained through certification. And if SONY is detecting T-mobile at the modem level then there isn't anything a ROM can do with or without a ROM. I had a Z5, but this drove me crazy so I switched to a Pixel.
I wouldn't expect this to change based on SONY de-prioritizing the US phone market, so either upgrade to a new supported sony phone or move on (shrug)
sovanyio said:
There is a standard spec, the problem is the certification. It requires a certificate from T-mobile to be used by the phone, which is gained through certification. And if SONY is detecting T-mobile at the modem level then there isn't anything a ROM can do with or without a ROM. I had a Z5, but this drove me crazy so I switched to a Pixel.
I wouldn't expect this to change based on SONY de-prioritizing the US phone market, so either upgrade to a new supported sony phone or move on (shrug)
Click to expand...
Click to collapse
That can't be true.
I accept that T-Mobile may issue a certificate but that must be processed on the rom/OS/phone.apk level. Otherwise, every custom ROM on any certified phone would work. We all know that is not the case.
If it's the rom/OS/phone.apk though, why can't we hack a phone to work with TMUS / VoLTE?
I have an x compact and while it is the best device I have ever owned it is essentially unusable on T-Mobile or att.
andTab said:
That can't be true.
I accept that T-Mobile may issue a certificate but that must be processed on the rom/OS/phone.apk level. Otherwise, every custom ROM on any certified phone would work. We all know that is not the case.
If it's the rom/OS/phone.apk though, why can't we hack a phone to work with TMUS / VoLTE?
I have an x compact and while it is the best device I have ever owned it is essentially unusable on T-Mobile or att.
Click to expand...
Click to collapse
Because the SONY modem firmware doesn't even attempt to negotiate VoLTE, which does *not* happen in user space. It is likely possible to hack the qualcomm modem with QPST to enable this, but without documentation and correct values one will not get very far.
sovanyio said:
Because the SONY modem firmware doesn't even attempt to negotiate VoLTE, which does *not* happen in user space. It is likely possible to hack the qualcomm modem with QPST to enable this, but without documentation and correct values one will not get very far.
Click to expand...
Click to collapse
If it was the modem, then flashing a new system (eg custom ROM) should not make any difference.
I also have a Nexus 5x. With stock it is fantastic and uses VoLTE on T-Mobile. With LineageOS, it is useless on Band 12. SAME MODEM!
Experience therefore shows that it is the OS/System that somehow prevents this from working.
andTab said:
If it was the modem, then flashing a new system (eg custom ROM) should not make any difference.
I also have a Nexus 5x. With stock it is fantastic and uses VoLTE on T-Mobile. With LineageOS, it is useless on Band 12. SAME MODEM!
Experience therefore shows that it is the OS/System that somehow prevents this from working.
Click to expand...
Click to collapse
The Nexus 5x is a different phone made by a different manufacturer with a different firmware scheme. You cannot compare them directly.
I noticed that the XZ1 Compact says right on the website compatible with t mobile band 12 and wifi calling... this is infuriating. It should be easy for them to patch the Xperia x compact.
I would have never purchased this if I had known. Especially since they apparently flashed an update to my old t mobile z3 that allows voice over lte and band 12.
Sony X Compact
sovanyio said:
There is a standard spec, the problem is the certification. It requires a certificate from T-mobile to be used by the phone, which is gained through certification. And if SONY is detecting T-mobile at the modem level then there isn't anything a ROM can do with or without a ROM. I had a Z5, but this drove me crazy so I switched to a Pixel.
I wouldn't expect this to change based on SONY de-prioritizing the US phone market, so either upgrade to a new supported sony phone or move on (shrug)
Click to expand...
Click to collapse
It has to be on Sony, use the t-mobile BYOD app to check, I have a Huawei mate 9 that I just purchased, connects perfectly on band 12, VoLTE works just like it's supposed to. On a side note I went through three Sony phones before I bought this Huawei, had to return all three due to quality control issues, one had worst touches that made the phone unusable, one wouldn't pick up the SIM card, and the third wouldn't power on at all, thank good Amazon refunded my money on all three. They may have the Sony name on the phone, but they are still build by the lowest bidder in China and makes with Sony's name.
revjamescarver said:
It has to be on Sony, use the t-mobile BYOD app to check, I have a Huawei mate 9 that I just purchased, connects perfectly on band 12, VoLTE works just like it's supposed to. On a side note I went through three Sony phones before I bought this Huawei, had to return all three due to quality control issues, one had worst touches that made the phone unusable, one wouldn't pick up the SIM card, and the third wouldn't power on at all, thank good Amazon refunded my money on all three. They may have the Sony name on the phone, but they are still build by the lowest bidder in China and makes with Sony's name.
Click to expand...
Click to collapse
See this: http://www.androidpolice.com/2015/0...cked-smartphones-and-yep-its-still-confusing/ It is up to an OEM to decide to go through this process per-phone. Since no US carrier carried the phone they didn't not bother spending the money or time to certify it. I loved the SONY design, but since they weren't supporting the market I had to abandon them for other phones.
Network provider is EE UK.
Sorry for the long post
I’ve had the 1+ since 2014 now, I am rooted and have used various Android 7 and 8 (recently) roms on the device until recently (probably 7 months ago) my 1+ started playing up. I would not get any signal whilst at work; although the building I work is generally poor with mobile signal however I use to get just enough signals to receive a call.
About 7+ months ago this started fading and I would get 0 bars, at first I thought it’s a modem issue so I tried all the different modems and made notes on which one was the best but in the end none of them helped with the situation. I then did what most people do and googled the issue and found that there are lots of other people with similar issue with the oneplus one not working on LTE, many suggested to make sure I visit the engineering menu *#*#4636*#*# and change the connection to LTE/GSM Auto (PRL), however this was already set and yet it was not making any difference. The main issue was not being able to make or receive calls when the device is connected to LTE.
On the odd occasion I was able to make/receive all on LTE when leaving the building but it would be not stable, at times I would get a call but people could not hear me, then sometime I would dial out and the screen would be stuck at “dialing” and nothing would happen. Then I would try few times and it may work or not work at all. So I switched to GSM only (via the secret menu) and the phone would work perfectly, no issues calling out at my work desk or outside and getting all calls without any issues. The issue with this was that on a reboot the settings would go back to LTE/GSM so it was a constant change. On top not being able to use 4G Data speeds was making life harder.
Even when selecting 3G in network settings the phone would not switch to 3G only. I also tried different network provides like 3 UK, Vodafone but still the same issue.
I’ve now come to a conclusion that this is something software related (perhaps?) as the device is failing to switch to 3G when making/receiving calls. When I check the secret menu I see that DATA and VOICE connection is LTE. Now I know this device does not support VoLTE so I thought it would always first aim to connect to 3G signal?? NO?
As a result i’ve moved to Pixel 2 device because I tried everything from different roms to modems, going back to kitkat, CM12.1 and 13 as well as Oxygen OS but was still getting the same problem.
I’ve also come across posts (on google) that people with different oneplus device are suffering from this so not sure if something has been switched on/off on my phone when flashing different roms to have caused this issue or is this a hardware problem?
I’ve spent numerous hours trying different things suggested by many on google but haven’t got anywhere. I have given up trying to get to the bottom of this.
If anyone is out there who have had this issue and have found a solution please let me know, I still very much like the oneplus but with this issue it’s hard to use the device.
Thank you for reading…..
v1ks said:
Network provider is EE UK.
Sorry for the long post
I’ve had the 1+ since 2014 now, I am rooted and have used various Android 7 and 8 (recently) roms on the device until recently (probably 7 months ago) my 1+ started playing up. I would not get any signal whilst at work; although the building I work is generally poor with mobile signal however I use to get just enough signals to receive a call.
About 7+ months ago this started fading and I would get 0 bars, at first I thought it’s a modem issue so I tried all the different modems and made notes on which one was the best but in the end none of them helped with the situation. I then did what most people do and googled the issue and found that there are lots of other people with similar issue with the oneplus one not working on LTE, many suggested to make sure I visit the engineering menu *#*#4636*#*# and change the connection to LTE/GSM Auto (PRL), however this was already set and yet it was not making any difference. The main issue was not being able to make or receive calls when the device is connected to LTE.
On the odd occasion I was able to make/receive all on LTE when leaving the building but it would be not stable, at times I would get a call but people could not hear me, then sometime I would dial out and the screen would be stuck at “dialing” and nothing would happen. Then I would try few times and it may work or not work at all. So I switched to GSM only (via the secret menu) and the phone would work perfectly, no issues calling out at my work desk or outside and getting all calls without any issues. The issue with this was that on a reboot the settings would go back to LTE/GSM so it was a constant change. On top not being able to use 4G Data speeds was making life harder.
Even when selecting 3G in network settings the phone would not switch to 3G only. I also tried different network provides like 3 UK, Vodafone but still the same issue.
I’ve now come to a conclusion that this is something software related (perhaps?) as the device is failing to switch to 3G when making/receiving calls. When I check the secret menu I see that DATA and VOICE connection is LTE. Now I know this device does not support VoLTE so I thought it would always first aim to connect to 3G signal?? NO?
As a result i’ve moved to Pixel 2 device because I tried everything from different roms to modems, going back to kitkat, CM12.1 and 13 as well as Oxygen OS but was still getting the same problem.
I’ve also come across posts (on google) that people with different oneplus device are suffering from this so not sure if something has been switched on/off on my phone when flashing different roms to have caused this issue or is this a hardware problem?
I’ve spent numerous hours trying different things suggested by many on google but haven’t got anywhere. I have given up trying to get to the bottom of this.
If anyone is out there who have had this issue and have found a solution please let me know, I still very much like the oneplus but with this issue it’s hard to use the device.
Thank you for reading…..
Click to expand...
Click to collapse
I can relate to you. have similar issue and also tried most of the things you have done. don't know what to do. if you have found something, then reply.
I think I have the same issue here in Italy too.
I tried all modems in the list and downgraded to kitkat but with no luck.
same issue reproduced on lineage os 16.0 India /Airtel
nik012003 said:
I think I have the same issue here in Italy too.
I tried all modems in the list and downgraded to kitkat but with no luck.
Click to expand...
Click to collapse
No calls incoming/outgoing over LTE network lineage os 16.0, when changed to 2G network calls works just fine
while LTE no issues with Data connectivity .
any luck for anyone.
Thanks
I don't have the phone anymore (in fact, the same issue made me get a new phone), but maybe try updating the modem?
Hello all,
Phone: Mi Mix 2S
MIUI: Global 9.6.4 Stable
Model: M1803D5XA
Carrier(s): T-Mobile(SIM1) & Verizon(SIM2)
Issue: MMS receiving is limited to 30kb when using the stock Xiaomi and Android Messages messaging apps. APN settings do not show on device for Verizon SIM(doesn't matter if in Slot 1 or Slot 2).
So I called Verizon and worked with level 2 tech support to try and troubleshoot this issue. Basically, the MMS and/or Device server on Verizon's end cannot verify the device and therefore limits MMS sending to the device as it cannot authenticate. This verification is done by verifying the IMEI of the SIM and the device identification.
So basically level 2 tech support cannot verify the device manually and cannot submit a request to add the device information either, it has to come from the vendor(Xiaomi) to Verizon.
Anyway we can request this from Xiaomi going forward? Seems weird to have all the bands for Verizon, can get full 4G LTE coverage but I can't receive more than 30kb per image.
I had this issue at first. Flashed latest stable and it was fixed. It's fixed on miui 10 beta and its fixed on treble builds
aeppacher said:
I had this issue at first. Flashed latest stable and it was fixed. It's fixed on miui 10 beta and its fixed on treble builds
Click to expand...
Click to collapse
Well I flashed to 9.6.4 stable, which I thought was the latest stable?
I'm flashing MIUI 10 right now...guess we'll see what happens.
*Edit, still not working on Verizon. And now on MIUI 10, Dual 4G is broken.
*Edit 2, now I have Dual 4G back. Verizon needs to be SIM 2, but be the default for Internet....
I'm on VZW only and I'm on the latest MIUI 10 beta. I'm experiencing this as well. My wife receives good quality images from my phone but when she sends from her Pixel XL to me they are terrible. As are images I receive from anyone else. Kind of a bummer.
Are you guys having issues getting connected on Verizon now? I'm not able to reliably connect at all, most of the time it just sits on 1xRTT on VOICE, and won't connect to data. I can get it to connect to LTE/VOLTE by smashing airplane mode or disabling radio over and over again. Occasionally it will go to LTE, but it doesn't stay working and drops out. I can't drive anywhere and even conduct a phone call as that doesn't stay up either. When it drops, it hard drops and acts like the modem is being reset, instead of roaming to a new cell tower.
Edit, forgot to mention, called VZW, they gave me the finger and tried to sell me an iPhone XS Max 512GB as a "suitable replacement" for my 8GB/256GB phone. They were not helpful, and told me that they have "teams taking steps to make uncertified phones not work on Verizon's network for security and safety reasons". I have tried two different sim cards as well, both with active service and both work in all 3 generations of Pixel XL that I have.
Why the hell would Verizon troubleshoot a phone they haven't certified for their network? Quit complaining.
Sent from my Mix 2S on VZW & Google Fi
JonMS said:
Why the hell would Verizon troubleshoot a phone they haven't certified for their network? Quit complaining.
Sent from my Mix 2S on VZW & Google Fi
Click to expand...
Click to collapse
Cause I pay them every month to provide me with service. They could've atleast escalated to someone with a brain and ability to look at logging on their side and tried to help. Your comment was not needed.
I have been struggling for days with my Verizon connected Mi Mix 2s. At times I could connect with VOLTE but I lost my MMS. This past weekend I tried various ROMs with no difference. I finally cleared everything, loaded TWRP and then flashed the Global developer beta.
I also put my SIM back into a phone that Verizon would recognize and reset the card.
When I was up and running again I did the *#*#86583#*#* to unlock VOLTE and then the 4636 dial to set LTE only. So far so good. I was then able to go back and add a correct apn for verizon. With Verizon Messaging app everything is working and stable, including MMS. Afraid to mees with it again. But it is possible to get the phone to work with Verizon.
mesament said:
I have been struggling for days with my Verizon connected Mi Mix 2s. At times I could connect with VOLTE but I lost my MMS. This past weekend I tried various ROMs with no difference. I finally cleared everything, loaded TWRP and then flashed the Global developer beta.
I also put my SIM back into a phone that Verizon would recognize and reset the card.
When I was up and running again I did the *#*#86583#*#* to unlock VOLTE and then the 4636 dial to set LTE only. So far so good. I was then able to go back and add a correct apn for verizon. With Verizon Messaging app everything is working and stable, including MMS. Afraid to mees with it again. But it is possible to get the phone to work with Verizon.
Click to expand...
Click to collapse
Hi - is your SIM a newer (or brand new) SIM? I am seeing something in the logging on the radio logs that the SIM doesn't contain any carrier information, and was also seeing several errors about missing CMDA specific settings. This weekend I spent most of the day on Saturday and Sunday testing build.prop edits, and messing with the apns-conf.xml file settings. I could not get anything other than 1xRTT most of the time (I modified one of the existing entries in the list of APNs to be an exact match of what my Pixel 3 XL has) and by forcing LTE Only in *#*#INFO#*#* I was able to get LTE for brief periods of time, but not consistently. On 8.11.29 and 8.11.23 builds I can't get data working consistently, and if VOLTE isn't turned on, I can't get it to even act like it's going to connect LTE. I checked the APNs and played with it for hours, but not much success. The device just seems to "connect" but if you try to call on VOLTE or use LTE data to do something, the radio appears to reset. I am wondering if someone at Xiaomi neutered something in the RIL setup for their builds that broke CDMA compatibility. When I have time again, I will do some more comparison to see if I can figure out why it's not working. I'm planning on decompiling some of the files in question and looking at the code and configurations to see if something in there is the cause. The radio logs do not have a smoking gun. I also grabbed a copy of the build.prop file from MIUI9/Oreo and I am going to compare to see if they have some kind of prop flags that are missing in the MIUI 10 builds and or PIE builds.
I am going to find a way to make this phone work on Verizon.
Eventually, I rolled back to MIUI9 on Oreo (I don't know the build off the top of my head and the phone isn't near me) via fastboot. I have been able to get decent connectivity with that software version on Verizon where I live. I had to create my own APN, and have been using that with limited success. I submitted a bug report on the MIUI bug reports page. If you want to upvote that bug, the link is here: https://en.miui.com/thread-4724630-1-1.html
Edit: I just went to lunch and couldn't get the phone to connect to anything but 1xRTT the whole time we were at lunch (I didn't force LTE only, as I haven't had to previously since I rolled back). My next steps when I have time is to compare the build.prop between the builds, but I am not expecting to find anything. I am starting to suspect from the differences in the way the logging looks that they may have messed with the code or config information for the the RIL setup in the Android before they built it.
Please keep posting what you try, I'll be following with interest! I had everything working for a while but since MIUI 10.0.6.0 mms has broken.
DeadJenkins said:
Please keep posting what you try, I'll be following with interest! I had everything working for a while but since MIUI 10.0.6.0 mms has broken.
Click to expand...
Click to collapse
Can you get data and phone services? Mine won't stay connected, but that could be a hardware problem.
PWn3R said:
Can you get data and phone services? Mine won't stay connected, but that could be a hardware problem.
Click to expand...
Click to collapse
Yeah, data and phone have been fine so far, I think a few times it's disconnected but messing with the APN has fixed it. In general, I'd say my data and phone have been pretty stable. MMS on the otherhand, I had working for a bit on 9.6. On 10.0.4.0 it's been really slow to send and receive or not working at all. When it did work, picture quality was awful.
PS, I have my phone set to Vietnam by mistake. I have an older SIM card, at least a few years.
PS still working fine.
Mine has been repaired, they had to resolder a connector for the antenna on the board and the logic board was dropped. I saw this happen, however, signal levels are as good if not better than the pixel devices in the same spots for me, so I don't think anything is permanently damaged. I've been debating trying to order another Mi Mix 2 from somewhere or ordering a Mi Mix 3. I have built roms and have a lot of android troubleshooting experience, and I can't seem to figure this one out. What I am seeing on my device is that once it is connected, it seems to not want to roam properly. Like disconnecting from one cell causes a modem reset and then it takes a long time to reconnect. I am going to keep working on it though.
PWn3R said:
Mine has been repaired, they had to resolder a connector for the antenna on the board and the logic board was dropped. I saw this happen, however, signal levels are as good if not better than the pixel devices in the same spots for me, so I don't think anything is permanently damaged. I've been debating trying to order another Mi Mix 2 from somewhere or ordering a Mi Mix 3. I have built roms and have a lot of android troubleshooting experience, and I can't seem to figure this one out. What I am seeing on my device is that once it is connected, it seems to not want to roam properly. Like disconnecting from one cell causes a modem reset and then it takes a long time to reconnect. I am going to keep working on it though.
Click to expand...
Click to collapse
So you had a hardware issue? After the fix, which things work and which don't work for you? When I disable VoLTE carrier check, I get the VoLTE symbol, but I can't make any calls. I've been messing with the SMSC, where it seems changes aren't persisting. I can't get mms to work anywhere but the stock app, which sucks because the stupid MIUI stock messaging app doesn't have group mms >.>
I had a screen break due to it falling on a very sharp corner of an object from about 6 inches up. I took it to a phone repair place locally. They dropped the logic board, camera, front facing camera/charging interface board as well from like 4 feet up onto concrete. The person who tried to repair the screen (which I provided the replacement for) did not follow the instructions on the video either and removed the plastic lining bezel from the phone body (you are supposed to remove the screen from the bezel with a heat gun). They had to send the phone out for micro-soldering to re-place and reattach the antenna connectors for the cellular and wifi antennas. They had to pay for that. I know what the phone looks like inside from watching the videos of how to replace the screen. When they gave the phone back, there was a substantial gap between the edge of the screen and the bezel in a couple spots (atleast 3 or 4 sheets of paper thickness). I ordered a new frame, bezel and screen all in one and replaced it myself (moved all the components from the original phone body to the new one). Everything appears to work, signal levels are good, but the cellular part will not stay connected, and the modem acts like it's resetting all the time. Sometimes it will stay connected to the repeater in the office I work in for 8 hours straight with no issues, and I can text and call. When I leave that area or go home, it doesn't seem to want to roam to service, and instead of switching cell sites it seems to just reset the modem. There is absolutely a possibility that some small transistor, resistor, cap or something else on this board got damaged when it fell. Given that you guys aren't reporting issues with your devices staying on the network, I'm starting to think I need to go back and make some serious noise at this repair place. I am no stranger to working on sensitive electronics, and I was extremely careful not to damage anything inside when I moved the components (and it was already exhibiting this behavior when I got it back from them before I took repairs into my own hands).
That said, I've spent the last two days trying to figure out if I can do anything that might be helpful with QPST and QXDM as well as playing with various additional build.prop configuration. Nothing there that seemed to help. Rolling back to MIUI9/Oreo seemed to help some but was not a magic bullet. I still had to manually configure APNs and find myself needing to reboot or airplane mode every time the device should roam to a new cell site. I am planning on trying to copy the "carrierconfig.apk" file that is part of the system settings off of a Pixel 3 XL onto the Android Pie MIUI10 beta to see if possibly Xiaomi has something jacked there, but since you guys aren't reporting issues, I am seriously starting to suspect that something is physically damaged after that drop on the logic board, but the intermittent behavior and the fact that the signal looks correct and normal when it's working is going to make it nearly impossible to identify the cause.
As a side note, there's a Mi Mix 3 on it's way from GearBest....
---------- Post added at 04:00 PM ---------- Previous post was at 03:10 PM ----------
DeadJenkins said:
So you had a hardware issue? After the fix, which things work and which don't work for you? When I disable VoLTE carrier check, I get the VoLTE symbol, but I can't make any calls. I've been messing with the SMSC, where it seems changes aren't persisting. I can't get mms to work anywhere but the stock app, which sucks because the stupid MIUI stock messaging app doesn't have group mms >.>
Click to expand...
Click to collapse
So on mine, I can't get it to connect whether VOLTE check is enabled or not. At the office I'm like 10 feet from a repeater, and it seems to connect on LTE/VOLTE (if that's toggled on) very quickly. I have VOLTE enabled on my Verizon account. On the extender, I can make calls on VOLTE, but can't call without VOLTE enabled. I can't get it to connect to VOLTE with the VOLTE carrier check enabled, I have to shut that off and manually toggle. I am noticing massive inconsistencies in the configuration information contained inside the carrierconfig.apk that is loaded in the system build by Xiaomi. I don't see a smoking gun there, but there's a metric crapton of differences.
If I am not next to this Verizon repeater, it usually takes multiple airplane mode cycles or reboots to get onto LTE, it just sits on 1xRTT forever, no texts or data come through when stuck in that mode. Any type of cellular roaming that should happen seems to just cause a radio reset, and it goes to blank bars with X and then it acts like it can't find a network to connect to for a while or goes 1xRTT with full bars and keeps resetting every 20-30 seconds.
PWn3R said:
Cause I pay them every month to provide me with service. They could've atleast escalated to someone with a brain and ability to look at logging on their side and tried to help. Your comment was not needed.
Click to expand...
Click to collapse
How is Verizon supposed to support a device they aren't familiar with? This post comes off as whiney. Verizon does NOT have to support every phone capable of their bands, that isn't up to them. Way too many variables using an outside device. With that said, running the latest global beta with the sim card out of my Pixel I have zero issues running Verizon Wireless as primary and Google Fi sim as secondary. Both networks getting VoLTE.
JonMS said:
How is Verizon supposed to support a device they aren't familiar with? This post comes off as whiney. Verizon does NOT have to support every phone capable of their bands, that isn't up to them. Way too many variables using an outside device. With that said, running the latest global beta with the sim card out of my Pixel I have zero issues running Verizon Wireless as primary and Google Fi sim as secondary. Both networks getting VoLTE.
Click to expand...
Click to collapse
I expect Verizon to use the standards defined for how these devices communicate. I expect Verizon to assist with troubleshooting by providing information and looking at logs as to what my device is doing on the network. This is not unreasonable. I am not asking them to tell me how to fix the problem on a device they don't support. I am not expecting them to just suddenly support a device, but I do expect them to be willing to look at logs and information on their side and provide feedback. I am glad to hear yours is working and am starting to suspect mine has some kind of hardware damage. The local repair place has refused to do anything to help out because "if it's got a signal, it's a software problem".
PWn3R said:
I expect Verizon to use the standards defined for how these devices communicate. I expect Verizon to assist with troubleshooting by providing information and looking at logs as to what my device is doing on the network. This is not unreasonable. I am not asking them to tell me how to fix the problem on a device they don't support. I am not expecting them to just suddenly support a device, but I do expect them to be willing to look at logs and information on their side and provide feedback. I am glad to hear yours is working and am starting to suspect mine has some kind of hardware damage. The local repair place has refused to do anything to help out because "if it's got a signal, it's a software problem".
Click to expand...
Click to collapse
Well, if it worked before the repairs.. it is definitely a hardware issue.
Check your APN settings. I had the exact same issue with my phone, especially after the latest update. I called Verizon for the customer support and they couldn't figure out as well. Then, I pretty much looked at every settings on my phone and tried almost everything, only to have the issue fixed by modifying the APN settings. For some reason, after the update, the SIM card removed the custom APN settings that I added when I first purchased the phone. Instead, it had the CBS, FOTA, IMS, LTE - Verizon Internet APNs available with the APN set as the CBS (Sorry I'm not an expert, so I really don't know what exactly they are. I suspect that those were pre-saved on my SIM cards as I have used the same one for 3-4 different phones?). Anyway, I googled Mi Mix 2s Verizon APN and set it according to the very first result I found. Since then, the MMS has started working well again. Hope it helps.
I have two brand new moto 5g 2022 phones for me and my wife and they both do everything but work right. You can call someone and they answer but you cannot hear them, as they answer their phone, my phone just keeps ringing while they keep saying hello. Other times it calls and won't even ring.They do all kinds of different things and sometimes even do work but when they do you can hardly hear each other. I should say we got these phones because our old phones did almost the same thing. They were so old they only got 2g and 3g so we upgraded to these. Also I checked the 5g map and it shows we have 5g ultra coverage in my area, also attached the file showing the area.
Thank you for anyone that can help with this problem.
[email protected] said:
I have two brand new moto 5g 2022 phones for me and my wife and they both do everything but work right. You can call someone and they answer but you cannot hear them, as they answer their phone, my phone just keeps ringing while they keep saying hello. Other times it calls and won't even ring.They do all kinds of different things and sometimes even do work but when they do you can hardly hear each other. I should say we got these phones because our old phones did almost the same thing. They were so old they only got 2g and 3g so we upgraded to these. Also I checked the 5g map and it shows we have 5g ultra coverage in my area, also attached the file showing the area.
Thank you for anyone that can help with this problem.
Click to expand...
Click to collapse
Is this only happening at home? while connected to wifi?
If so try disabling wifi calling.
sd_shadow said:
Is this only happening at home? while connected to wifi?
If so try disabling wifi calling.
Click to expand...
Click to collapse
No it happens everywhere. The phone is on cellular preferred.
[email protected] said:
No it happens everywhere. The phone is on cellular preferred.
Click to expand...
Click to collapse
I disabled wifi and same result. I have also rebooted both phones and disabled some apps that were transferred from the other phones.
That's crazy because ever since ive had my 2021 version of the phone, the EXACT same issues have occurred since day one. got the phone in Nov 2021 and still have so many issues with Tmobile towers. Tmobile has a huge handover issue with 5g SA and NSA. Old sprint towers that are still up and running on LTE only, work 100% with no issues, all other towers by 310260 that are configured for CA (carrier aggregation), whether its fdd or tdd ca doesnt matter, I have to airplane mode off then on, wait for the tower to connect, turn off data, wait 5 or so secs and turn data back on, go to the debug menu for the phone *#*#4636#*#* and go to phone information, go down to where it says Ping Test and hit it, make sure that BOTH ipv4 and ipv6 are passing the test. If only ipv6 is passing, then repeat the process until they both connect. This is the only way im able to tell if the tunnel is connected correctly to Tmo. I know HUGE pain in the A but that is the ONLY resolution i have found for this, tmo doesnt care, i have had 20+ tickets opened up and not 1 of them were ever resolved and instantly closed the tkt.
People have claimed that after rooting the phone and installing a custom rom with android 12, that all of the issues are resolved, however I am one of the unlucky people with the xt2131-1 device that will not allow anything other than the stock rom to be installed, bootloader unlocked and rooted but will not allow a custom rom. Last Moto phone I am ever buying.
wickedxjay said:
That's crazy because ever since ive had my 2021 version of the phone, the EXACT same issues have occurred since day one. got the phone in Nov 2021 and still have so many issues with Tmobile towers. Tmobile has a huge handover issue with 5g SA and NSA. Old sprint towers that are still up and running on LTE only, work 100% with no issues, all other towers by 310260 that are configured for CA (carrier aggregation), whether its fdd or tdd ca doesnt matter, I have to airplane mode off then on, wait for the tower to connect, turn off data, wait 5 or so secs and turn data back on, go to the debug menu for the phone *#*#4636#*#* and go to phone information, go down to where it says Ping Test and hit it, make sure that BOTH ipv4 and ipv6 are passing the test. If only ipv6 is passing, then repeat the process until they both connect. This is the only way im able to tell if the tunnel is connected correctly to Tmo. I know HUGE pain in the A but that is the ONLY resolution i have found for this, tmo doesnt care, i have had 20+ tickets opened up and not 1 of them were ever resolved and instantly closed the tkt.
People have claimed that after rooting the phone and installing a custom rom with android 12, that all of the issues are resolved, however I am one of the unlucky people with the xt2131-1 device that will not allow anything other than the stock rom to be installed, bootloader unlocked and rooted but will not allow a custom rom. Last Moto phone I am ever buying.
Click to expand...
Click to collapse
Thank you for the info, I thought it might be t-mobil itself since the old ones and the new ones are doing the same thing. I did get the one phone to upgrade to android 13 but the other one which is the same phone will not. It still did not make any difference.