S4GRU

Also, there's a good chance that there will be a way to disable CA on the device side. So if you start doing streaming activities and one carrier is more than plenty (which it almost always will be), then hopefully customers could turn off CA and experience some battery savings. Robert

Corporate customers is one of the big reasons. My company has no interest in upgrading my iPhone 4s. It meets the needs for what they give me a phone for. So until it breaks or the company decides my needs have changed, my work phone will not be LTE enabled. There are millions of people in the same position as me. Robert via Nexus 5 using Tapatalk

dstar2002 just was added on the list and shot way up the standings. It goes to how how there is not much separating the bottom half of the standings. As a result of dstar2002 joining the honored ranks, Denny was bumped off the bottom. Thanks for all your support! Robert

Not necessarily. I bet Sprint wastes a lot of money on things with little or no return. Sprint needs to be efficient, especially if it wants to lower prices and continue to move toward a consistent high quality network, nationwide. Robert via Samsung Note 8.0 using Tapatalk Pro

I believe in Washington State COW's now smoke digital grass. Robert via Samsung Note 8.0 using Tapatalk Pro

Metal Sonic Robert via Samsung Note 8.0 using Tapatalk Pro

No problem. Robert via Samsung Note 8.0 using Tapatalk Pro

Being discussed here: http://s4gru.com/index.php?/topic/6013-sprint-reportedly-bowing-out-of-t-mobile-bid-was-sprint-offer-and-iliad-threads/ Robert via Samsung Note 8.0 using Tapatalk Pro

I don't think I've seen numbers except VZW and Sprint. Robert via Samsung Note 8.0 using Tapatalk Pro

Battery drain is the biggest problem with CA. But it's not as bad as it used to be. Current CA devices idle on one carrier, and don't move to two or three carriers combined until data demand is high enough to warrant it. Only during large active data transfers does the per minute battery consumption go up. And since your data will arrive sooner, it can shut down the extra carrier activity much sooner, leaving very little difference in battery consumed. In most usage patterns, the difference will be negligible for most customers. If you were moving very large files for hours, or some types of streaming, it could reduce battery life in a more noticeable way. But most streaming types would not require CA to meet their maximum streaming speeds. But some network optimization may be needed to fine tune that. Also, if you think about it, when you look at how much battery items consume on your Android device at the end of its battery, cell radios don't take up the lion share of battery usage. For most of us it is screen and some intensive apps. Cell radios are typically in the bottom third. In a streaming a situation, the screen is what is going to be taxing your battery the worst. Even if cell radio battery consumption doubled in total for the discharge cycle, it wouldn't move up in the battery stat rankings very much. It may jump from 6% to 12% in the worst usage situations. I think most of us would notice a 2 to 3 point difference. Robert via Samsung Note 8.0 using Tapatalk Pro

Although I wasn't really for the merger, waffling between hell no and it wouldn't be the end of the world, your post was excellent. I'm disliking Chairman Wheeler more and more. His moves have mostly done more to ensure the Duopoly to reduce competition. Robert via Samsung Note 8.0 using Tapatalk Pro

This will not be a problem. Single carrier devices will not be effected, as they will run on each individual carrier installed that will be aggregated. It's the beauty of CA. To a non CA device, it just sees the individual carriers and can run on any of them. And with CA, the carriers do not even need to be contiguous. They can be anywhere in the band. And if they deploy inter band carrier aggregation, it can aggregate carriers from different bands. Robert via Samsung Note 8.0 using Tapatalk Pro

