PedroDaGr8
-
Posts
689 -
Joined
-
Last visited
-
Days Won
39
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Posts posted by PedroDaGr8
-
-
n41-SA just went fully live (not just a handful of select towers) over the past few days in the Seattle market. If you don't see it yet in your area, it will likely come soon. Seattle isn't normally the first market for changes but is usually one of the first Nokia markets. Changes in Seattle tend to roll out over the next few weeks/months to the vast majority of other areas.
- 5
-
@RAvirani Do you think you could implement a filter that converts all of the T-Mobile n7 to n41 (both ready logged and incoming)? At least in the meantime, until Mike implements his fix in the app. Now that n41-SA has finally gone live across the Seattle market, not just a couple choice sites, I will be doing a lot of logging of n41.
-
n41-SA appears to have gone live across the eastside (and likely all of metro Seattle). Pretty much every tower that supports n41 can now do n41-SA.
This finally allowed me to confirm the second n41 channel is 40MHz centered at 2570MHz.
- 3
-
On 7/14/2022 at 9:47 PM, PedroDaGr8 said:
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.
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.
-
T-Mobile rolling out some experimental n77 towers:
Thread includes a map of all of the towers they plan to deploy test equipment
- 8
-
1 hour ago, wispiANt said:
Looks like C-Band was a last minute add-on. They don't provide any info about the radios besides mislabeling them as "CBRS RRH Units".
Out here, Verizon will call them the very unhelpful name VZSUB6.
-
Looks like the Gregg's Bicycle site in downtown Bellevue is getting additional antennas:
https://permitsearch.mybuildingpermit.com/PermitDetails/22 114313 CD/BellevueConsidering 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.
- 3
-
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.
- 5
-
On 7/15/2022 at 10:01 PM, Dkoellerwx said:
Some of the early keep conversions here changed GCI's randomly in the last couple months. The first several conversions were 07Bxxx until they changed to using 01C/D/E which better fit the numbering system for the rest of their sites in the area. Not clear why they made that change or why they are going back and changing the first round of conversions.
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 hours ago, PedroDaGr8 said:
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.
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.
- 2
-
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.
- 1
-
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.
- 1
-
7 hours ago, PedroDaGr8 said:
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.
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.
- 1
-
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.
- 1
-
2 hours ago, Paynefanbro said:
Not sure how we missed this but looks like T-Mobile hasn't given up on mmWave in NYC:
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.
- 3
-
On 7/10/2022 at 1:54 AM, mikejeep said:
Not sure how it happened, but I missed all the posts in this thread for the past several weeks. I've been busy but certainly didn't mean to ignore everyone.. will start working on catching up today.
On 6/24/2022 at 10:28 AM, PedroDaGr8 said: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"
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.
-
3 minutes ago, mdob07 said:
July update out for AT&T already.
Wow, that is fast!
-
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.
- 4
-
1 hour ago, bigsnake49 said:
Is T-Mobile still trying to swap band 2/25 allocations to create larger adjacent blocks to band 25?
Here they canibalized all of but the PCS G-block for B2 but they already had everything contiguous.
-
1 hour ago, RAvirani said:
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).- 1
-
The site at t
On 6/20/2022 at 6:19 AM, PedroDaGr8 said:The rooftop Sprint Keep site at the 85th/405 interchange in Kirkland has been upgraded but isn't live.
This site is now live! So the newest site out of the 6 is already live while the others are not.
On 6/21/2022 at 12:41 AM, RAvirani said:I’ll get back to you on site #1.
Any updates on this one?
- 1
-
1 hour ago, jreuschl said:
I must have missed it. What does T-Mobile plan on doing with B26?
Very occasionally I used the Band Selection app to force B26 in an area that T-Mobile hasn't upgraded a tower. Obviously with the shut down that is probably not going to work anymore.
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.- 1
-
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.
- 1
-
19 minutes ago, dkyeager said:
Interesting add! Now if they would just enable the other bands the phone is capable of as well.
- 3
Galaxy S22 thread
in Samsung
Posted
n41-SA went live in my market over the past couple of days. As such, I have been logging a lot of NR. I noticed yesterday while logging that one of the recent updates fixed the slow update rate for NR, it now seems to update at a rate similar to LTE. That alone is a good improvement and will make logging NR much more accurate.