Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Got TNX'd yesterday. On chat to switch back now. SA n71 is cool, but speeds are pretty low (~30 Mbps) and unnecessary around here. Not seeing SA n41. And losing L-Sprint network access, other than 312-250 sites (which are few and far between here) is a downside. NR CA doesn't exist yet either. I'd rather catch L-Sprint LTE (and 1x) than L-TMo H+ (which is now down to a few Mbps). Only big benefit is theoretically T-Mobile roams on a solid carrier west of here, but I can just use a different (VZW/AT&T) SIM for that. Biggest downside though is that T-Mobile *still* haven't fixed the 1.5 Mbps streaming cap on TNX'd accounts. So I either VPN in (Cloudflare Warp+ works, but not while tethered) or I get heavily capped video throughput after an initial burst of speed. Of note, if you force SA (which *does* work in Samsung Band Selector; forcing NR 71 only gets you on SA n71) you can attempt to make calls, and they'll ring on the other end, but the call will fail after a half-second or so without ringing on your side. So VoNR definitely isn't there. Did some testing last night and the n41 site nearest me reaches about 0.6 mi on n41 (at which point I get 350-375 Mbps on 100 MHz). B41 LTE reaches a little over a mile, including indoors.
  3. Went up to Middletown, NY again for the first time in a few months and every T-Mobile site with the exception of one has been upgraded to include Band 2/12/66/71 and n71. The sole site without Band/n71 at this point is a flagpole site that likely won't be upgraded for a while. I got the chance to compare both Verizon and T-Mobile at more than just my friend's house this time around and they performed similarly. I got similar coverage on both carriers and generally slightly faster speeds on T-Mobile. This is because T-Mobile and Verizon are collocated nearly every tower there. There are only about two or three sites in the city where T-Mobile and Verizon aren't collocated. In those areas, one carrier or the other typically vastly outperforms the other in coverage and speeds. For example in Downtown Middletown I was getting speeds over 100Mbps on T-Mobile while on Verizon I was getting ~30Mbps because T-Mobile has a site near downtown (eNB 48775) that Verizon isn't on. On the other hand, in parts of East Middletown T-Mobile gets destroyed by Verizon because a large portion of it is served by Verizon eNB 74282 and T-Mobile isn't on that site. The good news is that Sprint is on that same tower with Verizon so hopefully that T-Mobile decides to keep/convert it.
  4. Yesterday
  5. Thanks everyone. Later in the day, I went to an area of town where all carriers have weak service (a residential area where no one want a cell tower "in my backyard"). With my old S7, I would not even be able to get LTE, it would connect to borderline unusable 3G. However, with my S21, I now get n71 and n71 only. Thus, the user experience was way better there since it didn't have a choice. Hope they fix the issue that occurs elsewhere, which seems to be quite widespread. When I get some time (and patience), I may try to contact support.
  6. Yeah these 5G phones like to jump around a lot of makes no sense, can't even lock them to SA the phone will ignore it and jump back on NSA even with them disabled.
  7. My S20 also bounces cotinually between bands and no signal, making it useless. However, there is a bypass: Lock it to band 71 with the Samsung Band Selection app.
  8. Last week
  9. That same behavior happens around the Harrisburg PA area as well. The phone (Note 20 Ultra 5G) bounces between bands with moments of "no connection). I've noticed that other people's T-Mobile phones exhibit the same behavior. It's not only just my phone. The strange thing is that when Signal Check Pro shows "no connection" during a VoLTE phone call, the call is not interuped, nor does it drop. Hopefully in the next year or so as the Sprint sites are converted over to T-Mobile, the system will be tweaked to have the phone park on a band with a good signal and stay there instead of the band hopping that currently persists.
  10. Just wanted to share my experience so far: -I'm in Fairfield County, CT and my house is shown on be on the edge of T-Mobile's "5G Ultra Capacity". -I upgraded my phone from an S7 to a Sprint S21 from Best Buy a few weeks ago. When Best Buy shipped it, the S21 included a factory installed Sprint SIM card and for some odd reason, they included another Sprint SIM card - stuck to the factory box with my BB order sticker, rather than include a T-Mobile SIM card. -When I activated the S21 online, the system told me it is highly recommended to install a T-Mobile SIM instead of a Sprint SIM (well, I would have if it was provided by your authorized retailer, lol). -I finally got around to ordering a T-Mobile SIM, which I installed last night. -When my S21 was on the Sprint SIM for a few weeks, on the 2nd floor of my house, it would stay on an unspecified 5G (I believe n41 (2500)). On the 1st floor of my house, 5G would drop and it would bounce between b12 (700) and b2 (1900). On the Sprint SIM, I never saw it connect to n71 or b71 (600). I used it on both floors with no issues (just technically slower on the 1st floor with no 5G, but not noticeable). -Now, with the T-Mobile SIM installed as of last night, I noticed a few things. First, I am noticing it being able to connect to n71 / b71 (600). But, with "more choices", it is bouncing around a LOT. On the 2nd floor, it bounces between n71, b71 (600), n41, b12 (700), b2 (1900). And on the 1st floor, it does a similar thing, but connects to n71 more so than on the 2nd floor, but it doesn't stay parked on n71. With all the bouncing around that it does, I seem to loose data service for a brief period while it is transitioning between bands. For instance, the NY Times and Twitter apps tell me "my device is not connected" and then after about 10 seconds, it works fine to load data. I never noticed this issue with the Sprint SIM in my S21 for a few weeks. So, although the T-Mobile SIM seems to make b71 / n71 (600) available (and of course SA 5G), the overall user experience in my case in my house is worse than that of the Sprint SIM. The network really aught to keep and leave my S21 on n71 while inside my house. I'm not sure what to expect in the future as far as real world improvements to the user experience. Are they continuing to optimize the network for proper common sense band selection? Also, is there anyway to report this to the network team and get actual results? (how do we even contact them these days? the My Sprint app? T-Mobile Twitter DM?)
  11. Still not out for my T-Mobile phone. It's funny that the June update came out super fast and now it'll be August before they push the July update.
  12. To clarify my comment earlier, I'd assume that TMo would want to run 40 MHz T-Mobile B41 on top of 100 MHz n41 at a minimum, so going > 100 MHz on mid-band even on full 194 MHz would only get them another 40 MHz of n41. Maybe 60 due to guard bands, which would require taking Sprint down to zero. Wouldn't make sense to deploy a 20 MHz n41 channel I don't think. Alternative would be dropping from 100 MHz in one channel to have two channels, each with >= 40 MHz capacity. If they did 100+40 n41 plus 2CA T-Mobile B41, they could fit 15-20 MHz of Sprint B41 in, at which point the band is maxed out...and they'd have online as much spectrum for n41 as VZW will have in many areas for n77 in late 2023. Their statement of 100 MHz mid-band on average by year end has gotta be n41 only, as n77 won't be live 'til late 2023, and I'm 99.9% sure they wouldn't include n2/25/66 on the mid-band side as you're not going to have more than 10x10 there this year, which is less than they have on n71 in a lot of areas. So, not very Ultra Capacity. Now, their "300MM on Ultra Capacity by YE23" statement? If they can move enough traffic to n71/41 that they can carve out 20x20 of dedicated n2/25/66, with at least 16x16 M-MIMO? That's probably enough to hit 300 Mbps and call it Ultra Capacity. That, or they're counting on massive range improvements on n41 when CA'd with n71, n25, or n66...which, yeah, that might work. As for the n41 coverage map, it's a bit generous around here. B41 from the same radio makes it to my location, but n41 does not, despite being supposedly covered by it. Checked with Premier Care and none of the sites closer to me are slated for imminent upgrades (though apparently the Sprint rooftop site close to me will be the one that survives rather than the legacy T-Mobile one further north that now has all three carriers on it...so I guess that site will get Dish eventually), so this is flat-out a case over overestimating coverage. I'll go on a walk in a bit to see whether moving the NR carrier down 50 MHz improved coverage any; guessing I'll have to get within 0.75 mi of the site to pick up n41 though.
  13. Just drove by this site again and it's no longer running Band 26. Just Sprint Bands 25 and 41. - Trip
  14. Interesting comment in the T-Mobile Q2 Earnings Report yesterday. https://s24.q4cdn.com/400059132/files/doc_financials/2021/q2/NG_TMUS-06_30_2021-EX-99.1.pdf Specifically, this part: • Approximately 80% of Sprint customer traffic is now carried on the T-Mobile network • One-third of Sprint customers have been moved to the T-Mobile network Not terribly surprising to me that the customers who use the most data were most anxious to move to T-Mobile, while the majority of customers--who don't use much data--are perfectly happy with the Sprint network as it is. I'm definitely in that category and in no rush to give up the superior coverage of the Sprint network for the possibly-superior capacity of the T-Mobile network. (Also, at least in my case, since LG phones are now discontinued, moving to a new T-Mobile phone means extensive phone shopping that I'm not looking forward to, rather than just picking up the latest LG device and being happy.) After all this time, I still have yet to see any Sprint site conversions that are operating. I've seen precisely one that has new gear, but still only seems to have Sprint bands running on it (along with 312250). I don't know what is taking them so long. - Trip
  15. FYI the Evergreen hospital n41 panels are live. They do a great job of covering I405, I was able to maintain a B41 connection to that tower almost all the way down to Kirkland exit 18.
  16. Quite accurate if not conservative in the Metro Seattle area. In fact I know of two recent B41/n41 towers that aren't on the map.
  17. Wouldn't surprise me, but I will say that the map looks accurate in terms of sites actually operating B41 gear, based on what I've seen. I was able to use it to add a number of sites I haven't visited yet based on the map. - Trip
  18. In a number of markets TMO effectively controls all 194MHz of band 41. Now I think n41 greater than 100MHz would need 5g CA.
  19. How does Dish spectrum align with those frequencies? Perhaps they will get wider bands better suited for 5g. Of course horse trading with other carriers and speculators also possible.
  20. They've made incredible progress here in such a short period of time. The network is great!
  21. Good point. I guess it could be helpful for when T-Mobile does mmWave deployments in the area. Bethesda Magazine has another interesting write-up about it: https://bethesdamagazine.com/bethesda-beat/government/council-approves-change-to-pave-the-way-for-expanded-5g-coverage/
  22. It looks pretty right on for Omaha. I actually can get n41 in a slightly larger area than what they show on the map.
  23. Doesn't show anything special. "Ultra capacity" is n41, so generally you'll need to check the engineering screen to see which 5G band you're connected to (n71 or n41). If you're on SA 5G, SCP may show 5G 2500 or something like that.
  24. Users on reddit are saying the N41 areas are greatly exaggerated. Unfortunately the MVNO map hasn't been updated yet that shows bands and strength per.
  25. T-Mobile has updated their coverage maps to include 5G Ultra Capacity (N41) coverage. Shows how quickly they've added it to towers in the DC area.
  26. Given that this mostly affects small cell mmWave deployments like the ones that Verizon and AT&T are using, I don't see much changing for T-Mobile. They're mostly focused on adding mid-band 5G to their existing T-Mobile and Sprint-keep macro sites, which have been happening in this area pretty quickly.
  1. Load more activity
  • Create New...