The two answers up top are correct. A separated, single carrier only piece will not need be isolated for Non CA devices. In 3x CA, you have three separate LTE carriers, that can be connected to with a single carrier device, a 2x CA device or a 3x CA device. The single carrier device can only use any one of the three carriers. The 2x CA device could run on two carriers at the same time. And the 3x CA device can run on all three LTE carriers at the same time. In LTE Advanced using Carrier Aggregation, the tower splits the data stream over more than one LTE carrier to get to your device, when your device is connected to more than one carrier at the site. It's like a truck that can deliver items to your house, can deliver two or three times as much in the same amount of time if two or three trucks came at the same time. That's what's happening with carrier aggregation. Two or three times the data can leave the site antenna to your device each second than without CA. This causes a speed boost of 2 to 3x on top of the single carrier's performance. Robert via Samsung Note 8.0 using Tapatalk Pro

And AT&T would not be doing this if it wasn't for Google Fiber. Robert via Samsung Note 8.0 using Tapatalk Pro

The last report I saw was 60% from Sprint also, if memory serves. But considering it's 60% and they don't have LTE over its entire footprint yet, that would make it higher than 60% in LTE coverage areas. Robert via Samsung Note 8.0 using Tapatalk Pro

It's probably not as high as you think. Robert via Samsung Note 8.0 using Tapatalk Pro

Not necessarily. There are contracted backhaul microwave vendors for Sprint in many places. And if there is a backhaul problem at the connection point, well, then, there is not going be any backhaul carried by microwave to begin with. Robert

Site acceptance report from Wednesday (7/30) through Monday (8/4): Austin - 1 update (1 CDMA 800) Baltimore - 4 updates (1 3G, 3 LTE) Boston - 15 updates (3 CDMA 800, 12 LTE) Buffalo - 1 update (1 LTE) Central Illinois - 1 update (1 LTE) Central Jersey - 2 updates (2 LTE) Central Pennsylvania - 1 update (1 LTE) Charlotte - 6 updates (3 CDMA 800, 3 LTE) Chicago - 1 update (1 3G) Cincinnati - 21 updates (9 3G, 8 CDMA 800, 4 LTE) Colorado - 23 updates (4 3G, 19 LTE) Columbus - 23 updates (9 3G, 9 CDMA 800, 5 LTE) Dakotas - 1 update (1 LTE) East Iowa - 1 update (1 LTE) East Kentucky - 2 updates (1 3G, 1 CDMA 800) East Michigan - 2 updates (1 LTE, 1 new iDEN Conversion) East Texas - 1 update (1 LTE) GA/SC Coast - 8 updates (7 CDMA 800, 1 LTE) Gulf Coast - 1 update (1 LTE) Houston - 2 updates (1 3G, 1 LTE) Indianapolis - 1 update (1 3G) Jacksonville - 11 updates (1 3G, 9 CDMA 800, 1 LTE) LA Metro - 8 updates (1 3G, 6 CDMA 800, 1 LTE) Las Vegas - 1 update (1 LTE) Long Island - 4 updates (1 3G, 3 LTE) Lower Central Valley - 1 update (1 LTE) Miami / West Palm - 15 updates (1 3G, 11 CDMA 800, 3 LTE) Milwaukee - 3 updates (1 CDMA 800, 2 LTE) Mississippi - 1 update (1 3G) Missouri - 6 updates (1 3G, 5 LTE) Myrtle Beach - 1 update (1 CDMA 800) Nashville - 18 updates (16 CDMA 800, 2 LTE) New Orleans - 2 updates (2 3G) New York City - 12 updates (1 3G, 11 LTE) North LA - 9 updates (1 3G, 8 CDMA 800) Northern Connecticut - 4 updates (2 CDMA 800, 2 LTE) Northern Jersey - 7 updates (7 LTE) Oklahoma - 20 updates (1 3G, 19 CDMA 800) Orange County - 4 updates (2 3G, 2 LTE) Orlando - 23 updates (3 3G, 18 CDMA 800, 2 LTE) Philadelphia Metro - 3 updates (1 3G, 2 LTE) Phoenix - 19 updates (14 CDMA 800, 5 LTE) Pittsburgh - 3 updates (1 CDMA 800, 1 LTE, 1 iDEN Conversion) Raleigh / Durham - 12 updates (5 CDMA 800, 7 LTE) Richmond - 2 updates (1 CDMA 800, 1 LTE) Riverside / San Bernardino - 4 updates (1 3G, 2 LTE, 1 iDEN Conversion) Rochester - 1 update (1 LTE) SF Bay - 118 updates (70 3G, 46 CDMA 800, 1 new 3G/800 site) San Diego - 4 updates (1 3G, 1 iDEN Conversion, 1 3G/LTE Pico Cell) Shentel - 1 update (1 CDMA 800) South Bay - 2 updates (2 LTE) South Texas - 1 update (1 CDMA 800) South West Florida - 4 updates (1 CDMA 800, 3 LTE) Southern Connecticut - 10 updates (4 CDMA 800, 6 LTE) Southern Jersey - 2 updates (2 LTE) Southern Virginia - 1 update (1 CDMA 800) Tampa - 5 updates (1 3G, 2 CDMA 800, 2 LTE) The Panhandle - 2 updates (2 LTE) Tucson / Yuma - 4 updates (4 LTE) Upper Central Valley - 28 updates (5 3G, 6 CDMA 800, 14 LTE, 1 new 3G/800/LTE COW) Upstate NY Central - 2 updates (2 LTE) Upstate NY East - 3 updates (1 3G, 1 CDMA 800, 1 LTE) Utah - 3 updates (3 LTE) VT / NH / ME - 7 updates (1 3G, 5 CDMA 800, 1 LTE) Washington DC - 3 updates (1 CDMA 800, 2 LTE) West Kentucky - 39 updates (36 CDMA 800, 3 LTE) West Texas - 3 updates (3 LTE) Winston / Salem - 1 update (1 CDMA 800) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Not all cable companies were good, and not all ILEC's were bad. I concede I was being very general. Robert

