Jump to content

Sprint LTE Coverage Maps via Sensorly

S4GRU
 Share

Recommended Posts

kckid Member Level: 4G WiMax

kckid

Posted
Posted

Is the coverage map suppose to default to display your location? Whenever I click the coverage map for Sprint LTE, it displays New York, City. This also happens when I'm mapping a trip and click view maps.

 

Let me know if there is a setting I need to change, but I've looked around and couldn't find one.

  • Like 1
Link to comment
Share on other sites
  • Replies 1.2k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

S4GRU
S4GRU

http://www.sensorly.com/iframe2/S4GRU/map/4G/US/USA/Sprint/lte_310sprint">Your browser doesn't support IFRAMEs, please upgrade

S4GRU
S4GRU

I just want to thank our sources here at S4GRU. You have to hide in the shadows and never get the public accolades you deserve. Thanks for all you do you to give us heads up about things like Howell.

SWMich4G
SWMich4G

I was bored and like comparing how Sprint is catching up to AT&T on the sensorly map so I made a map of all the spots Sprint has LTE where AT&T doesn't and vice-verse.  This ignores signal qua

Posted Images

tommym65 Member Level: eHRPD

tommym65

Posted
Posted

Is the coverage map suppose to default to display your location? Whenever I click the coverage map for Sprint LTE, it displays New York, City. This also happens when I'm mapping a trip and click view maps.

 

Let me know if there is a setting I need to change, but I've looked around and couldn't find one.

 

This also happened to me after my last Sensorly upgrade, about 3 or 4 days ago. Seems to be a bug in the release.

  • Like 1
Link to comment
Share on other sites
Machque Member Level: Digital

Machque

Posted
Posted

I went to that New York page, clicked on the Sensorly logo in the upper left corner which took me to a page that had locality displayed, and I then bookmarked that page. Now it takes me to my local map every time.

Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

Had to roll back to a previous version of Sensorly. Got tired of looking at NYC every time I hit coverage map, no offense NYCians.

That bug will be fixed in a release at the end of the week.. it was introduced in the last version when we added URL redirection : if you click on a link to a sensorly map (from twitter, FB or email..), it will open a menu asking you whether to open in the browser or the app.

 

I have been doing some digging and I believe I can make a simple app that would help me identify cell sites and LTE sites. I really wish Sensorly would capture and show us more than just signal info. In NOLA we already ran into several times where we wished we knew the LTE info on the signal. By no means is it going to be a Sensorly like app or replace it. It will just feed the need for more data that us wireless geeks are vying for everyday in our LTE hunting adventures.

Going to be cool.. Sensorly mapping the trip in the background building the map and a geeky all in one debug menu. Just hope I can pull this off.

Right now, phones don't provide LTE cell information so no way to lists sites.

What functionality is missing in Sensorly for you exactly ?

  • Like 2
Link to comment
Share on other sites
boomerbubba Member Level: eHRPD

boomerbubba

Posted
Posted

Right now, phones don't provide LTE cell information so no way to lists sites.

What functionality is missing in Sensorly for you exactly ?

 

There are LTE sector IDs (both short integers for Physical Cell IDs and long 28-bit integers for Cell Identity) available in the expanded API for Jellybean. It would be nice to see these in Sensorly's Detail screen.

 

The utility of all this would be multiplied if Sensorly provided the user a way to export a log of their own data points.

Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

There are LTE sector IDs (both short integers for Physical Cell IDs and long 28-bit integers for Cell Identity) available in the expanded API for Jellybean. It would be nice to see these in Sensorly's Detail screen.

 

The utility of all this would be multiplied if Sensorly provided the user a way to export a log of their own data points.

I implemented calls to that API using reflexion but I have yet to see anything be returned. Are you aware of any phones that do ?

Link to comment
Share on other sites
boomerbubba Member Level: eHRPD

boomerbubba

Posted
Posted

I implemented calls to that API using reflexion but I have yet to see anything be returned. Are you aware of any phones that do ?

 

Using what version of the SDK? In Jellybean, I don't think you need to go around the barn with reflexion and hidden APIs. There are direct API calls to this stuff. I have no hands-on experience, just read the docs.

Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

Using what version of the SDK? In Jellybean, I don't think you need to go around the barn with reflexion and hidden APIs. There are direct API calls to this stuff. I have no hands-on experience, just read the docs.

Ok, thought it was still hidden. Will look into this and try to include it in the Friday release.

  • Like 1
Link to comment
Share on other sites
MacPCS Member Level: 3G EVDO

MacPCS

Posted
Posted

I agree, what does that mean?

Basically the pixels are so small and close together that at a "normal viewing distance" (read: not eyes on screen) you cannot discern individual pixels like you can on a normal LCD screen with the naked eye (hence, retina). I have a gorgeous 24" monitor I'm typing this on right now for example. I can tell the pixels have a small black space between all of them. On a retina display (iPhone 4 / 4S / 5, iPod Touch 4th or 5th gen, iPad 3rd or 4th gen or 13 or 15" MacBook Pro w/ retina display)... you cannot. It also tends to include other technologies like In-plane switching (IPS) that enhance the quality of the display, but the 'retina' part could exist without that (see iPod Touch 4th gen).

 

I think I just met my daily quota of parenthetical statements.

Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

Ok, thought it was still hidden. Will look into this and try to include it in the Friday release.

