Jump to content

Coverage map edited to not include off network roaming


Recommended Posts

I edited one of the coverage maps from here to make it easier to tell the difference from native Sprint coverage and roaming. Darker spots have no coverage at all.

 

Sprint-Coverage-edited-to-make-roaming-d

Edited by xmx1024
  • Like 3
Link to comment
Share on other sites

And now with the recent changes, a lot more native coverage appearing with RRPP members. Bluegrass, Pioneer, Nextech, United, James Valley. Back on the upward swing!

 

Using Nexus 6 on Tapatalk

  • Like 7
Link to comment
Share on other sites

yup, the ironic thing is I just moved out west to CO. From Salina, KS to just about Colorado Springs, CO you are roaming at 1x data. Barely enough for Waze mapping.

And now it is 3G EVDO again on Nextech from Salina to Limon, CO along I-70.

 

Using Tapatalk on Nexus 6

  • Like 1
Link to comment
Share on other sites

Jeez, the network, when put like that, seems so... diminutive. 

 

Some of the coverage map is not accurate -- not overestimating but shortchanging Sprint.

 

California's Central Valley footprint, for example, appears to have been off for a long time now, probably since the Ubiquitel days.  While I have not been in the area in years, I honestly do not believe that the highway and rural Sprint sites in that exceedingly flat terrain produce just isolated lily pads of coverage with seemingly only 3-5 mile radii. 

 

Meanwhile, T-Mobile has an AWS site in the Texas Panhandle that its coverage map claims has something on the order of a 50 mile radius.  I do not believe that either.

 

AJ

  • Like 1
Link to comment
Share on other sites

California's Central Valley footprint, for example, appears to have been off for a long time now, probably since the Ubiquitel days.  While I have not been in the area in years, I honestly do not believe that the highway and rural Sprint sites in that exceedingly flat terrain produce just isolated lily pads of coverage with seemingly only 3-5 mile radii. 

 

 

AJ

 

Once you get out of the upper central valley it's about right since the site spacing once you get out of the UCV is very meh .

 

NW of Sacramento though is wrong since the only point that is not covered is a single 3G GMO site serving two small towns near Harrington. Other than that one can get almost ubuqitous LTE coverage from all the way south on i5 from Patterson, CA all the way to Redding, CA. 

Link to comment
Share on other sites

Some of the coverage map is not accurate -- not overestimating but shortchanging Sprint.

 

California's Central Valley footprint, for example, appears to have been off for a long time now, probably since the Ubiquitel days. While I have not been in the area in years, I honestly do not believe that the highway and rural Sprint sites in that exceedingly flat terrain produce just isolated lily pads of coverage with seemingly only 3-5 mile radii.

 

Meanwhile, T-Mobile has an AWS site in the Texas Panhandle that its coverage map claims has something on the order of a 50 mile radius. I do not believe that either.

 

AJ

It is about right. The lower Central Valley along the i5 is pretty awful. I use to work for ubiquitel. It was a fun little company.

  • Like 1
Link to comment
Share on other sites

Some of the coverage map is not accurate -- not overestimating but shortchanging Sprint.

 

California's Central Valley footprint, for example, appears to have been off for a long time now, probably since the Ubiquitel days.  While I have not been in the area in years, I honestly do not believe that the highway and rural Sprint sites in that exceedingly flat terrain produce just isolated lily pads of coverage with seemingly only 3-5 mile radii. 

 

Meanwhile, T-Mobile has an AWS site in the Texas Panhandle that its coverage map claims has something on the order of a 50 mile radius.  I do not believe that either.

 

AJ

 

I don't know why it's the case, but it's actually pretty accurate for the Los Banos/Merced/Turlock/Modesto area - on the highways interconnecting those cities. Sprint drops out completely in many areas, and I end up roaming on Cricket's legacy CDMA network (which always makes me wince, Cricket coverage but not Sprint) and sometimes Verizon. I don't know if it's site spacing or an issue with antenna optimization or what, but this is one of the areas that could use new sites or Nextel converts.

Link to comment
Share on other sites

And now it is 3G EVDO again on Nextech from Salina to Limon, CO along I-70.

 

Using Tapatalk on Nexus 6

Odd that the map still hasn't been updated to show the change to pseudo-native, yet LTE in nTelos land? Madness...  :hah:

  • Like 1
Link to comment
Share on other sites

I suppose I should get around to updating that map. So little free time these days.I

I'll post another thread with an edited image like the one here once you update yours!

Link to comment
Share on other sites

And now it is 3G EVDO again on Nextech from Salina to Limon, CO along I-70.

 

Using Tapatalk on Nexus 6

 

When did that happen?  I just traveled I-70 from Salina to Limon, CO and it was 1x roaming the whole way.  This was on Sunday 17 May 2015.  Can pull my SingalCheck Pro logs for this.

Edited by Cataract2
Link to comment
Share on other sites

When did that happen?  I just traveled I-70 from Salina to Limon, CO and it was 1x roaming the whole way.  This was on Sunday 17 May 2015.  Can pull my SingalCheck Pro logs for this.

 

It is actually EVDO roaming (possibly now native?), however you have to make sure you have it enabled. Sometimes it takes a PRL update, as I've noticed there is a tendency to grab on to Verizon 1x first for some reason, and then eventually changes to NexTech EVDO. If it grabs Verizon 1x, only a PRL update will get it to switch to NexTech.

Link to comment
Share on other sites

When did that happen?  I just traveled I-70 from Salina to Limon, CO and it was 1x roaming the whole way.  This was on Sunday 17 May 2015.  Can pull my SingalCheck Pro logs for this.

 

The Nex-Tech EV-DO network never went away -- it was just removed from the Sprint PRL.  Now, it is back in the PRL.

 

So, your PRL is out of date, and you need to update it.

 

AJ

Link to comment
Share on other sites

The Nex-Tech EV-DO network never went away -- it was just removed from the Sprint PRL.  Now, it is back in the PRL.

 

So, your PRL is out of date, and you need to update it.

 

AJ

My PRL shows 55025.  This is on an HTC One M8.  I certainly ended up on Verizon for a good chunk of the trip.  Verizons connection sucked.

  • Like 1
Link to comment
Share on other sites

My PRL shows 55025.  This is on an HTC One M8.  I certainly ended up on Verizon for a good chunk of the trip.  Verizons connection sucked.

 

As I mentioned earlier, last time I drove I-70 from KC to Denver, my brother's M8 ended up on Verizon 1x while my G3 was on NexTech EVDO (roaming). A PRL refresh on the M8 got it to latch onto NexTech EVDO. The PRL didn't necessarily change, but it did force the M8 to move over to NexTech. 

Link to comment
Share on other sites

Wait, this is the map from November of last year. We need a map of today's coverage!

And here is an updated map without off-network roaming...

 

Or at least emphasizing the ON-NETWORK coverage --

 

Sprint-NOROAM-2015.png?_subject_uid=3865

Edited by grndslm
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

  • Posts

    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No specific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
  • Recently Browsing

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