For the most part, cable companies did a very good job with backhaul and were typically the fastest backhaul providers schedule wise. Microwave and ILECs were typically the slowest at providing backhaul. Robert

It sure is looking that way. Robert

Marcelo sounds like he is a very busy person. Hope he will not be distracted. Being CEO of Sprint will be a full time plus position. They need all of his attention. Robert

by Robert Herron Sprint 4G Rollout Updates Tuesday, August 5, 2014 - 5:30 PM MDT The Wall Street Journal and Bloomberg are reporting this evening that Sprint will announce tomorrow morning that it will stop pursuing a purchase of T-Mobile USA. Furthermore, according to these leaks to financial media, it is also anticipated that Sprint CEO Dan Hesse will leave Sprint and his replacement will be named. The combination of the two companies was already cast as dubious by many because of the perceived reduction in competition in the American wireless landscape. CNBC stated that the final straw was the FCC decision last week not to allow Sprint and T-Mobile to jointly bid for spectrum in the 600MHz auction. It was seen that this move by the FCC was indicative of the Feds lack of tolerance of a combined entity. We will add to the rumors by wondering aloud if Nikesh Arora will be named the new Sprint CEO. Arora recently was announced to be leaving Google as Chief Business Officer for a new position at SoftBank. Could this have been a play to move him to Sprint all along? UPDATE: Later into the evening, more sources have outed Marcelo Claure as the heir apparent to Dan Hesse. Claure is best known as the majority owner of Brightstar and already serves on Sprint's Board. Stay tuned as more information is obtained! S4GRU Members are discussing this in our forums: http://s4gru.com/index.php?/topic/6013-sprint-reportedly-bowing-out-of-t-mobile-bid/?p=346787 EDIT: Added CNBC info at 5:55 PM MDT, Added Arora conjecture at 6:10 PM MDT. Added infor regarding Marcelo Claude at 8:15 PM PDT. Sources: Wall Street Journal, Bloomberg, CNBC

Looks like the end of the road: http://online.wsj.com/articles/sprint-abandoning-pursuit-of-t-mobile-1407279448 Masa, now it's time to take Sprint to the next level on your own! Robert Thanks Neal for the heads up!