Jump to content

Coverage map edited to not include off network roaming

xmx1024
 Share

Recommended Posts

WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

Sorry about that...

 

Sprint_NOROAM_2015.png

 

Are you still sorry, deeply sorry, sorry again?  What are you, BP?

 

AJ

  • Like 4
Link to comment
Share on other sites
Deval Member Level: LTE Advanced

Deval

Posted
Posted

AL And MS coverage still blows Im ready to see both tmobile and sprint at 300million pops of coverage on 4g lte. 

 

Eh, LTE is overrated. Let's get voice and EVDO coverage there first.

  • Like 2
Link to comment
Share on other sites
Thunder Member Level: Smoke Signals

Thunder

Posted
Posted

Eh, LTE is overrated. Let's get voice and EVDO coverage there first.

true. on sprint coverage map it shows the 3g 4-5 miles short of me but I get 1-2bars of 3g sometimes I think they underestimate their coverage.

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

Deval

Posted
Posted

true. on sprint coverage map it shows the 3g 4-5 miles short of me but I get 1-2bars of 3g sometimes I think they underestimate their coverage.

 

That's what they need to get first. LTE can come later, but solid EVDO is a good baseline to have.

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

WiWavelength

Posted
Posted

As a New Yorker, I don't get this.

 

I do not get it either.  And I do not think that grndslm got my former BP CEO Tony Hayward reference.  But what I do get is that grndslm tried twice, still did not manage to post a working image, and never fixed the broken posts.

 

AJ

  • Like 4
Link to comment
Share on other sites
grndslm Member Level: Smoke Signals

grndslm

Posted
Posted

I don't know of too many file hosting sites that don't have limits on what can be posted.

 

In my last post that that included the image, I can see the image just fine.  In WiWavelength's quote of my post, I can ALSO see the image clear as day.  Not sure why I can see it embedded in the posts and others can't.  Doesn't make sense.

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

WiWavelength

Posted
Posted

I don't know of too many file hosting sites that don't have limits on what can be posted.

 

In my last post that that included the image, I can see the image just fine.  In WiWavelength's quote of my post, I can ALSO see the image clear as day.  Not sure why I can see it embedded in the posts and others can't.  Doesn't make sense.

 

S4GRU allows standard image file extensions -- anything beyond that in the URL will not work.

 

Additionally, many members use TinyPic and Imgur with no problems.

 

AJ

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

Dkoellerwx

Posted
Posted

I don't know of too many file hosting sites that don't have limits on what can be posted.

 

In my last post that that included the image, I can see the image just fine.  In WiWavelength's quote of my post, I can ALSO see the image clear as day.  Not sure why I can see it embedded in the posts and others can't.  Doesn't make sense.

 

Maybe you need to be logged in to your account to see the posts... as AJ said, there are many different hosting sites that work just fine. Dropbox, Imgur, Photobucket... just to name a few.

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

Dkoellerwx

Posted
Posted

You care to add the "native" 3G roaming?

 

When Sprint actually adds pseudo-native EVDO to the map, it will show up as dark purple, just like regular EVDO. Right now there is no way to distinguish between pseudo-native EVDO and roaming EVDO.

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

Dkoellerwx

Posted
Posted

On Sprint's coverage map, if you change "Sprint Spark" to "3G and More" it will give you two shades of dark purple.

 

Correct. That second shade of dark purple is EVDO roaming. It does not denote areas that are pseudo-native. The light shade of roaming is 1x roaming.

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

red_dog007

Posted
Posted

Correct. That second shade of dark purple is EVDO roaming. It does not denote areas that are pseudo-native. The light shade of roaming is 1x roaming.

What isn't pseduo-native?  From what I have been able to gather so far, it is treated as native.

 

What all of those then are still roaming, and not psedo-native?  Maybe just add the ones that are confirmed psedo-native so far then?  Seems like in the PRL Update thread that a handful out west are.  I know Bluegrass is here on the East side. 

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

Dkoellerwx

Posted
Posted

What isn't pseduo-native?  From what I have been able to gather so far, it is treated as native.

 

What all of those then are still roaming, and not psedo-native?  Maybe just add the ones that are confirmed psedo-native so far then?  Seems like in the PRL Update thread that a handful out west are.  I know Bluegrass is here on the East side. 

 

At this point, many of the EVDO roaming areas (the second shade of dark purple) are now showing up as native EVDO for Sprint users. However, the map has not been updated to reflect that yet. We cannot treat every EVDO roaming spot as native yet. Not until Sprint updates the map to differentiate between the pseudo-native coverage and roaming coverage.

 

 

I can tell you that Aberdeen, SD 3G and more is native.

 

Yes, but the map does not reflect that yet. I think we've confirmed a number of roaming partners are now native, but Sprint does not show that yet.

  • Like 2
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

    • 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.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • CalebM
      SignalCheck Beta Crew Forum

      By CalebM · Posted

      Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 

  • Recently Browsing

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