I did double check, but it was doing about 2GB a day at 2.4 GHz and about 3GB a day on 5GHz. Now it's maybe couple hundred MB a day. Perhaps it's a slow rollout.
To be honest, I haven't tried VoLTE on MB yet. Sounds like it's time to give it a whirl...
BTW. This is all in San Francisco.
All depends on the terrain/intended coverage area, sector alignment/tilt and antennas used.
Wide beam antennas in a 4-sector 90° configuration can actually do a lot of damage to the SNR. Alternatively narrow beam antennas at a 3-sector 120° can leave big coverage holes between sectors. It's a pretty interesting balancing act.
I am not enjoying this t-mobile 5G in Astoria Queens or even LTE for that matter. Here is comparison between the 2 today at Astoria park. This area had even faster speeds before Sprint 5G was shut down. T-Mobile really needs to expand the N41 coverage outside of Manhattan asap. Some how Sprint really delayed it fast. Sent from my SM-G988U1 using Tapatalk
I'm still getting 50-90 Mbps (depending on how close I am to it). You might want to double check that it didn't fall to 2.4 GHz. Mine is Ethernet backhauled though.VoLTE has been live for many months on all the femtos. They don't need to cap anything for it to work. In my experience using LTE backhaul on a magic box with VoLTE, it didn't do well at congestion control (was cutting out because the donor was congested), so I'm skeptical that they tunnel VoLTE over a prioritized EUTRA session on relay. So if they aren't doing something as "basic" as this when they completely control the network, they almost certainly won't be doing anything on wifi or Ethernet backhaul to try to give VoLTE special treatment. Sent from my Pixel 4 XL using Tapatalk