JWMaloney

Actually, no. Didn't notice that column before

I agree. A Sprint Care rep confirmed to me today that a number of sites in the New Orleans market have 800 MHz upgrades scheduled.

I had that issue a while back for several weeks, had to call and get a network ticket opened to correct it.

I wish more people would switch to the FCC Speed Test app to keep the carriers honest.

Sprint Turns Up the Volume on 3G and 4G LTE in Chicago

Not sure if you'll have to do this on Nexus 5, but I had to explicitly specify my device info to get Sprint Zone fully working on my Nexus S. In the following file... /data/data/com.sprint.zome/shared_preferences/com.sprint.zone_preferences.xml ...I added the following lines... <string name="funnyPref1">%NAI%</string> <string name="funnyPref2">%MEID-HEX%</string> <string name="funnyPref3">%RESELLER-ID%</string> <string name="funnyPref4">%MSID%</string> <string name="funnyPref5">%PRL-VERSION%</string> <string name="funnyPref6">%MDN%</string> <string name="funnyPref7">%MAKE%</string> <string name="funnyPref8">%MODEL%</string> ...with my actual device data, of course. It looked something like this: <string name="funnyPref1">jason****@sprintpcs.com</string> <string name="funnyPref2">A00000**********</string> <string name="funnyPref3">Sprint</string> <string name="funnyPref4">504*******</string> <string name="funnyPref5">60798</string> <string name="funnyPref6">504*******</string> <string name="funnyPref7">Samsung</string> <string name="funnyPref8">Nexus S 4G</string> Prior to doing that, tapping Refresh would spit an error into the device log stating "mdn is a required parameter," which is what the server responds when it doesn't receive a valid MDN. After making the modification, account auto-login worked correctly, I could see all my devices and billing data, and service trender alerts appeared. This seems to be an issue because my device doesn't system properties for MDN, NAI, and PRL that Sprint Zone is looking for. I've been attempting to reverse-engineer the specific properties with no success. I'll post them here if I can find them, since using setprop is a lot easier than modifying shared preferences.

Never mind, figured it out. They're actually limiting connections to zone.sprint.com by IP address now. Once I disabled Wi-Fi on my Nexus S, the Sprint Zone app was able to successfully refresh. So I tethered my laptop to my phone, and I was able to pull up zone.sprint.com with Google Chrome. They must have freaked out when their server logs showed all of our connections from various IP addresses before, since they're leaking account-specific information if you just type in any phone number.

I was able to deodex the version in the LG G2 system dump (4.5.31) and load it onto my Nexus S. ADB log shows "connection refused" when the app itself attempts to contact zone.sprint.com, so it looks like the user agent doesn't make a difference.

Is there a newer version of Sprint Zone than 4.3.23?

I mean, most of the places that AT&T puts those camouflaged towers are actually surrounded by trees. It looks ridiculous standing on its own.

Can't connect today, anyone else?

You used to be able to get around this by blocking connections to 1.2.3.4. Sprint injects Javascript into all pages from that IP address. You also used to be able to get around this by changing your user agent. Unfortunately, it looks like Sprint is intercepting the image URLs themselves now (again depending on user agent).

Check out this awfully camouflaged AT&T tower in Lafayette, LA.

serviceTrenderMessage="Sprint has recorded some dropped call activity occurring on your line. To further troubleshoot these drops, please call Customer Care for assistance (message 231)." I would call, but they might tell me to clear my cookies

Here's one in Louisiana, although it isn't a Sprint tower. http://goo.gl/maps/aNcRg