Jump to content


S4GRU Premier Sponsor
  • Content count

  • Joined

  • Last visited

  • Days Won


ingenium last won the day on December 10 2016

ingenium had the most liked content!

Community Reputation

933 Trusted


About ingenium

  • Rank
    Member Level: 4G WiMax

Profile Information

  • Phones/Devices
    Google Pixel 2 XL
  • Gender
  • Location
    San Francisco, CA & Pittsburgh, PA
  • Here for...
    4G Information

Recent Profile Visitors

3,398 profile views
  1. 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
  2. ingenium

    Official Magic Box discussion thread

    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
  3. ingenium

    Official Magic Box discussion thread

    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
  4. 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...
  5. ingenium

    Sprint Tmobile merger Disc.

    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
  6. ingenium

    Network Vision/LTE - Northern Jersey Market

    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
  7. 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
  8. ingenium

    Network Vision/LTE - SF Bay Market

    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
  9. ingenium

    Network Vision/LTE - SF Bay Market

    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
  10. ingenium

    Network Vision/LTE - Northern Jersey Market

    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
  11. 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
  12. 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
  13. ingenium

    Essentially a sprint exclusive.

    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
  14. ingenium

    Network Vision/LTE - SF Bay Market

    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
  15. 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