S4GRU

Puerto Rico/Virgin Islands and Ft. Wayne/South Bend will not have LTE problems with Triband devices because NV 3G is complete in those markets. Markets that have NV 3G complete will be fine on Triband LTE devices. Robert via Samsung Note 8.0 using Tapatalk Pro

Thanks for all the member replies here in this thread. You guys are so helpful and give me more time to handle other things. Good job!! Sent from my Nexus 5 using Tapatalk

I have no idea what even cosplay is. I can he pretty naive. I asked my son, and he didn't even know. But he was raised by me. So there you go. Robert via Samsung Note 8.0 using Tapatalk Pro

station wagon Robert via Samsung Note 8.0 using Tapatalk Pro

I use Google Voice integration and have had no issues with voice quality. Robert via Samsung Note 8.0 using Tapatalk Pro

I agree. I think Sprint should offer a rural home ISP service. One 20MHz carrier on rural sites can carry bootloads of rural customers. The site next to my home in New Mexico would be greatly under utilized with a 20MHz TDD carrier. At worst, it would probably run 10% of capacity. However, the only terra-based ISP you can get in that area is Windstream DSL limited to 3-12Mbps, depending on how far you are from the DSLAM. Sprint could sell a great service to those people without sacrificing performance to the mobile customers. Robert

Yes. But my VZW SIM doesn't work in it, either. Robert

Yes. Robert

It only shows my devices that I own that are not currently active on any line. The active ones will not appear. I have to do them manually to switch to another account. Robert

This is true...in rural and tertiary markets. It is not true in primary and most secondary markets. Sprint could deploy a home ISP in rural areas no problem with their current spectrum without impacting their mobile plans the next few years. But not in places like New York City or Las Vegas. Robert

They made some changes. Now I can activate any of the past devices on my account just by clicking on them. No longer need to find the MEID except for the first time. Pretty cool. Robert

