Jump to content

Will Sprint ever share or roam on anyone's 700 MHz?

dro1984

By dro1984
in General Topics

 Share

Recommended Posts

WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

No, and no.  But no one knows the future.  So, no again.

 

AJ

Link to comment
Share on other sites
Tengen31 Member Level: 4G LTE

Tengen31

Posted
Posted

Does anyone know if Sprint will ever share or roam on T-Mobile's or AT&T's 700 MHz?   I thought the FCC mandated roaming abilities on the 700 band?

Sprint does Roam onto US CELLULAR LTE which I believe uses band 12. Tmobile coverage is close to Sprint So Sprint wouldnt do much roaming onto them .Yes their are spots where Tmobile covers that sprint does not but, its small. I wish sprint could get their hands on their Native 700 mhz. Can say for sure no LTE on VZW. Also Theres no band 17 support on Sprint phones only band 2,4,5,12.

Link to comment
Share on other sites
gusherb Member Level: eHRPD

gusherb

Posted
Posted

Sprint does Roam onto US CELLULAR LTE which I believe uses band 12. Tmobile coverage is close to Sprint So Sprint wouldnt do much roaming onto them .Yes their are spots where Tmobile covers that sprint does not but, its small. I wish sprint could get their hands on their Native 700 mhz. Can say for sure no LTE on VZW. Also Theres no band 17 support on Sprint phones only band 2,4,5,12.

Having band 17 support on Sprint phones is moot if they ever were to strike a roaming deal with at&t as they have MFBI active across their network so any band 12 device will work on at&t.

Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

Guys, this thread is largely pointless -- because it is all pie in the sky fantasy.  That is why I am being somewhat sarcastic.

 

The chances of Sprint LTE roaming on VZW, AT&T, or T-Mobile within the next several years are slim to none.  Sprint handsets do not support VZW band 13.  AT&T and T-Mobile do not support CDMA2000.  Game over.

 

The likelihood of Sprint becoming a merged company or going belly up is greater than that of LTE roaming on VZW, AT&T, or T-Mobile.

 

AJ

  • Like 2
Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

Just wondering.... I thought one of the FCC requirements when auctioning off 700 MHz years ago was carrier interoperability?

 

No.

 

AJ

Link to comment
Share on other sites
Sprke Member Level: 3G EVDO

Sprke

Posted
Posted

Guys, this thread is largely pointless -- because it is all pie in the sky fantasy. That is why I am being somewhat sarcastic.

 

The chances of Sprint LTE roaming on VZW, AT&T, or T-Mobile within the next several years are slim to none. Sprint handsets do not support VZW band 13. AT&T and T-Mobile do not support CDMA2000. Game over.

 

The likelihood of Sprint becoming a merged company or going belly up is greater than that of LTE roaming on VZW, AT&T, or T-Mobile.

 

AJ

What does CDMA have to do with it when VoLTE comes into play? Who's Sprint going to use when Verizon shuts off CDMA voice in the future?

 

 

Sent from my iPad using Tapatalk

Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

What does CDMA have to do with it when VoLTE comes into play? Who's Sprint going to use when Verizon shuts off CDMA voice in the future?

 

VoLTE is irrelevant to Sprint for now.  Carefully read my post.  See "within the next several years"?  No one knows what will be 4-5 years from now.  That is why this thread is just pointless speculation.

 

AJ

Link to comment
Share on other sites
Tengen31 Member Level: 4G LTE

Tengen31

Posted
Posted

What does CDMA have to do with it when VoLTE comes into play? Who's Sprint going to use when Verizon shuts off CDMA voice in the future?

 

 

Sent from my iPad using Tapatalk

Sprint phones have some GSM in them. so CDMA has nothing to do with it. I already said roaming onto VZW will never happen.

Link to comment
Share on other sites
  • 2 weeks later...
dfc Member Level: Smoke Signals

dfc

Posted
Posted

Guys, this thread is largely pointless -- because it is all pie in the sky fantasy.  That is why I am being somewhat sarcastic.

 

The chances of Sprint LTE roaming on VZW, AT&T, or T-Mobile within the next several years are slim to none.  Sprint handsets do not support VZW band 13.  AT&T and T-Mobile do not support CDMA2000.  Game over.

 

The likelihood of Sprint becoming a merged company or going belly up is greater than that of LTE roaming on VZW, AT&T, or T-Mobile.

 

AJ

 

iPhone 6S supports B13. Verizon is still gonna be a no-go.

 

Neither AT&T nor T-Mobile need to operate CDMA2000 to use a Sprint phone on their LTE. It's useless as far as voice right now, but it's been proven. More likely is T-Mobile or AT&T using Sprint LTE, since that is generally easier. 

 

OP: Don't get your hopes up, but as information becomes available to me, I will share as much as I'm allowed to disclose.

Link to comment
Share on other sites
stealth Member Level: 1xRTT

stealth

Posted
Posted

What does CDMA have to do with it when VoLTE comes into play? Who's Sprint going to use when Verizon shuts off CDMA voice in the future?

 

 

 

Sent from my iPad using Tapatalk

Vzn will shutdown evdo before the shutdown 1xrtt because 1x is far better in rural areas then lte. The roaming agreement will expire before they shutdown 1xrtt.

Link to comment
Share on other sites
greenbastard Member Level: 4G WiMax

greenbastard

Posted
Posted

Vzn will shutdown evdo before the shutdown 1xrtt because 1x is far better in rural areas then lte. The roaming agreement will expire before they shutdown 1xrtt.

Also don't forget about their CDMA M2M users. Shutting down won't be easy or painless. 1x may be around for longer than some expect.
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • dkyeager
      SignalCheck Beta Crew Forum

      By dkyeager · Posted

      Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • mikejeep
      SignalCheck - Android app to monitor your Wi-Fi/2G/3G/4G LTE/5G-NR signal strengths

      By mikejeep · Posted

      After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • clbowens
      Galaxy S23

      By clbowens · Posted

      Oct security update is out.
    • Paynefanbro
      Network Vision/LTE - New York City Market

      By Paynefanbro · Posted

      Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.

  • Recently Browsing

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