S4GRU

Who's talking? I didn't see any talking. Just firing. As if Sprint can stop the press from reporting it. Your comment makes no sense in context. You are seeing the symptom of Masa not accepting talking anymore, only results. You're just complaining in negative platitudes. Robert

If memory serves, Sprint sold off the rest of their tower structures to Crown Castle in the last transaction. Circa 2010 or 2011. After that, they pretty much only remained in ownership of really bizarre or specialty sites, where they could not really sell the site. We are talking about dozens of sites, not hundreds or thousands. Robert

Sprint can install Band 26 on all but 8,000 sites in the IBEZ. That means it can deploy LTE 800 on approximately 80% of its sites now. Tmo doesn't even have anywhere near 80% of its sites within their upcoming 700MHz A Block spectrum. And when you consider Channel 51 contours, the difference between Sprint's usable 800 spectrum and Tmo's usable 700 spectrum is vastly different. I'm sure it will change over time for Tmo. They will likely pick up more 700 in the future. And they may even come up with some practical CH 51 interference resolution. But Sprint will also have the IBEZ problem solved in the future too. I will take Sprint's current 800 situation over Tmo's current 700 situation, IMO. Robert via Samsung Note 8.0 using Tapatalk Pro

Happy Dance Robert via Samsung Note 8.0 using Tapatalk Pro

Rubicon Trail Robert via Samsung Note 8.0 using Tapatalk Pro

Hugo Boss Robert via Samsung Note 8.0 using Tapatalk Pro

Not enough sites in the Reno/Tahoe area to justify another market. Not enough sites in the Redding/Chico area to justify a separate market. So adding these areas to the Sacto/Stockton makes sense. The UCV market is pretty condensed if you remove the far flung Eureka and Wendover sites. Robert via Samsung Note 8.0 using Tapatalk Pro

crime spree Robert via Samsung Note 8.0 using Tapatalk Pro

I thought it was a pretty fair article. It did cover Sprint's plans and that new people were heading it up. But was rightly critical in the appropriate places. Let's face it, historical facts are not always on its side. It is what it is. Sprint needs to execute. And based on the how things have gone the past few months, I'm more optimistic about plans and schedules. More than I have been for about a year. Masa is shaking things up, and we are just now starting to see the evidence of that. Robert via Samsung Note 8.0 using Tapatalk Pro

