Jump to content

Hello from a white county on market map.


bubretti

Recommended Posts

Howdy from ashland ky. My county is in eastern ky borders wva. We have sprint stores, wimax (protection site from what I gather), and sprint evdo. So my question is do I have to wait till sprint purchases clear to get lte because of the 2500mhz.? Or will sprint give lte on every sprint tower? Also why is my county white are we not a market? Thanks for any and all help.

Link to comment
Share on other sites

Whoa, I thought this was going to be a racist thread! JK! Might want to think about those titles a little bit more haha. Anyway, Sprint will have NV on just about every tower. My guess is that the coverage in Ashland is provided by a partner carrier like Shentel, as in the East Kentucky map section there are no towers in Ashland and the closest one I found is near Wheelersburg, Ohio. Most likely the Sprint partner will deploy LTE in the near future. You should become a sponsor so you can view more maps!

Link to comment
Share on other sites

Haha. Yeah that couldve been bad. Ok will donate soon and check it out. The wimax isnt bad at all get 8mbps down. Just wanted to see where my community stood. Will find out more after I donate. Thanks for the help and I will be more careful with my titles here on in. Lol

Link to comment
Share on other sites

Ashland Kentucky is in a nTelos market, I believe. nTelos is not an affiliate of Sprint, but rather an independent company that sells Sprint native service in the area.

 

The nTelos network is not receiving Sprint Network Vision upgrades in the way Sprint corporate and affiliate markets are. nTelos is keeping it's 3G service as is, and will start adding a LTE layer for Sprint customers near the end of 2013 and into 2014.

 

We do not have much information about nTelos plans at this time. But their upgrades are not imminent.

 

Robert via Nexus 7 with Tapatalk HD

Link to comment
Share on other sites

Ok thanks Robert, makes sense lot of my friends have ntelos. I hope they get lte and sell it to sprint. I'm fine with WiMAX but that's going away too and I would like to have an up to date phone. Still rolloing with epic touch just for the WiMAX. I hope clear sticks around and doesn't move their protection site maybe that will give sprint a push to use their 2500mhz when sprint buys them.

Link to comment
Share on other sites

Ok thanks Robert, makes sense lot of my friends have ntelos. I hope they get lte and sell it to sprint. I'm fine with WiMAX but that's going away too and I would like to have an up to date phone. Still rolloing with epic touch just for the WiMAX. I hope clear sticks around and doesn't move their protection site maybe that will give sprint a push to use their 2500mhz when sprint buys them.

WiMax isn't going anywhere until 2015 at the earliest. Now, they may change the protection site to LTE rather than WiMax, but that probably won't be happening any time soon either. So if WiMax is usable in your area, you could probably stick with it for another year or so.

Link to comment
Share on other sites

Yeah I will. Only route i got really for 4g. Been with sprint about 11yrs not gonna change carriers now. AT&T and Verizon both have lte here. Ill just wait and see what nTelos does. Supposed to be rolling out 2md half this year hopefully they renew their agreement with sprint. Thanks for the help.

Link to comment
Share on other sites

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • 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. 
    • 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.
    • 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...