S4GRU

First Band 26 sites accepted in the Central Illinois market. Details in the Premier Sponsor B26/LTE 800 thread. Robert via Samsung Note 8.0 using Tapatalk Pro

First Band 26 sites accepted in the Georgia market. Details in the Premier Sponsor B26/LTE 800 thread. Robert via Samsung Note 8.0 using Tapatalk Pro

First Band 26 sites accepted in the Idaho market. Details in the Premier Sponsor B26/LTE 800 thread. Robert via Samsung Note 8.0 using Tapatalk Pro

First Band 26 sites accepted in the Milwaukee market. Details in the Premier Sponsor B26/LTE 800 thread. Robert via Samsung Note 8.0 using Tapatalk Pro

Site acceptance reports from Monday (3/10) and Tuesday (3/11): Arkansas - 3 updates (2 3G, 1 LTE) Atlanta / Athens - 145 updates (3 3G, 142 CDMA 800) Austin - 1 update (1 LTE) Baltimore - 1 update (1 3G) Buffalo - 3 updates (3 LTE) Central Illinois - 4 updates (2 3G, 1 CDMA 800, 1 LTE) Central Iowa - 1 update (1 LTE) Chicago - 13 updates (3 3G, 5 CDMA 800, 5 LTE) Cincinnati - 4 updates (3 3G, 1 LTE) Cleveland - 5 updates (5 LTE) Colorado - 1 update (1 LTE) Columbus - 2 updates (2 LTE) DFW - 1 update (1 LTE) East Iowa - 6 updates (1 3G, 1 CDMA 800, 4 LTE) East Kentucky - 1 update (1 3G) Georgia - 44 updates (2 3G, 39 CDMA 800, 3 LTE) Gulf Coast - 1 update (1 3G) Houston - 4 updates (2 3G, 1 CDMA 800, 1 LTE) Idaho - 25 updates (2 3G, 21 CDMA 800, 2 LTE) Jacksonville - 1 update (1 3G) Kansas - 437 updates (1 3G, 436 CDMA 800) Long Island - 1 update (1 3G) Lower Central Valley - 1 update (1 3G) Memphis - 1 update (1 LTE) Miami / West Palm - 2 updates (2 3G) Milwaukee - 208 updates (4 3G, 201 CDMA 800, 3 LTE) Minnesota - 1 update (1 3G) Missouri - 5 updates (4 3G, 1 LTE) Nashville - 125 updates (124 3G, 1 LTE) New York City - 1 update (1 LTE) Norfolk - 8 updates (8 3G) Northern Jersey - 1 update (1 3G) Oklahoma - 11 updates (11 3G) Orange County - 1 update (1 3G) Orlando - 6 updates (6 3G) Philadelphia Metro - 17 updates (17 CDMA 800) Phoenix - 1 update (1 3G) Pittsburgh - 1 update (1 CDMA 800) San Diego - 1 update (1 3G) South Texas - 2 updates (1 3G, 1 LTE) South West Florida - 3 updates (3 3G) Southern Connecticut - 2 updates (2 3G) Tampa - 1 update (1 3G) Toledo - 1 update (1 LTE) Upper Central Valley - 2 updates (2 CDMA 800) Utah - 1 update (1 3G) VT / NH / ME - 1 update (1 3G) West Iowa / Nebraska - 5 updates (2 3G, 3 LTE) West Kentucky - 7 updates (7 3G) West Texas - 2 updates (2 3G) West Washington - 6 updates (6 LTE) West Kentucky - 1 update (1 3G) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

I have heard the same thing. A couple of points though: WiMax Protection Sites are already counted in those 55,000. Adding 1,000 unique iDEN sites would not really substantially alter their projections of 55,000 sites. Also, once done reducing the 40% of Clearwire redundant sites, that would provide room to add about 6,000 new organic macro sites without having to go beyond the 55k sites. So there is a way to grow the network footprint and still hold true to the 55k number. I don't think that's what they're planning, but hey, I can see a roadmap of how to do it and not exceed 55,000 sites. If it is as I suspect and Masa is holding out network coverage expansion as a possible negotiating nugget in future battle with the feds, then I don't think they would discuss numbers beyond 55,000 now. Even if they planned to add 10,000 new organic sites. They would be strictly forbidden to discuss that. I don't really think Sprint will try to match AT&T's footprint. However, it is doable. And it won't even bankrupt the company. I do believe that Sprint should do it. And they might, especially as a negotiating tactic. So I'm not willing to rule it out. And they should at a minimum convert the WiMax Protection Sites. Robert

