ingenium

I use two of these https://ltefix.com/shop/antennas/700-2700mhz-15dbi-4g-lte-directional-antenna/ They work pretty well. Right now I'm using them on AT&T on a site that is 3.4 miles away. I get about -110 to -115 on a B2 20 MHz carrier, which gives me ~20 Mbps down. On my phone with an AT&T SIM, I can just barely get a B12 signal that doesn't work particularly well. The frequency of those antennas works for Sprint as well. The Sprint site is much closer in my case, but due to antenna positioning and topography doesn't work as well. Just make sure you orient the antennas properly for MIMO. Sent from my Pixel 3 XL using Tapatalk

The lack of ping response doesn't necessarily mean anything. My Airave 4 doesn't respond to pings on one of its IPs, but does on the other (but only if I do it from the same subnet/vlan as the Airave, which is odd. Using a different subnet it won't respond). My Magic Box responds, even from a different subnet. My guess is that something on your network is interfering with the Airave's ipsec VPN tunnel. It sets up two, one for LTE and one for CDMA. Perhaps something is only allowing one tunnel to be created, though I can't think of why/how. Or for some reason the CDMA side doesn't have internet access. I would contact Airave support and see if they can login to your Airave and see what the problem is. If you're able to do a packet capture on your network, that can be used to help diagnose the issue as well. Sent from my Pixel 3 XL using Tapatalk

I would try factory resetting it. Sent from my Pixel 3 XL using Tapatalk

No SIM is needed. You can set it up with eSIM. Such a shame they removed original quality photos backup. That was one of the things keeping me on the Pixel line. Thinking about jumping to One Plus now. Sent from my Pixel 3 XL using Tapatalk

It's not more likely to stay in 1x in the future. Sometimes the phone associates a 1x or 1x800 connection with a certain LTE connection, but in my experience once it switches to 1x800, it will hang onto it until it loses it (either no signal, or a new PRL region is encountered). The region thing was useful to me, because I'd be on 1x800 in more rural areas but I'd enter a different geo region when I got back to the city, so that caused me to switch back to 1x1900 (1900 is scanned before 800 in the PRL, but they have the same priority). Otherwise, you have to manually switch back to 1900 each time you enter Airave coverage if you usually drop to 800 coverage outside your house. And yes, they should swap it no problem. Sent from my Pixel 3 XL using Tapatalk

VoLTE technically works on the MB and Airave 4 if you force the phone to ignore the whitelist (only possible on a rooted Pixel 3 running Pie. Not possible in 10). But they haven't been whitelisted the devices yet. It's hypothesized that there is a whitelist of TACs that have VoLTE. So all Sprint needs to do is push a TAC change to the femtos. From a software perspective, they're ready (other than the relay link on the MB not being prioritized). VoLTE 100% does not work on an Airave 3, even forced, because the final update for the device broke IMS. The 3 shouldn't be used with any device that uses IMS (ie, any VoLTE device), because it will break SMS as well. This also includes pre SRLTE devices (2016 era and earlier, any device that uses eCSFB). Your only real solution is to use wifi calling and wait for an update to fix the location issue. Wifi calling is identical quality to VoLTE (they're the same system). That's weird and unfortunate that Samsung tied it to your location like that, and broke the location. I'm surprised it doesn't just use what cached/most recent location from Google Play Services. In one of your previous messages, you said the call drops when the signal goes to 0. You mean it drops when you're on the macro network on a call, right? Or are you saying that it drops on wifi calling when it loses the tower signal? Sent from my Pixel 3 XL using Tapatalk

1x isn't necessary, but a non wifi connection is. Can be LTE, roaming, etc. It doesn't seem to run over the ipsec tunnel. At least it was in January when I last tested. Sent from my Pixel 3 XL using Tapatalk

It doesn't seem to actively use 1x and instead just listens and maybe registers. It is kind of annoying that the signal bar becomes the 1x signal, but that's just the way they do it. I don't think it impacts battery much at all. The battery usage is from transmitting. Sent from my Pixel 3 XL using Tapatalk

How are you orienting the antennas? And which antennas are you using? Sent from my Pixel 3 XL using Tapatalk

Possibly. They could also be on wifi calling or be using Calling+. These both use the same codecs and system as VoLTE. Calls to 1xAdvanced (CDMA HD voice) won't cause one of the HD codecs to be used on VoLTE, so that can be ruled it. Sent from my Pixel 3 XL using Tapatalk

Anyone have NSG to check? Sent from my Pixel 3 XL using Tapatalk

Wait you never even get to login to your Sprint account? I don't think that's Sprint related then. This might be a silly question, but you're on wifi when you try to add the eSIM right? Do you have a regular Sprint account? Or is it through an MVNO? Sent from my Pixel 3 XL using Tapatalk

I'm not sure if any carrier is doing VoLTE roaming yet, are they? The tricky part might be setting up the EUTRA session? I just know it's not at straightforward as regular LTE data roaming. Sent from my Pixel 3 XL using Tapatalk

Could be. I have a Google purchased Pixel 3 XL and it worked fine. You get to the step where you login to your Sprint account and select the number right? Sent from my Pixel 3 XL using Tapatalk

It will definitely have VoLTE at launch. Since the 3 and 3a both officially have it now with the Android 10 update. All newly released phones have VoLTE out of the box, it's older phones where Sprint is dragging their feet. Sent from my Pixel 3 XL using Tapatalk

No. See my comment above. If you remove -w from the script and save it, it won't wipe data. Sent from my Pixel 3 XL using Tapatalk

Are you rooted? That can prevent the OTA from applying. If you aren't rooted, download the full factory image and flash it with adb. This will not apply though if you're currently rooted, and will also throw an error. If you are rooted (or bootloader unlocked at least), get the factory image and remove "-w" from the one line in the .bat (Windows) or .sh (Linux/Mac) file, so that it won't wipe your data. Leaving -w wipes the device, removing it preserves data. This is guaranteed to work. Sent from my Pixel 3 XL using Tapatalk

Yup! It came with the Android 10 update. Glad to have it officially supported instead of requiring a hack. The question is, does it continue to ignore the VoLTE flag on the eNB (ie, will it work on a Magic Box or Airave), unlike other VoLTE enabled devices? I've been out of the country since it came out, so haven't been able to test. Sent from my Pixel 3 XL using Tapatalk

It depends on the market. In Pittsburgh and other cities, I rarely see B26, and when I do, it performs well. I think in less urban areas there is higher B26 usage, but urban areas account for a majority of traffic. So that will affect the % of traffic on B26 in total. On the other hand, there are some cities where Sprint is lacking. The Bay area (SF, Oakland, Berkeley) doesn't have sufficient density for the topography, despite having a ton of sites. I'll be on B25 or B26 a lot, and it can be painfully slow. Even B41 gets congested, due to only 2 carriers on most sites (and only 2xCA on ones that do. Non contig B41 spectrum there). Sent from my Pixel 3 XL using Tapatalk

About time haha. Assuming this means FDD-TDD CA. Sent from my Pixel 3 XL using Tapatalk

I would love an 8GB Pixel. The question is, what 5G bands will it support? Verizon or Sprint and T-Mobile? Sent from my Pixel 3 XL using Tapatalk

It's hard to make further suggestions without being able to play with your router directly and see exactly what settings are enabled and disabled, or getting a packet capture to see what's happening. Lilotimz's suggestion is probably your best bet for now. Sent from my Pixel 3 XL using Tapatalk

I believe it is live in some non-Samsung markets, but I'm not sure. It's been coming soon for a while now. Sent from my Pixel 3 XL using Tapatalk

Yes. The Pixel 3 can do TDD-FDD CA I believe, as well as many other devices. The way it would work is B25 or B26 is the PCC and is used for upload (no UL CA). Then B41 is used as the SCC for supplemental download. Presumably they can prioritize B41 on the downlink over the PCC (to keep B25 capacity for when B41 is too weak), but I'm not sure if this is actually possible. Either way, in some markets where B25 is 15x15 and B41 coverage is very good, B25 is can be unused and has tons of capacity. Same for B26. It would also help at events where the network puts everyone on B41 which is unusable from congestion, but B25 and 26 are wide open. That's a decent amount of extra capacity to add. Sent from my Pixel 3 XL using Tapatalk

Did you try Calyx? That was one person reporting potential throttling (I was one of the commenters on the post) over a year ago, and I was still unthrottled when I last used Calyx a few months ago. I suspect his site just got congested (which happened on my site as well. Verified with my Sprint phone getting the same performance). Calyx is coded as a "Spectrum Mobile Broadband 30GB" plan, which should not be throttled or deprioritized. It is a metered plan just like the one you're on now. It incurs overages after 30GB (expensive on paper, like $20 or $30/GB) in theory, but Calyx / Mobile Citizen have basically an unlimited bucket that these overages come from.@lilotimz can explain it better, but basically Sprint doesn't charge them for the overages. Sprint would need to re-code the plan I believe to throttle it, since the Spectrum Mobile Broadband plan is not throttled since it charges for overages. Even if it did start getting deprioritized, if you can get a Magic Box and have it get a usable signal, it should bypass deprioritization. The deprioritization is done on a per eNB basis. Since you will be the only person on the MB eNB, it will be seen as uncongested and not deprioritized. In theory the MB is actually prioritized over other devices on the macro / donor. If your setup is working for you and you're happy with it, that's fantastic and is what really matters. But there may be ways to save you a substantial amount of money for basically the same service (that is less complex), which is why we're suggesting them. Sent from my Pixel 3 XL using Tapatalk