boomerbubba

If you are running custom ROMs, as your profile indicates, I suspect an incompatibility there.

Ahh. I misread the post in haste. This was not an announcement, but rather Sprint adding Austin and other cities to its own "coverage map." We all know that this map has little credibility.

I'm surprised about the Austin announcement. There is still a big coverage hole in central Austin, including downtown, the Capitol complex and the UT campus area. In places further out, coverage is better. And in some areas, such as Pflugerville and Wells Branch, it is almost complete. Austin went on the "in progress" list a long time ago. And this is not a launch today. Just another Real Soon Now statement that adds no real news.

Have you enabled the tethering service on your Sprint account? That is the only way to do this under the standard contract terms. Tethering without enabling the billed service is not supposed to work. And BTW, I believe that discussion of how to subvert the terms of service is a violation of S4GRU's policy.

You aren't.

Have you tried the embedded Sensorly map at S4GRU?

I doubt that it is blocked, exactly. More likely many OEMs just failed to implement all the Jellybean API. I have read that implementation of the whole Android telephony API was imperfect in earlier versions, too.

The IDs that app displays are not the LTE sector IDs. They are the CDMA sector IDs, which may be referring to a completely different site. Conflating the CDMA and LTE data like this is a common failing of several such apps. Looks cool, but misinformation.

The LTE sector IDs are available in the Jellybean 4.1.1 API. But according to what the devs at Sensorly say, so far there are few devices that populate it.

I misread patrickdurhamno's comment, mistaking the comma for a decimal point. A signal strength of -105 dBM RSRP is much more consistent with a full mile, rather than a tenth of a mile.

If you were that close to that tower with a clear line of sight, your relatively weak signal of -105 dBm RSRP is a good indicator that this signal is actually coming from somewhere else. It could be miles away.

The dev team at Sensorly is reporting success using the 4.1.1 Jellybean API to harvest this information, but only on certain devices that populate it -- which does include the stock Samsung GS3. Sensorly hopes to release this in its user interface before February.

Osborne I -- 64 KB RAM, 8-bit Z80 CPU, two 95-KB 5-1/4 inch floppies, 5 " screen, luggable, CP/M operating system. For $1,800 -- a price breakthrough -- it came bundled with WordStar and a Supercalc spreadsheet program. I then acquired dBase 2, a dot-matrix printer and a Hayes 1200 baud Smartmodem, which seemed very fast compared to the 300 baud acoustic coupler I had used with my Texas Instruments terminal to dial into CompuServe and write my first Basic program. Altogether this gave me more computing power than my midsized employer had available to managers there. Entrepreneur Adam Osborne then pre-announced the Osborne II before it was ready, just as the IBM PC was introduced Sales at his single-product company dried up and the company cratered. I think this is still taught as a business school case in how not to do tech marketing.

Are we talking about the same API calls? This LteCellIdentity element is what I was referring to in 4.1.1

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.