S4GRU

Small population, two bands on one site, one of them is low frequency. Should be a wonderful experience. And way better than Tmo out there, no doubt. Robert via Nexus 5 using Tapatalk

favorite position

Site acceptance report from Tuesday (6/24) through Monday (6/30): Alabama - 2 updates (1 LTE, 1 iDEN Conversion) Albuquerque - 20 updates (18 3G, 2 LTE) Arkansas - 4 updates (3 3G, 1 LTE) Atlanta / Athens - 3 updates (3 3G) Austin - 8 updates (7 3G, 1 LTE) Baltimore - 3 updates (2 3G, 1 LTE) Boston - 16 updates (6 3G, 10 LTE) Buffalo - 4 updates (4 3G) Central Illinois - 6 updates (6 LTE) Central Jersey - 11 updates (6 3G, 5 LTE) Charlotte - 1 update (1 LTE) Cincinnati - 79 updates (62 3G, 17 LTE) Cleveland - 4 updates (4 LTE) Colorado - 33 updates (33 3G) Columbus - 37 updates (32 3G, 5 LTE) DFW - 5 updates (5 3G) Delaware - 1 update (1 LTE) East Iowa - 3 updates (3 LTE) East Michigan - 4 updates (4 LTE) East Texas - 2 updates (2 3G) GA/SC Coast - 2 updates (2 3G) Georgia - 3 updates (2 3G, 1 LTE) Gulf Coast - 1 update (1 3G) Hawaii - 18 updates (18 3G) Houston - 14 updates (12 3G, 2 LTE) Idaho - 2 updates (1 3G, 1 LTE) Jacksonville - 5 updates (3 3G, 2 LTE) Kansas - 3 updates (2 3G, 1 iDEN Conversion) LA Metro - 18 updates (14 3G, 4 LTE) Las Vegas - 8 updates (4 3G, 4 LTE) Long Island - 15 updates (10 3G, 5 LTE) Louisiana - 1 update (1 3G) Lower Central Valley - 8 updates (7 3G, 1 LTE) Memphis - 4 updates (4 3G) Miami / West Palm - 8 updates (7 3G, 1 LTE) Milwaukee - 4 updates (4 LTE) Minnesota - 6 updates (1 3G, 5 LTE) Mississippi - 1 update (1 3G) Missouri - 16 updates (14 3G, 2 LTE) Myrtle Beach - 3 updates (1 3G, 2 LTE) Nashville - 1 update (1 3G) New York City - 31 updates (19 3G, 12 LTE) Norfolk - 1 update (1 LTE) North LA - 5 updates (5 3G) North Wisconsin - 1 update (1 3G) Northern Connecticut - 10 updates (4 3G, 4 LTE, 1 new 3G/LTE site) Northern Jersey - 21 updates (4 3G, 15 LTE, 1 iDEN Conversion) Oklahoma - 5 updates (5 3G) Orange County - 10 updates (8 3G, 2 LTE) Oregon / SW Washington - 3 updates (3 LTE) Orlando - 14 updates (12 3G, 2 LTE) Philadelphia Metro - 7 updates (3 3G, 2 LTE, 1 iDEN Conversion) Phoenix - 18 updates (9 3G, 9 LTE) Pittsburgh - 28 updates (20 3G, 8 LTE) Raleigh / Durham - 4 updates (4 LTE) Richmond - 11 updates (6 3G, 5 LTE) Riverside / San Bernardino - 18 updates (12 3G, 6 LTE) SF Bay - 15 updates (13 3G, 2 LTE) San Diego - 16 updates (12 3G, 4 LTE) South Bay - 1 update (1 3G) South Texas - 6 updates (6 3G) Southern Connecticut - 11 updates (5 3G, 6 LTE) Southern Jersey - 2 updates (2 3G) Southern Virginia - 14 updates (14 3G) Tampa - 4 updates (4 3G) The Panhandle - 3 updates (3 3G) Toledo - 4 updates (4 LTE) Tucson / Yuma - 6 updates (3 3G, 3 LTE) Upper Central Valley - 82 updates (69 3G, 13 LTE) Upstate NY Central - 7 updates (7 LTE) Upstate NY East - 4 updates (4 3G) VT / NH / ME - 4 updates (1 3G, 3 LTE) Washington DC - 16 updates (6 3G, 10 LTE) West Iowa / Nebraska - 1 update (1 LTE) West Kentucky - 13 updates (7 3G, 6 LTE) West Michigan - 1 update (1 LTE) West Texas - 8 updates (7 3G, 1 LTE) West Michigan - 1 update (1 LTE) West Washington - 3 updates (3 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

I believe Pratt has two bands of Sprint LTE now. And they have low frequency spectrum too. Which Tmo couldn't deploy there even if they wanted to add service in Pratt. Unlimited Sprint LTE would be the best bet for this guy. What on earth does he want? Robert

The system worked! Glory be!!! Robert

Sprint is phasing out Uniband LTE devices. All new releases since the end of 2013 are Triband only. Other than SVLTE, it is better to be Triband. Especially given that the Colorado market actively has all three bands available right now in many places. Robert

Just because Garrett got a new mistress, doesn't mean she is going to put out! Robert

EXCELLENT POINT! Robert

I feel like I should go hide in the bathroom when I look at those pics. Oh yeah! Robert via Samsung Note 8.0 using Tapatalk Pro

I love how Tmo's 230M is a triumph and Sprint's 225M is a failure. As if they aren't almost the same. And they are roughly the same when you consider that Sprint has not launched DC and Denver, even though they have significant deployments. If anything, this brings to light that Sprint is sprinting back into the pack and is right there neck and neck with Tmo in the hunt. Sprint has a lot of large markets that will be launching this summer. And Sprint has way more rural LTE coverage and Band 26 overlays. I'm actually more optimistic about a stand alone Sprint now than I have at any point since the deal with SoftBank closed. If Tmo is firing across Sprint's bow again, it's because they realize they are having to compete again with them. Robert via Samsung Note 8.0 using Tapatalk Pro

Found Band 41, you did!! Robert via Samsung Note 8.0 using Tapatalk Pro

Frederick has really suffered through Network Vision. It is among the very last. So it's day must be near. As for the reasoning, it could be the city. It could be Sprint and its subcontractors. Or it could be a combination thereof. I hope it happens for you soon. Robert via Samsung Note 8.0 using Tapatalk Pro

I did for about 3 days after upgrading to 4.4.4. But just as I was considering reporting it to mikejeep, it stopped consuming so much battery and went back to normal. Robert via Samsung Note 8.0 using Tapatalk Pro

plan vault Robert via Samsung Note 8.0 using Tapatalk Pro

Me too. Robert via Samsung Note 8.0 using Tapatalk Pro

Yeah, they already announced the June launch cities. And Denver did not make the cut. They may launch in July or August. However, they did complete all the equipment installs in the Denver metro area (excluding DIA and the Boulder cluster). So the LTE equipment is there now at almost every site. The ones where backhaul was ready, they have fired up LTE. About 1/3 of the city so far. So they are waiting on backhaul on the remaining 2/3. Once they get to the point where 40% are fired up, they will launch. People with a Triband device will get LTE coverage now over 50% of the metro area. But they will not formally launch the market until uniband device holders have at least 40% coverage. Robert via Samsung Note 8.0 using Tapatalk Pro

It reminds me of a friend of mine who's a doctor. Good person, but man is she an egomaniac. She had someone come in to take her open Office Manager position. The candidate was perfectly qualified and had a wonderful personality. Seemed her search for an Office Manager was over. However, she called her two professional references. And both said she was perfect, until she was caught stealing from them. So what did my doctor friend do? She hired her. She said the previous employers were just stupid and didn't manage her right. She just needed to put the proper safeguards in place and manage her new Office Manager properly, and she would have no problems. The Office Manager did a good job for the first year. No problems. But then, true to form, the Office Manager did the same exact things. She eventually stole over $20,000 before getting caught. I say this, because Ericsson is like the Office Manager in this scenario. AT&T and Verizon is the Doctor. They may think they're smarter than Sprint. They may even actually be smarter than Sprint. I believe my Doctor friend was likely smarter than the other doctors, especially having that info about her past problems and knowing to put in extra safeguards. AT&T and Verizon will even know many of the pitfalls of using Ericsson for network management and try to mitigate them. However, in my personal opinion, I wouldn't do it. Learn from Sprint's mistake in outsourcing their network management. Don't think you can do the mistake more niftily. Sprint's use of Ericsson seems to be an utter failure from my perch. We have seen time and time again where they go out to problem sites and do nothing, or pretend there isn't a problem, or just can't figure out the problem and just move on. A third party never has the accountability or vested interest in how your network performs. And even if it's an absolute necessity financially to outsource your network management, Ericsson just doesn't seem to be a good call. Let's see if ATT and VZW egos are so large that they blunder into this catastrophe. Doctoritis. There was a part of me that hoped my friend would fail for making such an ego driven poor decision. I counseled her against it. That same part of me now hopes that AT&T and VZW also choose Ericsson. They deserve Ericsson if they choose them knowing what's happened. Let's not forget that Ericsson managed the Clearwire network too. Disclaimer: The views expressed in this post are my personal opinions based on my amateur observations. Robert via Samsung Note 8.0 using Tapatalk Pro

mooeydj has moved up the list a few spots and nearing the top. Thank you for your continued contributions! Robert

I can tell you I have not experienced anything on my AT&T Nexus 5 that sounds even up to typical Sprint quality, let alone anything close to HD Voice. Whether to landlines, other AT&T customers, other AT&T N5's or to any other provider. Do you know of anywhere on my N5 where I can verify my bit rate when on an AT&T phone call? It seems to only work when I'm using a Sprint SIM card. Robert

Based on some requests from members to give extensions to the promotion, I will extend a few days for everyone until I leave for my Independence Day camping trip and fall of the grid. We will honor the $40 Premier Sponsor Discount through July 4th at 11:59 PM Hawaii Time. So this adds just a few more days. If you want to upgrade to Premier, do it now. We don't ever plan to offer a discount this steep ever again! Robert via Samsung Note 8.0 using Tapatalk Pro

Still waiting for increased call quality on AT&T. My voice connections sound circa 2003. Robert via Samsung Note 8.0 using Tapatalk Pro

If it is a temporary optimization issue, I would suspect things would return to normal in 6 weeks max. If it lasts longer than that, they may had to make a lot of physical downtilt adjustments that actually has permanently affected B25 coverage. Sometimes these changes just have unintended consequences. RF engineering is almost as much an Art as a science. Things sometimes just don't work out as planned when making changes. If you don't see any improvements within another week or two, I'd call Sprint and insist on opening a trouble ticket. There's a good chance that an Ericsson engineer will go check out the affected areas. If there is an obvious problem detected from recent work, he may be able to get that fixed. Hopefully this info helps. Robert via Samsung Note 8.0 using Tapatalk Pro

Launching is a good thing. Because now at least they acknowledge the service that is deployed and they can open up trouble tickets for you. When you are in prelaunch status, they won't do anything, ever. Robert via Samsung Note 8.0 using Tapatalk Pro

They are doing optimizations as they bring Band 26 LTE online that may effect B25 LTE signals. This could be affecting you, or it could be something completely different in your area. Robert via Samsung Note 8.0 using Tapatalk Pro

In my area, they deployed on every site where 700MHz was running slow (which was almost the entire city). They did that around Thanksgiving last year. They are using 15MHz channels here on AWS. And in many places it is just another 10MHz. But if you talk to the VZW Groupies, they'd have us to believe XLTE is on every site on 20MHz channels. I was glad to be able to explain this in my interview with Mark Davis of the KC Star. When you compare Sprint's capability with Spark, and VZW "XLTE", there really is no contest. Sprint just needs to get it deployed. And based on the early field reports, it's far exceeding our expectations and the NV 1.0 deployment rates. This is what an overlay deployment looks like. Robert via Samsung Note 8.0 using Tapatalk Pro