lordsutch

I believe you can attach the $15 hotspot option to the prepaid $30 plan. I haven't, since I really haven't found the need to do any tethering lately (all hail the spread of free wi-fi).

AFAIK Connection Optimizer will alert you that unencrypted WiFi points are available, but it won't automatically connect to any hotspot that you don't already have set for automatic connections under the WiFi Settings menu.

I went and read the thread. If it doesn't affect every phone, and some (but not all) people running custom ROMs like CM 10 have the same problem, and wiping the phone and reinstalling to a baseline, factory-fresh state where it is known to work on other Evo LTEs doesn't fix the problem, it has to be a hardware problem with specific phones by definition. Just because new software exposes the underlying hardware problem doesn't mean it's not actually a hardware problem.

The map shows your location; I will probably add a marker for the reported 1X tower position at some point, but that information is unreliable. Edit: I just updated the APK. The reported 1x tower position is now shown on the map. On some sites it will be offset from the actual tower location in the direction of the sector, while on others it will be at the actual base station location.

I've put together a new release of my cheesy ESMR/LTE base station tracker for Android 4.x. One of these days I'll get around to setting up a Google Play developer account... in the meantime, here's the link: here This version logs ESMR and LTE base stations discovered in files on your (emulated) SD card in Android/data/com.lordsutch.android.signaldetector/files. ESMR base station logging should work on any Android 4.x CDMA phone. The implementation is actually pretty stupid (it just looks for known ESMR SIDs). To find anything, though, you'll need a PRL that scans on ESMR bands (thanks to digiblur, sponsors have access to such a PRL) or you'll need to be in a market where Sprint has enabled ESMR scanning in their PRLs. LTE base station logging requires a phone that either implements the Android 4.2 CellLocationLte API or a HTC Evo LTE running a stock ROM (where reverse-engineering the proprietary API wasn't terribly painful). Unfortunately getting at the data on 4.0/4.1 Samsung devices requires deep magic that I can't quite wrap my brain around, and I haven't tried yet with LG's devices. At present the only stock devices that are likely to be able to log LTE base stations are: HTC Evo 4G LTE (hex cell ID only) HTC One (hex cell ID only) Samsung Galaxy Nexus (both IDs, with 4.2.1 update) Devices running a 4.2 ROM (both IDs: CM 10.1, Evervolv 3.2, etc. - NOTE: only if the radio reports the data using the Android 4.2 interfaces, so apparently Galaxy Nexus only) The app also includes GSM/WCDMA display but no logging since there didn't seem to be anything worth logging on those devices. It's mostly there (a.) because I could and (b.) if Google ever bothers to implement CellLocationLte on GSM+LTE devices like the Nexus 4 (perhaps in Key Lime Pie or a 4.2.x point release?). Source is on github: https://github.com/l...rength-Detector Still on the to-do list: background logging and adding a menu to control that. (Edit: I removed the legacy version link, because there is an error in its base station logging. PM me if you're really interested in a map-less version of the app.)

I've never had any navigation issues, including with this update. If a factory reset doesn't fix the issue, there may be a hardware problem with your phone's GPS.

The way I see it is my phone is going to end up in a case anyway, so neither I nor anyone else is going to see the bling very often, if ever. Now the CPU/GPU specs and panel, on the other hand, would make a difference in my mind. But I don't see anything from anyone that compelling in the next 12 months that would get me buying a new phone before my upgrade window (and in this neck of the woods, ESMR and 2600 LTE aren't likely to be here much before then, if at all, anyway).

As far as I've heard, the iPhone 5 is the only device that shows both IDs on its debug screen. Both should be exposed by the CellIdentityLte API in Android 4.2, although that relies on the OEM's radio reporting the data.

I've hit a bit of a brick wall; apparently on Samsung devices the cell ID and physical cell ID are only available via an internal API that can only be called from the dialer. However, I did figure out how to get the RSRP on most LTE devices, so that should now show up in the app at least. Hopefully when 4.2 hits the Samsung devices they'll implement the official APIs. Edit: The last few releases were refusing to actually stop, and thus eating a lot of battery. If you downloaded in the last 48 hours or so, be sure to update to the latest apk.

According to the FCC's public notice, Congress did override state and local authority in this matter. Whether it's constitutional or not is a separate question, but the law seems pretty unambiguous about Congress' intent:

Bummer. Guess I'll need to poke around dexdumps of the Samsung field test apk some more.

Yeah, I poked around the API... HTC only exposes the Hex ID (the only thing else I've found exposed by the same call is EVDO base station ID). Now, if someone out there has a rooted Evo LTE running a 4.2 ROM (like Evervolv), the official API may report the physical cell ID, and if it does my app should be able to fetch it. I haven't gotten annoyed enough yet at Sense to root mine yet though.

Cool. I got an email report from someone with a Samsung S3 where the v17 API doesn't seem to be reporting anything. That may have been a bug at my end; I'd be curious if it works now. I drove around a bit in some LTE areas and was able to fix a few buglets while I was out on the road (rapid application development in the car, always fun). I also added a new feature (which should work on any Jelly Bean CDMA phone): a second log, "esmrcells.csv", now logs your location, SID/NID/BSID, and 1x signal strength when connected to a 224xx SID. Might help people with finding live ESMR cells. I probably can tweak the app a little to actually run OK on ICS too, for people that are interested in doing some ESMR tracking.

Hacked some more on it. Found a problem (the getSectorId() call on HTC actually takes a single integer parameter, which is set to 1 by the field test apk - no idea what other values do yet, although I suspect the physical cell ID is available with a different value). It also now creates a logfile on your SD card/emulated SD directory called "ltecells.csv". And there's a notification icon but it doesn't do much yet. APK is here: https://www.dropbox....omeActivity.apk Again, it should also work on devices running Android 4.1 and later that support the official APIs (reportedly some Samsung devices work: Galaxy Nexus and S3), and it probably works on HTC's LTE devices on other carriers too, since I can't imagine HTC would have come up with a different API for those, although only tested on the Evo 4G LTE thus far.

I've been working today on adding some rudimentary support for the hidden LTE APIs on the Evo 4G LTE (and probably other HTC LTE phones on other providers). The top 3 lines in the app should now continuously report the location, signal strength, and LTE cell ID (if available). For phones that populate the official Android API, you should get both the Hex cell ID and the integer physical cell ID (0-503); HTC only exposes the Hex cell ID as far as I can tell, so that's all that I can report. The APK above is updated, and the source is now on Github. Unfortunately I'm not in an LTE area so I haven't had a chance to test the code, but it should work. (I do plan to try it out tomorrow.) What isn't done yet is any logging. I probably need to learn more about background tasks before I can get anything like that to work.

After poking around in the FieldTrial.apk source, I think I've figured out how to get the hex Serving cell ID on the HTC Evo 4G LTE, and probably other LTE phones by HTC: Object mHTCManager; Method method; String sectorID; mHTCManager = getSystemService("htctelephony"); if(mHTCManager) { // Workaround fact we don't have a usable HTCTelephonyManager declaration method = mHTCManager.getMethod("getSectorID", null); sectorID = method.invoke(); } Untested as of yet but I think it should work (modulo my lack of Java-foo). Other potentially interesting methods available seem to include: (some sort of object) requestGetLTERFBandInfo() (some sort of object) requestGetLTETxRxInfo() int getLastLTEErrorCode()