Jump to content

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
Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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.

Link to comment
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 ?

Link to comment
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.

Link to comment
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
Link to comment
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.

Link to comment
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

Link to comment
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
Link to comment
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.

Link to comment
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

Link to comment
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
Link to comment
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 :)

Link to comment
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!"

Link to comment
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
Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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
Link to comment
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.

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

    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No soecific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
    • T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.
    • Was true in my market. Likely means a higher percentage of 5g phones in your market.
  • Recently Browsing

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