Sprint LTE Coverage Maps via Sensorly

[z250kid]

This is what I get I can use it fine but the image wont go away.

[sensorly]

What happened to Sensorly on the Apple App store?

Speedtest is broken since we changed the control server's IP. Waiting for Apple to ok the new version

[sensorly]

Sensorly hasn't updated on most zoom levels in 2 days now.

It turns out half our import engines went down for 3 days and our monitoring missed it. It's catching up.

The following shows how far back in importing the data we are. Add another day or so to catch up with redrawing the maps. Bascially 25% of the CDMA data is backlogged 5 days.

 

 

<table border="1" style="font-family: Times;"> <tbody> <tr> <th> Worker</th> <th> Last updated</th> <th> Highest id</th> <th> Time delta</th> </tr> <tr> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.0</td> <td> 2013-03-25 21:04:00.0</td> <td> 45076676</td> <td> 4.91 days</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.1</td> <td> 2013-03-25 21:09:33.0</td> <td> 66539273</td> <td> 12.92 minutes</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.2</td> <td> 2013-03-25 21:08:37.0</td> <td> 66564618</td> <td> 5.25 minutes</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.3</td> <td> 2013-03-25 21:09:33.0</td> <td> 66538799</td> <td> 13.03 minutes</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.0</td> <td> 2013-03-25 21:08:37.0</td> <td> 63537224</td> <td> 15.89 hours</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.1</td> <td> 2013-03-25 21:05:24.0</td> <td> 66571119</td> <td> 1 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.2</td> <td> 2013-03-25 21:08:37.0</td> <td> 63537086</td> <td> 15.90 hours</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.3</td> <td> 2013-03-25 21:05:20.0</td> <td> 66570271</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.0</td> <td> 2013-03-25 21:06:21.0</td> <td> 66574463</td> <td> 6 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.1</td> <td> 2013-03-25 21:09:33.0</td> <td> 53471637</td> <td> 3.13 days</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.2</td> <td> 2013-03-25 21:06:29.0</td> <td> 66574895</td> <td> 6 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.3</td> <td> 2013-03-25 21:08:37.0</td> <td> 60067367</td> <td> 1.55 days</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.0</td> <td> 2013-03-25 21:05:25.0</td> <td> 66570609</td> <td> 7 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.1</td> <td> 2013-03-25 21:05:26.0</td> <td> 66570629</td> <td> 8 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.2</td> <td> 2013-03-25 21:05:26.0</td> <td> 66570636</td> <td> 8 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.3</td> <td> 2013-03-25 21:05:25.0</td> <td> 66570601</td> <td> 7 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.0</td> <td> 2013-03-25 21:05:34.0</td> <td> 66571789</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.1</td> <td> 2013-03-25 21:07:41.0</td> <td> 66580174</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.2</td> <td> 2013-03-25 21:07:41.0</td> <td> 66580168</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.3</td> <td> 2013-03-25 21:05:34.0</td> <td> 66571793</td> <td> 0 seconds

</td> </tr> </tbody></table>

[SuSuMcKi]

 

Speedtest is broken since we changed the control server's IP. Waiting for Apple to ok the new version

 

 

Does this mean that iPhones may be able to get the app in the near future?

[sensorly]

We've had an iOS app out for a while but it can't collect signal strength or the type of mobile network, due to Apple restrictions.

[SuSuMcKi]

Oh! It doesn't show up when I search for it in the App Store. Maybe when/if Apple removes their restrictions it will be available again in the App Store.

[tampaflusa]

 

It turns out half our import engines went down for 3 days and our monitoring missed it. It's catching up.

The following shows how far back in importing the data we are. Add another day or so to catch up with redrawing the maps. Bascially 25% of the CDMA data is backlogged 5 days.

 

 

 

Was any data lost during that period?

[sensorly]

Was any data lost during that period?

No, it was just being added to a database until it could be processed. Once the data reaches us, it can't get lost.

[CAREND]

No, it was just being added to a database until it could be processed. Once the data reaches us, it can't get lost.

Ok, this is good to know since i mapped out some areas that had no 4g earlier.

[hiwhatsup]

We've had an iOS app out for a while but it can't collect signal strength or the type of mobile network, due to Apple restrictions.

 

Any plans to release Sensorly App for jailbroken phones on Cydia where there are no such restrictions?

 

There is is plenty of good info out there regarding iOS Private API Documentation that will allow you to using private iOS functions to collect signal strength and/or mobile network.

[sensorly]

There is is plenty of good info out there regarding iOS Private API Documentation that will allow you to using private iOS functions to collect signal strength and/or mobile network.

I found plenty for iOS 3 but I never found anything for iOS4 ,especially for CDMA.

Any pointers you'd like to share via PM ?

[sensorly]

Quick update : all of the backlog of data is processed and drawn at least at some zoom levels. Except for 25% of the CDMA data which is 4.5 days late at most.

