Jump to content

dewbertdc

S4GRU Sponsor
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    2

dewbertdc last won the day on September 11

dewbertdc had the most liked content!

Community Reputation

101 Trusted

About dewbertdc

  • Rank
    Member Level: 1xRTT

Profile Information

  • Phones/Devices
    iPhone 11 Pro
  • Gender
    Male
  • Location
    Washington DC
  • Here for...
    Friends

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. FYI for anyone with a recent multi-line T-Mobile plan, they're offering another free line for life if you call in or chat via T-Force on Twitter/Facebook/iMessage. I now have five lines of Magenta Plus for $125, all taxes included. (Three free lines, plus a $15 discount match from when I ported one number over from Verizon that had an corporate discount attached to it).
  2. I am a legacy T-Mobile customer, and can observe that this *seems* to be what's happening now when connected to the 311-490 PLMN. Most T-Mobile and Sprint towers are broadcasting it (Shentel areas seem to be a notable exception), subscribers of both networks can now connect to it, and it will try to balance you across both legacy networks as necessary. I wish I had an Android phone and SCP so I could see better what was going on, but from what I can tell from iPhone field test mode: when I connect to the 311-490 (as of this morning showing as "T-Mobile," not "Sprint") network in the man
  3. There’s some weird stuff happening here. VoLTE is working just fine, but I’ll also occasionally see that I’m on T-Mobile bands with the 310-260 PLMN in field test mode when my phone is showing the Sprint alpha tag. Also I’m seeing B71 at my house for the first time ever. I’m also noticing that force selecting Sprint shows a ton more neighbor cells (both T-Mobile and Sprint) than being on T-Mobile. Will keep an eye on it... progress!!
  4. Looks like we’ve got Sprint network access in Washington, DC now as well...
  5. That’s specific enough for me - was just curious if it had expanded outside of the states we already know about.
  6. LOL - my comment was a bit tongue-in-cheek, but it's both good and bad - T-Mobile certainly keeps costs low by doing this and passes those savings on to the consumer, however, I've noticed that in DC proper, they haven't been able to keep up with the explosive growth in some of our neighborhoods. The NoMA and H Street NE areas blew up over the last couple of years, and until very recently T-Mobile has been spotty (especially indoors) and had poor data speeds even with a strong signal. The Fort Totten area of NE DC is starting to have the same problems - meanwhile, my AT&T work phone
  7. I don't see B41 LTE going away any time soon, either, but I also don't expect that we'll see 100MHz NR carriers everywhere soon either. T-Mobile is famous for only deploying capacity where they need it - I can see them reserving 100MHz of their 2.5 for NR but only deploying the full carrier where they know there's demand, leaving the 40-60MHz carriers in place elsewhere. They could use multiple panels to deliver LTE alongside it, or use the higher-capacity Ericsson AIR 6449 panels that are becoming available to deliver it all. The breadth of their 2.5GHz spectrum holdings gives them
  8. Marketing fluff aside, there's a pretty good explainer video for MU-MIMO in this press release. https://www.t-mobile.com/news/network/t-mobile-achieves-mind-blowing-5g-speeds-with-mu-mimo Sounds like we can expect 100MHz NR channels next year, after they consolidate/eliminate Sprint B41 LTE.
  9. I'm wondering if CA was accelerated due to the wildfires. Better to have two networks at their disposal during this time of need.
  10. Lots more of this being reported in the /r/tmobile Subreddit as well. Still nothing here in Washington, DC when I try to force roam. I'm going to try to stop by my office (with a Sprint DAS, but no T-Mobile) later to see if it's enabled there. Dallas Area: Irvine, CA: Las Vegas, NV:
  11. I think selling new phones is a secondary concern for the manufacturers as it relates to this change. The newest Samsung Galaxy phone on that list (the GS6 family) was released in 2015 with Android 5.0, and the last software update that Samsung released for it was Android 7.0 with the November 2018 security patches. There's no way Samsung's developers are going to want to re-open that codebase to include T-Mobile's WiFi calling bits for the few S6 devices that are still out there on Sprint. Anyone using a phone on that list will have a bad network experience with the new T-Mobile anyw
  12. I wouldn't be surprised to see the SprintLink backbone integrated into the Deutsche Telekom Global Carrier network. https://globalcarrier.telekom.com/network
  13. Maybe so, but if a software update to the device is required to enable T-Mobile WiFi calling on these devices, that would require coordination with the manufacturers who have no interest in supporting these old devices.
  14. Sprint's WiFi calling FAQ has been updated to note that a lengthy list of older phones will no longer support WiFi calling as of October 30, 2020. https://www.sprint.com/en/support/solutions/services/faqs-about-wi-fi-calling.html
×
×
  • Create New...