Jump to content

Cricket MetroPCS CDMA shutdown


signalchaser

Recommended Posts

I see Cricket's CDMA network is being shut down tomorrow. Is Sprint going to acquire any towers from this? Some of them have to be redundant with AT&T's network. 

 

Also did Sprint get anything from the MetroPCS CDMA shutdown? It seems like AT&T and Verizon are gobbling up everything.

Link to comment
Share on other sites

While I am not an expert on Cricket's site placement, they probably co located with everybody else rather than have their own towers. Same with MetroPCS. Sprint had the chance to acquire merge with either or both. They elected not to.

Link to comment
Share on other sites

While I am not an expert on Cricket's site placement, they probably co located with everybody else rather than have their own towers. Same with MetroPCS. Sprint had the chance to acquire merge with either or both. They elected not to.

 

I think a MetroPCS merger would have been great for Sprint since they had some nice markets of PCS spectrum that would have worked out for them.  However Tmobile obtaining MetroPCS works out better since they can use both the AWS and PCS spectrum holdings.  If Sprint had MetroPCS, they would have to do something with the AWS spectrum and I would have hoped that they would use it to trade AWS spectrum for more PCS spectrum.

 

It sucks that AT&T gobbled up Cricket since I would have much preferred Sprint and Tmobile to each merge with 1 of the smaller carriers to add to their depth. 

Link to comment
Share on other sites

Didnt matter much anyways, they would not of helped Sprint THAT much.

They did help out T-Mobile a lot though. It would have stymied T-Mobile in a lot of ways. What actually happened was sort of an LTE shotgun wedding with DT and Metro forming TMUS. Then the old MetroPCS network got shotgunned and TMUS built out new Nokia and Ericsson gear over it. The rest is history.

Link to comment
Share on other sites

They did help out T-Mobile a lot though. It would have stymied T-Mobile in a lot of ways. What actually happened was sort of an LTE shotgun wedding with DT and Metro forming TMUS. Then the old MetroPCS network got shotgunned and TMUS built out new Nokia and Ericsson gear over it. The rest is history.

I am referring to just Cricket, sorry, lol

Link to comment
Share on other sites

My bad, I did think that explanation was good for T-Mobile/MetroPCS though. [emoji23][emoji23][emoji23]

lol, do you agree with me that if Sprint got Cricket, it would not of helped all that much? The metroPCS yes would of helped but Cricket was so small it was barely a carrier in my opinion.

Link to comment
Share on other sites

lol, do you agree with me that if Sprint got Cricket, it would not of helped all that much? The metroPCS yes would of helped but Cricket was so small it was barely a carrier in my opinion.

Cricket was more dysfunctional. Not sure it would have done as much. Mostly, when AT&T got Cricket, it was really rebranded Aio becoming Cricket. Pour some liquor out for the Cricket CDMA network that got shut down in CA marking the end of Cricket CDMA....just kidding, don't actually waste good liquor on that. [emoji23][emoji23][emoji23]

  • Like 1
Link to comment
Share on other sites

Cricket was more dysfunctional. Not sure it would have done as much. Mostly, when AT&T got Cricket, it was really rebranded Aio becoming Cricket. Pour some liquor out for the Cricket CDMA network that got shut down in CA marking the end of Cricket CDMA....just kidding, don't actually waste good liquor on that. [emoji23][emoji23][emoji23]

Both of Cricket and Metro would have helped. It would have brought more customers, would have shored up Sprint's PCS spectrum and would have given them AWS spectrum to trade for more PCS. Or if they did not get out of the JV with the cable cos they could have implemented LTE on 20x20 channels.

The Sprint board has sucked for at least 15 years. No strategic thinking whatsoever.

Link to comment
Share on other sites

Both of Cricket and Metro would have helped. It would have brought more customers, would have shored up Sprint's PCS spectrum and would have given them AWS spectrum to trade for more PCS. Or if they did not get out of the JV with the cable cos they could have implemented LTE on 20x20 channels.

The Sprint board has sucked for at least 15 years. No strategic thinking whatsoever.

 

Ah, I see today we are playing revisionist historian again.  A few thoughts...

 

Sprint's SpectrumCo joint venture with the cable companies produced AWS-1 auction winnings of at least 20 MHz (10 MHz FDD) contiguous across nearly all Sprint major markets -- notable exceptions included St. Louis, Cincinnati, and Buffalo.  You can see the spectrum mapping that I did nine years ago following FCC Auction 66:

 

iejegy.png

 

That is not adequate spectrum to run band 4 LTE at 20 MHz FDD, only 10 MHz FDD.  Houston could do 15 MHz FDD.  But from 2006, that would have been way off in the future anyway.  And while your argument adds in AWS-1 spectrum from Cricket and/or MetroPCS in some markets, that spectrum not necessarily would have been contiguous with SpectrumCo's primarily AWS-1 B block license holdings.

 

Had the SpectrumCo joint venture survived, because LTE commercial availability was still years off, Sprint might have used the spectrum to start a switch over to 3GPP -- like Bell and Telus in Canada -- with a band 4 W-CDMA overlay.  In a comment board peanut gallery somewhere, Fabian Cortez is creaming his shorts at that thought.

 

