Jump to content

Major coverage map update 2016/01/10


JWMaloney

Recommended Posts

Old map data courtesy of dsatrbs posted to /r/sprint:

https://mega.nz/#!dcJEjRJS!2olvjpP-E699qe-bIENZykrfGtPKt8HdhNpSFfTMiTo

 

They also posted t-mobile tilesets and did a comparison map.

https://www.reddit.com/r/Sprint/comments/3y546q/tmobile_1115_to_1215_bonus_sprint_maps/

 

(edit: They aren't very zoomed in, but maybe you can compare larger differences.)

Edited by luvixuha
Link to comment
Share on other sites

Notice these black dots are appearing in Albuquerque with the latest update. Anyone know what these mean?

 

Qamw248.png

From what I can tell from looking at my market, it looks like they are sprint stores although I may be wrong.

Link to comment
Share on other sites

From what I can tell from looking at my market, it looks like they are sprint stores although I may be wrong.

No they are just general landmarks like shopping or sports complexs etc....

 

Sent from my Nexus 6P using Tapatalk

Link to comment
Share on other sites

I noticed this in the Pittsburgh market for a new LTE and B41 site. Other markets such as Columbus were unchanged.

 

If your market coverage map has changed I urge you to look carefully for new sites!

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

Hope they looked into el paso tx while updating the map. Hope they saw that we need b41

 

El Paso may continue to be a pain point.  Because of Mexico, Sprint presently cannot run band 26.  Sprint lacks adequate spectrum there to run a band 25 second carrier.  And El Paso is/was a WiMAX license protection market.  You may be stuck with what you have for the next year or so.

 

AJ

Link to comment
Share on other sites

El Paso may continue to be a pain point. Because of Mexico, Sprint presently cannot run band 26. Sprint lacks adequate spectrum there to run a band 25 second carrier. And El Paso is/was a WiMAX license protection market. You may be stuck with what you have for the next year or so.

 

AJ

That's what I've seen in my research. We had about 5 towers that had wimax on it but that's about it.... el paso is really struggling with just the 5×5 bandwidth on band 25..... this year alone we are up to over 800 thouand population.

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

That's what I've seen in my research. We had about 5 towers that had wimax on it but that's about it.... el paso is really struggling with just the 5×5 bandwidth on band 25..... this year alone we are up to over 800 thouand population.

 

Yeah, you were not far off.  In our sponsor section, we have maps of all Clearwire sites.  El Paso has/had three WiMAX license protection sites.  Band 41 also can be added to full build Network Vision sites, but there is no guarantee.  Right now, El Paso just is not a priority market.

 

AJ

  • Like 1
Link to comment
Share on other sites

Yeah, you were not far off. In our sponsor section, we have maps of all Clearwire sites. El Paso has/had three WiMAX license protection sites. Band 41 also can be added to full build Network Vision sites, but there is no guarantee. Right now, El Paso just is not a priority market.

 

AJ

I wonder why... we are a lower budget city. So the 50% off here would be a huge hit. But the towers can't handle many more people on it...its starting to get to the point..... where dropped and delayed text messages are starting to become a issue again just like on the legacy sites.

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

And our signal strength is on average higher then it needs to be.... so i assum there is a lot of gaps between towers.

 

That also may be to combat the Mexican operators.  They are notorious for spilling signal over the border, potentially trying to grab roaming traffic.  A border town is a less than ideal place to be for wireless, unfortunately.

 

AJ

Link to comment
Share on other sites

That also may be to combat the Mexican operators. They are notorious for spilling signal over the border, potentially trying to grab roaming traffic. A border town is a less than ideal place to be for wireless, unfortunately.

 

AJ

I mean i have other options. Verizon performs great here. Full xlte and 700 mhz. At&t great signal strenght penetrates well. Tmobile just passed at&t in network speeds. But all my money is tied into sprint

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

El Paso may continue to be a pain point. Because of Mexico, Sprint presently cannot run band 26. Sprint lacks adequate spectrum there to run a band 25 second carrier. And El Paso is/was a WiMAX license protection market. You may be stuck with what you have for the next year or so.

 

AJ

But even the year or so....is not a guarantee for el paso to even get band 41... im not even expecting lte plus lol

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

But even the year or so....is not a guarantee for el paso to even get band 41... im not even expecting lte plus lol

 

Sent from my SM-G928P using Tapatalk

 

Once Band 41 goes in, it will most likely go live with 2 carriers and carrier aggregation (LTE Plus). I would wager that installs start within a year. Even by summer. Though I don't have any inside info to back that up.

Link to comment
Share on other sites

Once Band 41 goes in, it will most likely go live with 2 carriers and carrier aggregation (LTE Plus). I would wager that installs start within a year. Even by summer. Though I don't have any inside info to back that up.

Im hoping, but in my research that i have seen sprint can't aggregate unless band 26 is present correct me if im wrong. El paso is a top 100 market according to number so i don't see why we wouldn't be a priority

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

Im hoping, but in my research that i have seen sprint can't aggregate unless band 26 is present correct me if im wrong. El paso is a top 100 market according to number so i don't see why we wouldn't be a priority

 

Sent from my SM-G928P using Tapatalk

 

Very wrong. Band 41 carrier aggregation is not dependent on Band 26 at all. There is no 25+25, 25+26, 25+41, 26+41 carrier aggregation, only 41+41. 

  • Like 1
Link to comment
Share on other sites

Very wrong. Band 41 carrier aggregation is not dependent on Band 26 at all. There is no 25+25, 25+26, 25+41, 26+41 carrier aggregation, only 41+41.

Perfect great to know..... so this is all really a toss to when sprint will try to get band 41 here. There are much smaller markets in Tx such as amarillo, odessa midland, Lubbock that have band 41.... i really wonder why we don't

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

Im hoping, but in my research that i have seen sprint can't aggregate unless band 26 is present correct me if im wrong. El paso is a top 100 market according to number so i don't see why we wouldn't be a priority

 

Sent from my SM-G928P using Tapatalk

Carrier aggregation on band 41 has nothing to do with Band 26, but I see I was beaten to it.
Link to comment
Share on other sites

Perfect great to know..... so this is all really a toss to when sprint will try to get band 41 here. There are much smaller markets in Tx such as amarillo, odessa midland, Lubbock that have band 41.... i really wonder why we don't

 

Sent from my SM-G928P using Tapatalk

 

It's done on a market by market basis (Sprint market, not cities). For example, the Oklahoma market has not started B41 deployment yet either. That includes Oklahoma City and Tulsa. The Albuquerque market (includes most of New Mexico, and El Paso) has not started deployment. The Oklahoma and Albuquerque markets are considered tertiary markets, and thus are much lower on the priority list.

 

See this post for a map of Sprint markets: http://s4gru.com/index.php?/page/index.html/_/articles/nationwide-sprint-market-map-is-here-r31

Link to comment
Share on other sites

It's done on a market by market basis (Sprint market, not cities). For example, the Oklahoma market has not started B41 deployment yet either. That includes Oklahoma City and Tulsa. The Albuquerque market (includes most of New Mexico, and El Paso) has not started deployment. The Oklahoma and Albuquerque markets are considered tertiary markets, and thus are much lower on the priority list.

 

See this post for a map of Sprint markets: http://s4gru.com/index.php?/page/index.html/_/articles/nationwide-sprint-market-map-is-here-r31

I see that makes sense...... i really hope it's soon, because band 25 is struggling very bad!

 

Sent from my SM-G928P using Tapatalk

Link to comment
Share on other sites

link was corrected, somehow got the wrong text in there!

 

Damn, I was all ready to go skiing.

 

;)

 

AJ

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

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • 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.
  • Recently Browsing

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