Site acceptance reports from Saturday (11/2) through Thursday (11/7): Alabama - 16 updates (12 LTE) Albuquerque - 3 updates (3G) Arkansas - 9 updates (7 LTE) Atlanta/Athens - 24 updates (3 LTE) Austin - 2 updates (1 LTE) Baltimore - 2 updates (3G) Boston - 8 updates (3 LTE) Central Illinois - 11 updates (3 LTE) Central Jersey - 7 updates (5 LTE) Charlotte - 3 updates (1 LTE) Chicago - 10 updates (9 LTE) Cincinnati - 4 updates (LTE) Colorado - 3 updates (LTE) Columbus - 2 updates (LTE) Delaware - 2 updates (1 LTE) DFW - 12 updates (5 LTE) East Kentucky - 1 update (LTE) East Michigan - 38 updates (3G) East Texas - 6 updates (3 LTE) GA/SC Coast - 9 updates (3 LTE) Georgia - 9 updates (4 LTE) Gulf Coast - 5 updates (2 LTE) Hawaii - 17 updates (3G) Houston - 20 updates (3G) Inland Northwest - 1 update (LTE) Jacksonville - 7 updates (4 LTE) Kansas - 13 updates (2 LTE) LA Metro - 13 updates (4 LTE) Las Vegas - 10 updates (5 LTE) Long Island - 2 updates (1 LTE) Louisiana - 3 updates (LTE) Lower Central Valley - 1 update (3G) Memphis - 8 updates (6 LTE) Miami/West Palm - 9 updates (6 LTE) Milwaukee - 31 updates (6 LTE) Minnesota - 34 updates (LTE) Mississippi - 2 updates (LTE) Missouri - 25 updates (22 LTE) Myrtle Beach - 1 update (LTE) Nashville - 6 updates (4 LTE) New Orleans - 3 updates (2 LTE) New York City - 15 updates (7 LTE) Northern Connecticut - 6 updates (1 LTE) Northern Jersey - 9 updates (5 LTE) North LA - 2 updates (3G) North Wisconsin - 1 update (LTE) Oklahoma - 4 updates (2 LTE) Orange County - 3 updates (1 LTE) Oregon/SW Washington - 3 updates (LTE) Orlando - 12 updates (6 LTE) Philadelphia Metro - 9 updates (2 LTE) Phoenix - 19 updates (5 LTE) Pittsburgh - 1 update (LTE) Providence - 6 updates (4 LTE) PR/VI - 1 update (LTE) Raleigh Durham - 48 updates (9 LTE) Riverside/San Bernardino - 5 updates (3 LTE) San Diego - 16 updates (9 LTE) SF Bay - 1 update (LTE) South Carolina - 5 updates (1 LTE) Southern Jersey - 16 updates (6 LTE) South Texas - 6 updates (LTE) Southwest Florida - 5 updates (3 LTE) Tampa - 3 updates (3G) The Panhandle - 9 updates (4 LTE) Tucson/Yuma - 5 updates (3G) Upstate NY Central - 3 updates (2 LTE) Upstate NY East - 4 updates (2 LTE) VT/NH/ME - 7 updates (3 LTE) Washington DC - 7 updates (3 LTE) West Kentucky - 9 updates (5 LTE) West Michigan - 25 updates (3G) West Texas - 1 update (LTE) Winston/Salem - 36 updates (6 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Information about Band 41 deployment for 2013 is in the Premier Sponsor section. Robert via Samsung Note 8.0 using Tapatalk Pro

Possibly. But not definitely. Since we do not know the exact reason of the problem, can't rule anything out right now. Currently we are just trying to determine the commonality. Robert via Samsung Note 8.0 using Tapatalk Pro

I don't recall off the top of my head. I'm mobile at the moment. But RDU does have WiMax. And it could even be that. I'd be interested to know if all the problems are in Band 41 LTE and/or WiMax areas. Robert via Samsung Note 8.0 using Tapatalk Pro

Ironically, when I put my Sprint SIM in my N5 from my Netgear Zing hotspot, it did connect to the Verizon network on CDMA as roaming for about 20 minutes. Then without advanced warning, a notification popped up and said my SIM was now locked because it could not authenticate after multiple attempts. It would be great to have a device on VZW that used AWS LTE only. It would be great for network testing. Robert via Samsung Note 8.0 using Tapatalk Pro

Are all people having LTE issues in Band 41 markets? Is it possible your device sees the Band 41 site and not allowing you to connect to Band 25 LTE? Robert via Samsung Note 8.0 using Tapatalk Pro

My Verizon MicroSIM card resulted in no connection. No bars shown...nothing. It wouldn't even show Verizon on the lock screen as the Carrier. Whereas Sprint actually shows up as the Carrier name when I put a Sprint SIM in. And I'm 400 miles from Sprint service! Robert via Samsung Note 8.0 using Tapatalk Pro

She is ruthlessly efficient! Robert

Because the Samsung devices are supposed to get an update shortly after their launch, not waiting until early 2014. Additionally, there are hotspots that use Spark now. You just seem to be trolling us. First post you already said you should leave Sprint. You seem to be an AT&T Astroturfer to me. They keep coming back. However, it is hard to get paid from AT&T being an Astroturfer on S4GRU, because we are just so aggressive on them and they get banned so quickly. It's better to astroturf on a site that you can actually make money on. Robert

You cannot use LTE and voice at the same time. However, you can use WCDMA and voice at the same time. And still can. Robert

Why did you omit that in that same announcement, they said that the Nexus 5 and G2 would not receive an update to enable "Sprint Spark" until early 2014? They didn't take advantage of you. They told you. They told us all. Robert

According to a source who is close to OEM's, it's not that Triband devices cannot support SVLTE. It's that getting SVLTE to work with TDD-LTE is difficult and expensive. According to this source, Sprint has decided not to pursue it as it would drive up the cost too high for consumers. We were told this information from this source long before Triband devices started going through the FCC, and his information has come to pass. None of the Triband devices to date have supported SVLTE. So we find this info to be credible. And since more and more devices are going away from SVLTE, Sprint feels like this is not going to hurt them a lot in the long run. So, basically, it is what it is. Sprint Triband devices do not support SVLTE. Perhaps in the future, Sprint may test a more expensive device that does support it and see if people are willing to pay more for it. Who knows? Robert

The Nexus 5 doesn't support SVLTE at all. Not on GSM/WCDMA carriers either. Actually, GSM/WCDMA carriers largely do not have any SVLTE devices. Based on a source, TDD-LTE makes it cost prohibitive to make a SVLTE smartphone. So Sprint is omitting that support. It also seems OEM's are avoiding trying to do SVLTE altogether. Seems like no one wants to spend the extra money for that support. You can still do simultaneous voice with WiFi, though. Robert

I have done much more frivolous things than that with student loans back in my day. When I consider I paid years of interest on food. Something that I only used for a few hours. At least you will get up to 2 years usage on a smartphone. Not that I would encourage such behavior. Unless it was to Sponsor S4GRU. Robert