kckid Posted January 12, 2013 Share Posted January 12, 2013 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. 1 Quote Link to comment Share on other sites More sharing options...
tommym65 Posted January 13, 2013 Share Posted January 13, 2013 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. 1 Quote Link to comment Share on other sites More sharing options...
Machque Posted January 13, 2013 Share Posted January 13, 2013 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. Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 16, 2013 Share Posted January 16, 2013 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 ? 2 Quote Link to comment Share on other sites More sharing options...
boomerbubba Posted January 16, 2013 Share Posted January 16, 2013 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. Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 16, 2013 Share Posted January 16, 2013 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 ? Quote Link to comment Share on other sites More sharing options...
boomerbubba Posted January 16, 2013 Share Posted January 16, 2013 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. Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 16, 2013 Share Posted January 16, 2013 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. 1 Quote Link to comment Share on other sites More sharing options...
MacPCS Posted January 16, 2013 Share Posted January 16, 2013 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. Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 16, 2013 Share Posted January 16, 2013 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 Quote Link to comment Share on other sites More sharing options...
digiblur Posted January 16, 2013 Share Posted January 16, 2013 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!" 1 Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 16, 2013 Share Posted January 16, 2013 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. Quote Link to comment Share on other sites More sharing options...
boomerbubba Posted January 16, 2013 Share Posted January 16, 2013 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 Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 16, 2013 Share Posted January 16, 2013 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. 3 Quote Link to comment Share on other sites More sharing options...
digiblur Posted January 16, 2013 Share Posted January 16, 2013 Awesome! Does the Note2 have it? Would there be any way to see the data on the map? -- "Sensorly or it didn't happen!" 1 Quote Link to comment Share on other sites More sharing options...
lordsutch Posted January 16, 2013 Share Posted January 16, 2013 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 Quote Link to comment Share on other sites More sharing options...
digiblur Posted January 17, 2013 Share Posted January 17, 2013 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!" Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 18, 2013 Share Posted January 18, 2013 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. 2 Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 18, 2013 Share Posted January 18, 2013 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) 8 Quote Link to comment Share on other sites More sharing options...
digiblur Posted January 18, 2013 Share Posted January 18, 2013 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. Quote Link to comment Share on other sites More sharing options...
S4GRU Posted January 18, 2013 Author Share Posted January 18, 2013 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 1 Quote Link to comment Share on other sites More sharing options...
jamesinclair Posted January 18, 2013 Share Posted January 18, 2013 It's intentional : it shows where you phone will work. That's what most people are interested in. Would be nice if roaming were a different color though. 2 Quote Link to comment Share on other sites More sharing options...
sensorly Posted January 20, 2013 Share Posted January 20, 2013 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. 6 Quote Link to comment Share on other sites More sharing options...
digiblur Posted January 20, 2013 Share Posted January 20, 2013 Thanks for the updates. We appreciate your posts here and listening to us wireless geeks. I think we would be lost without your app and maps it creates. -- "Sensorly or it didn't happen!" 1 Quote Link to comment Share on other sites More sharing options...
jamesinclair Posted January 21, 2013 Share Posted January 21, 2013 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.