Jump to content

ingenium

S4GRU Premier Sponsor
  • Posts

    1,717
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by ingenium

  1. T-mobile has the 5G indicator set to show when connected to any site that supports EN-DC, regardless of whether or not your phone is connected to NR. T-mobile allows NR aggregation between different sites (ie, you can be connected to one site for LTE, and another for NR). Since to my knowledge, no phones at the moment support B71 as the anchor band for N71, it's not uncommon to be using B2 as an anchor on a closer site, and N71 from a further site. For this to work, the sites without NR need EN-DC enabled. So what ends up happening is that if you're near a site that has NR deployed, it shows 5G in the indicator even if you're not connected to NR. Sprint does not have their 5G indicator configured this way. Also, with N41, usually using B41 as the anchor band, you're like getting NR and LTE from the same site. I'm not sure if Sprint even supports NR+LTE from separate sites. Sent from my Pixel 4 XL using Tapatalk
  2. I've had the choppiness while driving very briefly, and this was because I was on b41 and it got less than ideal. In those cases my phone goes to b26 and stays there for the duration of the call. As it should in my opinion. Congestion isn't an issue with VoLTE, and it uses minimal bandwidth, so it makes sense to use low band, especially when moving, to increase call quality. Normally I almost never drop B41, so the move to b26 was definitely an optimization for VoLTE. As soon as I ended the call, my phone moved back to b41. I'll add that I have noticed that I'll occasionallyhave brief cutouts when doing VoLTE via my MB or Airave (both with Ethernet backhaul), but not on macro VoLTE, and that wifi calling sounds better (I have a very good wifi setup though). So I generally keep my phone set to wifi preferred. VoLTE to/from vowifi handoffs have been flawless for me, minus the brief blip of silence during the handoff, so I see no reason not to do it. Sent from my Pixel 4 XL using Tapatalk
  3. VoLTE has always been perfect for me on Sprint. Crystal clear. I definitely can't say the same for 1x, which is complete robo garble all the time (every third word cuts out) due to congestion. At least that's the case in Pittsburgh and San Francisco / Bay Area. That being said, I've been on rural towers with a very weak 1x800 signal and had it sound very clear. So it's definitely a capacity problem. When 1x becomes congested, it cuts quality to increase capacity. In cities this results in absolute garbage calls. Sent from my Pixel 4 XL using Tapatalk
  4. They should be able to push a SIM update over the air. Sent from my Pixel 4 XL using Tapatalk
  5. I think it still works, or at least I saw someone replaying logs that way recently. I believe the non-licensed version of NSG will let you replay a log now? But I'm not certain. 5G NR is only in the beta of NSG at the moment (v 3.3.1). I have a copy if anyone with a rooted 5G device needs it. Sent from my Pixel 4 XL using Tapatalk
  6. The issue with forcing people onto the new network when they upgrade their device is that it can cause churn if the network isn't ready yet. For example, in area where I typically am, Sprint's network is much denser than T-mobile, and I'd be giving up coverage until T-mobile rebuilds Sprint sites. It would force some of my family members to change providers since they'd have no service at home. I suspect/hope there will be a time (a year? More?) where you can still stay on Sprint as the default network if you want. People with iPhones or Pixels can use either network as is, so the devices are already ready. They might be able to just push a SIM update OTA eventually, but I've heard that providers have sometimes bricked a bunch of SIMs in the past doing that. Sent from my Pixel 4 XL using Tapatalk
  7. I can only find an eBay listing of a C5000, no other info, but it appears to be an LTE only femtocell. There's no CDMA status light. It's probably from the Airave 3 days, but it's not an Airave 3. It's possible that it was an engineering unit and is on an engineering account at Sprint instead of your personal account. Some of us have engineering Magic Boxes (pre-release models) that are on internal engineering accounts instead of our personal accounts. Sent from my Pixel 4 XL using Tapatalk
  8. We can't tell what it is without an exact model number or pictures. Sent from my Pixel 4 XL using Tapatalk
  9. Airvana is an Airave 2.5 I believe (might be the 2.5+). No LTE. All Airaves have beeps on CDMA. Even the 4. If you don't hear the beeps, you aren't using the Airave. Sent from my Pixel 4 XL using Tapatalk
  10. Same here. It definitely wasn't live yesterday for me, but works today. Sent from my Pixel 4 XL using Tapatalk
  11. I wonder if they had issues with the Airave 3. The 3 always used the earfcn of the first macro carrier. I personally didn't notice any issues with interference with it. I think the bigger concern may be mixing LTE with NR on the same frequency. Specifically with the timing config. I was under the impression that NR can dynamically adjust the timing for upload: download, but LTE is pretty sensitive to everything having the same timing config. Sent from my Pixel 4 XL using Tapatalk
  12. Yeah, but it's not free. You incur overhead from having it enabled. If I remember correctly it's in the 10-20% range. So it's not insignificant. I'm not sure if it's the sort of thing that can be improved upon with software or hardware updates. Sent from my Pixel 4 XL using Tapatalk
  13. Supposedly it has for years. But never did for me (self hosted VPN). I'm not sure how they detect it... Possibly DPI, or possibly by just matching traffic to the popular VPN providers. Sent from my Pixel 4 XL using Tapatalk
  14. There shouldn't be an OTA to enable it. It's on the network side, and a configuration change that they make there. It would make the networks appear as one unified network, versus right now they're still separate networks and can't handoff active data sessions (or handoff period. Generally speaking, unless you lose service, the network completely controls handoffs between towers and bands. At the moment, the Sprint network will not move you to T-mobile, and vice versa; they aren't integrated like that yet). Generally the Sprint network is still preferred at the moment, but if some config change or lack of service or something kicks you off Sprint, it will move to T-mobile and it will probably be "sticky" and not want to move back to Sprint easily. When this happens, and airplane toggle will probably put you back on Sprint. This is because they are still separate networks. The information I've seen indicates that they will be actually merged sometime before the end of June. I don't know how they'll prioritize the bands in the merged network, but that's also something that is done on the network side, and can vary from region to region (and even tower to tower). Sent from my Pixel 4 XL using Tapatalk
  15. Something indicating T-mobile while on the call, such as T-mobile LTE bands. Also make sure that the field test screen isn't stuck. Sent from my Pixel 4 XL using Tapatalk
  16. T-mobile roaming got uncapped today on my home site. So seems like it was a gradual rollout versus an all at once thing. No VoLTE, calls went over 1x. Sent from my Pixel 4 XL using Tapatalk
  17. Do you have engineering screenshots showing it while on the call? Sent from my Pixel 4 XL using Tapatalk
  18. You didn't mention initially that it changes to b12. It sounds like there's something wrong with the device. It honestly wouldn't surprise me if Airave 3s are completely broken now. They've been end of life for years. It's possible that it was originally placed on an admin/corporate account instead of yours. And/or it was deactivated because it's end of life. Either way, it probably needs replaced with something else. Unfortunately I don't know if they have anything that would work for you. All the femtocell solutions use the MB config file now, and will only work in areas where Sprint has the B41 license for MBs, which personally I think is stupid, but that's just the way it is. Nothing uses the macro earfcn anymore. So you might be limited to roaming and wifi / wifi calling. Now that the merger is complete, and T-mobile intends to move all B41 over to N41 and turn off LTE on it, I doubt they would be releasing any new B41 femtocells. T-mobile has femtocells that I think use B2 or B4/66, but I doubt they would give you one, and I'm not sure if "roaming" would even work on it yet. Sent from my Pixel 4 XL using Tapatalk
  19. That's normal and exactly how it's supposed to function. Sent from my Pixel 4 XL using Tapatalk
  20. The Airave 3 can't do VoLTE. They really messed up IMS on it with one of the last updates pushed before marking it EOL. This also affected eCSFB (and texts on non SRLTE devices). So you could be having issues related to that, which is affecting your calls. You also could just be on 1x800, since the 3 doesn't have a 1x800 beacon. If the magic box is not licensed for your area, the Airave 4 won't work either. They use the same config file and use the same earfcn. Unlike the Airave 3, which used the macro earfcn. Let us know if you manage to get it to work, but you almost certainly won't have LTE from it unless something changed. Sent from my Pixel 4 XL using Tapatalk
  21. I guess they could keep it throttled on some sites. This particular site is a colocated Sprint and T-Mobile site (no other carriers on it), and Sprint's site density in this area is also higher than T-mobile, so they probably don't expect Sprint customers to be on it at all. Sectors oriented slightly differently though. Sent from my Pixel 4 XL using Tapatalk
  22. It's still throttled to 5 Mbps by the eNB in Pittsburgh. Sent from my Pixel 4 XL using Tapatalk
  23. If they eventually stop new activations, what happens to people on family plans? Does everyone need to get a new SIM at once and the whole plan migrated to T-mobile for one person to upgrade their device? Sent from my Pixel 4 XL using Tapatalk
  24. For me it started on the most recent beta. 4.592b. Sent from my Pixel 4 XL using Tapatalk
  25. I have this issue as well (just shows 1x in my case), but it populates once I turn off wifi. I see you're on wifi in your screenshot. Does it work when you turn it off? Sent from my Pixel 4 XL using Tapatalk
×
×
  • Create New...