JWMaloney

Those of you who are having issues with band 41 -- are you having issue with Clearwire LTE or with 8T8R equipment?

It can improve through optimization over time. I can't tell you for certain what will happen, but I can tell you anecdotally that in my area, 800 LTE performance was initially sub-par.

Are you saying that they were adding 2.5 GHz equipment to a legacy site, or that they were creating a new site with 2.5 GHz equipment only? Because you may see the latter frequently since 2.5 GHz requires denser site spacing.

If you have an Airave 2.0 or older, you should be fine. If you have an Airave 2.5 (the one with the internal, detachable GPS unit), it broadcasts a beacon on 1x 800 and will probably interfere.

If you have band 26 coverage, you undoubtedly have 1x 800 voice coverage and don't need the Airave anymore. I say unplug the Airave and test it. If that doesn't work, call Sprint and yell.

Sprint's official stance is that you need to disable LTE to use an Airave with a tri-band device.

No, but there's an updated radio interface layer (RIL) library in that last one.

They shouldn't have included Sprint's WCS holdings in that first map, as those are being sold to AT&T. I know they currently still own it, but it does bump Sprint into that > 150 MHz bracket in some places on the map.

I wouldn't recommend this. Google Voice integration itself causes me to miss plenty of calls. I've had a ticket open about it for months. They got some good data about it today though. Five of the recent examples didn't show up in my local MSC or the Google Voice switch.

The 1x location is often offset from the actual cell site into the serving cell. And if you're not seeing a performance improvement on 1x800, it probably isn't fully optimized yet.

If a site is specifically a GMO, it has legacy antennas, so it can't support any 800 MHz services. But that doesn't mean sites can't have RRUs mounted at the BBU cabinets and NV capable antennas (in which case they wouldn't be a GMO). At those sites, all bands should be possible. As far as I know, you usually only see something like that in places like rooftops or small/stealth sites (like "flagpole" sites) like this one from the in-progress thread:

In mature band 26 areas, I'm seeing band 26 used more frequently and more correctly, with proper hand-offs between sites. On sites with eCSFB issues on any band, I'm seeing a greater tendency to get pushed back to 3G.

Full acceptance of all five 800/1900 Network Vision upgrades on a cell site is a prerequisite to Nokia's rollout of 8T8R band 41 upgrades on the same site. That doesn't mean that 800 LTE is indicative of a band 41 upgrade coming soon, just that it won't be possible otherwise.

It varies even by city because of municipal fees and taxes.

The hub he was referring to in that video also showed up on the Network Vision map a while back: I confirmed it with permits dating all the way back to 2007 for all 4 major carriers when it was constructed, and with Street View imagery of the hut/cabinets themselves.

Comcast offers up to 105 Mbps in my market. We have an unenforced ("suspended") 250 GB data allowance back from when they first tried that a few years ago. You are able to monitor your usage from your account portal, but I regularly go over that amount without any issues.

Check your PM.

I believe this may be related to the recent announcement that Verizon has secured VOIP interconnects with Sprint and T-Mobile. This may have something to do with inter-carrier HD voice. It may also be related to some sort of cloud synchronization of services and/or storage.

No

My thoughts after a full day of testing and not losing LTE at all on launched sites:

ART, hands down.

RSRP (dBm) alone is a pretty useless measure of a modem firmware; there are plenty of other important numbers on the engineering screen too. What really matters is the performance on that firmware. I said this before the 4.4.3 update was released -- my own testing shows that, while the .17 radio shows higher dBm readings on LTE, the .23 radio connects to LTE in less places because of poor fringe performance. That said, I upgraded last night directly from the .23 radio, and I can tell you that the new 2.0.50.1.13 radio is absolutely giving me much better band 26 performance. I previously found it impossible to reliably hand off from site to site while connected to band 26 (the device would drop to eHRPD instead and park there for a long time); now I'm seeing my device idle on band 25 and correctly move to band 26 either when necessary -- either when the cell site tells it to (for capacity) or when approaching the edge of the band 25 cell (for coverage). And I'm actually seeing hand-offs across band 26 sites now. I'm also seeing the device grab onto band 26 in more places than before (for instance, in elevators and parking garages) where it would previously give up and fall back to eHRPD. And on a fringe signal, I'm seeing better speed tests. At home, where I have a good signal on either band, I'm seeing better behavior -- the device will camp out on band 25 while I'm on Wi-Fi, and it will immediately move to band 26 when I disable Wi-Fi. I tested that several times, and it moved after every toggle with no issues. And even at my desk at work, where I get a poor signal, I've been on band 26 all morning and haven't dropped to eHRPD once. Previously the device would move between band 25, band 26, and eHRPD all day in this spot. I'm starting to think some of you just have defective devices.

You may be on an older PRL which scans for 800 first.

Everyone tends to forget how many people rushed out to buy the $600 unsubsidized iPhone when it was first released. I can see prices decreasing, but not by much.

I do, because it's about time we have simultaneous voice & data. And there's no reason it should be less coverage, as the calls should hand off to 1x voice via SRVCC.