Jump to content

Coverage Map Updated 2/16/2018


Recommended Posts

Post below what changes you notice.

EDIT: Seems that Cumberland, MD has 3G only data back on the map. Last month they removed it completely, but the towers are still on. The map is highly inaccurate having 3G only data in areas where there are Extended LTE coverage, and vice versa. 

  • Like 1
Link to comment
Share on other sites

Ever since the massive B41 coverage overhaul for Cleveland, OH market back in December, they haven't kept up with adding B41 new coverage from sites that have been live for over a month. :wall:

Link to comment
Share on other sites

On 2/16/2018 at 7:55 AM, RAvirani said:

Take a peek at Rapid City, SD ;) .

That's B41 only from the Protection Site.  The roaming pseudo native is from Golden West Wireless.

  • Like 1
Link to comment
Share on other sites

That's B41 only from the Protection Site.  The roaming pseudo native is from Golden West Wireless.




Way to ruin our hopes of actual expansion coming. Lol. I’m also hearing 800mhz is close to clearing for SoCal soon. ??


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

22 hours ago, Joski1624 said:

Ever since the massive B41 coverage overhaul for Cleveland, OH market back in December, they haven't kept up with adding B41 new coverage from sites that have been live for over a month. :wall:

I imagine it takes time for this information to flow across teams. I’m not sure what the lead time is for generating the Coverage Map updates, but perhaps that has something to do with it.

If you’re aware of specific sites that are missing, you should mention it in a reply to /u/Craig-S (https://www.reddit.com/user/Craig-S) on the Sprint Subreddit in this current Coverage Map thread:

/u/Craig-S is one of the people in charge of Sprint’s Coverage Map, and he’s participating in this thread.

He also said about a month ago in an older Coverage Map thread that they were reviewing all of their processes:

 

  • Like 2
Link to comment
Share on other sites

On 2/18/2018 at 11:13 AM, RedSpark said:

I imagine it takes time for this information to flow across teams. I’m not sure what the lead time is for generating the Coverage Map updates, but perhaps that has something to do with it.

If you’re aware of specific sites that are missing, you should mention it in a reply to /u/Craig-S (https://www.reddit.com/user/Craig-S) on the Sprint Subreddit in this current Coverage Map thread:

/u/Craig-S is one of the people in charge of Sprint’s Coverage Map, and he’s participating in this thread.

He also said about a month ago in an older Coverage Map thread that they were reviewing all of their processes:

 

I love how much more active Sprint has been on Social Media; Dr. Saw and Craig-S especially!

  • 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

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Let me take a look tonight. 
    • Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked. Robert
    • I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung. EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.
    • I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.
    • I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.
  • Recently Browsing

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