Jump to content

sensorly

S4GRU Member
  • Posts

    109
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by sensorly

  1. But it didn't apply for LTE because the signal strength can't be reliably collected. I'm wondering if something just went wrong? It's made it incredibly hard to read. I did notice something weird in Chicago....

    Good catches everyone. We've just starting showing LTE signal strength (RSRP).

    What you're seeing is the artefact of having tens of millions of little images to update. It's being updated in real time and should be finished by tomorrow (there are only about 60.000 images to update on Sprint at the moment)

     

    Yes, the Android APIs are deficient for this but we found a way to harvest the information out of 90% of the datapoints we receive. We'll be deciding what we do with data points that show 4G but don't provide the signal strength in a couple days. We're open to input of course.

    • Like 5
  2. What happens when users report new data?

     

    IE: Say an area on sensorly says there is wimax, because in 2010, a phone found wimax there.

     

    But then say the tower is broken and clear wont fix it, so when a new user goes by, it reports no signal.

     

     

    At any point, does the new data replace the old?

    Not at the moment no. We're working on an expiration algorithm. But it needs to work while still allowing fast updates. It's taking a little longer than planned.

  3. What I thought was interesting was one time, a couple weeks ago, when I mapped a trip home from work. Most of the trip data showed up within a few minutes, maybe an hour or so, but there was an entire section from the end of the trip that wasn't updated. I checked it for a couple days, but it didn't get updated, and I forgot about it. A couple days ago, I looked at the coverage map again, and the final part of my trip had been added to the map. It's weird that only part of the trip update was delayed.

    It's actually pretty hard to do a algorithm that's both very fast and "consistent" in terms of data. Plus there's a little weird bug creeping in the update process that we haven't figured out yet that's delaying some updates to when someone else goes in the same place. We'll get it fixed eventually.

    • Like 1
  4. Wow, that's a lot of positive responses & feedback. Thanks !

     

    The maps update super super fast at the moment (like in minutes at all zoom levels). So if data is not visible with 24 hours there's either something wrong or the app isn't giving enough feedback about what's going on.

    For example : depending on the version, Galaxy S2 phones will or will not provide usable data. The latest release should make it usable on more version but still... The worst phone is the Galaxy Note which doesn't work at all in Europe but seems to work in it's AT&T avatar.

    AT the moment, data is added to the map when your phone is connected to that network because the phone reports LTE as its "telephony network" so we don't know if it's connected to EVDO or 1x..

     

    I added the thread to the market section because I posted market info :)

     

    It's still a little tough to add features fast to the app because of lack of time... be a little patient :)

  5. Hi everyone, we've been invited by one of your users to open a thread about Sensorly ( https://twitter.com/...890907013795841 ) so although I thought it was against the rules, I'll give it a shot.

    Admins : if this is bad bad bad nonetheless, I'm sorry...

     

    So... Sensorly is an app and a website that gives anyone the chance to see what kind of mobile network is available where.

    What makes it different from carrier maps is that it's not based on simulations & modeling but on actual data collected by the community of users. Yes : if you install the app and opt-in, you can contribute to the maps. It gets updated constantly and will show your data within the day for sure and within 15 minutes most of the time.

     

    Here's Sprint LTE picked up in Indianapolis by our users : http://www.sensorly....#q=indianapolis, ua

     

    We love to get feedback from our users and although sometimes stuff takes a little time to get done, we always answer (contact@....).

     

    Our app is also a great way to discover new markets being tested and/or deployed. Here are the markets where users have reported being connected to Sprint LTE since October 1st. As you can see, Indianapolis is there. Let me know if this is interesting and we'll find a way to get you regular updates.

     

     

    				  urban_area				  |	   first_seen	   | nbr_data_points | distinct_devices
    ----------------------------------------------+------------------------+-----------------+------------------
    Aberdeen--Bel Air South--Bel Air North, MD   | 2012-10-03 04:07:12+02 |			 236 |				1
    Atlanta, GA								  | 2012-09-27 15:48:07+02 |		   12835 |			   27
    Austin, TX								   | 2012-09-30 15:32:16+02 |			9297 |			   28
    Baltimore, MD								| 2012-09-29 19:52:21+02 |			 476 |				7
    Boston, MA--NH--RI						   | 2012-09-30 17:37:10+02 |			7021 |			   27
    Brookshire, TX							   | 2012-10-03 14:08:53+02 |			  11 |				1
    Calhoun, GA								  | 2012-09-30 22:14:36+02 |			 128 |				1
    Castroville, TX							  | 2012-10-01 19:39:21+02 |			  15 |				1
    Chicago, IL--IN							  | 2012-09-29 18:13:52+02 |		   41472 |			   71
    Conroe--The Woodlands, TX					| 2012-09-30 19:34:05+02 |			  94 |				1
    Dallas--Fort Worth--Arlington, TX			| 2012-09-30 15:20:35+02 |			6748 |			   27
    Denton--Lewisville, TX					   | 2012-10-03 21:14:22+02 |			 265 |				1
    Elkhart, IN--MI							  | 2012-10-01 15:29:57+02 |			 563 |				2
    Eudora, KS								   | 2012-10-01 19:01:44+02 |			 127 |				1
    Excelsior Springs, MO						| 2012-09-30 19:27:54+02 |			  38 |				2
    Galveston, TX								| 2012-10-03 00:12:56+02 |			   6 |				1
    Grangerland, TX							  | 2012-10-01 19:10:10+02 |			  31 |				1
    Hagerstown, MD--WV--PA					   | 2012-10-01 23:21:41+02 |			 334 |				4
    Harrisburg, PA							   | 2012-10-01 22:06:53+02 |			 107 |				2
    Houston, TX								  | 2012-09-30 03:23:05+02 |		   11856 |			   29
    Hutchinson, KS							   | 2012-10-01 18:21:44+02 |			 225 |				1
    Indianapolis, IN							 | 2012-09-30 17:09:45+02 |			 709 |				2
    Junction City, KS							| 2012-10-02 18:33:59+02 |			 221 |				1
    Kankakee, IL								 | 2012-09-30 20:04:44+02 |			2537 |				2
    Kansas City, MO--KS						  | 2012-09-30 07:29:48+02 |			4425 |			   10
    Lake Conroe Westshore, TX					| 2012-09-30 18:41:11+02 |			  12 |				1
    Lawrence, KS								 | 2012-10-01 18:56:00+02 |			 125 |				1
    Lee's Summit, MO							 | 2012-10-01 18:31:52+02 |			 352 |				1
    Leominster--Fitchburg, MA					| 2012-09-30 21:59:12+02 |			 945 |				1
    Manhattan, KS								| 2012-10-04 01:04:33+02 |			  87 |				1
    Marlin, TX								   | 2012-10-02 01:12:42+02 |			   6 |				1
    McKinney, TX								 | 2012-10-02 20:42:15+02 |			  43 |				1
    McPherson, KS								| 2012-10-01 00:21:23+02 |			 733 |				3
    Nashua, NH--MA							   | 2012-10-02 20:46:31+02 |			  16 |				1
    New Bedford, MA							  | 2012-09-30 05:48:35+02 |			 504 |				2
    New York--Newark, NY--NJ--CT				 | 2012-09-30 11:55:21+02 |			  42 |				2
    Providence, RI--MA						   | 2012-09-30 11:33:53+02 |			 216 |				2
    Rockford, IL								 | 2012-10-01 18:59:09+02 |			1075 |				2
    Round Lake Beach--McHenry--Grayslake, IL--WI | 2012-09-30 04:38:12+02 |			 215 |				3
    San Antonio, TX							  | 2012-09-30 21:11:17+02 |			3417 |				5
    San Jose, CA								 | 2012-09-30 21:42:47+02 |			 440 |				3
    Springfield, MA--CT						  | 2012-09-30 07:40:34+02 |			 553 |				2
    St. Joseph, MO--KS						   | 2012-10-01 20:21:08+02 |			 178 |				1
    Topeka, KS								   | 2012-10-01 18:18:46+02 |			 531 |				1
    Waynesboro, PA--MD						   | 2012-10-03 22:03:17+02 |			   3 |				1
    Weatherford, TX							  | 2012-10-03 19:18:57+02 |			  13 |				1
    Wichita, KS								  | 2012-09-30 21:09:33+02 |			5078 |				9
    • Like 16
×
×
  • Create New...