Jump to content

Sprint LTE Coverage Maps via Sensorly


Recommended Posts

The speed test worked, but way off what I normally see if I run one on my home wifi.

I don't ever use the speed test function. The servers they use are not local and almost always show much slower speed than I'm actually getting.

 

Sent from my HTCONE using Tapatalk

 

 

  • Like 1
Link to comment
Share on other sites

I don't ever use the speed test function. The servers they use are not local and almost always show much slower speed than I'm actually getting.

 

Sent from my HTCONE using Tapatalk

 

I don't regularly use there speed test, but I wanted to see if I could get any part of Sensorly to work. The last time I tried one (with the old version) it was still slower than what it should be, but no where as near as slow as this one reported.

 

I am wondering if it will even map for me. I had planned on spending at least a half day tomorrow mapping and photographing, but this upgrade just sucked a lot of that enthusiasm out...

Link to comment
Share on other sites

I don't regularly use there speed test, but I wanted to see if I could get any part of Sensorly to work. The last time I tried one (with the old version) it was still slower than what it should be, but no where as near as slow as this one reported.

 

I am wondering if it will even map for me. I had planned on spending at least a half day tomorrow mapping and photographing, but this upgrade just sucked a lot of that enthusiasm out...

Works fine for me on my ONE. Maybe uninstall and install again?

 

Sent from my HTCONE using Tapatalk

 

 

Link to comment
Share on other sites

I am wondering if it will even map for me. I had planned on spending at least a half day tomorrow mapping and photographing, but this upgrade just sucked a lot of that enthusiasm out...

Just reinstall the old version, it is linked earlier in this thread..

 

-Mike

Link to comment
Share on other sites

It's still crap. Kind of.

Want to expand on that? I think since the latest revisions they've done a pretty good job of correcting most of the things I had issues with. There's a couple tweaks I'd like to see, but otherwise it seems like a perfectly good app now.

Link to comment
Share on other sites

Want to expand on that? I think since the latest revisions they've done a pretty good job of correcting most of the things I had issues with. There's a couple tweaks I'd like to see, but otherwise it seems like a perfectly good app now.

 

Just my opinion. Still loads really slow. The old one I think was more user friendly when you are driving. Shhhhh, I know.

Link to comment
Share on other sites

Just my opinion. Still loads really slow. The old one I think was more user friendly when you are driving. Shhhhh, I know.

I think it's much easier to start mapping a trip with this version. Nice big button on the screen rather than having to find the little menu button at the bottom of the screen like before.

 

I do missing have the point counts on the map while mapping, but the maps loads very quickly for me, so no issues there. Some of the comparison tools that are new are pretty neat.

 

I say all of this, but now it appears they've broken something with this latest release >_<

  • Like 1
Link to comment
Share on other sites

I searched but could not find an answer. Do we know yet how Sensorly will treat Band 41 signals?

I was talking about it with them and also about getting a 224xx SID map as well but the new release and re-new release kinda took over the show.

 

Hard to do though without any phones being able to pick them up yet.

Link to comment
Share on other sites

Two things I still miss with the current version: 1) data point collection counter on the mapping map.  2) Satellite view.  I hope that both of those make it back in.

 

I was talking about it with them and also about getting a 224xx SID map as well but the new release and re-new release kinda took over the show.

 

I don't know if they could do it, but I think it would be really cool if there was a way for a "show my device coverage" map.  They would take the device the app is running on, know what bands it supports and then show a voice coverage map or a data coverage map for the bands it supports.  If the device is unknown (in their database), they  would drop back to the current style maps.  For most normal people that is what they want to see.....What the coverage is for their current device.  (If they could let you choose your carrier and device for comparison purposes, they would get major bonus points!)  People don't care or understand PCS voice, SMR voice, CDMA 1xRTT, 850 CDMA, 1900 LTE, 800 LTE, 2500 LTE, Band 25, Band 1, Band 41, etc.  They know they have a iPhone 5c, Galaxy S4, Note 2, Nexxus 5, some flip phone or slider and want to see its coverage.

 

I know for most of us this suggestion still wouldn't be perfect as different phones have different RF properties, but it would get us pretty close.

 

My idea is pretty far out of this world as the data required to make it work, number of devices to track, and other stuff make it almost impossible.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

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

    • I assume that any agreement is not perpetual and has an end date. - Trip
    • I think it is likely that T-Mobile will be forced to honor any existing US cellular roaming agreements in those areas as a condition of them taking over the spectrum.  In that case, there would be no improvement of service unless T-Mobile improves the service offering in those areas.
    • My understanding is the MNO carriers are the one who have objected to the use of cell phones in commercial planes.  I understand that it ties down too many cell phones at once, thus I can not see this changing. However this depends on how it is structured. Use of a different plmn for satellite service might make it possible for planes only to connect with satellite. Private pilots have been using cellphones in planes for many decades. Far fewer phones at a lower altitude.
    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
  • Recently Browsing

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