Jump to content

ingenium

S4GRU Premier Sponsor
  • Content Count

    1,500
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by ingenium

  1. Speculation is that it's some Qualcomm limitation or something, but yeah it's odd. Sent from my Pixel 4 XL using Tapatalk
  2. Yes. The McLaren version I believe. Interesting that it disables B13 and B14. https://fccid.io/2ABZ2-EE143 Sent from my Pixel 4 XL using Tapatalk
  3. This recently appeared on the FCC site. Sent from my Pixel 4 XL using Tapatalk
  4. I've noticed it too. It seems to be more picky about a GPS signal now. For example, if I'm driving and my phone is in my lap, it won't record as many points as it does when it's sitting upright in my cup holder. Sent from my Pixel 4 XL using Tapatalk
  5. VoLTE doesn't work if it's not using LTE backhaul? That would be really surprising if true. Sent from my Pixel 4 XL using Tapatalk
  6. Yeah it should be able to go faster, but honestly does it really matter? On macros and SCs, the added speed is more about the capacity to handle more users. But on a MB where you'll likely only have a couple users (or at least only a couple simultaneous users), I don't know why faster would make a difference on a phone. I doubt anyone would notice 80 vs 140 Mbps outside of speed tests. Now that I think about it, I wonder if something internally is limited to 100 Mbps. If it was, that, combined with the ipsec VPN overhead, might explain the ~80-85 Mbps max speed. Sent from my Pixel 4 XL using Tapatalk
  7. Oops, typo on my part. I meant as postpaid. I have that prepaid plan now. Sent from my Pixel 4 XL using Tapatalk
  8. This is the setup that I use. Slow DSL as backup to AT&T LTE (DSL is also used for DNS and wifi calling). Nighthawk as the router. How do you get the iPad plan as prepaid? Is there any different other than being prepaid and the price? Contract? Sent from my Pixel 4 XL using Tapatalk
  9. No, the radio is only capable of B41. It can be resolved though if they quit using it he Magic Box config for the Airave 4. Right now, the 4 uses the same earfcn as a Magic Box, and uses the same availability restrictions as a result. And in some markets, Sprint doesn't have enough spectrum for 4 or 5 B41 carriers (macro + SC + MB). But they always seem to have enough for at least 1 B41 carrier. The Airave 3 used the same earfcn as the first B41 carrier on macros, which allowed it to be used pretty much anywhere. If Sprint setup a separate Airave 4 config like they did with the 3, this wouldn't be an issue. They could also edit the current Airave/MB config to just use the macro earfcn when non-LTE backhaul is used, but I'm not sure if the config actually allows that type of setup. Sent from my Pixel 4 XL using Tapatalk
  10. ingenium

    Pixel 4/4XL

    Sorry, I edited the post and left in the 1x (meaning single carrier) by mistake. It can't do B26+41 at all. CA combos: 2xCA: 25-25, 25-26, 25-41, 41-41 3xCA: 25-25-25, 25-25-26, 25-41-41, 41x3 And 4x and 5x CA B41. 2xCA upload on B41. Like the Pixel 3, it's also limited to 10 MIMO streams. So you can do 4x4 on 2 B41 carriers, but only 2x2 on the last one. Likewise, with 5xCA B41, it can only do 2x2 per carrier. No 4x4 at all. No idea when Sprint will push the update to enable FDD-TDD. Sprint Speed [emoji769]. Could be next week, could be 6-12+ months. Magic Boxes and Airaves for example have been capable of VoLTE for 11+ months, just waiting for Sprint to whitelist them. Things can be ready and working but just sit for a year for seemingly no reason... Sent from my Pixel 4 XL using Tapatalk
  11. ingenium

    Pixel 4/4XL

    No. The menu is exactly the same on the 4. You can enable and disable individual bands, but not carrier aggregation combinations. Sent from my Pixel 4 XL using Tapatalk
  12. ingenium

    Pixel 4/4XL

    It's not enabled on phones. He had to force enable it on his phone. Can't do that on Pixels. So we have to wait for Sprint to push the network config update to devices to tell them they can use it. Sent from my Pixel 4 XL using Tapatalk
  13. ingenium

    Pixel 4/4XL

    Apparently the Pixel 4 is capable of B25 + 2xCA B41 (3xCA total), no B26 + 1x B41, and 2xCA upload B41. So whenever Sprint enables it, it should work. (Edited with correct CA combos)
  14. ingenium

    Pixel 4/4XL

    Speed test when Sprint enables it, or with NSG once Sprint enables it. Or possibly FCC docs, but I don't know if they publish that. Lilotimz would know. Sent from my Pixel 4 XL using Tapatalk
  15. ingenium

    Pixel 4/4XL

    It's the same SoC and modem, so yes it's capable, unless Google did something with the RF front end to disable it. Sent from my Pixel 4 XL using Tapatalk
  16. ingenium

    Pixel 4/4XL

    His speed is because of FDD-TDD CA. B25 is being used for upload, possibly with 4x4 and 64 QAM up. The NSG developer doesn't have a Pixel 4 to test with. Someone sent him logs from trying to run it, and the developer basically said "wtf?". So the Pixel 4 is doing some weirdness. I'm pretty sure he'll be able to get it working whenever he gets a 4 to test with, but he's based in China and Pixels aren't exactly easy to come by there. There was a similar issue with the 3 last year. I think he got it working around mid December, so fingers crossed that it's soon. Sent from my Pixel 4 XL using Tapatalk
  17. ingenium

    Pixel 4/4XL

    No benefit for limiting streams, Google just cheaped out on engineering the RF front end. NSG is Network Signal Guru. It's a root application that ties into the Qualcomm diagnostics port on the modem. It basically let's you see everything. Here's a screenshot showing 3xCA B41 from my Pixel 3 XL recently Yes I'm in a Samsung market. I don't have another device to test with simultaneously. But I believe B41 with 64 QAM upload maxes out around 12 Mbps. So if I can get 17-20 Mbps, then it's doing 2xCA. That speed isn't possible on a single B41 carrier unless 4x4 is used with rank 3 or 4. Sent from my Pixel 4 XL using Tapatalk
  18. ingenium

    Pixel 4/4XL

    With 3xCA, I think the 3 and 4 are both limited to 4x4 on 2 carriers and then 2x2 on the third? Or else it's 4x4 on one carrier and 2x2 on the other 2. Basically neither can do 4x4 on all 3 carriers. Since the engineering screens are basically broken, the only way would be to hope you have a good signal in a store and run a speed test on B41. See if the upload is higher than a single carrier can do. Or wait until NSG gets support for it and I can check and let you know. I'll try to remember to run a speed test when I'm near a site and see what my upload is. Sent from my Pixel 4 XL using Tapatalk
  19. ingenium

    Pixel 4/4XL

    The 4's SoC / modem is capable of all of those. It's possible that Google gimped the RF front end in a way that disables them (like they did with limiting MIMO streams), but they should all work. Generally Pixels support all CA combos that the SoC does. Sent from my Pixel 4 XL using Tapatalk
  20. Kölbi I believe has the best coverage, and should work pretty much everywhere. But they're also the most congested. They are the state owned provider. Movistar is pretty good, with very good coverage and good speeds. I've used prepaid SIMs on both when there for several weeks, along with Sprint roaming (open world, so no speed throttling). When I was there in January, I found their coverage to generally be the same now, whereas 5-6 years ago (pre LTE) Kölbi was king. The only differences are in very rural, mountainous areas, where you might have no service on one but BARELY have service on another (enough to send a text for example, but not much else). It's interesting that your phone dynamically switched between them. I was able to force mine to use any provider with my Sprint SIM, but when left on automatic it always preferred Movistar. Even after locking it to a provider, it would eventually go back to automatic on its own and switch to Movistar. Movistar is generally Sprint's preferred roaming partner in any country where they have service. Sometimes that's great, and sometimes it's awful haha. Sent from my Pixel 4 XL using Tapatalk
  21. ingenium

    Pixel 4/4XL

    All can do 3xCA B41. The Pixel 2 I think can also do 2xCA B25, along with the 4. Not sure about the 1. Only the 4 can do 4x4 MIMO I think, but at least in Samsung markets Sprint isn't using rank 3 and 4 yet so there's no speed improvement with it, only improved signal quality. The 4 can do 256 QAM, but I'm not sure about the others. The 2 might be capable as well. The 4 should also be able to do B25-41 and B26-41 CA. It's in testing in some markets, but there's no way to force it on Pixels unlike Samsung devices. Who knows when Sprint will actually push out the carrier provisioning to turn it on on devices. The 4 can also do HPUE on B41, but in my experience HPUE doesn't help much. When the signal is low B41 is crap and sending messages can fail. It seems like it just makes the phone hold onto B41 past the point of being usable. The 4 can also do B41 2x UL CA I think, and the others can't. Honestly, the only thing that would make a real world difference in my opinion is FDD-TDD CA, but it's almost certainly not live yet on the 4 (NSG isn't working on the 4 yet so no way to confirm, but I never saw FDD-TDD on the 3 and it should be capable of it as well). And the fact that the 4 supports wifi calling and VoLTE. Sent from my Pixel 4 XL using Tapatalk
  22. Not that I've been able to find. Specs only seem to list what bands it can use. Since it has the RF front end for each of those bands, and since the SOC supports that CA combo, I don't see why it wouldn't work. The only thing is that Pixels are limited in the number of simultaneous streams (due to the RF front end), which doesn't really matter for Sprint because while they're using 4x4 MIMO, they aren't actually utilizing all the streams, at least in Samsung markets. You only see rank 1 or rank 2. Not 3 or 4. Rank 3 or 4 is required for the additional throughput on 4x4 MIMO. Sent from my Pixel 4 XL using Tapatalk
  23. If I remember correctly it's also possible on the Pixel 3. Not sure about the 2. Pixels don't have a CA combos screen like Samsung (and maybe LG) phones. The only way to confirm to my knowledge is with NSG when it's active. Google disables the diagnostic port so you can't use Qualcomm tools to pull the CA combos directly from the modem. Sent from my Pixel 4 XL using Tapatalk
  24. I think some Samsung phones support it, but it's disabled in the US at the request of the carriers. For a single connection, it would need to utilize Multipath TCP. And the destination server would also need to support it (which is rare). The only major deployment that I'm aware of is Apple using it for I think FaceTime, and maybe other Apple services. It's done so that when connectivity changes (for example going from wifi to LTE) there is no interruption. I don't know if they actually aggregate the connections otherwise. It's possible that Sprint also does it for VoLTE -> Vowifi hand-off. I know that Vowifi uses an ipsec tunnel (UDP), but within that tunnel the SIP connection uses TCP, which surprised me. This could be a valid reason for using TCP I guess, to allow seamless transitions. Sent from my Pixel 4 XL using Tapatalk
  25. The MB maxes out at about 85-90 Mbps, regardless of backhaul. It seems to be some kind of hardware limit, either on the LTE eNB or on the ipsec tunnel. The Airave 4 is exactly the same. Both my Airave and MB are connected via Ethernet on a gigabit connection and max out at that. Sent from my Pixel 4 XL using Tapatalk
×
×
  • Create New...