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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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