One problem with that, however, is Cox was partitioned spectrum in its own cable markets, then attempted a triple play offering by deploying a band class 15 CDMA2000 network in several of those markets.  Cox's second entry into wireless was short lived, unsuccessful rather quickly.  So, maybe that spectrum could have been rolled back into SpectrumCo, but that would not have occurred until 2011-2012 -- by which point Network Vision was already underway.  The only real possibility would have been if Sprint, SpectrumCo, and Cox all would have agreed earlier to a 3GPP transition for Sprint and band 4 W-CDMA rollout for all.

 

In the end, with the perspective of time, the dissolution of the SpectrumCo joint venture may seem like a mistake.  However, Sprint had too many irons in the fire as it were -- running CDMA2000, iDEN, and WiMAX networks across PCS 1900 MHz, SMR 800 MHz, and BRS/EBS 2600 MHz spectrum bands -- with Public Safety 800 MHz rebanding and PCS G block boutique replacement spectrum adding to the complexity.  Imagine if Sprint also had been tasked with a band 4 W-CDMA overlay or a band class 15 CDMA2000 deployment.  That would have been the fuster to end all clucks.

 

AJ

  • Like 7
Link to comment
Share on other sites

Ah, I see today we are playing revisionist historian again.  A few thoughts...

 

Sprint's SpectrumCo joint venture with the cable companies produced AWS-1 auction winnings of at least 20 MHz (10 MHz FDD) contiguous across nearly all Sprint major markets -- notable exceptions included St. Louis, Cincinnati, and Buffalo.  You can see the spectrum mapping that I did nine years ago following FCC Auction 66:

 

iejegy.png

 

That is not adequate spectrum to run band 4 LTE at 20 MHz FDD, only 10 MHz FDD.  Houston could do 15 MHz FDD.  But from 2006, that would have been way off in the future anyway.  And while your argument adds in AWS-1 spectrum from Cricket and/or MetroPCS in some markets, that spectrum not necessarily would have been contiguous with SpectrumCo's primarily AWS-1 B block license holdings.

 

Had the SpectrumCo joint venture survived, because LTE commercial availability was still years off, Sprint might have used the spectrum to start a switch over to 3GPP -- like Bell and Telus in Canada -- with a band 4 W-CDMA overlay.  In a comment board peanut gallery somewhere, Fabian Cortez is creaming his shorts at that thought.

 

One problem with that, however, is Cox was partitioned spectrum in its own cable markets, then attempted a triple play offering by deploying a band class 15 CDMA2000 network in several of those markets.  Cox's second entry into wireless was short lived, unsuccessful rather quickly.  So, maybe that spectrum could have been rolled back into SpectrumCo, but that would not have occurred until 2011-2012 -- by which point Network Vision was already underway.  The only real possibility would have been if Sprint, SpectrumCo, and Cox all would have agreed earlier to a 3GPP transition for Sprint and band 4 W-CDMA rollout for all.

 

In the end, with the perspective of time, the dissolution of the SpectrumCo joint venture may seem like a mistake.  However, Sprint had too many irons in the fire as it were -- running CDMA2000, iDEN, and WiMAX networks across PCS 1900 MHz, SMR 800 MHz, and BRS/EBS 2600 MHz spectrum bands -- with Public Safety 800 MHz rebanding and PCS G block boutique replacement spectrum adding to the complexity.  Imagine if Sprint also had been tasked with a band 4 W-CDMA overlay or a band class 15 CDMA2000 deployment.  That would have been the fuster to end all clucks.

 

AJ

You're right about WCDMA first on AWS-1. Heck they could have implemented WCDMA TDD on their 2.5GHZ spectrum.

Link to comment
Share on other sites

Why wouldn't Cricket been good?  ATT grabbed them up for $1.2 billion.  Maybe that is expensive?  But Sprint would have been able to add a second PCS LTE carrier in many markets.  What, I count at least 40 major markets.  Maybe a fourth they could have done two carriers.  

 

The H-Block went for 1.56 billion and is nationwide, but incompatible with everything.  So Cricket spectrum would be a bit of a premium + the customers, and I'm sure a lot of the tower locations would help with cell density.  Seems like that would have been a pretty fast conversion for Sprint to make getting that spectrum shifted around and merging ~5 million customers into Sprint. 

Link to comment
Share on other sites

Cricket had virtually zero unique coverage.  Sprint would have had use of probably less than 5% of their locations.  If that.  Everywhere I lived that had Cricket, they were colocated on Sprint sites almost every time, or an adjacent site.  Except in most cases they had thinner coverage.  The only time I roamed on Cricket in New Mexico is if Sprint went offline for some reason.

Link to comment
Share on other sites

Cricket had virtually zero unique coverage. Sprint would have had use of probably less than 5% of their locations. If that. Everywhere I lived that had Cricket, they were colocated on Sprint sites almost every time, or an adjacent site. Except in most cases they had thinner coverage. The only time I roamed on Cricket in New Mexico is if Sprint went offline for some reason.

I found their network superior to Sprint's in both Austin and Houston.

Link to comment
Share on other sites

I found their network superior to Sprint's in both Austin and Houston.

In Houston, that definitely was not the case. Sprint pre-NV and cricket both had congested EVDO networks that had a bunch of sites crawling along with dual up speeds. As far as voice, they were both respectable, but not great.

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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • 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!
    • Oct security update is out.
    • 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.
    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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