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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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