S4GRU

Quiz Day

There is no imminent CDMA equipment shortage. Not on the device side nor network side. The costs for CDMA equipment will not be cost prohibitive for years. What it takes to include CDMA 1xRTT or 1xAdvanced in new cell phones is minimal. Even if for 5 Million customers, let alone 50 Million. Sprint/SoftBank may chose to make steps in other directions like VoLTE, and possibly even WCDMA (which I doubt), but it is not because there is an imminent CDMA cliff coming in 2-3 years. They will have no problem supporting CDMA until at least 2020. Additionally, Verizon has not said to my knowledge they are abandoning CDMA in their networks nor in their devices. They only said they were going trial some LTE only phones in 2014 to see how they worked out. So even if they did just love LTE only, given the extent of existing devices and contracts, Verizon would still need to keep their CDMA network going for another 3-4 years minimum. And they would likely keep CDMA still being installed on devices to allow roaming for some time further. Also, Sprint will likely develop in the VoLTE ecosystem about the same timelines as everyone else. This is much ado about nothing, and is getting WAY off topic. Robert

It's actually logging which 1x site you were connected to while on LTE in that log. Robert from Note 2 using Tapatalk 4 Beta

I'm sitting here impatiently waiting for the FedEx guy to show up with my new Nexus 7 tablet and my replacement Note 2. Robert from Note 2 using Tapatalk 4 Beta

As a person from Northern California/Northern Nevada, I must dispute the combining of Auburn and Roseville. They are 20 miles apart and separated by hills. Roseville is an upper middle class suburb of Sacto and Auburn is a distinctively separate Sierra Nevada foothills community. There is no link to these communities other than they are both in Placer County and I-80 runs through them. On a side note, Downtown Auburn is one of the nifitiest places to visit in Northern California. Auburn was also once the capital of California, I believe. Robert from Note 2 using Tapatalk 4 Beta

Hmm. How far apart were these taken? 10 minutes or so? I'm wondering if these are two different sites based on the wild variation in signal strength. WiMax is measured in RSSI and LTE in RSRP. Sprint uses 14dBm subtracted from RSSI to come up with an RSRP equivalent in their LTE 1900 testing. If the same is applied, the WiMax RSRP would be approximately -75dBm. So that appears to be a big spread, making me think of different sites. Gotta like that ping though! Robert from Note 2 using Tapatalk 4 Beta

