S4GRU

Ahhh yes. BGR waited until it could compare Sprint to Tmo: http://bgr.com/2014/07/31/t-mobile-vs-sprint-prices/ It couldn't write a hit piece on just yesterday's news alone. Robert via Samsung Note 8.0 using Tapatalk Pro

Let the Frenchies have it! Robert via Samsung Note 8.0 using Tapatalk Pro

I have used 1x only for audio streaming in the past with good successes. The coverage and handoffs are perfect for most audio only streaming situations. In a few instances, I would come across a channel that was saturated. Voice takes priority over data on 1x. So if you get to a spot where voice is overloaded, you will have no data throughput at all. But since Sprint has added so much 800MHz CDMA, it likely will not be much of a problem now except at maybe during events, etc. Robert via Samsung Note 8.0 using Tapatalk Pro

The delay in Springfield is certainly backhaul related. All the sites have received their Network Vision upgrades and have LTE equipment installed. I thought though that the sites were CenturyLink around Springfield? Maybe Sprint switched to Comcast because of CL delays? Robert via Samsung Note 8.0 using Tapatalk Pro

Or so you thought. If it has been a year, then it didn't receive the backhaul upgrade you thought it did. Either the backhaul was for another provider, or you only saw them install the conduit for a future fiber pull, or they only did the work near the tower and the fiber connecting to the main line was held up for some reason (like permitting, easements, etc.). Sites that have NV upgrades already accepted and backhaul in place typically only sit around a few weeks waiting for OEM Integration teams to arrive and fire things up. The only caveat I would add is there have been instances where the integration team does show up and they can't integrate LTE because of an install error or backhaul problem. When that happens, the OEM reports the site and it sits in limbo until a Tiger team comes out and fixes the install problem or the backhaul provider fixes the issue. And sometimes that can take months depending on the issue. And once it's resolved, the integration team will come back out and integrate the site for LTE. If it's been over a year, than I am all but certain that backhaul was not actually live to Sprint back then. And only recently has gone live. Robert via Samsung Note 8.0 using Tapatalk Pro

And yet the network is markedly better ever quarter too. Robert via Samsung Note 8.0 using Tapatalk Pro

Yep. We have to wait for the people who fired up sites turn in their paperwork to corporate. So formal acceptances typically follow the day after integration teams are at the site. Robert

It's nice that you like them. But I fail to see how the counter opinion leads to the connection to socialism. Not that I even want to encourage further discussion on this. Robert

I don't blame you. I blame the melancholy ferret people. You can't trust those bastards!!! Robert

The more I think about the $180M number, I think it's bogus. It has to be way lower than that for a total network upgrade. Swiftel only has about 50 sites in their network. It is one of the smallest Sprint markets of all. That would be more than $3M per site! The typical Shentel NV site cost them about $250k all costs to upgrade to NV1.0. That is taking their total NV costs reported, divided by total number of sites. For supposition's sake, let's double Shentel's per site number from $250k to $500k for Swiftel. Even though that is double, they definitely should be able to do it for at least double the cost of Shentel. That would make a total upgrade cost for Swiftel around $25M. Definitely not chump change. But a way far cry less than the $180M that was mentioned to me. Granted, this is still a HUGE number for a city of 12,000 people to pay to upgrade right now. But it sure makes it seem possible. And the value of Swiftel is definitely something Sprint can quickly and easily absorb. Masa, make it so! Robert

I have to wonder if Chairman Wheeler is a Verizon customer on unlimited. Robert