Site acceptance reports from Saturday (3/22) and Sunday (3/23): Albuquerque - 2 updates (2 LTE) Austin - 1 update (1 3G) Boston - 6 updates (6 LTE) Central Illinois - 1 update (1 LTE) Central Iowa - 1 update (1 LTE) Central Jersey - 3 updates (3 LTE) Charlotte - 2 updates (2 LTE) Cincinnati - 3 updates (3 LTE) Cleveland - 2 updates (2 3G) Colorado - 3 updates (3 LTE) East Michigan - 2 updates (2 LTE) GA/SC Coast - 7 updates (7 LTE) Hawaii - 4 updates (4 3G) Indianapolis - 4 updates (3 CDMA 800, 1 LTE) Inland Northwest - 1 update (1 LTE) Jacksonville - 11 updates (5 3G, 1 CDMA 800, 5 LTE) Kansas - 4 updates (4 CDMA 800) Las Vegas - 2 updates (2 LTE) Long Island - 1 update (1 LTE) Louisiana - 1 update (1 LTE) Memphis - 2 updates (2 3G) Miami / West Palm - 1 update (1 3G) Minnesota - 18 updates (17 CDMA 800, 1 LTE) Myrtle Beach - 1 update (1 LTE) Nashville - 3 updates (1 3G, 2 LTE) New York City - 7 updates (1 3G, 6 LTE) Norfolk - 7 updates (7 LTE) Northern Connecticut - 5 updates (1 3G, 4 LTE) Northern Jersey - 2 updates (2 3G) Oregon / SW Washington - 4 updates (4 LTE) Orlando - 8 updates (4 3G, 4 LTE) Philadelphia Metro - 1 update (1 LTE) Phoenix - 4 updates (4 LTE) Providence - 25 updates (25 CDMA 800) Raleigh / Durham - 5 updates (5 LTE) Richmond - 13 updates (10 3G, 3 LTE) Riverside / San Bernardino - 1 update (1 LTE) San Diego - 2 updates (2 LTE) South Bay - 1 update (1 LTE) South West Florida - 2 updates (1 3G, 1 LTE) Southern Connecticut - 3 updates (3 LTE) Southern Jersey - 1 update (1 LTE) Tampa - 3 updates (3 3G) Tucson / Yuma - 5 updates (1 3G, 4 LTE) Upper Central Valley - 1 update (1 LTE) Upstate NY East - 1 update (1 LTE) Washington DC - 12 updates (2 3G, 10 LTE) West Iowa / Nebraska - 1 update (1 3G) West Kentucky - 1 update (1 LTE) West Michigan - 1 update (1 LTE) West Texas - 1 update (1 LTE) Winston / Salem - 1 update (1 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Sprint uses all tower companies. Crown Castle, SBA, American Tower, pretty much all of them. Whoever owns a site where they need to be, that's who they use. Sprint doesn't own towers, and leases them from others. Robert

I'm still not in favor of the merger. Guess I'm an idiot. But after hearing about the duopoly conspiring together, it sure makes me just a little bit more for it. I'm almost neutral in may stance, now. Robert

Possibly. It can affect any Sprint customer. I don't know anything about your problem. Robert

It cannot connect to WiMax. However, it can connect to B41 LTE that is present on many WiMax towers in the Denver area. But it can only do that automatically if new 3G upgrades have been completed around them allowing CSFB to work properly. Robert

There is a new Las Cruces area acceptance. I will post more details in the Sponsor section. Robert

It certainly isn't normal. But I wouldn't rule it out as possible. Robert via Samsung Note 8.0 using Tapatalk Pro

Lone Tree Robert via Samsung Note 8.0 using Tapatalk Pro

It's got to be a lot better in the Phoenix area than when I was there last September! Robert via Samsung Note 8.0 using Tapatalk Pro

I heard recently from a source that Sprint decided to do the Spark logo on all LTE after the fact. Because of the limitations of Android right now, it could not support a separate icon for different bands of LTE without some key changes in the OS. He said none of them were major deals, but would have taken time to resolve with Google and each OEM. The way it was described to me is that now in the Android OS it currently pays no attention to Bands when determining LTE icons. It could care less. It determines LTE connectivity just by authenticating with an LTE network, and then calls for the LTE logo (as saved in the device) to be displayed. Whether it says LTE, 4G or some sort of custom icon. But it currently cares not about band, displaying the same LTE icon regardless of band. So Sprint had a choice of just letting B41 be called 4GLTE like the other bands, or they all can be Spark. As they all have to be displayed the same. Or possibly delay longer. But Sprint decided that it was better to get that Spark branding out there and has decided to let the LTE Logo to be changed on all Triband devices to include Spark. I still think this was a judgment error. But this is how it came to be. I guess I can understand why. But if limited to one, I would have just let B41 continue with the standard LTE logo in Triband devices. I asked about whether they would change it back in future Android releases when they can get additional LTE icons tied specifically to band. He said that probably cannot be done now, because that a ship has sailed. How do you dock it back in the port now? I guess it can't. Robert via Samsung Note 8.0 using Tapatalk Pro

Porky Pig Robert via Samsung Note 8.0 using Tapatalk Pro

I don't mind the new commercials. Robert via Samsung Note 8.0 using Tapatalk Pro

Site acceptance reports from Thursday (3/20) and Friday (3/21): Albuquerque - 2 updates (2 LTE) Arkansas - 5 updates (4 3G, 1 LTE) Boston - 2 updates (1 LTE, 1 new 3G site) Buffalo - 4 updates (4 LTE) Central Jersey - 1 update (1 LTE) Cincinnati - 4 updates (4 LTE) Cleveland - 26 updates (22 3G, 4 LTE) Colorado - 10 updates (9 3G, 1 LTE) Columbus - 3 updates (3 LTE) Delaware - 1 update (1 LTE) East Michigan - 6 updates (6 LTE) East Texas - 6 updates (6 LTE) GA/SC Coast - 3 updates (2 3G, 1 LTE) Georgia - 1 update (1 3G) Gulf Coast - 3 updates (3 3G) Hawaii - 4 updates (4 3G) Houston - 1 update (1 LTE) Inland Northwest - 1 update (1 LTE) Jacksonville - 2 updates (2 3G) Kansas - 3 updates (3 LTE) LA Metro - 2 updates (2 LTE) Las Vegas - 2 updates (1 3G, 1 LTE) Long Island - 2 updates (1 3G, 1 LTE) Lower Central Valley - 1 update (1 LTE) Memphis - 2 updates (2 3G) Miami / West Palm - 6 updates (6 3G) Milwaukee - 2 updates (2 LTE) Minnesota - 21 updates (21 3G) Missouri - 15 updates (12 3G, 3 LTE) Nashville - 1 update (1 3G) New York City - 5 updates (2 3G, 3 LTE) Norfolk - 1 update (1 3G) North LA - 2 updates (2 3G) Northern Jersey - 2 updates (2 3G) Oklahoma - 14 updates (14 3G) Orange County - 2 updates (2 LTE) Oregon / SW Washington - 17 updates (16 3G, 1 LTE) Orlando - 5 updates (5 3G) Philadelphia Metro - 4 updates (1 3G, 3 LTE) Phoenix - 13 updates (3 3G, 10 LTE) Pittsburgh - 4 updates (1 3G, 3 LTE) Raleigh / Durham - 1 update (1 3G) Richmond - 8 updates (7 3G, 1 LTE) Riverside / San Bernardino - 1 update (1 3G) SF Bay - 5 updates (5 LTE) San Diego - 4 updates (3 3G, 1 LTE) South Bay - 5 updates (5 LTE) South Carolina - 47 updates (47 CDMA 800) South Texas - 6 updates (5 3G, 1 LTE) Southern Jersey - 1 update (1 LTE) Tampa - 4 updates (3 3G, 1 LTE) Upper Central Valley - 3 updates (1 LTE, 1 new iDEN Conversion) Utah - 2 updates (2 LTE) VT / NH / ME - 1 update (1 LTE) Washington DC - 6 updates (1 3G, 3 LTE, 1 new 3G/LTE site) West Iowa / Nebraska - 1 update (1 3G) West Kentucky - 4 updates (2 3G, 2 LTE) West Michigan - 1 update (1 LTE) West Texas - 6 updates (6 3G) West Washington - 3 updates (3 LTE) Winston / Salem - 1 update (1 LTE) Maps were updated last night. Robert Links: Comments regarding this thread, NV Sites Complete Map

Fire Exit Robert via Samsung Note 8.0 using Tapatalk Pro

And I was at a hockey game last night with only 5,000 fans. And my AT&T data was unusable most of the night. There is no perfect provider when a sector gets overloaded. My texts to AJ would time out half the time and I would have to resend over and over again. Robert via Samsung Note 8.0 using Tapatalk Pro