This is what I'm thinking as well. Robert

I am an AT&T and Verizon customer. All throughout the West, Verizon has far better coverage than AT&T. I believe Sprint can organically at least come darn close to matching AT&T's coverage for probably just $4-$5 Billion. Converting all the unique iDEN and WiMax Protection Sites to full NV with CDMA 1900/800 and LTE 1900/800 would be a good start. If Sprint could claim coverage to the extent that AT&T does and get NV2.0 complete, it could compete with the duopoly on that alone. People stay with the duopoly because of coverage. Otherwise, all the providers are really just fighting over those price sensitive subs who will jump ship only because of a cost/benefit analysis. I meet lots of Verizon customers who hate their prices. And they would love unlimited back. But they will continue to pay for Verizon until Sprint offers a consistently good data experience and a coverage footprint that meets their needs. Even when visiting their parents on the farm or while camping in the foothills. Robert EDIT: A quick number crunching and just converting 1,000 unique iDEN and 700 WiMax Protection sites to CDMA/LTE would be approximately $200M. That's chump change in the grand scheme of Network Vision. They need to just do that now. That would start making some headway right away and would resolve most of their G block building requirements.

It should be. But I have heard reports that CSFB still seems to be a problem in North San Jose, Milpitas and Mountain View. Hopefully it has been corrected now. Robert via Samsung Note 8.0 using Tapatalk Pro

There is a hidden menu in most phones called an LTE Engineering screen that provides specific info about your LTE connection. Like signal strength, signal quality, channel, cell ID (sector), etc. It is a must for any wireless nerd to help see and understand what is occurring, Robert via Samsung Note 8.0 using Tapatalk Pro

You know when you're roaming on AT&T, because your head snaps back with sudden whiplash when you go from 8Mbps Faux G to sudden EDGE speeds. You don't need a triangle or R next to the signal strength indicator to know. You'll know. I have repetitive stress injury from it. Whock-chaw! Robert via Samsung Note 8.0 using Tapatalk Pro

We need the Engineering screens the next time that happens, please. Then we will know if you found something and if we should be excited. Thanks! Robert via Samsung Note 8.0 using Tapatalk Pro

In Manhattan where they have so many sites without B25, just completing more sites will likely be sufficient for awhile. In the parts of Brooklyn and the Bronx where full site density is already there, it will take a second B25 carrier. But ideally, we should be on B41 and only use B25 for backup. Robert via Samsung Note 8.0 using Tapatalk Pro

I don't agree with anyone. Robert via Nexus 5 using Tapatalk

I don't disagree with you. However, I wonder if you'd say the same thing about Sprint if they just raised rates on unlimited only. And whether you or I think so or not, I can guarantee you that it would be seen by the public as Sprint is raising prices. Even if limited to one group. Robert via Nexus 5 using Tapatalk

I was in the shadow of the tower. If it fell just right, it would have hit my house square. Sprint was mounted at 100' AGL. Had a great PCS signal. Usually between -65 RSSI and -80 RSSI, depending on where in my house I was and what device I was using. Jug Jug, it was fantastic! Robert

The chokepoint in this case is not the fiber backhaul on new LTE sites, but rather the 5MHz air link. With too few sites complete and too many users per 5MHz channel, the only relief will be to bring on more LTE sites and spread out the load over many more channels. Backhaul should never be a problem again at upgraded sites. Just air link capacity when over saturated. Also, now that permitting is starting all over the country, you may start seeing some B41 permitting start in the Tucson area soon. I have a feeling you'll be the first to spot them. Robert via Samsung Note 8.0 using Tapatalk Pro

