Jump to content

Sprint LTE Coverage Maps via Sensorly


Recommended Posts

I tried to give the new update a try again, but it is such a pain to use. I just want the old map trip functionality using Google maps and having the current amount of points collected at the top. I strongly hate the crap that keeps on taking over the bottom half of the display.

  • Like 1
Link to comment
Share on other sites

 

'digiblur', on 17 Jan 2013 - 4:04 PM, said:snapback.png

One thing I have noticed is Sensorly incorrectly reports roaming coverage as Sprint coverage. Not sure if this is done by design or possible limitation at the time.

 

Went to an area that I know is roaming and wanted to map where Sprint stopped, I left it on accidentally. And it mapped the roaming coverage. DOH! It looks like Sprint has coverage there now.

 

Now that I look at things with all the times I am roaming in places, really looking at the Sprint CDMA map means nothing about Sprint's service coverage area since it includes all the other CDMA services as well.

 

-- "Sensorly or it didn't happen!"

 

 

 

 

Unfortunately, for me, that is not what I am interested in. I am using BoostMobile and am using the maps to see only Sprint coverage, as I do not get roaming.

 

 

It will possibly be best for you to use the actual maps on the boost site given your specific needs.

Link to comment
Share on other sites

The ping times on the Sensorly app for speed tests are generally wrong on my device. My WiFi ping in usually 17ms or less and the app tells me it is at 127ms.

 

How does that mean it's wrong? It just indicates that the route between your device and whatever speed test server Sensorly is using has higher latency than whatever server you've used before..

 

-Mike

  • Like 1
Link to comment
Share on other sites

I tried to give the new update a try again, but it is such a pain to use. I just want the old map trip functionality using Google maps and having the current amount of points collected at the top. I strongly hate the crap that keeps on taking over the bottom half of the display.

 

The latest releases uses Google maps again. You can turn off the information that covers the map, most of it is not there anymore. Have you recently updated your app?

 

The ping times on the Sensorly app for speed tests are generally wrong on my device. My WiFi ping in usually 17ms or less and the app tells me it is at 127ms.

 

I generally do not use Sensorly for speedtests if I need to run one. It almost never reflects that actual status of the network. I don't know if it's because of the servers they're using or what, but the Speedtest.net app generally gives more accurate results. 

  • Like 1
Link to comment
Share on other sites

How does that mean it's wrong? It just indicates that the route between your device and whatever speed test server Sensorly is using has higher latency than whatever server you've used before..

 

-Mike

 

You're correct. It is just that in general, every speed test app/service that I have used found my ping to be around 17ms, whereas using Sensorly's speed test often brings up pings of 100ms or greater on average.

Link to comment
Share on other sites

Hmmm...

https://db.tt/d7ok7DWA

 

Downgrading again

 

 

I uninstalled and reinstalled, I'm definitely not getting Google maps on the latest update.

 

Perhaps it's the latest beta version since I'm in the beta testing group. I thought it had been pushed out to the play store for everyone already. Guess I was wrong. They are pushing a new official version to the Play Store either tomorrow or Tuesday, so just give it a couple of days. I've been using the latest update for the last couple of days and it is much much better. 

  • Like 1
Link to comment
Share on other sites

I am in no hurry to upgrade the old version still works. And the new features I saw I most likely won't use that much. I will upgrade in case they have something in the code to make their servers more efficient. I don't know if they changed the code that sends the data and as a user I don't really need to know.

 

One question though did they fix the map freshness for the mapper of the data? It was was mentioned last page in this thread and someone in the Pittsburgh thread said his info was not added. In the Pittsburgh thread he did not mention what version he was on.

Link to comment
Share on other sites

I am in no hurry to upgrade the old version still works. And the new features I saw I most likely won't use that much. I will upgrade in case they have something in the code to make their servers more efficient. I don't know if they changed the code that sends the data and as a user I don't really need to know.

 

One question though did they fix the map freshness for the mapper of the data? It was was mentioned last page in this thread and someone in the Pittsburgh thread said his info was not added. In the Pittsburgh thread he did not mention what version he was on.

 

I know that data I map, while watching the details screen, does seem to be uploading faster than in the past. I don't know if that an artifact of my network, or the app.

 

I haven't encountered any issues mapping since this summer when there was a glitch with the HTC One. Haven't seen that info since then. Typically, if data is not getting mapped, the user is rooted and the ROM authors had the brilliant idea to change the carrier name from Sprint, so Sensorly doesn't know what to do with the data. 

Link to comment
Share on other sites

The new update is including google maps again and is much better. For anyone else irritated with the bug (at least I'm assuming its a bug) stating maps are not available at this zoom level, just change the DPI of the app and you will be able to zoom out again. I went with ~110 DPI to see the United States.

 

https://db.tt/nspCJkY5

Link to comment
Share on other sites

Well it is great that I should be able to get 4g through virgin now. But I am wondering if it would possibly reach the loop. So would anyone be able to know if it would be able to reach the dutchtown loop since it is getting almost full signal on 74 it looks like. Also I was wondering how accurate these maps are. As don't phones take a minute sometimes to update on what the signal is?

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

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • 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.
  • Recently Browsing

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