ingenium

I suspect it won't fix it. The Pie update has lots of issues with Sprint. See my post here http://www.s4gru.com/index.php?/topic/5375-Nebraska/Iowa-Premier-Thread#entry533932 Sent from my Pixel 2 XL using Tapatalk

It's hypothesized to be a basestation upgrade/hardware replacement in Samsung markets. Started happening in April in the SF market and spread quickly to other markets. It's needed to enable 256 QAM and 4x4 I believe, and maybe VoLTE prep. It's definitely required for FDD-TDD CA, since CA requires all carriers to be on the same eNB (ie GCI). Sent from my Pixel 2 XL using Tapatalk

Seems to be an external module that connects to the Ethernet port. Unsure if the MB has 1 or 2 Ethernet ports; if it's just 1 then it would prevent you from using wired backhaul. Sent from my Pixel 2 XL using Tapatalk

Presumably it would keep the connection active but at a higher metric, so that it will fail over (like having wifi and LTE at the same time on a phone, or wifi and Ethernet on a laptop). It would just have to re-establish the ipsec tunnel when it changes backhaul. Or they could enable MOBIKE (since it uses IKEv2) to allow fast roaming without dropping any connections running over the tunnel. If setup properly it could fail over within seconds and no UEs will have their connections interrupted. Sent from my Pixel 2 XL using Tapatalk

I'm getting 64 QAM upload regularly on B25 and B26. I saw it briefly on B41 today. Did catch a very brief blip on 256 QAM in Pittsburgh. So it's coming...

I roamed on T-Mobile for a bit in the outskirts of the Pittsburgh market (may have technically been Western PA market) for probably 20 minutes. Was a big dead spot for Sprint, but the T-Mobile coverage was solid. Sent from my Pixel 2 XL using Tapatalk

Sorry, no more pictures. I detected most of them at night via SCP. I'd guess there are at least 100, about a block apart. Sent from my Pixel 2 XL using Tapatalk

Completely agree. There are some sites near me that are already struggling daily with single digit download speeds on 3xCA B41. No way that T-Mobile can absorb that on their existing AWS without serious problems or high densificiation. In my opinion, they'll stop deploying new B41 carriers, make sure 4x4 and 256 QAM are enabled, and then use the remaining spectrum for 5G instead. And as load on B41 is reduced as 5G capable handsets become available, they'll shut down carriers and refarm to 5G. Sent from my Pixel 2 XL using Tapatalk

I mean in theory is should improve B41 performance if the site was using original triband antennas. The old tribands were 4t4r b41. However the 16 port tribands, while being 8t8r, have a narrower beamwidth compared to NV 1.0 and I believe standalone 8t8r, meaning coverage is weaker between sectors. I'm unsure how they compare to the original triband antennas. So if you're between sectors, that could explain the worse performance. That being said, it should be a direct replacement at basically the same positioning. The b41 and b25 RRUs likely aren't touched. They usually add a second b26 rru or replace it with a 4t4r capable one. But since the antenna is different, there probably is some sort of of optimization that they'd do. Sent from my Pixel 2 XL using Tapatalk

They could have maybe swapped out equipment. 25% of SF market's B41 is from triband sites. Even higher within the city. They may have swapped out the antennas for a 16 port triband? Sent from my Pixel 2 XL using Tapatalk

Found a ton of the strand mounts from the Altice partnership in your market. They're everywhere around Saddle River. Sent from my Pixel 2 XL using Tapatalk

I've never heard of it interfering. Ethernet is pretty resilient, even AC power in my experience hasn't been a problem when I've done runs. As long as the wires aren't parallel and very close together, I would think that you'd be fine. As lilotimz said, the cellular frequencies are way above the frequency of Ethernet. Nothing will be below 600 MHz, with most over 1500 MHz. AC power can cause issues because the frequency overlaps with Ethernet. As a real world example, my college dorm was wired with Ethernet, and Sprint equipment was literally mounted next to my window, on the other side of the wall. The back of the antenna was maybe 5 feet from my computer. No one in my dorm had Ethernet issues. Sent from my Pixel 2 XL using Tapatalk

It was just scanning for a signal that it can connect to. Field test would show what it's currently scanning. Sent from my Pixel 2 XL using Tapatalk

Technically no. The Android VoLTE framework allows for the VoLTE config to be added to the firmware, or it can be included with any app that's signed by the same certificate used to sign the SIM card. In other words, Sprint can publish an app on the play store (or maybe add it to the My Sprint app) and deploy it on every device running Marshmallow and up, assuming that it's FCC certified for VoLTE (nothing technical is preventing it). But I have a strong feeling that they won't do this for whatever reason. Google made it very easy for carriers to add their VoLTE config to devices without needing an OS update. Sent from my Pixel 2 XL using Tapatalk

