Jump to content

Coverage Map Update 6/9/17


RAvirani
 Share

Recommended Posts

Coverage map updated. As I hinted at a few times in the forums, Extended LTE/3G has been added on Comnet in Nevada as well as Colorado, Utah, Wyoming, New Mexico and Montana :). Cool stuff!

  • Like 9
Link to comment
Share on other sites

And Georgia!

 

http://www.commnetwireless.com/wireless-wholesale.html

https://rf.jwmaloney.name/sprint-coverage.html

https://coverage.sprint.com/IMPACT.jsp?

 

Their website coverage wise just says UMTS.  So is that HSPA, not LTE? 

Also, is there a map out there with Comnet's spectrum holdings?  Seem to have holdings in a lot of places, but I'm sure they are thin.

Link to comment
Share on other sites

Commnet has been saying the are adding LTE for a long time. They may have not added LTE coverage maps, yet.

 

Using Tapatalk on Note 8.0

Link to comment
Share on other sites

And Georgia!

 

http://www.commnetwireless.com/wireless-wholesale.html

https://rf.jwmaloney.name/sprint-coverage.html

https://coverage.sprint.com/IMPACT.jsp?

 

Their website coverage wise just says UMTS. So is that HSPA, not LTE?

Also, is there a map out there with Comnet's spectrum holdings? Seem to have holdings in a lot of places, but I'm sure they are thin.

Try here:

 

http://specmap.sequence-omega.net

Link to comment
Share on other sites

Coverage map updated. As I hinted at a few times in the forums, Extended LTE/3G has been added on Comnet in Nevada as well as Colorado, Utah, Wyoming, New Mexico and Montana :). Cool stuff!

Comnet was the worst! It was 1x only that barely worked when I traveled through Nevada, Utah, Wyoming​ last year.

 

Sent from my Pixel XL using Tapatalk

Link to comment
Share on other sites

Comnet was the worst! It was 1x only that barely worked when I traveled through Nevada, Utah, Wyoming​ last year.

 

Sent from my Pixel XL using Tapatalk

.

 

LTE now :). They have 5x5 700 in most areas as well as some midband IIRC.

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...