Jump to content

SVLTE and Tri-band LTE – Provider/Device Capabilities


Recommended Posts

This came about from someone’s post over on XDA and my response to it (link) in which I promised to check its accuracy with the gurus here. Basically, the poster interpreted the lack of SVDO/SVLTE on the Sprint HTC One M8 as an “oversight,” and I respectfully disagreed, but it raised a few questions that I haven’t been able to answer.

1.) Will Sprint be transmitting LTE on more bands nationwide than the other carriers?
2.) If the answer to question 1 is “yes,” then does tri-band LTE come at the cost of SVLTE because Sprint tri-band phones will be switching between bands more frequently so the network can distribute the load?

Here’s my rationale:

1.) Knowing that NV rollout is nationwide, and knowing that the end-goal is to have 2600 and 1900 MHz on all towers as well as 800 MHz LTE on 80% of the towers, it’s safe to say that Sprint will have tri-band LTE across the country.  From what I understand, AT&T, T-Mobile, and Verizon might only have 1 or 2 bands per market (maybe more in certain places for AT&T/T-Mobile):

AT&T: 700/AWS/1900/2300 MHz
Sprint: 800/1900/2500 (2600) MHz
Verizon: 700/AWS MHz
TMUS: 700/AWS/1900 MHz

List of LTE networks - Wikipedia
AT&T Mobility - Wikipedia
Sprint - Wikipedia
Verizon - Wikipedia
T-Mobile USA - Wikipedia
2.) Since the other carriers have fewer bands in a given region, the phones will be switching between them less, leaving extra room (for lack of a better word) for SVLTE on certain devices.  Since we’re talking about the HTC One M8, let’s use it as an example.  Here are the frequencies for each of the carrier-specific models:

AT&T: 700/850/AWS/1800/1900/2600 MHz
Sprint: FDD 800/1900 MHz , TDD 2600 MHz
Verizon: 700/AWS/1800/2600 MHz

Source: M8 spec page

AJ referenced this issue with the radio paths which may be related to this (not for the M8, but possibly still applicable):

Now, one reason for that could be largely, even exclusively Sprint specific because Sprint is running CDMA2000 and LTE in the same PCS 1900 MHz band.  Off the top of my head, I can think of no other operator in the world running CDMA2000 and LTE in the same frequency band.  So, for SVLTE devices, that presents a filter challenge.  Both of the two separate radio paths are transmitting/receiving at similar PCS frequencies, and they are only centimeters, even millimeters apart inside the handset.  Keeping CDMA1X 1900 from interfering with LTE 1900 and vice versa becomes a challenge or a shortcoming of SVLTE devices.

…which prompted the following question in that same thread which remains unanswered:

But if thats the case in a triband phone wouldn't it be easier to handle than on a single band hone since during a call say 1900, just have the phone use LTE band 41 or fallback to 800Mhtz for LTE to preserve SVLTE (while not causing 1900 issues)?

Link to comment
Share on other sites

No provider has SVLTE capable devices except Verizon (on new devices).  AT&T and Tmo do not have SVLTE.  They fallback to their 3G network to do voice and data together.  Verizon is the only one who has decided to run dual transmission paths for LTE and pay the price accordingly to allow SVLTE.  This is not a network issue, it is a device issue.


The more bands you add, it becomes more and more difficult and expensive to try to keep dual path transmission for LTE and a 3G voice technology to be used together.  And it becomes really difficult when one of those bands is TDD (supposedly).



  • Like 3
Link to comment
Share on other sites

This is turning into a place where trolls can bash Sprint, and extol the virtues of Tmo.  I am closing the thread and posts have been removed.  This is OLD NEWS, and has been discussed to death throughout our forums.  No one is saying anything new, including me.  


If someone needs simultaneous voice and data, they will need a Sprint Uniband device or another provider.  Period.



  • Like 9
Link to comment
Share on other sites

This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Or, more simply, have a physical SIM that I can just move from one device to another.  Problem [already] solved.  Carrier doesn't have to be involved at any point in the process. I'll be among many (I'm sure) who will be glad to know if you see it.  Here in the DC area, Dish hasn't really done much yet.  I think I've seen some Dish gear around Richmond, but nothing here. - Trip
    • I like VICE.  They actually report on news no one else is willing to report. A lot of the places they go no sane person would want to be there.  They put their life on the line in many cases to get a story. From stories about the avocado wars in Mexico, being in the front lines against ISIS and Ukraine, to being embedded with terrorist organizations.   FAA might have some conspiracy 5G nut on their team or something.  At work ever year we have some one come in and say "hey, can you turn off the WIFI in my room? I don't want its radiation".  It doesn't make sense and their reasoning is always uneducated conspiracy. I can see someone coming into my office and acting crazy over C band disregarding everything else.
    • I think on esims it depends on how they implement it. If you can freely activate them on one phone while having it loaded on many that would be great.   I will let you know when I see Boost Mobile native 5g live here. So far no sign of even the plmn being active which I figure will be my first indicator. I look at changing networks with the TNX Sim and seem to get a full list of all carriers and their alternate plmns.
    • This is a result of the change I mentioned above, sparked by @PedroDaGr8 trying to log AT&T cells with a non-AT&T SIM that was reporting "out of service" but still capturing cell info. For the moment (subject to change as I keep testing and getting feedback), the "Connecting to" prefix will disappear when you connect in a scenario like that. I may adjust it to show a special prefix like "Limited LTE" or "No Data LTE" to make it more clear what is going on, but I also need to make sure that's only appearing at the proper times. When you were seeing just "LTE" in your screenshots, was there anything unusual about your connection? I see the app indicated you couldn't make calls; could you transfer data? Can you send a diagnostic report next time you see that?   I'm seeing this more frequently, unfortunately -- it has something to do with Android's power saving efforts I believe. Was the app in the foreground when it happened? When the screen updates, the notification and home screen widget are also updated -- but as seen with the widget for the past couple of years, Android doesn't always execute the update. I'm constantly trying to find ways around these limitations, since the app is useless if it's displaying stale data.
    • Bleh, hope not.  The eSIM is a huge step backwards to the bad old days and I have no desire to encourage their use. But in any event, maybe I should get Boost service, then, if people are already seeing it.  I can use it for AT&T until Dish native gear goes live in this area.  Have to ponder that a bit. - Trip
  • Recently Browsing

    • No registered users viewing this page.
  • Create New...