Jump to content
S4GRU

Sprint LTE Coverage Maps via Sensorly

Recommended Posts

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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 ?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Awesome!

 

Does the Note2 have it?

 

Would there be any way to see the data on the map?

 

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

 

 

  • Like 1

Share this post


Link to post
Share on other sites

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 :)

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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

 

Would be nice if roaming were a different color though.

  • Like 2

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Thanks for the updates. We appreciate your posts here and listening to us wireless geeks. I think we would be lost without your app and maps it creates.

 

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

 

 

  • Like 1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Looks like Sprint and T Mobile have been active around my house.   I see at least 3 new small cells that have going up in the last 2 weeks and are active.    I can pull a band 41 signal from 2 of them... the 3rd I'm assuming is Sprint  or T-Mo?   I'm not sure what the T-Mobile small cells look like.   Its very good to see progress.    Does anyone know if the small cells can broadcast more than one frequency?  Ie... if the merger is approved and T-Mo turns band 41 into 5G... then I assume I will not be able to pull that in with my Samsung 9+? 
    • Oh and I assume much of this is was a negotiation to renew their lease.




      Sent from my iPhone using Tapatalk
    • That’s what happens when you have a plan and can execute on it. And have customers....


      Sent from my iPhone using Tapatalk
    • https://www.t-mobile.com/news/first-600mhz-5g-test Bellevue, Washington — November 20, 2018 — T-Mobile (NASDAQ: TMUS) plans to bring 5G to everyone, everywhere, and together with Nokia, the Un-carrier just took a big step toward making that a reality. The companies just completed the world's first 5G data transmission on low-band spectrum (600 MHz) … and they did it on the Un-carrier’s live commercial network. Low band 600 MHz spectrum is key to building a nationwide 5G network, as it reaches much farther than other frequencies.  That's certainly a big step forward....
  • Recently Browsing

    No registered users viewing this page.

×