S4GRU

I think the pausing when connecting to 3G and the difficulty in reobtaining LTE is the issue. If the transition to 3G was seamless or near seamless, and the reacquiring of LTE was as quick as it could be, I think the frustration would be much lower. Now I remember something I should have said earlier...if you are actively streaming 3G data, it will not bump you back up into LTE when you come into range. It needs a sizable pause of inactivity to move you back to LTE. This is also true of Verizon when on 3G and AT&T/Tmo on WCDMA. Devices don't want to hand up when you come back into LTE range when you are actively using data or in a continual data stream. You may be experiencing something much more than this, but I thought I should still at least mention this. Robert via Samsung Note 8.0 using Tapatalk Pro

Irwinshere did fine by me. Kick the whiners to the curb. We don't host Sprint complaints. Period. I could complain as much as the rest of you. No one is even disagreeing with them. But people don't come here to read through complaints, they come here to find out and track progress. So please leave your complaints at the door and post productively. Everyone is free to complain about Sprint. They can even lodge formal complaints. But they can't do it here. Carry on. Robert via Samsung Note 8.0 using Tapatalk Pro

Robert via Nexus 5 using Tapatalk

The grass isn't greener on AT&T either. I'm dying at events and games too. I keep having to pull out my VZW hotspot. Damn you Randall Stephenson! AT&T's network heyday was 2013. They are really starting to suffer in MANY places. It feels like the iPhone craze in 2008 all over again. Robert via Nexus 5 using Tapatalk

Site acceptance report from Monday (3/24) through Thursday (3/27): Arkansas - 3 updates (2 3G, 1 LTE) Atlanta / Athens - 66 updates (1 3G, 64 CDMA 800, 1 LTE) Austin - 183 updates (8 3G, 173 CDMA 800, 2 LTE) Baltimore - 9 updates (3 3G, 1 CDMA 800, 5 LTE) Boston - 53 updates (2 3G, 44 CDMA 800, 7 LTE) Central Iowa - 2 updates (2 LTE) Central Jersey - 2 updates (2 3G) Central Pennsylvania - 2 updates (2 LTE) Charlotte - 1 update (1 LTE) Cincinnati - 36 updates (36 3G) Cleveland - 37 updates (20 3G, 1 CDMA 800, 15 LTE, 1 new 3G site) Colorado - 4 updates (4 LTE) Columbus - 7 updates (7 3G) DFW - 1 update (1 3G) Delaware - 5 updates (1 3G, 1 CDMA 800, 3 LTE) East Iowa - 1 update (1 CDMA 800) East Kentucky - 4 updates (4 3G) East Michigan - 2 updates (1 3G, 1 LTE) East Texas - 4 updates (4 LTE) GA/SC Coast - 5 updates (1 3G, 4 LTE) Georgia - 3 updates (2 3G, 1 LTE) Gulf Coast - 3 updates (1 3G, 2 LTE) Hawaii - 8 updates (8 3G) Houston - 3 updates (3 LTE) Indianapolis - 1 update (1 3G) Inland Northwest - 1 update (1 LTE) Jacksonville - 5 updates (2 3G, 3 LTE) LA Metro - 4 updates (4 LTE) Las Vegas - 2 updates (2 LTE) Long Island - 4 updates (4 3G) Louisiana - 1 update (1 LTE) Memphis - 2 updates (1 3G, 1 LTE) Miami / West Palm - 11 updates (10 3G, 1 LTE) Milwaukee - 5 updates (1 CDMA 800, 4 LTE) Minnesota - 8 updates (8 LTE) Missouri - 12 updates (10 3G, 2 LTE) Myrtle Beach - 2 updates (2 LTE) Nashville - 183 updates (179 3G, 4 LTE) New Orleans - 2 updates (2 3G) New York City - 4 updates (1 3G, 3 LTE) Norfolk - 3 updates (3 LTE) North LA - 5 updates (2 3G, 3 LTE) North Wisconsin - 3 updates (2 CDMA 800, 1 LTE) Northern Connecticut - 1 update (1 LTE) Northern Jersey - 4 updates (3 3G, 1 LTE) Oklahoma - 9 updates (9 3G) Oregon / SW Washington - 27 updates (7 3G, 14 CDMA 800, 6 LTE) Orlando - 8 updates (5 3G, 3 LTE) Philadelphia Metro - 27 updates (1 3G, 20 CDMA 800, 6 LTE) Phoenix - 4 updates (1 3G, 3 LTE) Providence - 1 update (1 3G) Raleigh / Durham - 1 update (1 3G) Richmond - 11 updates (11 3G) Riverside / San Bernardino - 2 updates (2 3G) SF Bay - 4 updates (4 LTE) San Diego - 2 updates (1 3G, 1 LTE) SF Bay - 1 update (1 LTE) South Carolina - 1 update (1 LTE) South Texas - 7 updates (6 3G, 1 LTE) South West Florida - 3 updates (1 3G, 2 LTE) Southern Connecticut - 2 updates (1 3G, 1 LTE) Southern Jersey - 3 updates (1 CDMA 800, 2 LTE) Tampa - 3 updates (3 3G) The Panhandle - 1 update (1 LTE) Toledo - 36 updates (36 3G) Tucson / Yuma - 2 updates (1 3G, 1 LTE) Upper Central Valley - 29 updates (25 3G, 4 LTE) VT / NH / ME - 4 updates (1 3G, 3 LTE) Washington DC - 8 updates (1 3G, 7 LTE) West Iowa / Nebraska - 4 updates (1 3G, 3 LTE) West Kentucky - 7 updates (2 3G, 5 LTE) West Washington - 6 updates (1 3G, 5 LTE) West Texas - 1 update (1 3G) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

