PedroDaGr8

SignalCheck was reporting n25-SA properly. The diagnostics screen shows "mBands = [2]" As an aside, I decided to test out n2 to see if that is what AT&T n2-SA reports. The diagnostic screen also shows "mBands = [2]". That being said, whatever you did to fix the issue with the reporting of bands now causes AT&T to report n25-SA instead of n2-SA.

As an aside, your button had me look at Radio Info and look at what I see: I wonder how it is getting this info because it clearly says the mNetworkType=NR and mBand=25

This right here would be super useful if possible.

The issue with mmWave has never really been about line-of-sight (LOS) distance. LOS performance should be pretty good to excellent (when it comes to bandwidth) as the amplifiers and antennas improve. This new distance is a sign that things are getting better on that front. The real issue with mmWave is the fact that it is READILY attenuated by objects which have a negligible impact on other frequency bands (things like people's bodies, trees, etc.) For example, to get a decent mmWave signal for my phone, I have to remove the phone case. This is an example of things which can be engineered out. Future phones will be better at receiving signals so this won't be an issue. No matter the engineering, mmWave will not go "through" buildings or around corners because it is a physical limitation of the frequencies used. To be clear, this doesn't mean mmWave isn't useful, it is highly useful in the right scenarios. It just isn't useful in the same way that the mid-range bands are useful. I think Verizon has the right idea on how it will be used in the future. The better the amplifiers and antennas can target specific stationary objects, the better they can use it to eliminate "last mile" hard wired access to provide competition

I wonder if both are planning a larger update for the phone

On the S22 you have to unlock n25-SA. Otherwise, you won't see it until they officially roll it out.

Someone in another thread mentioned that T-Mobile will only call n25 UC if they have 30-40MHz of contiguous spectrum for n25, so it will be pretty similar to your comment about 40MHz n77 being 5G+. Assuming 4xMIMO and 256QAM, a 40MHz NR carrier has around 1Gbps of theoretical bandwidth. Even at half of that real-world, 500Mbps for a single carrier seems reasonable to call it UC/5G+. At this time, neither AT&T nor VZW have deployed 30-40MHz of contiguous n2 or n66. As they migrate to NR-SA and sunset the related LTE bands, it couldn't surprise me if they do start to use similar marketing.

If it is 40MHz then I have less of a problem with it. Per the online calculator that I used, that's almost a gig of theoretical bandwidth (assuming 4xMIMO and 256QAM). Once you break around 500Mbps, I think it begins to at least be not dishonest to call it UC.

Can confirm that this change fixed it. I was able to log-in successfully and finally update the 4.5k datapoints I had queued up.

Diagnostics sent.

Sent an immediate diagnostic report

I am getting the same issue. My devices show up on the SignalCheck website but the app doesn't seem to know that it occurred successfully. I sent a diagnostics immediately after the failure.

Thanks for the heads=up! So they added n78 to the mix but still no n25-SA?

A number of Verizon NR-SA sites are starting to pop-up near me with n5-SA and n77-SA.

The powerline tower overlooking downtown Redmond has FINALLY been upgraded. I guess it took this long due to the large birds nest on top of the tower. During the upgrade, they moved all LTE frequencies including B41 to one eNB 84782 and decommissioned eNBs 97521 and 95988. Additionally, the tower finally has all three 5G-SA bands (gNB 1852420).

My S22U is currently showing 2.400001 after a Carrier Services Update. It was at 2.380001 yesterday.

You would think but it has been like this since they changed things up. Really not sure what's going on there and not sure who I could report it to.

I just noticed that the two n41 bands have moved around a bit. The 100MHz band moved up to 520110, placing it right at 2600MHz +- 50MHz. Strangely, the 40MHz band has moved to 512190 which is 2560MHz +- 20MHz. That means that 75% of the second carrier is overlapping with the first. I have no idea why they made this move.

3x CA has been absolutely for a while in the S22U. it only appears when you stress the connection like with a speed test.

Honestly, I was driving in heavy traffic so I can't fill in many details about coverage and what not. Here's my previous post showing the equipment: As for the area, its in downtown Seattle, right next to Interstate 5 and the Convention Center. The area is super dense but it has line of sure to a late area to the west due to the geography.

Haha, that's just the icon not updating, which may not be SC fault. Occasionally the notification bar freezes on my phone until a new notification comes through. That being said, mmWave is NSA only, so SC wouldnt see it (I think). I was connected to B66 as the anchor IIRC. I'll send you a Diagnostic now just in case. I won't be back over there for a few weeks though. As for the 3°, the wife and I use Celsius. 😁

n258 is now live in Seattle. This is the tower I posted a couple months ago. It is aggregating 4x100MHz. Has anyone else seen n258 live yet?

@RAvirani It looks like they listened to you and shut off the site by the Totem Lake McDonalds. Went by the McDonalds to get the wife some frys and was surprised that I couldn't pick up the signal from that site. Looks like the last time it was seen was mid-Sept.

I think I copied the wrong permit, I will see if can figure out which one I intended to copy. Found it: https://permitsearch.mybuildingpermit.com/PermitDetails/WCF2022-32542/Bothell Technically the same parcel but not really. The tower is the green one in the center, located here: https://www.google.com/maps/place/16001+124th+Ave+NE,+Woodinville,+WA+98072/@47.7431505,-122.1749793,3a,75y,297.03h,107.54t/data=!3m6!1e1!3m4!1s1fgQXLYWWxmA3Zb2r00DaA!2e0!7i16384!8i8192!4m5!3m4!1s0x54900dda6f2be3cb:0x31061dfdc68aa722!8m2!3d47.7438019!4d-122.1753217

T-Mobile is really started ramping up their decommissioning of sites in the past few months: Site 1: https://permitsearch.mybuildingpermit.com/PermitDetails/PUB22-06523/Kirkland (This one was actually a T-Mobile site and has already been decommissioned). Site 2: https://permitsearch.mybuildingpermit.com/PermitDetails/WCF2022-32251/Bothell Site 3: https://permitsearch.mybuildingpermit.com/PermitDetails/WCF2022-32718/Bothell Site 4: https://permitsearch.mybuildingpermit.com/PermitDetails/22 118927 BE/Bellevue Site 6: https://permitsearch.mybuildingpermit.com/PermitDetails/22 117455 TJ/Bellevue Site 7: https://permitsearch.mybuildingpermit.com/PermitDetails/BLD22-0818/Kenmore Site 8: https://permitsearch.mybuildingpermit.com/PermitDetails/PRE22-00596/Kirkland (Dish taking over this one) Site 9: https://permitsearch.mybuildingpermit.com/PermitDetails/ELEC22-0081/King County Site 10: https://permitsearch.mybuildingpermit.com/PermitDetails/ELEC22-0084/King County Site 11: https://permitsearch.mybuildingpermit.com/PermitDetails/ROW2022-03987/Sammamish To be clear, these are all straight decoms and not upgrades or sites where T-Mobile was already on the site.