<table border="1" style="font-family: Times;"> <tbody> <tr> <th> Worker</th> <th> Last updated</th> <th> Highest id</th> <th> Time delta</th> </tr> <tr> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.0</td> <td> 2013-03-27 08:22:52.0</td> <td> 54168312</td> <td> 4.48 days</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.1</td> <td> 2013-03-27 08:18:08.0</td> <td> 73104784</td> <td> 2 seconds</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.2</td> <td> 2013-03-27 08:18:08.0</td> <td> 73104704</td> <td> 4 seconds</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.3</td> <td> 2013-03-27 08:18:07.0</td> <td> 73104759</td> <td> 2 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.0</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112429</td> <td> 5 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.1</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112344</td> <td> 6 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.2</td> <td> 2013-03-27 08:21:28.0</td> <td> 73112234</td> <td> 5 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.3</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112334</td> <td> 6 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.0</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112739</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.1</td> <td> 2013-03-27 08:22:52.0</td> <td> 70917597</td> <td> 12.31 hours</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.2</td> <td> 2013-03-27 08:18:17.0</td> <td> 73105057</td> <td> 3 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.3</td> <td> 2013-03-27 08:18:15.0</td> <td> 73104961</td> <td> 3 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.0</td> <td> 2013-03-27 08:18:09.0</td> <td> 73104570</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.1</td> <td> 2013-03-27 08:18:09.0</td> <td> 73104569</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.2</td> <td> 2013-03-27 08:18:09.0</td> <td> 73104562</td> <td> 10 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.3</td> <td> 2013-03-27 08:18:08.0</td> <td> 73104564</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.0</td> <td> 2013-03-27 08:20:21.0</td> <td> 73109445</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.1</td> <td> 2013-03-27 08:20:22.0</td> <td> 73109476</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.2</td> <td> 2013-03-27 08:20:21.0</td> <td> 73109445</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.3</td> <td> 2013-03-27 08:20:22.0</td> <td> 73109484</td> <td> 0 seconds

</td> </tr> </tbody></table>

[hiwhatsup]

I found plenty for iOS 3 but I never found anything for iOS4 ,especially for CDMA.

Any pointers you'd like to share via PM ?

 

Ole Begemann did an excellent write-up built upon Nicolas Seriot's iOS Runtime Headers github repo:

 

http://oleb.net/blog/2013/02/new-undocumented-apis-ios-6-1/

 

I believe what your looking for specifically is the coretelephony.framework:

 

https://github.com/nst/iOS-Runtime-Headers/tree/76cc1d4a6e6bc5546f04448535f9e64ec22a9716/Frameworks/CoreTelephony.framework

[sensorly]

Exactly, thanks. I'll take a look

[hiwhatsup]

Exactly, thanks. I'll take a look

 

Awesome.. I hope it's what you need. I would love to see Sensorly app on Cydia.

[delta772er]

Quick update : all of the backlog of data is processed and drawn at least at some zoom levels. Except for 25% of the CDMA data which is 4.5 days late at most.

 

Just out curiosity about how long does it normally take to draw new data on the map? For example I mapped quite a bit of new LTE this morning around 1:30 AM Eastern and it's not on the map yet. I'm not complaining I'm just curious...

 

Correction: If I zoom in it's there, just not at the higher levels.

[GMAC]

Anyone want to help answer this question... in the map area type in 01904 and look for Western ave ...its a main drag thru the city...you will see a small patch of purple in the area of Ryans Terrace and Western ave ....

 

The question is there are no towers in the area and I live there ....the 4g is very spotty and the towers from the old maps showed there are 2 towers a mile in either direction ...on Western Ave and I am directly in the middle of the 2 !!!! how can it show 4g when there are no towers in the general area !!! They also don't show the towers that were in the old maps that SGRU put up for that area ...

 

GMAC

[sensorly]

Just out curiosity about how long does it normally take to draw new data on the map? For example I mapped quite a bit of new LTE this morning around 1:30 AM Eastern and it's not on the map yet. I'm not complaining I'm just curious...

Correction: If I zoom in it's there, just not at the higher levels.

Yeah there's a lof of optimization going on to update the maps as fast as possible so zoom levels aren't updated all at the same time. There's no backlog for LTE at the moment.

[digiblur]

Anyone want to help answer this question... in the map area type in 01904 and look for Western ave ...its a main drag thru the city...you will see a small patch of purple in the area of Ryans Terrace and Western ave ....

 

The question is there are no towers in the area and I live there ....the 4g is very spotty and the towers from the old maps showed there are 2 towers a mile in either direction ...on Western Ave and I am directly in the middle of the 2 !!!! how can it show 4g when there are no towers in the general area !!! They also don't show the towers that were in the old maps that SGRU put up for that area ...

 

GMAC

 

Could be several things. A well performing phone like the Note2, Galaxy Nexus that "pollutes" the map with its solid 4 bar signal when it is one bar or no signal. Referred to "Gnex pollution" in many of the market threads. Wish that phone wasn't allowed to map. I don't know that area but if there are any high buildings or structures that can also allow a phone to catch LTE since it is above all the ground clutter.

[JimBob]

Nice. I finally see the map shows more LTE in the Fayetteville, NC area.

[tampaflusa]

 

 

Could be several things. A well performing phone like the Note2, Galaxy Nexus that "pollutes" the map with its solid 4 bar signal when it is one bar or no signal. Referred to "Gnex pollution" in many of the market threads. Wish that phone wasn't allowed to map. I don't know that area but if there are any high buildings or structures that can also allow a phone to catch LTE since it is above all the ground clutter.

Yes can you please block Gnex from mapping? Some of the points are so off it looks like they mapped in hotair balloons and such.

[Yuhfhrh]

Yes can you please block Gnex from mapping? Some of the points are so off it looks like they mapped in hotair balloons and such.

 

I map all the time with my gnex (cm10), and have never had any issues or inaccuracies.

[mellimel2212]

 

I map all the time with my gnex (cm10), and have never had any issues or inaccuracies.

 

Me to and I know for a fact my data was correct because I know my real lte signal.

 

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

 

 

[dmchssc]

Perhaps some statistical filtering could be used to screen bad data? Devices that consistently report perfect signal strength should not have their "measurements" added to the database.

[JohnHovah]

Me to and I know for a fact my data was correct because I know my real lte signal.

 

Sent from my Sprint Galaxy Nexus rockin 4.2.2 using Tapatalk 2

 

I think the concern is that the GNex keeps and reports a much stronger LTE signal than other devices, so it will throw "true" coverage off for a majority of users.