Jump to content


S4GRU Premier Sponsor
  • Content Count

  • Joined

  • Last visited

  • Days Won


Paynefanbro last won the day on July 4

Paynefanbro had the most liked content!

Community Reputation

5,127 Wireless Expert

About Paynefanbro

Profile Information

  • Phones/Devices
    Unlocked Samsung Galaxy S20 Ultra 5G
  • Gender
  • Location
    Brooklyn, NY
  • Here for...
    4G Information

Recent Profile Visitors

14,357 profile views
  1. T-Mobile must've heard my complaints about n41 because I ran into it a bunch of times today in Manhattan and in Brooklyn. I've also seen a bunch of sites that have n41 panels installed but that aren't active. A few of the sites with inactive n41 also have those new Ericsson AIR 3446 antennas that support mid-band FDD 5GNR. Fun fact for people wanting to test n41. If you're on the Prospect Expressway in Brooklyn, there is a site that is eye-level with the highway that has n41. Here is a speed test from it and take a look at that signal strength and upload!
  2. Got my fastest speeds on T-Mobile 5G yet, today. This is on mmWave in Brooklyn. I have a feeling that the reason I never connect to n41 is because I'm either close enough that I can connect to n261 or so far that I can only connect n71. Edit: The site has Band 2/12/46(LAA)/66, and n41 installed but it doesn't have Band 71/n71. T-Mobile really confuses me sometimes.
  3. I know that. I'm talking about further down the line for 5G. What I'm saying is that with the addition of Sprint's PCS, they can expand LTE on PCS and shift HSPA from AWS to the remaining 5MHz in PCS-B so that they can have a 25MHz n66 carrier down the line and a 20MHz n2 carrier since n2 is not currently registered for greater than 20MHz carriers. The other solution would be to simply get rid of HSPA altogether and have two 25MHz n66 and n25 carriers since n25 allows for 25MHz carriers. Then T-Mobile could retain the 5MHz PCS-G for legacy LTE service.
  4. They poached it from the lower 5MHz of Sprint's PCS B-block. I'm assuming the plan is to eventually expand PCS to 20MHz, leaving two 5MHz blocks (one in B-block and one in G-block) for legacy HSPA and Sprint LTE.
  5. That's not 100% true. The X55 modem supports mmWave carrier aggregation of up to 8 carriers or 800MHz. In NYC T-Mobile aggregates two 50MHz n261 carriers. It also supports aggregation of a select few sub-6GHz bands. However, the sub-6GHz aggregation won't be meaningful until the x60 launches which will likely have CA support for nearly every sub-6GHz band. In May, Qualcomm and Fujitsu achieved a multi-gigabit connection by aggregating NSA 3.5GHz and 4.9GHz with a X55 modem in a smartphone. https://www.fiercewireless.com/tech/qualcomm-fujitsu-validate-5g-carrier-aggregation
  6. I can confirm that 15MHz PCS is live across all of northern Brooklyn at the very least. I went to Red Hook, Williamsburg, Park Slope, Sunset Park, and everywhere in between today and encountered 15MHz PCS everywhere.
  7. Likewise. Despite my good experiences with T-Mobile, Sprint was definitely better here. T-Mobile now has the scale and revenue to throw the money at the wall like AT&T and Verizon. They really should focus on upgrading every single site to have every single technology available. There's no reason to hold back anymore. That's part of the reason why AT&T's network shot up to first place in the U.S. according to independent testing. They stopped bs-ing and started throwing money at the problem. They did it in Mexico too and now their network there is second best and only marginally so.
  8. Spotted it on multiple sites in Crown Heights so far. I forced Band 2 and this is what it shows. Speeds have gone up accordingly. I'm getting 153 down and 46 up in my house now. Typically around this time speeds would be just over 100Mbps.
  9. It's happening! T-Mobile seems to already be thinning Sprint's PCS spectrum and using it for their own LTE in NYC. Today T-Mobile expanded Band 2 LTE to 15MHz from 10MHz in NYC. If you take a look at this chart from speedtest.net, you can see that the only way T-Mobile can do that here is by taking 5MHz from Sprint's B-block.
  10. Band 2 on T-Mobile got expanded to 15MHz. That means that they officially poached 5MHz of Sprint's PCS B spectrum to do this, leaving Sprint with a contiguous 10MHz in PCS-B and the PCS-G block.
  11. Can confirm that this happened for me when I was using Sprint's VoLTE. When I switched to T-Mobile's network I stopped experiencing this. It's super annoying. I used to tell my mom to hang up and I'll call her back just for HD Voice to work.
  12. I think you are misunderstanding what I'm saying. I'm not saying that it matters what band people are connected to or arguing the merits of T-Mobile's deployment vs Sprint's deployment. I'm flat-out saying that if the metric is "as long as their devices work acceptably the majority of the time" Sprint has done a better job than T-Mobile at that and the root of the issue is that T-Mobile has done a poor job of deploying all bands to all sites here. I feel like this is a cop-out because there are a lot of sites that literally only have Band 66 and Band 2 on them and perform poorly here. These are sites that went live in 2013 and likely haven't been visited again in several years. Meanwhile, Sprint has managed to (in the same span of time) deploy Band 25, 26, and 41 to almost every site in the city, and then remove and replace Clearwire and 8T8R Band 41 antennas with new dual-mode Massive MIMO n41/Band 41 antennas at at least half of their sites while simultaneously building out the largest or second largest (after Verizon) small cell network in NYC. I simply think that in NYC T-Mobile should be much farther along with its n71 rollout than it is at this point.
  13. I can only speak for NYC once again, but here it didn't work as well as Sprint's choice to put everything everywhere. T-Mobile's deployment method led to some neighborhoods being under-deployed while others have the "full experience". This is as opposed to Sprint where everywhere I went, I always knew that the site I was connected to had all 3 bands available. I also don't know if it's fair to say that Sprint didn't deploy based on data. It looks like they simply deployed where it made the most economic sense to invest heavily. That ended up being their largest markets. The unfortunate side effect of this is that if you aren't in a large market the network languished until work was completed in the bigger markets. There are definitely pros and cons to both styles of deployment. Sprint's biggest issue to me is that they tried a Verizon and AT&T deployment style without Verizon or AT&T money.
  14. That's why I've been quiet about the numerous posts here regarding T-Mobile's competency when it comes to deploying spectrum. My experience on T-Mobile's network has been good overall but they aren't magical. n71 started going live in NYC at the end of 2018. It's the middle of 2020 and I'm on n71 about 10-15% of the time, maybe less. Not to mention despite T-Mobile owning Band 2, 4, 12, and 71 here it seems like probably 10% of their sites actually have all bands on it. The rest are a random combo of bands with some literally having only Band 66. One thing I can say about Sprint is that (here in NYC) despite all the claims about slow deployment, they were incredibly thorough and >90% of their sites had Band 25/26/41 deployed on them.
  • Create New...