Site acceptance report from Friday (7/25) through Tuesday (7/29): Alabama - 3 updates (2 3G, 1 LTE) Albuquerque - 5 updates (1 3G, 4 LTE) Atlanta / Athens - 1 update (1 3G) Austin - 2 updates (2 3G) Boston - 2 updates (2 LTE) Buffalo - 1 update (1 LTE) Central Illinois - 1 update (1 LTE) Central Iowa - 1 update (1 3G) Central Pennsylvania - 2 updates (1 3G, 1 LTE) Charlotte - 1 update (1 CDMA 800) Cincinnati - 10 updates (10 LTE) Cleveland - 2 updates (2 LTE) Colorado - 42 updates (42 LTE) Columbus - 3 updates (1 3G, 2 LTE) DFW - 1 update (1 LTE) Dakotas - 4 updates (1 CDMA 800, 3 LTE) East Iowa - 1 update (1 LTE) East Kentucky - 11 updates (11 CDMA 800) East Michigan - 4 updates (4 LTE) East Texas - 4 updates (4 CDMA 800) Ft. Wayne / South Bend - 1 update (1 LTE) GA/SC Coast - 1 update (1 LTE) Gulf Coast - 1 update (1 3G) Houston - 2 updates (1 3G, 1 LTE) Jacksonville - 5 updates (4 CDMA 800, 1 LTE) LA Metro - 5 updates (1 3G, 4 LTE) Long Island - 1 update (1 3G) Memphis - 3 updates (2 LTE, 1 new 3G site) Miami / West Palm - 3 updates (1 3G, 2 LTE) Milwaukee - 3 updates (3 LTE) Minnesota - 3 updates (1 CDMA 800, 2 LTE) Nashville - 77 updates (76 CDMA 800, 1 LTE) New York City - 3 updates (3 LTE) Norfolk - 1 update (1 LTE) North LA - 1 update (1 3G) North Wisconsin - 2 updates (2 LTE) Oklahoma - 16 updates (1 3G, 13 CDMA 800, 1 LTE, 1 new 3G site) Orange County - 2 updates (1 3G, 1 LTE) Orlando - 6 updates (4 3G, 2 LTE) Philadelphia Metro - 1 update (1 LTE) Phoenix - 1 update (1 LTE) Pittsburgh - 1 update (1 CDMA 800) Providence - 1 update (1 LTE) Raleigh / Durham - 5 updates (5 CDMA 800) Richmond - 2 updates (2 LTE) Riverside / San Bernardino - 3 updates (3 LTE) Rochester - 1 update (1 LTE) SF Bay - 1 update (1 LTE) San Diego - 2 updates (2 3G) Shentel - 2 updates (1 CDMA 800, 1 LTE) South Bay - 1 update (1 3G) South West Florida - 3 updates (1 3G, 2 LTE) Southern Jersey - 1 update (1 LTE) Tampa - 1 update (1 LTE) Upper Central Valley - 47 updates (39 3G, 4 CDMA 800, 4 LTE) Upstate NY East - 1 update (1 LTE) Utah - 1 update (1 LTE) Washington DC - 5 updates (1 3G, 4 LTE) West Iowa / Nebraska - 4 updates (2 CDMA 800, 2 LTE) West Kentucky - 7 updates (1 3G, 3 CDMA 800, 3 LTE) West Iowa / Nebraska - 1 update (1 CDMA 800) West Michigan - 1 update (1 LTE) West Texas - 1 update (1 LTE) West Washington - 3 updates (3 LTE) Winston / Salem - 1 update (1 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Yes. I was using a Nexus 5 with an AT&T SIM card in it in this instance. However, if AT&T and Sprint had an LTE roaming agreement, it would have been possible for me to roam on that AT&T Band 5 site with my Nexus 5 using Sprint service. US Cellular is much more likely to allow LTE roaming for Sprint than AT&T, though. Robert

It typically happens between 2 weeks and 6 months after LTE 800 is fired up on NV complete sites with backhaul in a given area. Robert

Agreed. Robert

Agreed. Far from out the woods. But some good signs are appearing. It's the first steps to the ship being righted. And if they fall down on the job the next few months, it could get worse. However, things are likely to get better and better. They are starting to gain some momentum. Robert

CNET article does a fair job of summing it up: http://www.cnet.com/news/sprint-stems-customer-bleeding-in-return-to-q1-profit/ Robert via Samsung Note 8.0 using Tapatalk Pro

Nope. You'll likely see GMO's converted in East Iowa before Western PA market. Robert via Samsung Note 8.0 using Tapatalk Pro

I couldn't live with 2.5GB of data, let alone 1GB. Robert via Samsung Note 8.0 using Tapatalk Pro

I haven't heard of any promises about Sprint LTE in State College. In fact, I believe I have been saying for years that State College will be one of the last places to get Sprint LTE. I wouldn't expect it this year at all. Robert via Samsung Note 8.0 using Tapatalk Pro

http://s4gru.com/index.php?/topic/3767-adding-images-to-posts-imgur-links/ Robert via Samsung Note 8.0 using Tapatalk Pro

I considered that. However, the discussion was about how AT&T stopped deployment. And we're talking about the things we have seen that show they are still deploying by our observations. Robert via Samsung Note 8.0 using Tapatalk Pro

And you were so close. Missed it by 48 hours! Robert via Samsung Note 8.0 using Tapatalk Pro

Thanks for donating and supporting S4GRU. Robert via Samsung Note 8.0 using Tapatalk Pro

No more ad nauseum complaints saying the same thing over and over again. Any further Sprint complaints from you morningside78 will be treated as a violation of the rules. You won't consider any explanation or evidence. You are just stuck on 'Sprint sucks.' You're entitled to your opinion. But we don't have to hear it here. Especially since it violates the rules. http://s4gru.com/index.php?/topic/1197-s4gru-posting-guidelines-aka-the-rulez/ You seem like you will not be happy with Sprint. You should lower your blood pressure and get another provider. Robert via Samsung Note 8.0 using Tapatalk Pro