I miss the days when I had a Sprint site in my yard. Robert via Samsung Note 8.0 using Tapatalk Pro

Yeah, Samsung eCSFB is not a common thing in the South Bay. Robert via Samsung Note 8.0 using Tapatalk Pro

The HTC M8 is a Sprint Triabnd LTE device, and it will work on all three Sprint LTE bands. Sprint does not yet have an LTE Advanced device that supports Carrier Aggregation, and neither the HTC M8 nor the Samsung GS5 support CA on Sprint. Sprint will not likely have a LTE Advanced/Carrier Aggregation device on the market until toward the end of 2014. The first round of Band 41/Sprint Spark is just a natural 20MHz TDD-LTE carrier without LTE Advanced or Carrier Aggregation, supporting up to approximately 75Mbps. In 2015 and 2016, Sprint will deploy LTE Advanced and will aggregate two and three Band 41 LTE carriers and possibly more MIMO antennas that will push throughput speeds even higher. Robert

Site acceptance reports from Thursday (3/6), Friday (3/7), Saturday (3/8) and Sunday (3/9): Arkansas - 2 updates (2 3G) Atlanta / Athens - 2 updates (1 3G, 1 LTE) Austin - 2 updates (2 3G) Boston - 3 updates (3 LTE) Buffalo - 7 updates (7 LTE) Central Jersey - 3 updates (3 LTE) Central Pennsylvania - 3 updates (3 LTE) Charlotte - 1 update (1 LTE) Chicago - 1 update (1 LTE) Cincinnati - 2 updates (2 LTE) Cleveland - 19 updates (5 3G, 14 LTE) Columbus - 5 updates (3 3G, 2 LTE) DFW - 4 updates (1 3G, 1 LTE, 1 new 3G/LTE site) Delaware - 1 update (1 LTE) East Michigan - 6 updates (6 LTE) GA/SC Coast - 3 updates (3 LTE) Georgia - 2 updates (2 3G) Gulf Coast - 1 update (1 3G) Inland Northwest - 2 updates (2 LTE) Jacksonville - 8 updates (8 LTE) Kansas - 8 updates (5 3G, 3 LTE) LA Metro - 4 updates (2 3G, 2 LTE) Las Vegas - 3 updates (1 3G, 2 LTE) Long Island - 9 updates (1 3G, 8 LTE) Lower Central Valley - 2 updates (2 LTE) Memphis - 1 update (1 3G) Miami / West Palm - 4 updates (4 3G) Minnesota - 10 updates (5 3G, 5 LTE) Missouri - 17 updates (5 3G, 12 LTE) Nashville - 5 updates (5 LTE) New York City - 11 updates (5 3G, 6 LTE) Norfolk - 28 updates (28 3G) North LA - 3 updates (1 3G, 2 LTE) North Wisconsin - 1 update (1 LTE) Northern Connecticut - 2 updates (1 3G, 1 LTE) Northern Jersey - 9 updates (9 LTE) Oklahoma - 9 updates (6 3G, 3 LTE) Orange County - 5 updates (1 3G, 4 LTE) Oregon / SW Washington - 2 updates (2 LTE) Orlando - 2 updates (2 3G) Philadelphia Metro - 4 updates (1 3G, 3 LTE) Phoenix - 4 updates (1 3G, 3 LTE) Pittsburgh - 9 updates (1 3G, 8 LTE) Raleigh / Durham - 2 updates (2 LTE) Riverside / San Bernardino - 2 updates (2 LTE) Rochester - 3 updates (3 LTE) SF Bay - 5 updates (5 LTE) San Diego - 3 updates (3 LTE) South Bay - 2 updates (2 LTE) South Texas - 4 updates (3 3G, 1 LTE) Southern Connecticut - 4 updates (1 3G, 3 LTE) Southern Jersey - 2 updates (2 LTE) Tampa - 3 updates (2 3G, 1 iDEN Conversion) The Panhandle - 8 updates (2 3G, 6 LTE) Toledo - 2 updates (2 3G) Tucson / Yuma - 1 update (1 LTE) Upper Central Valley - 9 updates (9 LTE) Upstate NY East - 2 updates (2 LTE) Utah - 6 updates (6 LTE) Washington DC - 1 update (1 3G) Tucson / Yuma - 1 update (1 LTE) West Kentucky - 2 updates (2 3G) West Michigan - 1 update (1 LTE) West Texas - 2 updates (2 3G) West Washington - 9 updates (8 LTE, 1 iDEN Conversion) Winston / Salem - 2 updates (2 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Site acceptance reports from Monday (3/3), Tuesday (3/4) and Wednesday (3/5): Alabama - 3 updates (1 3G, 2 LTE) Arkansas - 2 updates (1 3G, 1 LTE) Atlanta / Athens - 134 updates (12 3G, 121 CDMA 800, 1 LTE) Boston - 7 updates (2 3G, 5 LTE) Central Jersey - 4 updates (4 LTE) Central Pennsylvania - 41 updates (6 3G, 35 CDMA 800) Charlotte - 2 updates (1 3G, 1 LTE) Chicago - 1 update (1 LTE) Cincinnati - 4 updates (4 LTE) Cleveland - 7 updates (7 LTE) Colorado - 4 updates (1 CDMA 800, 3 LTE) DFW - 1 update (1 LTE) East Iowa - 1 update (1 LTE) East Kentucky - 2 updates (2 3G) East Michigan - 3 updates (3 LTE) East Texas - 103 updates (4 3G, 95 CDMA 800, 4 LTE) Ft. Wayne / South Bend - 1 update (1 LTE) Gulf Coast - 2 updates (2 3G) Idaho - 1 update (1 LTE) Jacksonville - 3 updates (1 3G, 2 LTE) LA Metro - 1 update (1 3G) Las Vegas - 45 updates (3 3G, 41 CDMA 800, 1 LTE) Long Island - 4 updates (4 LTE) Lower Central Valley - 2 updates (2 LTE) Memphis - 2 updates (2 3G) Miami / West Palm - 7 updates (7 3G) Missouri - 7 updates (6 3G, 1 LTE) Myrtle Beach - 2 updates (2 LTE) Nashville - 1 update (1 LTE) New Orleans - 1 update (1 3G) New York City - 5 updates (3 3G, 2 LTE) Northern Connecticut - 68 updates (67 CDMA 800, 1 LTE) Northern Jersey - 5 updates (1 3G, 4 LTE) Oklahoma - 4 updates (4 3G) Oregon / SW Washington - 1 update (1 LTE) Orlando - 6 updates (5 3G, 1 LTE) Philadelphia Metro - 3 updates (1 3G, 2 LTE) Phoenix - 88 updates (4 3G, 84 CDMA 800) Pittsburgh - 146 updates (5 3G, 139 CDMA 800, 2 LTE) Raleigh / Durham - 3 updates (2 3G, 1 LTE) Riverside / San Bernardino - 2 updates (2 LTE) San Antonio - 43 updates (43 CDMA 800) San Diego - 2 updates (1 3G, 1 LTE) South Bay - 2 updates (1 3G, 1 LTE) South Carolina - 70 updates (2 3G, 65 CDMA 800, 3 LTE) South Texas - 1 update (1 3G) Southern Jersey - 1 update (1 LTE) Tampa - 64 updates (16 3G, 48 CDMA 800) The Panhandle - 3 updates (2 3G, 1 LTE) Toledo - 1 update (1 LTE) Washington DC - 1 update (1 LTE) West Iowa / Nebraska - 1 update (1 3G) West Texas - 3 updates (3 3G) West Washington - 10 updates (5 3G, 5 LTE) Maps were updated last Thursday with this info, I'm just now getting around to posting the summary. Sorry for the delay. Robert Links: Comments regarding this thread, NV Sites Complete Map

That is definitely Dakota Snow. Robert

Yep. That's all you're getting. You can expect that everywhere. Or, it could still be in deployment. Which it is. It will get better. But if you don't want to wait you should get another provider. But please do not complain about it here. Doing so violates the rules. Robert

Yes. That's how we understand it. NSN is doing B41 LTE upgrades at NV sites in the Ericsson region. Robert