Jump to content

PedroDaGr8

S4GRU Sponsor
 View Profile  See their activity

  • Posts

    685

  • Joined

  • Last visited

  • Days Won

    39

 Content Type 

Everything posted by PedroDaGr8

  1. PedroDaGr8
    This tower (the colo by the Cross Kirkland Corridor) is already live, while the Motel 6 site across the 405 is not. My guess is the Motel 6 site needs a backhaul upgrade. That site was B25/B26 only when it was Sprint, so I doubt it had much backhaul.
  2. PedroDaGr8
    T-Mobile rolling out some experimental n77 towers: Thread includes a map of all of the towers they plan to deploy test equipment
  3. PedroDaGr8
    Out here, Verizon will call them the very unhelpful name VZSUB6.
  4. PedroDaGr8
    Looks like the Gregg's Bicycle site in downtown Bellevue is getting additional antennas: https://permitsearch.mybuildingpermit.com/PermitDetails/22 114313 CD/Bellevue Considering that site has the full suite of T-Mobile bands including mmWave (2/12/41/66/71/261), this might mean they are planning on adding n258 to that site. Unfortunately, Bellevue tends to be pretty scant in their permit details so this is only conjecture.
  5. PedroDaGr8
    Came across a Sprint tower tonight still broadcasting B25. I'm on TNX and my phone hopped on that due to the signal lack of good TMo signal there. Interestingly, it is no longer using the PCS G-block. It's now centered at 1882.5/1962.5. This frees up the G-block for n25.
  6. PedroDaGr8
    This wasn't even a first round conversion, it was relatively recent. The 5***** was far more common for Sprint conversions. That being said, recently, there are no standards. The eNBs are all over the place. On a related note, at least one tower is still broadcasting B25. Interestingly, it is no longer the PCS G-block. It's now centered at 1882.5/1962.5. This frees up the G-block for n25.
  7. PedroDaGr8
    Confirmed, 505970/506079 is now 887558/887561. I have no idea why they changed the eNBs or what the difference in meaning is between them.
  8. PedroDaGr8
    Also, it looks like they may have changed the eNB for the Sprint Keep tower in downtown Bellevue. A new eNB showed up (887558) right by 505970/506079 which has the same PCIs for sectors 1 and 2. I will investigate that one later.
  9. PedroDaGr8
    At this point, Totem Lake will have four towers with the full suite of bands within a radius of 1300 ft, an additional tower 1/2 mile away overlooking everything, and a sixth in the opposite direction around a 1/2 mile away (Forbes Creek). Absurd. I just saw a permit for a new T-Mobile site at UW Bothell right by the 405/522 interchange. That is just as ridiculous as some of the towers in Totem Lake. Combine this with the 85th/405 interchange in Kirkland and it seems like T-Mobile is going for absurd numbers of towers around specific interchanges. Strangely though, in other areas nearby, the coverage is less than stellar. For example, the 70th/405 interchange in Kirkland (especially on the elevated 70th at the interchange and just east of there) continues to have horrible coverage.
  10. PedroDaGr8
    And, wow. It's getting the full suite of bands as well. They were in the process of putting n41 on the tower. I couldn't snap a good pic but everyone knows what the looks like.
  11. PedroDaGr8
    I think I found out why the Totem Lake Motel 6 isn't live yet. Drove by the tower right across I405 from there (right next to the CKC) and there were workers installing a new rack a few inches above the T-Mobile "rack". Link to StreetView of the tower (T-Mobile is the lower "rack"). It was MUCH too close to be a different operator, so my guess is T-Mobile is going to be installing larger antenna's and/or equipment on this site as well. I'll try to get an image later if I can.
  12. PedroDaGr8
    A while back (around 6months ago), I posted a permit for a site in Seattle which will have n258 and n261. That one was issued recently, so it looks like they have started rolling out the test sites for n258. It makes sense, as they begin to reach saturation for n41 in many areas, that they start to roll out mmWave where beneficial. I believe the S22Ultra (and maybe the S22+) also support n258 even though it isn't visible in band selection screen.
  13. PedroDaGr8
    Welcome back Mike! Just confirming that these issues are still present in the July update. Of note, along with those issues the n41 reporting as n7 issue continues. CellMapper seems to record it properly, as n41, but not SignalCheck. I have only seen this occur with n41, B41 is not impacted.
  14. PedroDaGr8
    Wow, that is fast!
  15. PedroDaGr8
    Several T-Mobile upgrade sites in my area came online last week. Interestingly, every single one used a single eNB for all LTE bands including B41. This is extremely unusual for my area and, from my understanding, most areas. Typically, B41 and the second B2 carrier will be on a different eNB than B2(first carrier)/B12/B66/B71. I've never understood the logic T-Mo has used for splitting eNBs but here's hoping it leads to them consolidating a number of the existing sites under single eNBs rather than creating even more chaos.
  16. PedroDaGr8
    Here they canibalized all of but the PCS G-block for B2 but they already had everything contiguous.
  17. PedroDaGr8
    I guess that makes sense. I know that ZiplyFiber (my ISP) has had issues with sourcing fiber as well. Also, that recently upgraded site is interesting. NOt only does it have a strange eNB value, 236960, which is different from the ones usually around here but also, all of the LTE bands (including B41) are on the same eNB. This is the first time I have seen T-Mobile do that in this area. Also found another upgraded site, eNB 84770, by FireStation 26 has been upgraded with B71/n71 (no n41).
  18. PedroDaGr8
    The site at t This site is now live! So the newest site out of the 6 is already live while the others are not. Any updates on this one?
  19. PedroDaGr8
    I believe one of the merger conditions was they had offer to sell it to Dish. EDIT: Oops didn't see that this had already been answered.
  20. PedroDaGr8
    Also, I somehow hopped on N41-SA yesterday but SignalCheck logged it as n7. This resulted in the uploaded data being assigned to n7 as well.
  21. PedroDaGr8
    Interesting add! Now if they would just enable the other bands the phone is capable of as well.
  22. PedroDaGr8
    It is pretty easy to use, once you get the hang of it. For example, to select a specific LTE Band(s) Click on [7] --Clear selected bands Click on [5] LTE Band Preferences Click on the specific band(s) you want to enable. Click on [F] Go Main Click on [9] --Apply band configuration The same holds for NR5G, just you would click on [5] NR5G Band preferences instead of [5] LTE Band Preferences To re-enable all bands: Click on [8] --Select all bands Click on [9] --Apply band configuration
  23. PedroDaGr8
    This is correct, it appears that Samsung is disabling the menu that the app served as a shortcut to. It looks like on TMo models, *#2263# still works for band selection though.
  24. PedroDaGr8
    Hey Mike, a couple other things you might be able to post for S22Ultra owners, In particular, these deal with the *#0011# menu. The following are true for even the June update: 1. Does not show the second n41 carrier (when it is connected) on LTE+NSA. It shows "NR_NumCC:2" but no additional Carrier. It simply states "CA-Not Config 0 0"This works fine on the S21. 2. There is a line that states "Code Review Required" 3. There is a line that states "Unknown 0"
  25. PedroDaGr8
    So annoying, they also didn't add n258 either which they have been slowly rolling out. Also, they didn't fix the issue where the *#0011# menu doesn't show the second n41 carrier. At this point, it seems like the S21U is their chosen phone and they are intent on ignoring the S22.
×
×
  • Create New...