Jump to content

Sprint LTE Coverage Maps via Sensorly


Recommended Posts

A VPN will skew the results. You should not have a VPN on whole doing speed test mapping. VoLTE will not matter, they operate on different EUTRA sessions https://s4gru.com/entry/439-sprints-casting-call-of-voice-over-actors-an-in-depth-analysis-of-volte-calling-and-vowifi/ it shouldn't even be able to tell that you have VoLTE on. That being said, if you're on an active VoLTE call, then that may affect things. Recently, Sprint started preferring dropping to band 26 during tower handoffs while on a VoLTE call. So a call may start out on B41, but if you're moving, when it hands off to the next tower it often switches to B26. This improves VoLTE performance and quality, but will result in slower data speeds and showing B26 available instead of b25 or b41 in your mapping. Congestion on B26 has no effect at all on VoLTE calls, but will be reflected in speed tests performed while on the call

 

Sent from my Pixel 3 XL using Tapatalk

 

Interesting info about dropping to B26 before a handoff. I will give it a try with the VPN disabled.

Link to comment
Share on other sites

  • 3 weeks later...
13 hours ago, techfranz said:

Haven’t gotten Rootmetrics or OpenSignal to record my iPhone tests on the map.

I guess I will just stick to to the iPhone engineering screen.


Sent from my iPhone using Tapatalk

Rootmetrics has been working fine for me on my iPhone and I’ve seen the Map Layer update.

Are you running speed tests and looking at the “Fastest Speed Found” Map Layer?

Under Settings:

Do you have the “Baseline Data Experience” setting enabled as well as “Send data Points Using” set to “Any Network”?

Link to comment
Share on other sites

Rootmetrics has been working fine for me on my iPhone and I’ve seen the Map Layer update.

Are you running speed tests and looking at the “Fastest Speed Found” Map Layer?

Under Settings:

Do you have the “Baseline Data Experience” setting enabled as well as “Send data Points Using” set to “Any Network”?

 

Quite strange, but I just checked again and Rootmetrics processed all my data.

 

Rootmetrics is working as you say. I wonder why it took 1-2 weeks to process all my tests? Very nice to see the results on the map.

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Link to comment
Share on other sites

  • 2 months later...
22 hours ago, Yuhfhrh said:

Sensorly is shutting down. I'll never forget all the time I spent and fun I had mapping the Sprint LTE launch.

https://www.reddit.com/r/Sprint/comments/di83m3/sensorly_is_officially_dead/

A somber moment.  So many happy memories.  Oh, what could have been!!!  :cry:

Now if Cellmapper would just add a signal heat map that displayed more like Sensorly!

Robert

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

    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
    • At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
    • Did you mean a different site? eNB ID 112039 has been around for years. Streetview even has it with C-band back in 2022 - https://www.google.com/maps/@40.7303042,-73.9610924,3a,24.1y,18.03h,109.66t/data=!3m8!1e1!3m6!1s2ossx06yU56AYOzREdcK-g!2e0!5s20220201T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D2ossx06yU56AYOzREdcK-g%26cb_client%3Dmaps_sv.share%26w%3D900%26h%3D600%26yaw%3D18.027734930682684%26pitch%3D-19.664180274382204%26thumbfov%3D90!7i16384!8i8192?coh=205410&entry=ttu Meanwhile, Verizon's eNB 84484 in Fort Greene has been updated to include C-band and CBRS, but not mmWave. I've seen this a few times now on updated Verizon sites where it's just the CBRS antenna on its own, not in a shroud and without mmWave. Odd.
    • Drove out into the country today.  Dish stuck to my phone like glue. At least -120 rsrp. Likely only good for phone calls (should have tested.) It then switched to T-Mobile. Getting back on Dish was another issue. I am used to dragging out coverage so I expected a few miles, but had to drive at least 10 miles towards a Dish site. Airplane mode, which worked for Sprint, did nothing. Rebooting did nothing. Finally got it to change over about 2 miles from the site by manually setting the carrier to Dish then it had great reception. Sprint used to have a 15 minute timeout but I did not have the patience today.  Previously I did a speed test on Dish out in the country at the edge of Dish coverage. My speeds were 2g variety. Dish has really overclocked some of these sites. Seen rssp readings in the 50s. Would have called them boomer sites with Sprint but much  more common with Dish.  
  • Recently Browsing

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