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.
Related
So will the Nexus 5 support VoLTE?
AT&T has said VoLTE starts deployment by the end of this year. Does anyone think the Nexus 5 will work on AT&T's VoLTE?
This thread doesn't have to be about speculation. This is XDA and I expect more technically from this forum. Let's think about this systematically. What is required for a phone to work on VoLTE? Is the LTE hardware enough? Probably not. I think we can all agree that the software has to support it. I've read that the LG Connect 4G on MetroPCS supports VoLTE since they have already deployed VoLTE and it is supported using that phone. So that means Android has had VoLTE since Android 2.3 Gingerbread. Was that custom software for the LG Connect or is there still code in Android supporting VoLTE? Is anyone knowledgeable to look at Android 4.3 source files to see evidence of VoLTE living there, in comparison to the Android source in the LG Connect? Maybe there are system files in Android that have VoLTE in their name. That would be a good clue.
Was there anything in the LG Connect's FCC documentation that specified VoLTE testing or specifications? Is this needed for VoLTE? Or is LTE testing alone enough since it is all the same from a physical frequency perspective?
I brought this topic up in another forum and I got some good responses. I just want to take it to the next level here with all the gear heads and XDA wizardry that lives here.
Sent from my Nexus 10 using Tapatalk 4
galfert said:
So will the Nexus 5 support VoLTE?
AT&T has said VoLTE starts deployment by the end of this year. Does anyone think the Nexus 5 will work on AT&T's VoLTE?
This thread doesn't have to be about speculation. This is XDA and I expect more technically from this forum. Let's think about this systematically. What is required for a phone to work on VoLTE? Is the LTE hardware enough? Probably not. I think we can all agree that the software has to support it. I've read that the LG Connect 4G on MetroPCS supports VoLTE since they have already deployed VoLTE and it is supported using that phone. So that means Android has had VoLTE since Android 2.3 Gingerbread. Was that custom software for the LG Connect or is there still code in Android supporting VoLTE? Is anyone knowledgeable to look at Android 4.3 source files to see evidence of VoLTE living there, in comparison to the Android source in the LG Connect? Maybe there are system files in Android that have VoLTE in their name. That would be a good clue.
Was there anything in the LG Connect's FCC documentation that specified VoLTE testing or specifications? Is this needed for VoLTE? Or is LTE testing alone enough since it is all the same from a physical frequency perspective?
I brought this topic up in another forum and I got some good responses. I just want to take it to the next level here with all the gear heads and XDA wizardry that lives here.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
i love your inquiry!
as we all know, tmobile's launching VOlte in seattle, via s/w upgrade to various phones, but why that way?
wouldn't it had been easier via an updated volte capable sim card with the needed provisioning?
what governs any phone's baseband code on certain networks; is it HARD coded, or SOFT coded, to change on the fly, depending on the network? -
iPhone can support VoLTE
that link also addresses how volte is implemented on tmobile's network..
or if one prefer - How it works: Voice over LTE (VoLTE)
one thing for sure, qualcomm & erricsson trialed volte on an earlier snapdragon chipset (Qualcomm's Snapdragon S4 MSM-8960)
the nexus 5's snapdrag, is a newer **Qualcomm MSM8974 snapdragon 800** .. i would doubt it DOESN'T
support volte, why add the feature to an older chipset, & not include it by default in a newer.. -
Qualcomm's Snapdragon almost ready for Voice over LTE (VoLTE) (February 2, 2012)
~edit~
i'm so glad i'm not mentally lazy (that's why i use linux dammit) the nexus 5 CAN DO VOLTE! -
Doug M.
Chief Operating Officer (COO) and Chief Sales & Marketing Officer (CSMO) at D2 Technologies, Inc.
We (www.d2tech.com) are trying to break the "chicken/egg" cycle by providing a commercial-ready reference implementation for native IR.92 VoLTE, IR.94 and RCS 5.1 / joyn for mobile devices. At MWC, we demo'd it on a Nexus 5, Huawei Ascend G716-L070, Nvidia’s Tegra 4i reference platform and an Intel® Atom™ based commercial handset. We're also providing several LTE modem IC vendors with an embedded IR.92 VoLTE solution that has APIs in the LTE modem IC to the mobile AP that allow the RCS/IR.94/WiFi calling capabilities embedded in the mobile OS to leverage the IMS registration and SIP signaling stack, and DSP voice engine that now reside in the modem IC. This makes it very easy for device OEMs to provide native RCS and/or VoLTE and IR.94 video calling.
from - http://www.linkedin.com/groups/China-Set-Lead-RCS-Integration-1890406.S.5849549644362706944
the nexus 5 can do volte on china mobile now, from china mobile's volte white paper - http://www.lte-tdd.org/upload/accessory/20138/20138271114319913691.pdf
3.4 Terminal Aspects
3.4.1 Multi-Mode and Multi-band
To meet the requirements for domestic frequency access and international roaming,
five radio modes including FDD LTE, TD-LTE, TD-SCDMA, WCDMA, GSM
should be supported by China Mobile TD-LTE terminals, which are divided into the
basic type and the enhanced type: the basic type terminal should support 5 modes and
10 bands, the enhanced type terminal should support 5 modes and 12 bands.
Furthermore, terminals with other multi-mode and multi-band capabilities can be
introduced to meet the market needs.
Supporting the Band41（2496-2690MHz）is mandatory for TD-LTE terminals in
2014. If the terminal support Band 41 without Band 38, it must comply with the
3GPP TS36.331 R8.H.0 and later versions, while for the terminal with both
Band41 and Band38, it is not needed to support the 3GPP TS36.331 R8.H.0
version.
qualcomm msm8974ab bring up kernel log ( that the nexus 5 has)
<6>[ 11.666645] pil-q6v5-mss fc880000.qcom,mss: modem: loading from 0x08000000 to 0x0d100000
<6>[ 11.667153] asoc: snd-soc-dummy-dai <-> SLIMBUS4_HOSTLESS mapping ok
<6>[ 11.668196] asoc: snd-soc-dummy-dai <-> VoLTE mapping ok
<3>[ 11.669309] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while writing to '/proc/sys/vm/extra_free_kbytes'
& this is an interesting read, (not for the lazy) -
The State of Qualcomm's Modems - WTR1605 and MDM9x25
**comment from the article** -
iwod - Sunday, January 06, 2013 - link
"Interesting, i was late to the article and there is only 10 comments, compared to 3 page on ARM vs Atom. People not interested in LTE / Baseband at all??
Anyway, so do LTE UE 4 offer better bandwidth efficiency then UE 3? Since both only required 20Mhz, but UE 4 gives up to 150Mbps.
Apart from Beidou and TDS-CDMA, WTR1605 seems like a small step, no size reduction?
Are there any power improvement with 9x25? LTE seems to be draining battery a lot.
So i gathered all current Qualcomm already support VoLTE, we are only waiting for carrier to support it, right? And may be off topic, why aren't carrier doing it / Faster?
I am not sure if i am right, the more port there are, the more supported band / wireless spec there will be. It seems to be one of the reason iPhone 5 could not come with world wide LTE supported. So wouldn't ditching GSM help? ( 4G is here.... time to ditch 2G right? )
How do WiFi and Bluetooth fits into the scenario? They are all wireless tech, why do they requires another chip? Couldn't Qualcomm fits those in?
I remembered there was a article about Intel Digital Radio. I admit i still do not understand much of it. Any relation to this? Or is Digital Radio more on the antenna side of things."
**reply to that**-
DanNeely - Sunday, January 06, 2013 - link
"VoLTE increases the load on their 4g networks by reducing the load on 2g/3g; since 4g is only going to get more crowded with time while 2g is becoming a ghost town and 3g will become one in the next few years as LTE deployments are completed, VoLTE does nothing beneficial for the carriers in the short term.
Long term it's needed to let them shut down their legacy networks; but that's at least 4-5 years out according to occasional talking points they make (and if Sprint/iDEN is any indication even farther out in the real world) which makes it not worth enabling for handsets that will probably be junked well before it happens."
...........
we can deduct, that all current qualcomm chipsets have the VOlte feature baked in (but dormant for some odd reason);
tmobile, enables it on selected handsets via a pushed software update, not via an updated **VOlte sim** = Generic Bootstrapping Architecture
&
Subscriber Authentication in the IP Multimedia Subsystem
..
~shrugz shoulderz~
Probably to tie you into T-Mobile branded handsets where they make huge margins. Same as Wi-Fi calling.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Probably to tie you into T-Mobile branded handsets where they make huge margins. Same as Wi-Fi calling.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know how it works now;
the tmobile update *FULLY* enables the sip protocol on it's IMS ( IP Multimedia Subsystem) to match what's dormant in the phone ALREADY..
it's basically SIP ( with heightened QoS) -
read that - http://www.howardforums.com/showthread.php/1833821-Tmobile-launches-VoLTE-in-Seattle/page6
then
this - http://lteuniversity.com/get_trained/expert_opinion1/b/bbest/archive/2012/12/17/the-volte-conversation-between-ims-and-lte.aspx
...voLTE basically , speaks in SIP (session initiated protocol) -
http://www.sharetechnote.com/html/Handbook_LTE_VoLTE.html - the picture in this link with the raw network traffic can be mimicked with a tmobile sanctioned volte device, tethered wirelessly to a laptop in promicous mode, with wireshark or tcpdump, with the right arguments, or both, & with the said tmobile phone in a call session, the packets can be dumped & analyzed afterwards..
j'vai said:
i know how it works now;
the tmobile update *FULLY* enables the sip protocol on it's IMS ( IP Multimedia Subsystem) to match what's dormant in the phone ALREADY..
it's basically SIP ( with heightened QoS) -
read that - http://www.howardforums.com/showthread.php/1833821-Tmobile-launches-VoLTE-in-Seattle/page6
then
this - http://lteuniversity.com/get_trained/expert_opinion1/b/bbest/archive/2012/12/17/the-volte-conversation-between-ims-and-lte.aspx
...voLTE basically , speaks in SIP (session initiated protocol) -
http://www.sharetechnote.com/html/Handbook_LTE_VoLTE.html - the picture in this link with the raw network traffic can be mimicked with a tmobile sanctioned volte device, tethered wirelessly to a laptop in promicous mode, with wireshark or tcpdump, with the right arguments, or both, & with the said tmobile phone in a call session, the packets can be dumped & analyzed afterwards..
Click to expand...
Click to collapse
@galfert.. now that we KNOW at it's heart, VOlte speaks sip, it would be work to mimc the sip settings from another tmobile VOlte phone to a nexus 5 on the tmobile network..
it'll be lengthy, adding the bearer info, secondary bearer info, number + proper sip addy, & parking it on lte..
*BUT* it wouldn't work STILL, unless the UE (user equiptment) gets the OK'd update on tmobile's IMS gateway, *TO* set up & tear down the voice bearer connection with properly enhanced Q0S offered by the IMS..
the sip setting for the nexus 5 are in the phone setting for internet calls, & actually, i'll plug a thread started in here from 13 on this very subject -
Nexus 5 - Internet Calling Experience/SIP Thread by BinkXDA ..
the tools are in the device, but aren't complete from the network perspective..
& yet, i know NOT if tmobile could fashion this update for phone(s) a lil bit more heavier, where those un-known fields needed, are automatically populated.. maybe they're working on that for the future..
Here is something else to consider. T-Mobile has WiFi calling. Google Voice users for a long time have used apps to do VoIP over Google Talk XMPP and still can despite it being past the date. So who is to say an app couldn't just do it or they couldn't use just the SIP part of the phone app? Get the right codec and it is golden.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Here is something else to consider. T-Mobile has WiFi calling. Google Voice users for a long time have used apps to do VoIP over Google Talk XMPP and still can despite it being past the date. So who is to say an app couldn't just do it or they couldn't use just the SIP part of the phone app? Get the right codec and it is golden.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
you're so right...
i use groove IP to call over lte, evdo, & wifi at times, after tinkering with the echo settings, it's as clear as any voice call..
only with the tmobile volte set up, the plus is you're using your same mobile number still (google snatched that away when breaking xxmp protocol in gv) ..
but with adjusting, the QoS can be just as good as your connection allows the call to be.. mine's is with groove IP / ring.to
galfert said:
So will the Nexus 5 support VoLTE?
AT&T has said VoLTE starts deployment by the end of this year. Does anyone think the Nexus 5 will work on AT&T's VoLTE?
This thread doesn't have to be about speculation. This is XDA and I expect more technically from this forum. Let's think about this systematically. What is required for a phone to work on VoLTE? Is the LTE hardware enough? Probably not. I think we can all agree that the software has to support it. I've read that the LG Connect 4G on MetroPCS supports VoLTE since they have already deployed VoLTE and it is supported using that phone. So that means Android has had VoLTE since Android 2.3 Gingerbread. Was that custom software for the LG Connect or is there still code in Android supporting VoLTE? Is anyone knowledgeable to look at Android 4.3 source files to see evidence of VoLTE living there, in comparison to the Android source in the LG Connect? Maybe there are system files in Android that have VoLTE in their name. That would be a good clue.
Was there anything in the LG Connect's FCC documentation that specified VoLTE testing or specifications? Is this needed for VoLTE? Or is LTE testing alone enough since it is all the same from a physical frequency perspective?
I brought this topic up in another forum and I got some good responses. I just want to take it to the next level here with all the gear heads and XDA wizardry that lives here.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
One thing you've forgotten to mention is Qualcomm's proprietary baseband firmware that has to have VoLTE support enabled. It's all closed source and signed.
We know that N5's baseband processor itself is capable, but if the firmware isn't there to enable and drive VoLTE, no matter which software you create over-the-top, it won't magically turn on VoLTE.
The main and most important difference between VoLTE and third party VoIP solutions like Skype, FaceTime, etc, is that VoLTE processing happens at the very baseband level, which handles phone call continuity between LTE and UMTS/GSM, and also makes it more efficient.
On the other hand, OTT processing is all OS/SoC.
I asked T-Mobile's technical guru about it a while back, here's what I got:
https://twitter.com/askdes/status/469582255191388160
Hilbe said:
I asked T-Mobile's technical guru about it a while back, here's what I got:
https://twitter.com/askdes/status/469582255191388160
Click to expand...
Click to collapse
https://twitter.com/TMobileHelp/status/479798004627427328
from 20 days ago.
Sorry for digging up this old thread, but after reading the how-does-VoLTE-work article, there's a point that nobody has mentioned yet...
While engaged in a voice call, a user might pass outside of an LTE coverage area, so that call needs to be able to fall back onto legacy networks. The VoLTE standard accomplishes this with Single Radio Voice Call Continuity (SR-VCC).
[...]
SR-VCC requires the network provider to have the IMS framework in place, but it also impacts device design. To support SR-VCC, devices must not only be able to connect to both the LTE and the legacy networks, but be able to connect to both at the same time. This is governed by the antenna architecture in the device. In order to conserve space, some devices, like the iPhone 5, will have 3G and 4G traffic sharing the same physical antennae, toggling between the two standards as needed. SR-VCC requires devices to have dedicated antennae for both 3G and 4G connections.
Click to expand...
Click to collapse
I may be mistaken about this, but the antenna is shared on the Nexus 5, isn't it? So it cannot support the LTE-to-3G handoff and as a result may never support VoLTE...
I've read it cannot, but by the time this technology is rolled out in a major way the phone will be verging on obsolete, I'm still happy with mine though
code65536 said:
Sorry for digging up this old thread, but after reading the how-does-VoLTE-work article, there's a point that nobody has mentioned yet...
I may be mistaken about this, but the antenna is shared on the Nexus 5, isn't it? So it cannot support the LTE-to-3G handoff and as a result may never support VoLTE...
Click to expand...
Click to collapse
Just watched a disassembly video on YT and he showed the Nexus 5 has two antennas. One for 2/3G and one for LTE.
Gesendet von meinem C5502 mit Tapatalk
Any confirmation on this?
I also only saw two antennas as I replaced my screen.
Ifixit.com says its MIMO and GPS antenna:
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016/[URL]
Any confirmation? Any help?
Planning to buy a new Mi4 from kijiji. Wondering whether it supports LTE bands in Canada? I;'m with telus
Short answer. No, not yet.
veladem said:
Short answer. No, not yet.
Click to expand...
Click to collapse
OK.Thanks
Is this a software issue or the LTE version is a different hardware in the future? In other words, if i buy the mi4 now, will i be able to get LTE when its available?
Sadly it seems to be a hardware limitation. Xiaomi was smart when they made the phone and only have it what it needed unlike some companies that overlook the small things and pay in the end.
yes it does not. as no opomart and other sites are selling FDD-LTE version which 1700/2100 works perfect with ATT / T-Mobile in US
4G:FDD-LTE 1800(B3)/2100(B1)MHz
This may seem far fetched but I'll ask anyway. Is there a way to change the hardware frequencies set within the phone to match the connectivity frequencies that's in your area?
shakim24 said:
This may seem far fetched but I'll ask anyway. Is there a way to change the hardware frequencies set within the phone to match the connectivity frequencies that's in your area?
Click to expand...
Click to collapse
In theory, the chip should support them. It would be a matter of writing the specific band values into your phones memory (NV). However, this pre-supposes that the phone could be modified on that level to begin with, which is doubtful.
You would need:
Unlock/root
Custom rom
Custom kernel
QPST (for editing)
QXDM (write enabling)
access to switch usb diagnostic mode
The majority of the work would be getting around MIUI and Qualcomm's restrictions they implement in their code. While not impossible, as you can see, the changes required aren't necessarily for the faint of heart. I suppose one upside would be the phone doesn't cost an arm and a leg, so if you wound up with a brick, you might have an easier time bouncing back from the loss.
kibmikey1 said:
In theory, the chip should support them. It would be a matter of writing the specific band values into your phones memory (NV). However, this pre-supposes that the phone could be modified on that level to begin with, which is doubtful.
You would need:
Unlock/root
Custom rom
Custom kernel
QPST (for editing)
QXDM (write enabling)
access to switch usb diagnostic mode
The majority of the work would be getting around MIUI and Qualcomm's restrictions they implement in their code. While not impossible, as you can see, the changes required aren't necessarily for the faint of heart. I suppose one upside would be the phone doesn't cost an arm and a leg, so if you wound up with a brick, you might have an easier time bouncing back from the loss.
Click to expand...
Click to collapse
Thanks for the insight bro. You really broke down into detail what was needed to be done. Was scrolling around and found this thread http://forum.xda-developers.com/showthread.php?t=2871269. Would like your opinion on it. It's for unlocking LTE as well.
I think they released the LTE-FDD version , seach for it!
already got one with LTE...its out already
Hi, I don't know how helpful this is for you but I have bought two from China for myself and my wife. Although I have not tried on the MIUI OS, I have flashed AOSP on to both phones and they both work at least on O2 and EE. I am receive 4G on my EE Mi4, however my wife does not have a 4G sim so can not confirm hers but she does receive 3G signals.
O2s 4G sim did not receive 4G signals on my Mi4 though (reason for me switching)
Hope this helps you
Only bands 1, 3, 41
I'm having a hard time finding a definitive answer about which LTE band I'll lose using the tmobile variant on att.
I don't think any, I think both are identical. I am using the N920T with AT&t. I would suggest you consider using DarthStalkers ROM, he was able to pull the AT&T carrier files.
The N920T & A are the same. If you had bought the N920I you might lose bands.
Does anyone know where I can get a band 12 coverage map? I can only find the LTE coverage map which doesn't specify if band 12 is used there
wdkingery said:
I'm having a hard time finding a definitive answer about which LTE band I'll lose using the tmobile variant on att.
Click to expand...
Click to collapse
17 and 30 (I don't think the 920t's band 12 will work with AT&T's B17 - even though 12 is a subset of 17 (or do I have that backwards?) Possibly 29 (downlink only for AT&T) - but there's very little documentation on B29, so I'm not sure if the N920A supports it or not.
garyd9 said:
17 and 30 (I don't think the 920t's band 12 will work with AT&T's B17 - even though 12 is a subset of 17 (or do I have that backwards?) Possibly 29 (downlink only for AT&T) - but there's very little documentation on B29, so I'm not sure if the N920A supports it or not.
Click to expand...
Click to collapse
Could you be so kind as to translate what that will mean to me? I have a t-mobile note 4 here on att and it seems to do fine.. Do you think I'll be so lucky with the note 5?
wdkingery said:
Could you be so kind as to translate what that will mean to me? I have a t-mobile note 4 here on att and it seems to do fine.. Do you think I'll be so lucky with the note 5?
Click to expand...
Click to collapse
Band 29 is rarely used by AT&T (only as a downlink in heavily congested areas.) This shouldn't be a problem.
Band 30 (WCS band) is something AT&T _just_ started deploying, but I've never seen it in actual use. In fact, until very recently, none of AT&T's own phones supported it. B30 is really of limited value for general use due to it's propagation (or lack thereof.) Like 29, its probably only used as a supplement to other bands. I wouldn't worry about B30.
B17, however, is a Big Deal for AT&T. That's AT&T's primary "lower frequency" LTE band. Because of the low frequency, it has excellent propagation (meaning it moves farther and through trees, buildings, etc.) They use this band to cover large geographical areas with minimal towers. If you will be using your phone in a non-urban area, B17 is almost essential for AT&T. (My phone spends the majority of the time at my home on B17.)
I haven't heard of anyone with a TMO Note 5 device (without explicit B17 support) attaching to AT&T's B17, but that doesn't mean it won't work. However, Unless someone confirms B17 functionality on the n290T from actual use (and not just what they think), I'd suggest assuming that it won't work.
garyd9 said:
Band 29 is rarely used by AT&T (only as a downlink in heavily congested areas.) This shouldn't be a problem.
Band 30 (WCS band) is something AT&T _just_ started deploying, but I've never seen it in actual use. In fact, until very recently, none of AT&T's own phones supported it. B30 is really of limited value for general use due to it's propagation (or lack thereof.) Like 29, its probably only used as a supplement to other bands. I wouldn't worry about B30.
B17, however, is a Big Deal for AT&T. That's AT&T's primary "lower frequency" LTE band. Because of the low frequency, it has excellent propagation (meaning it moves farther and through trees, buildings, etc.) They use this band to cover large geographical areas with minimal towers. If you will be using your phone in a non-urban area, B17 is almost essential for AT&T. (My phone spends the majority of the time at my home on B17.)
I haven't heard of anyone with a TMO Note 5 device (without explicit B17 support) attaching to AT&T's B17, but that doesn't mean it won't work. However, Unless someone confirms B17 functionality on the n290T from actual use (and not just what they think), I'd suggest assuming that it won't work.
Click to expand...
Click to collapse
An informative post if ever there was one indeed.
What app do you use to determine which hand your phone is connected thru? I have found this app "LTE discovery", and it seems my att note 3 stays connected to 5 mostly, or 4 for lte. But then for GSM is doesn't list a band, but appears connected. On her t-mobile note 4 connected to att, she stays on 5, but the GSM doesn't appear to be connected to anything..
We will be almost exclusively in the middle of a city, but as with anything that could change or in the event of a road trip..
Is there a place I can sit and study this information? Perhaps a website with all of this data? Or do you happen to work in the field?
In a sea of noobs, an informed person is a real diamond in the rough - I appreciate your time.
wdkingery said:
What app do you use to determine which hand your phone is connected thru? I have found this app "LTE discovery", and it seems my att note 3 stays connected to 5 mostly, or 4 for lte.
Click to expand...
Click to collapse
That's a good app to use. I also use my phone's diagnostic menu's, but I doubt AT&T left those enabled on the 'a' variant.[/QUOTE]
wdkingery said:
But then for GSM is doesn't list a band, but appears connected. On her t-mobile note 4 connected to att, she stays on 5, but the GSM doesn't appear to be connected to anything..
Click to expand...
Click to collapse
Is that with "lte discovery" that she doesn't appear to have any GSM side connection? She most likely does, as that's where voice calls will take place...
wdkingery said:
Is there a place I can sit and study this information? Perhaps a website with all of this data?
Click to expand...
Click to collapse
Google. Then google some more. If you run out of pages from google, use another search engine. All the information is readily available - it just takes time to find it all.
garyd9 said:
That's a good app to use. I also use my phone's diagnostic menu's, but I doubt AT&T left those enabled on the 'a' variant.
Click to expand...
Click to collapse
Is that with "lte discovery" that she doesn't appear to have any GSM side connection? She most likely does, as that's where voice calls will take place...
Google. Then google some more. If you run out of pages from google, use another search engine. All the information is readily available - it just takes time to find it all.[/QUOTE]
so i got through all the hoops.. don't have LTE ;-(
it connects to band 4 or 5 when i first come out of airplane mode, but it jumps right back off. stuck on 4g. called at&t for an hour, they said initially it wasn't provisioned on my sim card, but then afterwards they determined it was a problem on my end, walked my thru APN settings and then ended the call.. still no LTE.
do you have an opinion of what i could do?
wdkingery said:
do you have an opinion of what i could do?
Click to expand...
Click to collapse
Quoting me in a thread was enough... didn't have to also PM me...
@TEKHD has a firmware that might work for you. Check it out over here: http://forum.xda-developers.com/tmo...h6-tekxodus-n5-urv1-00-00-lollipop-5-t3201869
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
I haven't tried this (and I don't even have a 't' variant myself.) On the other hand, a quick search of that thread seems to show that other people are having successes with AT&T sim's on 't' variant devices.
Good luck!
Gary
sorry about the double.
after a precursory examination, idon't see exactly what you are talking about in his thread..
is it a download?
garyd9 said:
Quoting me in a thread was enough... didn't have to also PM me...
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
Good luck!
Gary
Click to expand...
Click to collapse
the search feature doesn't appear to work for me; shows 0 results on att or at&t.. i'm having to sift thru all 114 pages by hand.
garyd9 said:
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
Gary
Click to expand...
Click to collapse
i searched all 114 pages and didn't find reference to any of that.. now i know why search provided no results; there weren't any!
so i need to find the att ril libraries. how will i ever find that.
wdkingery said:
i searched all 114 pages and didn't find reference to any of that.. now i know why search provided no results; there weren't any!
so i need to find the att ril libraries. how will i ever find that.
Click to expand...
Click to collapse
Maybe that was the wrong firmware... it's something in the TMO dev section. Please search.
garyd9 said:
Maybe that was the wrong firmware... it's something in the TMO dev section. Please search.
Click to expand...
Click to collapse
i've searched the entire tmo dev section for term "at&t" and there are sparse hits; there is some conversation about CSC for a guy in canada getting his VoLTE working, but nothing on att.
wdkingery said:
i've searched the entire tmo dev section for term "at&t" and there are sparse hits; there is some conversation about CSC for a guy in canada getting his VoLTE working, but nothing on att.
Click to expand...
Click to collapse
Apparently, you already found it: http://forum.xda-developers.com/tmo...on-1-aroma-t3212091/post63516726#post63516726
This has AT&T RIL's in the update.zip, and from a quick look at the first post in that thread, they are installed based on an aroma installer. Others in that thread claim it works for them. You're using a TMO device on ATT, so you have to expect some level of incompatibility. There are AT&T LTE bands that the TMO device simply doesn't support. It doesn't matter what happens with your Note 4. Different device and different modem.
So, if you want to use a TMO device on ATT, you'll have to make some sacrifices. Most people will find the sacrifices are less drastic using an international version of the phone. For some reason, US carriers go out of their way to ensure their devices are incompatible with each other.
garyd9 said:
Apparently, you already found it: http://forum.xda-developers.com/tmo...on-1-aroma-t3212091/post63516726#post63516726
This has AT&T RIL's in the update.zip, and from a quick look at the first post in that thread, they are installed based on an aroma installer. Others in that thread claim it works for them. .
Click to expand...
Click to collapse
ok this is where i started, by flashing the ATT option for this rom. but that doesn't solve the problem. i'm in the process of clean flashing the tmobile choice like he suggested.
thanks for all your help.
i'm afraid this isn't going to work either. i realize the wife's note 4 may have different hardware, and isn't a good reference.
i can see the thing connect to band 5, then band 4, lte .. but it's in "emergency calls only" mode, then it gives up on that, connects to HSUPA or HSPA+ and that's the last of an LTE connection.
i feel like it would connect if it could, and that i'm having a software issue.
problem solved guys sorry for the large headache..
Solution:
AT&T did not recognize my IMEI as being LTE capable. Because of that, they decline to allow my phone to connect to LTE. My phone would connect to an LTE tower (as in the screen shots a few pages back), but wouldn't receive anything back from AT&T, so it would say "emergency calls only" and then give up after about 10 seconds, and then never go back. Crap data all around at this time.
What you'll need to do is walk into an AT&T store, take a picture of the IMEI off an LTE phone, and then call in and change your IMEI to the phone you found. This will cause the system to recognize your phone as LTE capable, and like magic, you'll have LTE.
I can confirm that I have a tmobile branded unit that attaches to band 17. It isn't as frequently as on my note 4, I'm generally on band 2. With that said I've had virtually no trouble with service. I was initially worried about the b17 issue, but it hasn't seemed to make any difference.
intifadamericana said:
I can confirm that I have a tmobile branded unit that attaches to band 17. It isn't as frequently as on my note 4, I'm generally on band 2. With that said I've had virtually no trouble with service. I was initially worried about the b17 issue, but it hasn't seemed to make any difference.
Click to expand...
Click to collapse
Does it attach to band 17 on AT&T or t-mobile?
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.