Fraydog

Please don't think I'm an AT&T fan. I just like their 4G LTE logo better.

http://forums.androidcentral.com/showthread.php?t=178232 My head hurts after reading this thread.

Sprint has existing 3G roaming contracts with them in my neck of the woods. Occasionally I'll fall back to extended roaming off VZW on them. Speeds are really good, but I kind of operate under the assumption that I'm usually the only user on that EV-DO channel. They sure shed a lot of customers here. Billing and customer service in particular were large issues.

Bainbridge is an area that is severely affected because of the FCC's ignorant decision to not block the acquisition of spectrum squatter ATN's acquisition of Alltel properties in six states of which Georgia is one. How bad is ATN? AT&T should have been allowed to take the other six markets that VZW shed off in addition to the 18 they did acquire for Verizon as part of the Alltel divestures. Yes, ATN/Commnet is that bad. I bet they hit Sprint bad on roaming rates as well. Just a really rotten example of the FCC screwing the pooch. I wouldn't blame Sprint for the lack of competition which is eluded to here. If anything the FCC should be cutting a check to Sprint for providing completion of NV in these six states, specifically in the areas where they screwed the pooch with Alltel.

DeKalb is served by Frontier which is a major pain in the arse to deal with from a backhaul perspective.

That's AT&T's RRU. Same around STL where AT&T is doing a Network Vision like upgrade in getting 4G LTE running.

It is the same with the VZW version since they are almost the same device.

You think that's bad? So is the AT&T Facebook. So is VZW's and T-Mo's, for that matter. It really makes me feel empathy for the social media people at all these companies who have to clean up after these messes (HIRE ME PLEASE).

Tea time

On HoFo someone found a live LTE site near Highland, IN, which is in the Chicago metro SE of the Loop.

Foot pain

Royal poisoning.

No play.

Gave me

They gave

That they

Case that

I didn't want to seem like I was just singling out Sprint. AT&T isn't saying a peep yet about the One X LTE/Wi-Fi issues it has, or their own customs issues. AT&T will soon issue the 1.85 update that should fix a lot of the issues. It just sucks users have to be the beta testers here. I don't find it surprising these issues are popping up with the S4, a chipset with loads of potential but still having bugs to work out. That is a big reason why I have not yet pulled the trigger on a One X yet. I unfortunately don't live in a town with much in the way of native Sprint coverage so that rules the EVO out for me.

Why did they not stick with the original launch date in the first place? Yeah, launch a device that has customs issues and LTE issues, on a network that is not even close to be fully baked. Sorry to the EVO LTE owners but that sucks Sprint put you in that spot.

Say cheese

Multiple options

Kill switch

The VZW version tested has dual core Snapdragon S4 MSM8960 according to PDADB.http://pdadb.net/index.php?m=specs&id=3533&c=samsung_sch-i535_galaxy_s3

Good question. I live right on a SRA boundary for a SRA that is currently building out (Mobilenation). My hometown is a zip code that is eligible for Sprint service but does not have native service all the way through. I'd like to have this as well.

record time