S4GRU

I want to say it did populate when I can get it to register on Verizon and gives me signal bars. I will take a screen shot the next time I do it. I could do it now, but my SIM card and ejection tool are upstairs. And I'm cold and tired...and lazy. Robert via Samsung Note 8.0 using Tapatalk Pro

Yes, Band 26 is LTE 800. Robert via Nexus 5 using Tapatalk

There will not be any unlimited price increases any time soon. No way. Robert via Nexus 5 using Tapatalk

sidewalk crack Robert via Nexus 5 using Tapatalk

If I go into LTE only mode, I can get it to stop on a Verizon Band 4 channel. Even with an AT&T SIM installed. If I switch to a VZW SIM and APN, it will show me bars on my N5. But it will never authenticate. Robert via Nexus 5 using Tapatalk

One of the reasons why they went with a wide uplink ratio. Because at 4:1, as the MIMO increased over time it would only even make the low upload speeds look worse and worse. Since MIMO will go to 4x4 and 8x8 in time and the download speeds will rocket, might as well have a better ratio for the uplink now. Robert via Nexus 5 using Tapatalk

We just don't want to hear the negative posts in 30 days because Earl in East Cleveland is pissed because his block doesn't have LTE. We like to give out facts. S4GRU is definitely not in the marketing biz. Robert via Nexus 5 using Tapatalk

So you think AT&T is also firing up LTE here in South Dakota today too? Because mine says LTE also. And I'm in 3G only coverage. These apps mean nothing. It's what the LTE Engineering screen says that is important. That's where these apps are essentially getting data from. And your LTE Engineering screen is saying nada. Robert via Nexus 5 using Tapatalk

Robert via Nexus 5 using Tapatalk

If it was on a Triband phone, it sounds like CSFB must have went offline at that site. But you list a Note 2 as your device. If that's what you were using, then that can't be it. Robert

12 LTE acceptances in the Rochester market posted today. That's pretty spiffy! Robert

AT&T doesn't recognize my Nexus 5. Bastards! But obviously Verizon does, as they block me from their network!! Robert

I know they were using 4:1 in initial FIT testing and were hitting 100Mbps consistently. However, they must have thought it was worth sacrificing some of the top end of the performance to maintain solid upload performance and settled on 3:2. Robert

I have not received any CDMA 800 acceptance reports for the DFW market since November. So there likely has been CDMA 800 sites accepted since then. The 3G/4G sites are posted every day. The CDMA 800, LTE 800 and LTE 2600 site acceptances I receive on a market or region basis at infrequent/inconsistent intervals. I never know what I'm going to get and when. But I post what I receive after I get it. Robert

I used every emoticon that made sense in response to that. Robert

If you were able to see an LTE network you could not connect to, your LTE Engineering screen would look more like this: This is what Verizon Band 4 LTE (AWS) looks like on my Nexus 5 with a VZW SIM that will not authenticate. It would give you the correct DL channel, but not UL channel. The UL channel will not populate until you authenticate with the network. Robert via Nexus 5 using Tapatalk

I hate to burst everyone's bubble, but in LTE Discovery it actually defaults LTE in the left box. I have it too and I am on AT&T and outside of an LTE area by 45 miles. When you see in your LTE Engineering screen Band 50 and Channel 65535, it means it cannot find an LTE channel at all. That's the default no value return. See my screenshots below: Robert via Nexus 5 using Tapatalk

Site acceptance reports from Friday (1/24), Saturday (1/25) and Sunday (1/26): Alabama – 2 updates (3G) Arkansas – 1 update (LTE) Atlanta/Athens – 5 updates (CDMA 800) Baltimore – 1 update (LTE) Boston – 2 updates (1 LTE) Buffalo – 11 updates (3G) Central Iowa – 1 update (3G) Central Jersey – 1 update (LTE) Charlotte – 1 update (LTE) Colorado – 1 update (LTE) Columbus – 1 update (LTE) East Michigan – 14 updates (3G) Georgia – 1 update (LTE) Gulf Coast – 4 updates (1 LTE) Houston – 1 update (3G) Idaho – 4 updates (LTE) Inland Northwest – 2 updates (LTE) Jacksonville – 1 update (3G) Kansas – 1 update (3G) LA Metro – 3 updates (2 LTE) Long Island – 1 update (LTE) Louisiana – 1 update (LTE) Miami/West Palm – 1 update (3G) Milwaukee – 2 updates (LTE) Minnesota – 5 updates (3 LTE) Mississippi – 1 update (3G) Missouri – 9 updates (4 LTE) Myrtle Beach – 2 updates (LTE) Nashville – 17 updates (2 LTE, 15 CDMA 800) Norfolk – 15 updates (3G) North LA – 2 updates (LTE) Northern Connecticut – 1 update (3G) Northern Jersey – 2 updates (1 LTE) Orange County – 1 update (3G) Oregon/SW Washington – 1 update (LTE) Orlando – 3 updates (3G) Philadelphia Metro – 4 updates (LTE) Providence – 1 update (LTE) Raleigh/Durham – 1 update (LTE) Rochester – 12 updates (LTE) San Diego – 4 updates (3 LTE) South Carolina – 87 updates (CDMA 800) South Texas – 7 updates (5 CDMA 800) South West Florida – 2 updates (1 LTE) Southern Connecticut – 1 update (LTE) Southern Jersey – 1 update (3G) Tampa – 1 update (3G) The Panhandle – 3 updates (2 LTE) Tucson/Yuma – 1 update (3G) Utah – 1 update (LTE) VT/NH/ME – 31 updates (2 LTE, 28 CDMA 800) Washington DC – 1 update (LTE) West Iowa/Nebraska – 4 updates (LTE) West Kentucky – 3 updates (1 LTE) West Michigan – 2 updates (LTE) West Texas – 22 updates (CDMA 800) West Washington – 6 updates (LTE) Winston/Salem – 5 updates (LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

I've seen it do that when it is scanning LTE channels and find an active one. It will say N/A until it registers with the network and then those fields populate. If it cannot connect to LTE, it will go back to eHRPD in a few minutes. The next time that happens, take a screen shot of your LTE Engineering screen. Because if it is stopping on a bona fide LTE channel, it will populate the info there. Robert

It probably was counted because AT&T and/or Verizon did in their announcements. Robert

I've always wanted to know what the story was with that. Did the backhaul vendor mislabel the year in the anticipated delivery date? Robert

I say that's a pretty good description. Robert

Since this is a switch to Ericsson equipment from another vendor, it suffers CSFB issues. Sprint says they will not launch markets officially until CSFB upgrades are complete in that market. Robert

I noticed that too. When I saw it on the list, I thought, "Hey, I thought there was only one site with LTE active in Georgetown?" Went to the NV map, and sure enough. But I guess it covers 40% of the POPs. I was quite surprised though. Robert

toy truck