Looked at it and indeed the "hidden" 4.1 api was released in 4.2 but every call to getAllCellInfo() returns null on my GSM Nexus 4.

If anyone is reading this and has seen values returned by that call, let me know and we'll test together

Link to comment
Share on other sites
digiblur Member Level: LTE Advanced

digiblur

Posted
Posted

Looked at it and indeed the "hidden" 4.1 api was released in 4.2 but every call to getAllCellInfo() returns null on my GSM Nexus 4.

If anyone is reading this and has seen values returned by that call, let me know and we'll test together

 

I am sure there are several folks here that could test an apk for you in an LTE area.

 

This would be awesome if it could report the lte cell info as we are always trying to track down what site the signals came from as new ones come online.

 

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

 

 

  • Like 1
Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

I am sure there are several folks here that could test an apk for you in an LTE area.

This would be awesome if it could report the lte cell info as we are always trying to track down what site the signals came from as new ones come online.

Well, if there are any phones that do report data, we should have it on our servers (unless we're unlucky and there was a bug in the un-testable code). I'm working on importing that data right now to check.

Link to comment
Share on other sites
boomerbubba Member Level: eHRPD

boomerbubba

Posted
Posted

Looked at it and indeed the "hidden" 4.1 api was released in 4.2 but every call to getAllCellInfo() returns null on my GSM Nexus 4.

If anyone is reading this and has seen values returned by that call, let me know and we'll test together

 

Are we talking about the same API calls? This LteCellIdentity element is what I was referring to in 4.1.1

Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

Are we talking about the same API calls? This LteCellIdentity element is what I was referring to in 4.1.1

Yes, obtained from CellInfoLte.

 

It looks like only the Galaxy Nexus, Galaxy S3 Sprint, Galaxy S3 VZ phones provides that info right now.

If someone has one of these running JB, send me an email to contact@sensorlyDOTcom so I can send you a debug build.

If not, we'll shoot a fix on Friday and hope for the best. If that works, I'll add the info on the details screen next week.

  • Like 3
Link to comment
Share on other sites
lordsutch Member Level: eHRPD

lordsutch

Posted
Posted

Looked at it and indeed the "hidden" 4.1 api was released in 4.2 but every call to getAllCellInfo() returns null on my GSM Nexus 4.

 

Same here. I've been playing with it this afternoon and it always returns null on my Nexus 4 running 4.2 (whether getAllCellInfo() or through listening to the LISTEN_CELL_INFO events).

 

It also returns null on my Evo LTE running 4.1.1, although at least it doesn't throw any exceptions or blow up otherwise. Didn't bother testing on my Nexus 7 since it doesn't have a cellular radio :)

Link to comment
Share on other sites
digiblur Member Level: LTE Advanced

digiblur

Posted
Posted

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!"

Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

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!"

It's intentional : it shows where you phone will work. That's what most people are interested in.

  • Like 2
Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

We fixed the cell info gathering using the new api with the help of a user (thanks Ross!).

The upcoming release will include it. We'll have the info on the details screen in the following release which we'll try to make before Feb.

Remember that only some phones seems to be reporting it (very few)

  • Like 8
Link to comment
Share on other sites
digiblur Member Level: LTE Advanced

digiblur

Posted
Posted

We fixed the cell info gathering using the new api with the help of a user (thanks Ross!).

The upcoming release will include it. We'll have the info on the details screen in the following release which we'll try to make before Feb.

Remember that only some phones seems to be reporting it (very few)

 

Much appreciated! Fantastic work. Hopefully more phones will be upgraded and support the new calls.

Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
  • Author
Posted
We fixed the cell info gathering using the new api with the help of a user (thanks Ross!).

The upcoming release will include it. We'll have the info on the details screen in the following release which we'll try to make before Feb.

Remember that only some phones seems to be reporting it (very few)

 

Ross is a great resource to S4GRU too! Thanks Boomerbubba!

 

Robert via Nexus 7 with Tapatalk HD

  • Like 1
Link to comment
Share on other sites
sensorly Member Level: 1x Advanced

sensorly

Posted
Posted

Regarding roaming being a different color, we might be able to improve & do that later this year: we'll give it a shot.

 

The version has been delayed because of a bug. But we also slipped in some stuff like the LTE cell information in the details screen so you should be able to get LTE physical cell ids in a couple days (it looks like cell ids are not being reported) for the few phones that support it.

  • Like 6
Link to comment
Share on other sites
jamesinclair Member Level: 4G WiMax

jamesinclair

Posted
Posted

Regarding roaming being a different color, we might be able to improve & do that later this year: we'll give it a shot.

 

Sounds good!

 

When I first got the ap, my initial assumption in the 3G map was that blue was roaming, until I realized it was 2G........which at least in my area was roaming.

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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • topdownat4
      Keep a Word, Drop a Word #7

      By topdownat4 · Posted

      Fury Gran Coupe (My First Car - What a Boat...)
    • dkyeager
      Dish Network/Boost Mobile cell/5G buildout thread

      By dkyeager · Posted

      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.
    • dkyeager
      SignalCheck Beta Crew Forum

      By dkyeager · Posted

      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.
    • S4GRU
      Keep a Word, Drop a Word #7

      By S4GRU · Posted

      Nissan Coupe
    • Paynefanbro
      Network Vision/LTE - New York City Market

      By Paynefanbro · Posted

      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...