Jump to content

ingenium

S4GRU Premier Sponsor
  • Posts

    1,717
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by ingenium

  1. On 11/9/2021 at 12:31 PM, Thomas L. said:

    I have ordered the unlocked Pro 6. I wanted to use my Cricket SIM and T-Mobile on eSIM since Cricket doesn't support eSIM. Will that not be possible?

    It is, but you'll have to active it without DSDS enabled (if it is enabled, you have to do *#*#4636#*#* and disable it), otherwise the network won't allow you to connect. Then you need to find a T-Mobile rep who is willing and able to change the eSIM binding from IMEI1 to IMEI2. I was able to escalate it enough through T-Force (Twitter DM) to get a rep to do it. Once the eSIM IMEI binding it changed, you can enable DSDS again.

    • Like 1
  2. Unfortunately it seems that dual SIM doesn't work if you use eSIM for Sprint/T-Mobile. The eSIM moves to IMEI 2 on Pixels when you enable dual SIM, so the IMEI no longer matches and the network rejects the attachment. 

    Not sure who to report this to or how to go about getting it fixed... 

    It wasn't an issue with previous Pixels because they used Sprint SIMs, and the Sprint SIM only checks the IMEI when you provision or do a profile update (I've checked signaling messages in NSG and the network doesn't ask for it upon attachment). So enabling dual SIM basically was a SIM swap. But T-Mobile SIMs apparently report the IMEI upon attachment, so the network immediately sees that it doesn't match and rejects it.

    • Like 1
  3. 22 hours ago, thisischuck01 said:

    image.png

    Super happy to see continued n41 rollout/densification in NYC. This site (eNB 128041) was upgraded within the last week. Unfortunately B41 isn't yet live, so couldn't map, but pulled some very healthy speeds on NSA n41. 

    Across the street from this is one of the few Sprint sites I've found with B25/B26 deployed on 310-120 but B41 deployed on 311-940. Does anyone know what is up with these? I feel like I am totally out of the loop as to why they still have sites configured like this.

    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.

  4. 8 hours ago, iansltx said:

    Either 66 at 20 MHz or 2 at 15, with the other as SCC. Sometimes with B71 at 5 MHz as an SCC.

    I've likewise seen plenty good speeds out of even 40 MHz n41, so this was definitely a surprise. This was near the Embarcadero BART station (so, an area where I believe VZW says they have mmW), so rather dense, though traffic still isn't quite to normal levels yet.

    If T-Mobile can't get more than 40 MHz n41 to play with there, I wouldn't be surprised if they threw mmW, LAA, or CBRS in some areas to supplement capacity once outdoor usage picks back up.

    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.

  5. On 5/11/2021 at 11:30 PM, crazy_vag said:

    Has anyone on eSIM switched to T-Mobile eSIM?

    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.

    • Like 1
  6. On 3/18/2021 at 3:24 PM, mdob07 said:

     

    Well I have finally noticed an issue with the double NAT. I run Unifi Voice on my Ubiquiti UDM Pro and when I'm on my T-Mobile connection I can't make or receive calls on my IP phone. As soon as I switch to my Spectrum connection it works fine. Assuming this is because on T-Mobile it shows a 192.168 address for WAN connection. I'm hoping to port my existing Spectrum phone number to Unifi eventually and get rid of Spectrum all together and save about $100 a month, but I guess I'll have to find or build a cellular router that can pass though the public IP to my UDP Pro. If nothing else this proves that this is a viable option with the right equipment. 

    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 

  7. On 2/25/2021 at 1:49 PM, Trip said:

    Wi-Fi calling drops more often than VoLTE does, and I've yet to see it successfully hand off to the cell network.  Actually, I suspect that's part of the problem; I have Wi-Fi calling disabled on my phone, yet I seem to get a notification that Wi-Fi calling can't connect on a semi-regular basis, as if it's enabled.  I suspect T-Mobile has my phone set to ignore my preference and use Wi-Fi calling anyway.  I've taken to turning off Wi-Fi on my phone as well to get around that particular issue when I know I'm leaving the house.  I'd love to block it at the router if I could figure out how.

    - Trip

    Block the DNS lookups (return NX or something like 127.0.0.1) 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 208.54.0.0/16 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.

    • Thanks 1
  8. On 3/1/2021 at 1:49 PM, Terrell352 said:

    Can anyone tell me if there device on TNX is allowing to use CA with tmobile or sprint b41? Mine doesn't but TNA still let's you on Sprint or Tmo.

    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.

    • Like 7
  9. On 2/11/2021 at 8:52 AM, shaferz said:

    700mb/s seems like such a weird speed cap to me.  At least for residential customers, tiers are normally 100/500/1gig.  I'm struggling a bit with understanding the 700 limit that appears to be in place

    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.

    • Like 2
  10. 4 hours ago, Trip said:

    Beats me.  I honestly don't remember how well it worked before the buy-out, as I didn't make a lot of long calls on my cell phone before COVID-19.  But it definitely irks me now.  One would think that T-Mobile would have this sorted out by now.  I'll drop a call and when I call back it'll be on CDMA.  Or I've taken to just turning off VoLTE entirely before making calls that I know, in advance, will be lengthy.  Doesn't help when someone calls me.

    Beyond the lack of service in the Shentel region, lack of ability to turn off VoLTE was one of the reasons I had myself removed from ROAMAHOME.

    - Trip

    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.

    • Like 1
  11. On 1/28/2021 at 2:00 PM, mmark27 said:

    Floorguy, you are on Sprint SIM (ROMAHOME) and not getting calls?? I rarely get calls on my S20+ with Sprint SIM. Telemarketers get through just fine, but people on my plan usually go to VM or nothing like you said.

    I'm feverishly trying to decide if I want to use the TNX SIM that is in the box with our new S21 phones. I too live very near a Sprint tower that I believe is a keep site, but the nearest TMO tower is quite some distance away...so the interim might be rough. 

    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. 7 hours ago, mikejeep said:

    The website seems fine, but S4GRU has completely vanished from Tapatalk for me. Searching for it turns up nothing! :(

    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. On 11/13/2020 at 8:52 PM, TechGuru said:

    If I switch to a T-Mobile SIM (TNX) will I lose the ability to roam on AT&T? (I know I'll lose the ability to roam on Verizon 1x voice). There is a area I travel though frequently that literally has nothing but AT&T and Verizon and has been fine for me for many years with Sprint as I would always just roam on Verizon there and the past year and a half I started roaming on AT&T there instead.

    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. 5 hours ago, Dkoellerwx said:

    When you say center, are you talking about the RRUs? The Nokia M-MIMO B/N41 is the center antenna is it not?

    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.

    • Like 3
  15. On 11/4/2020 at 11:50 AM, red_dog007 said:

    When I switched to RedPocket GMSA in December from Sprint using a Verizon Palm Phone, VoLTE was working through February before it was disabled. That was a RP sim card straight into the Palm and activated in the Palm.

    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.

  16. 13 minutes ago, jporter12 said:

    Which one you device connects to can vary, dependent upon what you were connected to previously.  It's all as clear as mud right now!  

    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.

    • Like 1
  17. 7 hours ago, PedroDaGr8 said:

    I find it interesting that the tower reports AT LEAST two different PLMNs. I noticed if I was connected to a T-Mobile (310-260) tower before connecting to a 312-250 tower, then the tower will report 312-250. On the other hand, if I switch from a Sprint tower which is reporting either 310-120 or 312-530, then the same tower will report 312-530. This makes it really hard to find these towers, since locking my signal to any Sprint band will inherently force me onto 310=120 or 312-530. 

    Sprint has 5-6 that they broadcast:

    Ruu6xo2.jpg

    QilvJhF.jpg

    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. 

    • Like 2
  18. 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.

    ZPVddBB.png

     

    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>

     

    • Like 2
  19. I've been looking for someone else to notice this.. all summer, the Sprint B41 GCI's in my area have been slowly transitioning to new 000xxxxx ones that don't seem to correlate to anything. B25/B26 hasn't changed at all. Do we know if this is a temporary "work in progress" sort of thing, or permanent?
    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

    • Like 1
  20. Well, I'm sitting here northwest of Pittsburgh near the Ohio border using a v60, and i can tell you that Sprint has coverage where T-Mobile wasn't even trying.

    One infuriating thing is that this phone isn't currently working properly when it has to use Sprint B26, which is pretty much all the time because it connects to 800 as well when using 1900 and 2500 most of the time.

    Phone loses its mind: LTE flag on, VoLTE flag on, VoLTE flag off, Roaming flag on, radio resets and we start all over.

    It gets stuck in this loop sometimes even when returning to T-Mobile coverage.
    Android Auto connects and disconnects every time the radio resets.

    It's infuriating, and all I can get Sprint to admit to is an "outage" that's supposed to be fixed by a date that keeps getting pushed back.
    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

    • Like 1
  21. Hi Folks, wondering if you could weigh in on the following.  I'm still rocking a 4 year old S7 and I'm on an Unlimited Freedom plan from 2017 w/ 2 lines for $100/month ($60 1st line + $40 2nd line) that includes HD streaming.  My account is still on Sprint.  I'm thinking of changing my phone to a Pixel 4a (the 2nd line phone is an iPhone 7 which would remain).  I'm thinking of buying it unlocked from Best Buy online and activating it with Sprint during the checkout process.  My question is, will my existing plan be able to remain intact, or will be I forced onto a current Sprint plan?  The HD streaming is important to me and a current plan with HD steaming would raise the monthly fee to $120/month.  I'm hoping that since it would be an unlocked "bring your own device" that the plan would not change.  Also, how is it that Best Buy can provide a $50 discount on the phone for "activating today"? (and not relevant to me, but the discount is $100 for "activating today" for a new line)  In addition, if I wait until the Pixel 4a 5G comes out, would that phone upgrade purchase force me onto a current plan (since 5G access would be required)?
    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

×
×
  • Create New...