Jump to content


S4GRU Premier Sponsor
  • Content Count

  • Joined

  • Last visited

  • Days Won


ingenium last won the day on March 23

ingenium had the most liked content!

Community Reputation

1,214 Wireless Expert


About ingenium

  • Rank
    Member Level: 4G WiMax

Profile Information

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

Recent Profile Visitors

5,359 profile views
  1. You'll be in an inconsistent state. LTE will stop working immediately and switch to the new SIM. CDMA I believe will be stuck on the old one until it's powered off. Or at least it will prevent the 7 from completing setup or using CDMA until it is. I don't remember if the 6s or 7 use eCSFB or SRLTE, but either way you'll likely have CDMA issues as well. Sent from my Pixel 4 XL using Tapatalk
  2. ingenium

    Pixel 4/4XL

    PRL isn't just for roaming. It's for native CDMA too. If you didn't have a valid PRL then you wouldn't be able to use CDMA. It basically says "these sites are native, these are roaming, try them in this order and prefer this group over this other group". You can also try the #*#*72786*#*# dialer code. That will wipe CDMA provisioning and force it to run again. But like I said, as long as CDMA works, I wouldn't worry about it. Sent from my Pixel 4 XL using Tapatalk
  3. ingenium

    Pixel 4/4XL

    Does CDMA work? If so, I wouldn't worry about it. Sent from my Pixel 4 XL using Tapatalk
  4. ingenium

    Pixel 4/4XL

    I'm also using eSIM. No idea why yours is like that. Seems like it hasn't actually downloaded the PRL or something. Sent from my Pixel 4 XL using Tapatalk
  5. This discussion just made me wonder if Sprint GCIs will have to change when MOCN is deployed. That would be a mess for mapping and tracking... Sent from my Pixel 4 XL using Tapatalk
  6. ingenium

    Pixel 4/4XL

    Yeah devices usually take a bit to find a MB initially. My PRL is fine. Sent from my Pixel 4 XL using Tapatalk
  7. My issue seems to be tied to one tower (MMIMO equipment). About once a year it has a similar issue, where it randomly prevents UE attachments. I get handed off to it (or switch earfcns on B41), and get kicked off Sprint's network and start roaming. Airplane mode tries to connect to the same tower, and triggers it again. Nearby towers are fine. I was able to confirm that T-mobile roaming is indeed throttled to 5 Mbps. Well, 4.9 Mbps to be exact. Normally with Sprint roaming, such as with AT&T, Sprint is doing the throttling at their gateway, because they're paying per megabyte. But in this case, it's T-Mobile that's setting the throttle. Also, Sprint roaming is QCI 7 instead of 6, so it's at a lower QoS priority than T-Mobile customers. Sent from my Pixel 4 XL using Tapatalk
  8. Sprint changed the default QCI from 9 to 6. Matching T-mobile's. Another sign of prep for MOCN I think. I've also been roaming on T-Mobile at home all day. Going back and forth between Sprint and T-Mobile macros, despite having an Airave and MB at home... Haven't connected to either all day. 3xCA on T-Mobile, but shit performance. Sent from my Pixel 4 XL using Tapatalk
  9. "Roaming" will be whenever they enable MOCN. Could be as early as the closing date if they're ready. We've seen signs that they're preparing for it now and making the necessary configuration changes. T-Mobile towers will appear as native, with the Sprint PLMN. And vice versa. They'll do some behind the scenes "magic" to basically merge the RAN / radio layer, but keep the backend cores separate. As for MBs, my guess is we'll have a while. It depends when they need to refarm the MB earfcn for 5G. In which case they'd probably move the MB to a macro earfcn and use B2/B25 for backhaul. Sent from my Pixel 4 XL using Tapatalk
  10. It likely just needs a software update to enable it. Extended LTE I'm guessing is B71, which it probably doesn't support. VoLTE is 100% software though. Sent from my Pixel 4 XL using Tapatalk
  11. Sprint TACs have changed to match T-Mobile TACs. This is a prerequisite for MOCN. So they might roll that out soon after the merger completes. Would basically merge the radio part of the networks, but keep the cores separate. Sent from my Pixel 4 XL using Tapatalk
  12. It's a physical limitation of the antennas I believe. Current antennas used for LTE are the same. There's also a power limit per port, but I don't know how that translates to all in one units like MMIMO. For example, on PCS, when Sprint had more CDMA carriers on air, they were limited in what they could deploy for LTE in the same way. No 4x4 for example until CDMA carriers were pruned down. I'm pretty sure it was because of power limitations per port that would be exceeded. As I think about it more, I think the B41 MMIMO equipment can now do 160 MHz, but it definitely drops to 32t32r in dual mode. If there are gaps in the spectrum where Sprint doesn't own it all (such as in SF), and they need more carriers on air as a result, they might run into the same power restrictions and need a second antenna for LTE. Also, with PCS, T-Mobile's current antennas might have power restrictions with the additional Sprint spectrum and the number of carriers that would have to be on air (LTE + HSPA). They might need 2 antennas anyway. Sent from my Pixel 4 XL using Tapatalk
  13. I think part of the agreement is that New T-Mobile is required to host B26 for several years. So they can't just take it down or reduce the footprint. Until they have MMIMO units on all sites, I don't see why they wouldn't keep using the triband antennas. I guess it depends how they perform on B2/25 relative to what T-Mobile is using now, but they can definitely keep doing B26 and B41 on them. Possibly put HSPA on B2 on the triband if their current antennas have any sort of power limitations or something running both LTE and HSPA together. Also, having separate B41 and N41 might be advantageous. Current MMIMO units have BW limitations and I don't think they can use the full 160 MHz of B41 (possibly soon to be more if the auction goes through). Or at least they can't in dual mode with full MIMO (N41 drops to 32t32r from 64t64r). So they'd be better off doing 100-120 MHz of NR on a MMIMO unit, and 40-60 MHz B41 on current antennas. Sent from my Pixel 4 XL using Tapatalk
  14. New T-Mobile will be hosting it for a while, so my guess is they will just leave it all in place on colocated or existing Sprint sites that they keep, and put it on the T-Mobile core like B41 equipment (and shutoff 1x800 at the same time). I somewhat doubt they'll deploy it on new sites. Or at the very least they won't purchase more equipment, and would just reuse what they have from decommissioned Sprint sites. It does give them added low band capacity that they can use, so why not use it while they can if they already have the equipment. Presumably then Dish will purchase the equipment from New T-Mobile. And then I guess they'd move it to their own rack on the tower eventually? Unless Dish decides to move B26 to NR only and replace it all. Sent from my Pixel 4 XL using Tapatalk
  15. I'm pretty sure it won't work until they merge the core networks. It results in a hard drop in data connections switching between Sprint and T-Mobile sites now. They might be able to configure it to allow a VoLTE call while on a T-Mobile site, but the user would have to stay on T-Mobile sites for the duration of the call. And vice versa. Sent from my Pixel 4 XL using Tapatalk
  • Create New...