Site acceptance reports from Wednesday (7/24) and Thursday (7/25): Alabama – 3 updates (2 LTE) Albuquerque - 4 updates (3G) Arkansas - 2 updates (1 LTE) Atlanta/Athens - 3 updates (1 LTE) Austin - 2 updates (1 LTE) Boston - 5 updates (2 LTE) Central Iowa - 1 update (LTE) Central Jersey - 2 updates (LTE) Central Pennsylvania - 1 update (LTE) Chicago - 2 updates (3G) Cleveland - 10 updates (3G) Colorado - 1 update (3G) DFW - 4 updates (2 LTE) East Michigan - 4 updates (LTE) East Texas - 1 update (3G) Ft. Wayne/South Bend - 1 update (LTE) GA/SC Coast - 2 updates (3G) Georgia - 2 updates (3G) Gulf Coast - 1 update (3G) Houston - 3 updates (3G) Jacksonville - 5 updates (3 LTE) Kansas - 16 updates (2 LTE) LA Metro - 4 updates (3G) Las Vegas - 2 updates (3G) Louisiana - 3 updates (2 LTE) Memphis - 4 updates (3 LTE) Miami/West Palm - 9 updates (3 LTE) Milwaukee - 3 updates (2 LTE) Minnesota - 12 updates (4 LTE) Mississippi - 2 updates (LTE) Missouri - 3 updates (3G) Myrtle Beach - 1 update (3G) Nashville - 13 updates (4 LTE) New Orleans - 2 updates (LTE) New York City - 3 updates (3G) Norfolk - 2 updates (LTE) Northern Jersey - 3 updates (3G) North Wisconsin - 2 updates (LTE) Oklahoma - 2 updates (1 LTE) Orange County - 4 updates (3G) Oregon/SW Washington - 7 updates (2 LTE) Orlando - 7 updates (3 LTE) Philadelphia Metro - 7 updates (3G) Phoenix - 2 updates (3G) Pittsburgh - 8 updates (3G) Providence - 1 update (3G) Raleigh/Durham - 3 updates (LTE) Richmond - 1 update (LTE) Riverside/San Bernardino - 5 updates (3G) Rochester - 4 updates (3G) San Diego - 2 updates (1 LTE) SF Bay - 2 updates (LTE) South Bay - 4 updates (3G) South Carolina - 3 updates (3G) Southern Connecticut - 1 update (3G) Southern Jersey - 2 update (1 new 3G site) South Texas - 2 updates (LTE) South West Florida - 2 updates (LTE) Tampa - 3 updates (2 LTE) Tucson/Yuma - 1 update (3G) Upstate NY Central - 3 updates (3G) VT/NH/ME - 1 update (3G) Washington DC - 2 updates (3G) West Iowa/Nebraska - 1 update (LTE) West Michigan - 29 updates (5 LTE) West Texas - 5 updates (LTE) West Washington - 7 updates (3G) Winston/Salem - 1 update (LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Yes, they will continue to advertise WiMax service, but not through retail stores. Only through their website. You might as well make money on it, and use all those devices you've purchased. But it was already slowly being phased out by Clearwire. It will likely be even accelerated under Sprint. Robert

Just got the email from Amazon that my new 16GB Nexus 7 FHD has left the facility and on its way via FedEx with a delivery by 1:30 PM tomorrow. Also my replacement Note 2 is also supposed to be coming via FedEx tomorrow. Oh, happy day! Robert

Actually, Clearwire has been quietly shutting down retail stores and been getting away from a home business model. I don't expect Sprint to sell TD-LTE as a home ISP at all. I think they'll let home WiMax users stay until the network ends in 2015. But they probably will stop seeking new WiMax ISP users. Robert from Note 2 using Tapatalk 4 Beta

Get your MSL code for your hotspot and put it into Band 41 only mode. In my experience in Denver, TD-LTE 2600 was going considerably farther than WiMax from the same site. I sometimes would get usable TD-LTE with a -120 to -130dBm RSRP signal. In the 2-5Mbps range. Robert from Note 2 using Tapatalk 4 Beta

They could do as you suggest, or, push for a very fast overlay of TD-LTE on WiMax sites. It would be a similar type of deployment as Tmo LTE overlay on its HSPA+ network. If vendors can produce the equipment fast enough and the workers can be secured for it, it seems plausible to me that Sprint could get TD-LTE deployed on all Clearwire legacy sites in 4-5 months. It's only 10,000 more sites approximately to go. I think I would do it. Every Sprint site that has not been converted and is colocated with Clearwire, I would priortize these to be converted immediately and connect to Clearwire backhaul temporarily until new fiber backhaul arrives. Simultaneously, I would start a mega ambitious project of adding TD-LTE to every Clearwire WiMax site, including Protection Sites. This would usher in a new LTE quickly and allow Sprint to dump all the Huawei equipment out there. Also, simultaneously I would begin planning for Network Vision/Clearwire integration. Plan for all Clearwire sites that are presently colocated with Sprint to be moved over to the Sprint side on New NV base stations and racks. Allow Clearwire colocated sites to be decommissioned, saving lots of money. Then the Clearwire sites that are not colocated with Sprint should be converted to Network Vision or decommissioned if redundant in coverage. These Clearwire sites that are not colocated with Sprint should have the other LTE bands and CDMA installed too where it makes sense. Robert from Note 2 using Tapatalk 4 Beta

I expect that one of the things SoftBank is going to push with its new funding in Sprint is that the WiMax network gets overlaid with TD-LTE quickly. I used TD-LTE 2600 in Denver this week. So it is likely coming to the Wasatch Front too. It's just a matter of when. Robert from Note 2 using Tapatalk 4 Beta

Yes, this is possible at those sites where Sprint and Clearwire are colocated. However, Clearwire legacy backhaul isn't exactly high capacity. I think Clearwire has sites with as little as 10-20Mbps service. And sometimes even less at some Protection Sites. So it might be OK as a temporary stop gap to share Clearwire backhaul at colocated sites, upgraded backhaul would still be needed. As the Sprint LTE may drop to way below acceptable levels. Robert from Note 2 using Tapatalk 4 Beta

It has nothing to do with how much Sprint coverage there is. It most likely has to do with Sprint's LTE band. Robert from Note 2 using Tapatalk 4 Beta

LTE 2600 is on the Clearwire network and is set up on all the existing WiMax sites in the Denver Metro. Eventually Sprint will also start deploying LTE 2600 on Network Vision sites. But currently it is only occurring on existing Clearwire sites. Robert from Note 2 using Tapatalk 4 Beta

Requires MSL code. Guess I'll have to call Sprint and get that. Robert from Note 2 using Tapatalk 4 Beta

Yes, I did. I got solid TD-LTE 2600 signals all over Stapleton. In the Walmart parking lot I hit over 40Mbps on my new triband LTE hotspot. You can only get it on a new triband hotspot, though. The iPhone 5 is single band. LTE 1900 hasn't made it into Stapleton yet. Triband LTE smartphones should go on sale in a few months. Robert from Note 2 using Tapatalk 4 Beta

Hmm, I haven't discovered that ability yet. Where is that located? Robert from Note 2 using Tapatalk 4 Beta

Site acceptance reports from Sunday (7/21), Monday (7/22) and Tuesday (7/23): Alabama – 4 updates (3G) Albuquerque - 1 update (3G) Arkansas – 3 updates (2 LTE) Atlanta/Athens – 19 updates (17 LTE) Boston - 2 updates (LTE) Central Pennsylvania – 2 updates (3G) Charlotte – 2 updates (LTE) Chicago – 1 update (LTE) Cincinnati – 2 updates (LTE) Colorado – 1 update (3G) Columbus – 1 update (LTE) DFW – 1 update (3G) East Kentucky – 1 update (LTE) East Michigan – 20 updates (2 LTE) East Texas – 1 update (3G) GA/SC Coast – 2 updates (3G) Georgia – 4 updates (3G) Houston – 4 updates (3G) Jacksonville – 8 updates (2 LTE) Kansas – 7 updates (1 LTE) LA Metro – 4 updates (1 LTE) Las Vegas – 2 updates (LTE) Louisiana – 2 updates (LTE) Lower Central Valley – 7 updates (3G) Memphis – 8 updates (5 LTE) Miami/West Palm – 7 updates (3 LTE) Milwaukee – 21 updates (3 LTE) Minnesota – 11 updates (2 LTE) Mississippi – 1 update (3G) Missouri – 4 updates (3 LTE) Nashville – 7 updates (3 LTE) New Orleans – 4 updates (LTE) New York City – 6 updates (2 LTE) Norfolk – 1 update (LTE) Northern Connecticut – 2 updates (3G) Northern Jersey – 6 updates (2 LTE) Orange County – 3 updates (1 LTE) Oregon/SW Washington – 6 updates (3G) Orlando – 7 updates (LTE) Philadelphia Metro – 8 updates (7 LTE) Pittsburgh – 6 updates (3 LTE) Providence – 1 update (3G) Raleigh/Durham – 11 updates (LTE) Riverside/San Bernardino – 3 updates (1 LTE) San Antonio – 3 updates (1 LTE) San Diego – 2 updates (1 LTE) SF Bay – 14 updates (7 LTE) South Carolina – 12 updates (3G) Southern Connecticut – 3 updates (LTE) South Texas – 3 updates (1 LTE) South West Florida – 1 update (3G) Tampa – 16 updates (7 LTE) Upstate NY Central – 1 update (3G) Washington DC – 1 update (3G) West Kentucky – 1 update (LTE) West Michigan – 10 updates (LTE) West Washington – 4 updates (3G) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Yes, we had heard that SVLTE may not be capable on the new tribands. However, it was not a rumor we could corroborate. I guess now it is. Robert from my Nexus 4 using Tapatalk 4 Beta

No issues. Robert from Note 2 using Tapatalk 4 Beta

It was around -80dBm RSRP. Robert from Note 2 using Tapatalk 4 Beta

It was running N. I thought N maxed out at 300Mbps? Robert from Note 2 using Tapatalk 4 Beta

No one with a Galaxy Nexus should use Sensorly. The GN pollutes data to Sensorly. It often locks up the signal strength and it will show dark purple all over the place. Even in areas with little to no signal. GN users should not map on Sensorly. Let the rest of us do it so the results will be accurate. Robert from Note 2 using Tapatalk 4 Beta