Jump to content

Coverage Mapping Tools


mhammett

Recommended Posts

RootMetrics is okay but they measure 1x signal and ever since the single path devices came out, they've been reading Sprint device signals as -120dbm or something like that because the 1x side isn't active.

 

OpenSignal's heat map is poor in general.

  • Like 2
Link to comment
Share on other sites

RootMetrics is okay but they measure 1x signal and ever since the single path devices came out, they've been reading Sprint device signals as -120dbm or something like that because the 1x side isn't active.

 

OpenSignal's heat map is poor in general.

I let RootMetics run accidentally and mapped a large chunk of my town that now shows -120dB for call performance and LTE as the best technology.  

  • Like 1
Link to comment
Share on other sites

As others have said, rootmetrics still hasn't updated their app to support sprint triband devices, and it's been over a year. They don't seem interested in supporting their app.

 

Sensorly seems to be the best, although they do have a few problems with their mapping. I.e. Sprint LTE mapped in Oklahoma where there is none.

Link to comment
Share on other sites

As others have said, rootmetrics still hasn't updated their app to support sprint triband devices, and it's been over a year. They don't seem interested in supporting their app.

 

Sensorly seems to be the best, although they do have a few problems with their mapping. I.e. Sprint LTE mapped in Oklahoma where there is none.

Or that the Sprint maps in NYC aren't very accurate anymore. The map should be way darker in many areas but that simply isn't the case.

Link to comment
Share on other sites

I've had the exact same issue up here in Washington. All of a sudden it won't map LTE anymore.

I hope they fix it soon Sprint has been very busy firing up LTE 800 and there are tons of new areas to map here.

Link to comment
Share on other sites

Refuses to map? That's a new one. They do have a support thread here on the forums. Not sure the last time they checked it though.

Refuses, failed to perform an action, "Sensorly refuses to map."   :P

 

On the same note I've emailed them many times without a response, so now I refuse to use Sensorly.  :angry:

Link to comment
Share on other sites

Refuses, failed to perform an action, "Sensorly refuses to map."   :P

 

On the same note I've emailed them many times without a response, so now I refuse to use Sensorly.  :angry:

When is the last time you tried Sensorly? I had issues before and removed it about 6-7 months ago, but I decided to try it again and it works fine now.

Link to comment
Share on other sites

When is the last time you tried Sensorly? I had issues before and removed it about 6-7 months ago, but I decided to try it again and it works fine now.

I actually tried to use it today and still nada.

Link to comment
Share on other sites

  • 2 weeks later...

My Sensorly still won't map nor will it upload any of the speed tests I run. It's incredibly frustrating.

 

It looks like everything is working as it should, but it never shows up. I wonder if the developer has given up on the product?

  • Like 1
Link to comment
Share on other sites

  • 4 months later...
  • 2 weeks later...

The guys over at Cellmapper are willing to add in band information, but I don't think they're in the US, so I don't think they have the ability to test this themselves. They were wondering if we could provide how to map out the frequencies. Do we have a tried and true sector ID (or other information) to band method?

Link to comment
Share on other sites

I would like to know this too because I have done a significant amount of mapping on Cellmapper on my Nexus 5 (new member from HoFo and T4GRU). SignalCheck Pro displays the band perfectly. If the guys over at Cellmapper had a way to distinguish B26 from B25 and B41, maybe we could see just how far B41 goes (lots of B41 holes in Lansing MI).

  • Like 1
Link to comment
Share on other sites

00,01,02 band 25 

03 split between second carrier Samsung and  first carrier

04,05 second carrier Samsung band 25

09,0A,0B second carrier band 25

0F,10,11 band 26

19,1A,1B band 26

 

 

 

band 41 

GCI 3rd is number from the left is "odd" if(GCI && 0x00100000){}//band 41 

00,01,02 First carrier

03,04,05 Second carrier

31,32,33 First carrier

39,3A,3B Second carrier

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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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