Jump to content


S4GRU Premier Sponsor
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by ingenium

  1. Sprint sites broadcast 5-6 PLMNs typically. All have 310-120 and 311-490 (and 312-530). Which your phone connects to depends on a few things, but honestly I wouldn't read too much into it. The Android API will also return a mixture of the PLMNs depending on which API method is used, if you have TNA, etc. Sometimes it will report the SIMs native PLMN, sometimes it'll report the PLMN that the cell is broadcasting, etc. On Sprint these are often different. For example, with TNA, it will report 311-490 for the SIM's native PLMN, but the LTE17 API (what the connected cell is broadcasting itself as) will be 310-120.
  2. They're limited to 40 MHz carriers in SF due to a squatter. Sprint had the same issue which was why they deployed only 2 B41 carriers. There were a few sites that had a third non contiguous carrier, but it was pretty rare.
  3. ingenium

    Pixel 4/4XL

    With a Sprint account (ie, as TNX)? It so, it's not possible yet. Pixel 3 and newer can't be TNX'd yet, regardless of whether you use eSIM or physical SIM.
  4. These are the NR CA combos that it supports
  5. I'm assuming that Unifi voice also maintains a connection to a remote server, rather than relying solely on port forwarding and the server initiating a connection for a call? If so, see if you can decrease the keep alive interval. It's possible that T-Mobile's NAT kills the connection due to inactivity. Some NAT implementations are aggressive at closing connections if they haven't seen a packet in a certain period of time. Otherwise, you'll never get a public IPv4 address on an LTE network. They're all CGNAT. Sprint had the option, but they were the only one
  6. Block the DNS lookups (return NX or something like for epdg.epc.mnc260mcc310.pub.3gppnetwork.org and epdg.epc.mnc120.mcc310.pub.3gppnetwork.org and epdg.epc.mnc530.mcc312.pub.3gppnetwork.org And/or block UDP outbound to port 4500. You could probably just block all outbound to that subnet, but if you want to be sure it just blocks wifi calling, also restrict to that UDP port. The latter is probably preferred, but the DNS block should work if you don't have the ability to set outbound firewall rules on your router. Regarding the handoffs, that has always worked reliably for me. But you might have to make sure that "always on mobile data" is enabled under developer options.
  7. Is it easy to put back together in a way where they wouldn't know that you look it apart?
  8. It depends on the device, and what the carrier_policy file from the ROM dictates. On devices still receiving updates, they'll probably enable it. Older ones not. For example, the Pixel 1 has b41 disabled entirely with a T-mobile SIM. No way to enable it without a software update, which won't come. On newer devices, they typically leave all bands enabled, but limit the carrier aggregation combos that a device will use/report based on the SIM and PLMN. Since T-mobile didn't use B41 before, they probably don't enable those CA combos. But they should get enabled with an Android update for the device at some point. They still don't have all the CA combos correct on my Pixel 4 XL, but thankfully I can enable them all with EFS Explorer until then. The reason why they limit CA combos reported by the device is because the LTE signaling message where the device reports it's capabilities has a max size. With modern devices, the number of supported combos exceeds the message size, and gets truncated, resulting in your device potentially not using supported combos on the network. So instead they limit the device to report only a subset of combos based on the PLMN. The downside to this is if a new band is deployed, the devices needs a software update to enable it for that PLMN.
  9. It's probably a 1 gbps circuit. But you have ipsec overhead, and they likely reserve some percentage of the bandwidth so that it's not saturated completely (admin functions, inter eNB communication for CA between different sites, allowing QoS to function properly for VoLTE, etc). So 700 Mbps is probably about right for 1 gbps of backhaul.
  10. You could try forcing wifi calling preferred. I started doing this before my phone got VoLTE since the call quality was so much better than CDMA. And now I keep it since VoLTE on my magic box cuts out a lot. At the very least it should prevent it from dropping calls, since it should handoff to and from VoLTE.
  11. If the closest site is a keep site, then TNX will readily use it. It's seen as native T-mobile (equivalent to 310-260 PLMN), and will be equal priority as any other T-mobile site. Basically keep sites are literally T-mobile native sites now.
  12. Same here. It seems to have happened when there was an issue that took the site down for a bit. Once that was corrected, Tapatalk integration was gone. I guess it got removed with the restore or whatever was done to fix the site.
  13. Yes. Switching to TNX will cause you to lose all Sprint roaming partners. You would only have access to T-mobile roaming, and whoever their partners are. I know there is some att roaming but it's more restrictive than Sprint. And you also lose high speed international roaming.
  14. Yes, sorry, the RRUs. Antennas (looking straight on) are 12/71 on the left, 41 middle, 2/25/66 on the right. Interestingly, there was a lot of interference around it. The video feed was really laggy. And when the drone was directly in front of the MMIMO unit it started reporting strong interference warnings. The video feed is 2.4 Gh so I guess it's close enough to 2.5 to cause issues.
  15. Got some drone pics of a recently upgraded T-Mobile site: B66/N66 + B25/N25 AHFIG center. AHBOA B71/ N71 right. Nokia Flexi Zone B12 left. Behind AHFIG is network converging box where the hybrid flex splits output and fiber to the RRUs. Gen 2 Nokia M-MIMO (courtesy of lilotimz). More pics: https://www.joshuajhill.com/s4gru/img/PT43XC804/
  16. On the Pixel 4 at least, the MVNO profile that's loaded for the SIM disables the ability to turn on VoLTE. Same for red Pocket T-Mobile. I used root to set a prop that forces the toggle to always be present in settings and VoLTE works fine on GSMA and GSMT. AT&T is now at least allowing VoLTE on MVNOs on their network. But devices need updated to allow it to be turned on.
  17. Turn off wifi and make a call. Does your phone still display LTE? If so, then VoLTE is enabled. If not, and your phone is connected to it (you can use an app like Signal Check to confirm), then it's not enabled.
  18. Generally I don't think it matters which you connect to. I haven't seen a difference between them. It seems 310-120 might be used to regular data, and 312-530 is used for the IMS session for text and VoLTE. Or at least on VoLTE capable devices, some Android APIs report 310-120, and some report 312-530, so they're both likely being used somehow. Signal Check and CellMapper seem to always report 310-120, but Network Signal Guru always reports 312-530. 311-490 is only used for T-Mobile or ROAMAHOME. It's likely sticky and persists for a bit, but there should be no practical difference. 312-250 seems to only be accessible with a T-Mobile SIM. I don't know if they get routed any differently, or if it's like broadcasting multiple wifi networks from the same access point (and on the same vlan). 312-250 makes sense in that it's an easy way to restrict access to a subset of sites. Same for the Magic Box one. It makes it very easy to restrict which sites can be magic box and small cell donors, and they won't even try to connect to one that they're not supposed to. You don't want the UE trying to connect or get handed off to a site it's not supposed to be on and get rejections. You risk getting dropped calls or data interruptions. 311-490 was likely the same, as a way to restrict roaming access to some sites. Then they rolled it out to all of them, and rather than reconfigure the roaming side, they just added the PLMN everywhere since the current config was known to work.
  19. Sprint has 5-6 that they broadcast: 312-120 is seemingly non-VoLTE. 312-530 is VoLTE. 310-830 is for Magic Boxes and small cells to connect to (note that it's marked as "reserved". This means it needs a special SIM to access it). 311-882 I think is prepaid? 311-490 is for T-Mobile roaming, and 312-250 on some sites for T-Mobile native. The others are on all sites. Magic Boxes broadcast 3. 310-120, 312-530, and 311-490.
  20. I found a couple interesting tidbits. First, network signaling on T-Mobile shows 312-250 as an "equivalent PLMN" to 310-260, meaning it's treated as native and behaves like the Clearwire PLMN did with Sprint back in the Clearwire days. Should have soft handoffs with no IP address change nor drop of a VoLTE call, but I haven't tested this yet. Second, it seems that T-Mobile has disabled CA for Sprint users without ROAMAHOME or TNX if they're "roaming" on T-Mobile. The carrier policy marks 311-490 as Sprint (whereas it's T-Mobile for non ROAMAHOME or TNX users) and only enables Sprint CA combos on it. Likewise, 312-250 only has some B41 CA combos enabled, but not all, and no B25-41 nor B25-25. This is the carrier policy that it loaded on the eSIM of my Pixel 4 XL without ROAMAHOME. Previously all CA combos were enabled. <?xml version="1.0" encoding="UTF-8"?> <!-- Device configuration file for SRLTE with CHGWL roaming $Header: //commercial/MPSS.HE.1.0.c12/Main/modem_proc/mmcp/policyman/configurations/Carrier/Sprint/1xSRLTE/CHGWL_roam/subsidized/carrier_policy.xml#1 $ --> <policy name = "generic" changelist = "$Change: 19460658 $" policy_ver = "28.1.17" > <initial> <mcc_list name="sxlte_mccs"> 310 311 312 313 314 315 316 330 </mcc_list> <!-- These are the serving system PLMNs for which SRLTE will be allowed --> <!-- NOTE: Proper functioning of the SXLTE policy requires that there be an PLMN list named "sxlte_plmns". Do NOT rename this list. --> <!-- Google: Add Sprint hplmn 312530, add roaming partner plmn --> <!-- Pixel MOD, b/148088645#comment8 - add USCC plmn(311-580) into list --> <plmn_list name="sxlte_plmns" include="hplmn ehplmn"> 310-120 311-490 311-870 311-940 311-180 310-410 310-150 310-170 310-380 310-560 310-680 310-070 310-090 310-030 310-280 312-530 312-420 312-660 311-910 311-810 310-130 310-580 312-290 311-930 312-570 311-340 310-920 310-500 312-720 310-136 311-580 </plmn_list> <plmn_list name="plmn_tmo">310-160 310-200 310-210 310-220 310-230 310-240 310-250 310-260 310-270 310-310 310-490 310-660 310-800</plmn_list> <define_fullrat_config> <ue_mode> CSFB </ue_mode> </define_fullrat_config> <!-- Google: Remove 5G RAT--> <rat_capability base="none"> <include> C H G W L </include> </rat_capability> <ue_mode_if> 1X_CSFB_PREF </ue_mode_if> <rf_bands base="hardware" /> <feature single_sim="srlte"> dualmmode </feature> </initial> <!-- Google: Add Sprint and TMO CA combo list --> <!-- Pixel MOD, b/148088645#comment10 - add UL BW class for CA_41E --> <if precond="none"> <cond> <location_mcc_in list="sxlte_mccs" /> </cond> <then> <if> <cond> <serving_plmn_in list="plmn_tmo" /> </cond> <then> <ca_band_combos string="12AA-2A-mAll;12A-2AA-mAll;2AA-2A-mAll;46A-2AA-mAll;48AA-2A-mAll;48A-2AA-mAll;4AA-2A-mAll;4A-2AA-mAll;5AA-2A-mAll;5A-2AA-mAll;66AA-2A-mAll;66A-2AA-mAll;71AA-2A-mAll;71A-2AA-mAll;2CA-mAll;66AA-12A-2A-mAll;66A-12AA-2A-mAll;66A-12A-2AA-mAll;12AA-2A-2A-mAll;12A-2AA-2A-mAll;4AA-2A-2A-mAll;4A-2AA-2A-mAll;66AA-2A-2A-mAll;66A-2AA-2A-mAll;71AA-2A-2A-mAll;71A-2AA-2A-mAll;46A-46A-2AA-mAll;66AA-46A-2A-mAll;66A-46A-2AA-mAll;46C-2AA-mAll;48AA-48A-2A-mAll;48A-48A-2AA-mAll;66AA-48A-2A-mAll;66A-48AA-2A-mAll;66A-48A-2AA-mAll;48CA-2A-mAll;48C-2AA-mAll;12AA-4A-2A-mAll;12A-4AA-2A-mAll;12A-4A-2AA-mAll;4AA-4A-2A-mAll;4A-4A-2AA-mAll;5AA-4A-2A-mAll;5A-4AA-2A-mAll;5A-4A-2AA-mAll;71AA-4A-2A-mAll;71A-4AA-2A-mAll;71A-4A-2AA-mAll;66AA-66A-2A-mAll;66A-66A-2AA-mAll;71AA-66A-2A-mAll;71A-66AA-2A-mAll;71A-66A-2AA-mAll;66CA-2A-mAll;66C-2AA-mAll;66AA-2C-mAll;66A-2CA-mAll;66AA-66A-12A-2A-mAll;66A-66A-12AA-2A-mAll;66A-66A-12A-2AA-mAll;66CA-12A-2A-mAll;66C-12AA-2A-mAll;66C-12A-2AA-mAll;66AA-12A-2A-2A-mAll;66A-12AA-2A-2A-mAll;66A-12A-2AA-2A-mAll;12AA-4A-2A-2A-mAll;12A-4AA-2A-2A-mAll;12A-4A-2AA-2A-mAll;66AA-66A-2A-2A-mAll;66A-66A-2AA-2A-mAll;71AA-66A-2A-2A-mAll;71A-66AA-2A-2A-mAll;71A-66A-2AA-2A-mAll;66CA-2A-2A-mAll;66C-2AA-2A-mAll;66AA-46A-46A-2A-mAll;66A-46A-46A-2AA-mAll;66AA-46C-2A-mAll;66A-46C-2AA-mAll;46D-2AA-mAll;71AA-66A-66A-2A-mAll;71A-66AA-66A-2A-mAll;71A-66A-66A-2AA-mAll;71AA-66C-2A-mAll;71A-66CA-2A-mAll;71A-66C-2AA-mAll;66AA-66A-2C-mAll;66A-66A-2CA-mAll;66AA-46C-46A-2A-mAll;66A-46C-46A-2AA-mAll;66AA-46D-2A-mAll;66A-46D-2AA-mAll;46E-2AA-mAll;12AA-4A-mAll;12A-4AA-mAll;46A-4AA-mAll;4AA-4A-mAll;5AA-4A-mAll;5A-4AA-mAll;71AA-4A-mAll;71A-4AA-mAll;46A-46A-4AA-mAll;46C-4AA-mAll;12AA-4A-4A-mAll;12A-4AA-4A-mAll;71AA-4A-4A-mAll;71A-4AA-4A-mAll;46D-4AA-mAll;66AA-12A-mAll;66A-12AA-mAll;66AA-66A-12A-mAll;66A-66A-12AA-mAll;66CA-12A-mAll;66C-12AA-mAll;66AA-46A-mAll;66AA-46A-46A-mAll;66AA-46C-mAll;66AA-46D-mAll;48AA-48A-mAll;66AA-48A-mAll;66A-48AA-mAll;48CA-mAll;66AA-48A-48A-mAll;66A-48AA-48A-mAll;48CA-48A-mAll;48C-48AA-mAll;66AA-48C-mAll;66A-48CA-mAll;48DA-mAll;66AA-48D-mAll;66A-48DA-mAll;48EA-mAll;66AA-48E-mAll;66A-48EA-mAll;66AA-66A-mAll;71AA-66A-mAll;71A-66AA-mAll;66BA-mAll;66CA-mAll;71AA-66A-66A-mAll;71A-66AA-66A-mAll;66CA-66A-mAll;66C-66AA-mAll;71AA-66C-mAll;71A-66CA-mAll;41AA-41A-mAll;41CA-mAll;41CC-mAll;41CA-41A-mAll;41C-41AA-mAll;41DA-mAll;41DC-mAll;"/> <continue/> </then> <else> <ca_band_combos string="25AA-25A-mAll;26AA-25A-mAll;26A-25AA-mAll;41A-25AA-mAll;25AA-25A-25A-mAll;26AA-25A-25A-mAll;26A-25AA-25A-mAll;41C-25AA-mAll;41D-25AA-mAll;41AA-41A-mAll;41CA-mAll;41CC-mAll;41CA-41A-mAll;41C-41AA-mAll;41DA-mAll;41DC-mAll;41CA-41A-41A-mAll;41C-41AA-41A-mAll;41DA-41A-mAll;41D-41AA-mAll;41CA-41C-mAll;41E4422A-0;41E4222A-0;"/> <continue/> </else> </if> </then> <else> <!-- Choose an CA band that is not supported by HW, CA will be disabled by doing this --> <ca_band_combos string="41AA-39A-0;" /> <rf_bands base="hardware" /> <continue/> </else> </if> <!-- DSDS: Remove LTE on non-DDS when VOLTE is disabled in home. --> <if> <all_of> <not> <is_subs_dds /> </not> <not> <volte_enabled /> </not> <location_mcc_in list="sxlte_mccs" /> </all_of> <then> <rat_capability base="none"> <include> C H G W </include> </rat_capability> <continue/> </then> <else> <rat_capability base="none"> <include> C H G W L </include> </rat_capability> <continue/> </else> </if> <if> <any_of> <not> <phone_operating_mode> ONLINE </phone_operating_mode> </not> <not> <have_serving_system /> </not> </any_of> <then> <stop /> </then> </if> <!-- Beyond this point, the device is ONLINE and has a location. --> <if> <all_of> <any_of> <serving_rat_in> C H </serving_rat_in> <serving_plmn_in list="sxlte_plmns" /> </any_of> <location_mcc_in list="sxlte_mccs" /> </all_of> <then> <ue_mode> 1X_CSFB_PREF </ue_mode> </then> <else> <ue_mode> CSFB </ue_mode> </else> </if> </policy>
  21. Has B41 been moved to the B25/26 GCI in your area? In Samsung markets at least they've all on the same GCI now. So this would make sense if your market was still separate. Sent from my Pixel 4 XL using Tapatalk
  22. Yup, in western PA and northeast Ohio, Sprint coverage blows away T-Mobile's. T-mobile seems to have built a barebones network just to claim coverage. In the Youngstown area I'd estimate that Sprint has 2x as many towers as T-mobile. Pittsburgh also has better site density and site placement. The only places I know where T-mobile has better coverage are along 376 between the 76-376 interchange near Beaver Falls and 224, and on the route northeast of Pittsburgh going up to I-80, where there is a 20 minute stretch of no Sprint service but T-mobile does. T-mobile built their network in this area to cover highways and major roads, but once you get off those, Sprint wins. Hopefully they keep most of the sites. Sent from my Pixel 4 XL using Tapatalk
  23. If you activate it at the time of purchase, I think you get charged an activation fee ($35 I believe), which may go to best buy. Hence the discount. If you buy it without activating and just swap it on, there is no activation fee. Neither of them will affect your plan. Sent from my Pixel 4 XL using Tapatalk
  24. Sprint sites have begun broadcasting the Clearwire PLMN (311-490, the same one that T-Mobile broadcasts for Sprint roaming). Even my Airave has it, whereas it didn't a month or so ago. I'm pretty sure the reports on reddit showed T-Mobile customers using this PLMN on Sprint. So my assumption is that this is the PLMN for the merged network. We've seen other signs of true MOCN, such as T-Mobile neighbors showing up while connected to Sprint in some areas (for me this is only in rural areas. It doesn't happen in Pittsburgh for example, where Sprint has the better network). The phone only scans neighbors that the tower asks it to, so the tower is specifically asking the phone to check on the T-Mobile neighbors and report back signal strength and quality. Normally this is used so the tower can determine if it should do a handoff. I haven't seen it handoff from Sprint to T-Mobile directly (and can't get a NSG log to confirm it's a real handoff), but I know others have seen it happen. So it's definitely a sign that they're close to having active handoffs between both networks, which would effectively merge them. Sent from my Pixel 4 XL using Tapatalk
  25. Sprint's 8T8R radios have been recertified for NR. If Sprint was still independent they could flip a software switch and basically have N41 coverage everywhere... but a more likely scenario is that T-mobile will redeploy the 8T8R equipment as they decommission Sprint sites. Either to add N41 to a T-Mobile site, or to add it in addition to a M-MIMO unit to add B41 and eventually additional N41 carriers (M-MIMO units can't utilize the full 160 MHz of B41). Having that much equipment already should hopefully speed up the deployment and number of sites they put it on. Sent from my Pixel 4 XL using Tapatalk
  • Create New...