sensorly

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 ?

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

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.

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>

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

There's no caching on the servers, there's an eternal cache on the device until you exit the app and there's a 30mn cache on devices between app runs.

Oh how I hate that the OS shows it that way...

Is that a real 24% or is that 24% of the battery drain of the day ? The Android OS shows the latter and it's confusing to users. Send me your anonymous id to contact@sens.... and I will investigate.

When you set it to "No Contribution" and start a map, there's a popup that will reset contribution to Active when you touch "Ok". I've never ever had the case of Passive setting itself back on by itself and I've tried over multiple days too. Are you 100% sure ? Is this consistently the case ?

Sometimes it takes a while, either there's a sudden traffic spike or we may be doing a bit of maintenance. This weekend, I re-initialized the mapping process and fixed a long standing bug that was making updates to some areas slow, so there shouldn't be any discrepancies left. Go ahead and contact us (contact@se....) if you see any.

Humm.. that's strange : if you set it to "no contribution", it should never map, even if you hit map trip. There should be a warning, isn't there one ?

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.

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)

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

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.

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.

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

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

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 ?

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. Right now, phones don't provide LTE cell information so no way to lists sites. What functionality is missing in Sensorly for you exactly ?

Try tapping the icon at the top right : it will screenshot the map without the status bar and add a caption to the bottom.