Could be congestion. Also on newer Samsung phones, there are some carrier aggregation combos that for some reason dramatically lower speeds at the moment. It will eventually get fixed, but that could be a reason. You can try disabling some CA combinations if you have a Samsung device, or do a profile update to reset them to the current default. Sent from my Pixel 2 XL using Tapatalk

Not for band 41. It has to be contiguous for most handsets. I think the current Samsung flagships can do non-contiguous B41 CA though (any device that can do 4xCA B41 can do non-contig, and I'm pretty sure those handsets support 4xCA), so it's coming. Sent from my Pixel 2 XL using Tapatalk

That looks like a hexdecaport antenna for sure. Here are some pictures that I took of one in Pittsburgh in January (along with lots of other pictures of the tower). https://photos.app.goo.gl/G4T06PyC5hZHU1dE3 Sent from my Pixel 2 XL using Tapatalk

I wonder if they can broadcast different disconnect thresholds for different devices. I guess it comes down to whether LTE signaling is broadcast/multicast or unicast. The Pixel 2 for example always maintains a 1x connection (SRLTE) with Sprint, so if LTE is too weak for a VoLTE call, then Sprint can just send it via 1x and pretend the phone isn't on LTE. With a Verizon SIM, my phone often will maintain SRLTE as well, at least for a little while before going LTE only. So I expect Sprint would keep SRLTE active all the time until they're confident in their network density. If they can't have different disconnect thresholds for different devices, then yeah we might start seeing drops to CDMA more frequently unfortunately. Sent from my Pixel 2 XL using Tapatalk

Not contiguous. SF is one example. There's a spectrum squatter (owned by AT&T) right in the middle of their allocations in the city. They can do at most 2 contiguous carriers. Once you get further out you start to see 3 carriers. Sent from my Pixel 2 XL using Tapatalk

Oh interesting. I last successfully used it in January 2017 in Peru, but none of the carriers had LTE deployed. When I tried in Indonesia a little over a year ago, it gave me this error (but I assumed it was just a temporary bug). So maybe it doesn't let you actually change it while connected to LTE. Sent from my Pixel 2 XL using Tapatalk

I think some models support OTA updates. I want to say they aren't completely automatic, and you have to trigger them by issuing a modem command (the same way you control the modem in general). The modems expose a serial interface that you use to issue commands and see the result. For the modem I have, MC7455, the updates are not OTA. You have to flash them manually. It's still a pretty easy process, though the last update caused a BSOD on Windows when it completed. But everything was updated and fine after that. The modems often have 2 modes they can operate in, MBIM and QMI. MBIM I think is more established and has broader support in software, but I think is mostly a legacy/compatibility mode on the modems. QMI I think has lower overhead and is the protocol that they're moving towards. I believe it's a Qualcomm protocol. Sent from my Pixel 2 XL using Tapatalk

You can force it to roam on any of the carriers that Sprint has an agreement with. Under wireless settings, you can select which network you want it to use. Sent from my Pixel 2 XL using Tapatalk

The aggressive roaming has stopped for me. Yesterday and today, I was driving through a Sprint dead zone for 10-15 minutes. -110 1x (basically useless, you can't make a call on this stretch of highway, it drops almost immediately) and no evdo. My car has AT&T and had full service, but my phone wouldn't roam despite having no usable data. Sent from my Pixel 2 XL using Tapatalk

Here's a spreadsheet that I put together that shows the new GCI layout, along with some example setups (with earfcns). https://docs.google.com/spreadsheets/d/1Zhb37AO4gh2kWOz598FBrWKK478RvujRzN1G4TDLcF4/edit?usp=sharing

I agree, build your own. Sierra Wireless modem with a USB enclosure for it will let you use any router that supports Openwrt basically. I'm using one with a Netgear R7800 and it works very well. The Sierra Wireless MC7455 has a bug that causes it to disconnect 1-2 times a day that may be fixed in the newest driver (I'll know for sure within a couple days), but is the only one that supports B25. They have other modems that don't have this issue, but lack B25. If you don't need B25, get a model that does 3xCA B41. Check out the ROOTer firmware (build of openwrt with mods for LTE modems) https://www.ofmodemsandmen.com the developer is almost done with a new build using the latest openwrt, and you can get the pre-release builds on their forum thread (might be required for some routers). He seems willing to add any routers not listed as long as they work with openwrt. Sent from my Pixel 2 XL using Tapatalk