It will improve as Band 26 gets optimized. Whenever you start to get a weak LTE signal, the network tries to find you somewhere to hand off to. If it can't, you get sent back to 3G. Band 26 downtilit needs to be adjusted, and the neighboring Cell ID's need to be better configured. Soon your device will be able to see LTE just about everywhere in the Houston area, and this will no longer be a problem. But this optimization will likely take a few months. So every little pocket will improve one by one as they track down the issues and work them out. Robert

Thanks for the donation. You have already been reupgraded to Sponsor. Since you have ruled out a device problem, I would call Sprint and report it. 2 weeks is an awful long time to have no LTE service in a launched market. Let me ask this though...is the whole site down, or are you just not able to get a signal in a place you used to? Because if you used to just get a weak LTE signal in an area (say -105dBm or weaker) and now it's not there anymore, it's possible that the sector has been optimized and you are now out of coverage until B26 arrives. If the whole are doesn't have LTE anymore, including near the site where you connect to, then report it to Sprint as an outage. Robert via Samsung Note 8.0 using Tapatalk Pro

Exactly. VoLTE will handle data and voice simultaneously in one path, similar to the way WCDMA works. Robert via Samsung Note 8.0 using Tapatalk Pro

Since you are in a launched market, have you reported the outage to Sprint? Have you confirmed it is out for other devices too? Robert via Samsung Note 8.0 using Tapatalk Pro

We have gotten several reports that HD Voice codec to landlines sound very clear and almost HD sounding. Seems like if the switch is fully upgraded to support HD voice, then the quality of the voice when hits the telephone system beyond it is still going to be at least as good as what is on the other end of the connection. Robert via Samsung Note 8.0 using Tapatalk Pro

Yea, I can support that reasoning. Since many of us now use wireless phones as our only telephone service (me included), it seems perfectly reasonable to want the HD Voice service at home. Robert via Samsung Note 8.0 using Tapatalk Pro

Yes, and the notifications won't work when I update the Tapatalk extensions, either. This is an ongoing Tapatalk problem. They are like Sprint, that is their answer for everything. Every time one of you bothers me with a Tapatalk problem, it makes me want to stop using it all together. You will need to use S4GRU Email notifications because Tapatalk app is inconsistent. Sorry "The Administrator"

Yes I do! But not in the cards for awhile. Robert via Samsung Note 8.0 using Tapatalk Pro

Hey wait! I see what you were doing there!

What?

Since the partners don't have any SMR or PCS G Block spectrum, but do have Cellular and PCS spectrum, I think they were relating it into language they understand. We will help you get devices that run on your Band 2 & 5, by virtue of getting Band 25 & 26 devices. That's how I took it. Robert

Please join me in welcoming COZisback to the S4GRU Staff. He will be helping us moderate the forums. We are excited to have someone so dedicated to the great S4GRU Experiment join our ranks! And he was crazy enough to accept the invite... Robert

It certainly came off that way. I agree. Robert

To me I hear the old way was not good. This seems like a Pro CCA argument, if anything. We know Sprint is not going to overbuild Alaska. So this is the next best thing. Also, I don't believe Sprint ever sold service in Alaska. So the only Sprint customers that could have been in Alaska are those who moved there with Sprint service. And they would have been let out of their contract ETF free. It's not as bad as you're making it out to be. Robert

That's why the CCA is attractive. You'll be pretty much all in or all out. And since Sprint is allowing CCA members to strike deals to get access to Sprint spectrum and even capex funding, there is a lot of benefit for local wireless providers to jump in with this and stay. I just watched the whole video, and I'm impressed. It's too bad Sprint couldn't have done this two years ago. But listening to Masa breeds confidence. You know this will be done right. It actually may be better to have it done now, and be done right. I like listening to Masa speak. It makes me want to get off my duff and do something. Robert

Look a the the coverage map. That will tell you what they consider launched. Robert via Samsung Note 8.0 using Tapatalk Pro

Agreed. All things we knew in the past as definite plans are all back up for negotiation. Robert via Samsung Note 8.0 using Tapatalk Pro

Down to stated speeds is to be expected. Especially in a place with only one band deployed. Robert via Samsung Note 8.0 using Tapatalk Pro

It's not likely the current roaming limits will be a part of this deal. Although it has not been announced how it will be counted, our collective wisdom concludes it will be treated as native or at least the amount of roaming allotment will be increased. Sprint will not need to be as constrained with the amounts used on CCA networks because the fee per GB will be less expensive and the rural carriers are more likely to have more usage on Sprint than Sprint customers have on their networks. In general, rural customers travel to urban areas and spend more time in them than urban customers spend time in rural areas. Robert via Samsung Note 8.0 using Tapatalk Pro