Jump to content

Sprint LTE Coverage Maps via Sensorly


Recommended Posts

i know the s3 and htc evo lte do (but only when on lte only mode and its a very weak (unusable signal) 

Something's definitely mapping gray when there is absolutely no signal at all, not just a weak signal, and people are mapping thousand mile trips through zones without LTE and it's littering the maps.  I wouldn't mind it mapping "no coverage" areas once a carrier has reached a level like verizon, but with the other carriers they are obviously so far from done upgrading towers that most of the "no coverage" areas will eventually be LTE areas. 

Link to comment
Share on other sites

 

 

Lte on most devices. There is 1 device in particular which it does 1x but counts as lte. Fail for that device. (Galaxy nexus I think, someone correct me if I'm wrong)

 

 

Sent from my HTCONE using Tapatalk 2

 

 

Which device maps the gray "no coverage" on the map? It's barely there for Sprint, but the AT&T and T-Mobile maps almost have more gray than purple.

 

Every device will map gray if it has "no service." So you basically have to be in LTE only mode.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

  • Like 1
Link to comment
Share on other sites

With all due respect to Sensorly, it gravely needs to revise its generic labeling system.  The current labels (e.g. Sprint - 2G-3G, T-Mobile - 4G) are problematic.

 

First, neither Sprint nor VZW has any "2G" coverage remaining.  It is all CDMA1X and/or EV-DO -- both of which are classified as "3G."

 

Second, both T-Mobile and AT&T have mucked with the system, whined, and gotten their W-CDMA, if evolved, reclassified as "4G."  Sensorly does not recognize that charade, fortunately.  But users will be confused, since their T-Mobile and AT&T devices tell them that they are on "4G" HSPA+.  Sensorly, on the other hand, logs as "4G" only the LTE deployments.

 

So, here are some examples of well thought out revisions to the current network coverage labels:

 

Sprint - 3G CDMA1X/EV-DO

Sprint - 4G WiMAX

Sprint - 4G LTE

T-Mobile - 2G-3G GSM/W-CDMA/HSPA

T-Mobile - 4G LTE

 

AJ

  • Like 4
Link to comment
Share on other sites

Is there a scale somewhere indicating how your RSRP (dBm) measurement translates into the "bars" shown in sensorly? e.g. 4 bars is 85 dBm or better (or something like that) for 0 to 4 bars.

Link to comment
Share on other sites

I'm having the same issue with the website, however the iPhone app is working and loading up new mappings for a tower that just went live today. 

Link to comment
Share on other sites

What is going on with the Sensorly website, all I get is "Nothing here".

http://www.sensorly.com/

"ALL YOUR SENSORLY DATA ARE BELONG TO US."

 

AJ

Link to comment
Share on other sites

With all due respect to Sensorly, it gravely needs to revise its generic labeling system.  The current labels (e.g. Sprint - 2G-3G, T-Mobile - 4G) are problematic.

 

On the Android application, they list the signals as Sprint (LTE), Sprint (CDMA), T-Mobile (GSM), T-Mobile (LTE).

Which is a lot clearer.

 

They should also list Sprint (Roaming)

Link to comment
Share on other sites

At least the mapping is still working. I mapped out a new little piece of a site and it showed up.

All my Tmo LTE mapping in ABQ from today showed up when my phone connected to my home WiFi tonight. I just had to go to the app to see it.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

  • Like 1
Link to comment
Share on other sites

Spoke with the developer at Sensorly and they stated the problem with the website has been corrected and all is well.  Nothing to worry about, carry on and continue to lay down that purple folks!

  • Like 4
Link to comment
Share on other sites

I run Sensorly every day to and from work.  Yes, it is the same route every day, but you never know, a new tower may have gone live or something.

 

I am getting a new dock for my HTC One that will allow me to more easily see my phone while driving (compared to the cupholder).  I always leave the Spring 4G LTE map up while I drive so I have a good idea of what to expect and where.  It is a good feeling noticing you are mapping a new area of LTE that has not been mapped before, and later that night you can see your contribution on their website.

 

One thing however, sometimes (as one of my posts in another thread mentioned), I don't get signal where Sensorly claims there should be signal.  I wish there was a way (without triggering Airplane Mode or using an app that cycles Airplane Mode) to have the phone scan more often.

Link to comment
Share on other sites

I wouldn't map the same area over and over. Only map when new coverage is added. If you map an area at one bar for 50 times and a site is upgraded right there then it will take a LOT of passes to bring it up. If it is already mapped and I don't see new serving cell numbers then I don't fire up sensorly.

 

Sometimes at places where others have done this I drive off to the side streets right next to the site that was recently upgraded in order to lay down some dark purple on the map.

Link to comment
Share on other sites

I was under the impression Sensorly only displays the latest information.

 

For example, if I drove by with 1 bar (like you suggest), and that was the only information for that location, that would be displayed.  And if a new tower went live there, then newer information would be available, and that would override the older information.

 

I guess this could be both good and bad.  If someone got full bars at a location, then later someone else only got 1 bar for whatever reason, the site would update to the lower signal.

 

Either way, I thought it really only went off the latest information for a site.  If this is not the case, I will stop mapping every day to and from work, unless a new area goes live.

Link to comment
Share on other sites

I was under the impression Sensorly only displays the latest information.

 

For example, if I drove by with 1 bar (like you suggest), and that was the only information for that location, that would be displayed. And if a new tower went live there, then newer information would be available, and that would override the older information.

 

I guess this could be both good and bad. If someone got full bars at a location, then later someone else only got 1 bar for whatever reason, the site would update to the lower signal.

 

Either way, I thought it really only went off the latest information for a site. If this is not the case, I will stop mapping every day to and from work, unless a new area goes live.

No, the data is averaged. If you map 1 bar for weeks, a new tower comes online and it's suddenly full bars, it will take weeks to reflect the change properly.

 

Sent from my HTC ONE

 

 

Link to comment
Share on other sites

Very good to know.

 

Is there any way to keep it from mapping new data, but still allow me to keep the coverage map on my phone.  That way, if I find a location with 4G that is not mapped, I can tell it to start mapping.

Link to comment
Share on other sites

I wouldn't map the same area over and over. Only map when new coverage is added. If you map an area at one bar for 50 times and a site is upgraded right there then it will take a LOT of passes to bring it up. If it is already mapped and I don't see new serving cell numbers then I don't fire up sensorly.

 

Sometimes at places where others have done this I drive off to the side streets right next to the site that was recently upgraded in order to lay down some dark purple on the map.

This is my Sensorly strategy as well. I can confirm Sensorly definitely averages data at each point.

 

Robert from Note 2 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites

Very good to know.

 

Is there any way to keep it from mapping new data, but still allow me to keep the coverage map on my phone. That way, if I find a location with 4G that is not mapped, I can tell it to start mapping.

I believe if you set your contribution level to "no contribution," you can run the app and look at the map without collecting any data. If you find a spot that hasn't been mapped, just hit the map trip button and it will start collecting.

 

Sent from my HTC ONE

 

 

Link to comment
Share on other sites

I believe if you set your contribution level to "no contribution," you can run the app and look at the map without collecting any data. If you find a spot that hasn't been mapped, just hit the map trip button and it will start collecting.

 

Sent from my HTC ONE

 

 

That's how I map right now, always using the map trip button.  I like seeing how the points break down between 3G and 4G.

 

I also think I have it set to no contribution (used to do passive scans, but didn't like how my phone would randomly get hot in my pocket).

 

Thanks for the information.  Like I said, I will only contribute when I know there is a new site.

  • Like 2
Link to comment
Share on other sites

With all due respect to Sensorly, it gravely needs to revise its generic labeling system. The current labels (e.g. Sprint - 2G-3G, T-Mobile - 4G) are problematic.

 

First, neither Sprint nor VZW has any "2G" coverage remaining. It is all CDMA1X and/or EV-DO -- both of which are classified as "3G."

Agreed. From what I can tell based on my own mapping adventures, Sensorly maps Sprint 1xRTT data coverage as "2G" and EV-DO/eHRPD as "3G".

 

-Mike

Link to comment
Share on other sites

This is my Sensorly strategy as well. I can confirm Sensorly definitely averages data at each point.

We average measurements and give priority to "upper" layers so if we get grey (no LTE) for 6 months and then get 1 reading with LTE, we'll display LTE there. And from there on, it will average out with other "LTE present" signal measurements but ignore the "no LTE" measurements that might come in.

  • Like 4
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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
    • Looks like a great place for for FWA. Many apartment dwellers only have one overpriced choice.
  • Recently Browsing

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