mdob07

10 minutes ago, Grabber5.0 said:

Is this a phone bug, a SCP big, or a brain bug? I occasionally run a speed test on my S21 when I drop my daughter off for work. There's a tower a few hundred feet away, so results are usually very good. The other day, I got almost 1Gbps (a couple days later I hit 1073Mbps) but SCP claimed I was connected to N71 and LTE B2. I'm quite sure that combination isn't capable of that speed. Later I searched how to open service mode, and when SCP was showing the same thing, service mode appeared to show I was connected to N41 and B2. Screenshots attached so y'all can confirm or educate me if I don't understand. Edit: attachment max, will add 2nd post.

I've seen that before usually when I had been connected to SA n71 before switching back to LTE. SCP keeps identifying the 5g connection as 5G-NR 600. In NSA mode if should just say 5G-NR as I don't think the phone can tell what NR band it is in nsa mode at least for now. When I see that if I exit using the menu and reopen SCP it just shows 5G-NR. Hope this helps.

It looks like even the unconverted keep sites are turned off now also here in Louisville. I tried to connect to 2 known keep sites today and both times would get Verizon on B26 and AT&T on B25. On B41 it would just pick up T-Mobile.  

It's funny that the size was different for AT&T vs T-Mobile. Pretty sure the update on AT&T was over 800MB, the T-Mobile update was only 551Mb. Doesn't look like any of the known issues were fixed on T-Mobile yet. 

July update out for AT&T already.

36 minutes ago, Paynefanbro said:

I've always hated the split eNBs. They make it that much harder to track upgrades of sites and more importantly it also makes it slightly worse for carrier aggregation. While T-Mobile has enabled the ability to aggregate bands across eNBs, it seems like the network avoids doing that as much as possible.

Agreed on the split eNBs being a pain. AT&T, Verizon, and T-Mobile all do it around here, I've always wondered what the technical reasoning was for it. AT&T and Verizon's follow a pattern at least which helps. Still better than the 5 eNBs Sprint sites had around here. 

I'm a little disappointed that AT&T didn't include C band equipment on a new tower build here. A new monopole was recently built and Verizon was first to install on it about a month ago, and they did include C band in their setup. AT&T was added about a week ago. 

16 hours ago, mdob07 said:

Looks like the remaining Sprint network might be dead here now. Forcing my phone to B25 or B26 gives me no network, sad day for sure. 

Confirmed on my way to work this morning and while out on lunch that the only Sprint sites I connected to were keep sites. All others seem to now be offline at least around Louisville and Shepherdsville KY. 

Looks like the remaining Sprint network might be dead here now. Forcing my phone to B25 or B26 gives me no network, sad day for sure. 

Found some AT&T c band live in Cincinnati today. Not too bad considering I was driving past on the interstate at speed.

1 hour ago, PedroDaGr8 said:

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. 

Yeah its weird how they aren't standardized on at least the same brand of phone with what they have enabled. On my s20+ they didn't even have n66 enabled on it as of end of February when I traded it in even though there were n66 hits on cellmapper, so it was live in at least some parts of the country. 

The 2263 menu is still working post update thankfully. I noticed T-Mobile still hasn't added either n2 or n25, so the S22 they used for that 3gbps test must have been using custom firmware. Currently my S22 Ultra has n1 NSA, n3 NSA, n5 NSA, n7 NSA, n8 NSA, n20 NSA, n28 NSA, n38 NSA, n41 SA and NSA, n66 SA and NSA, n71 SA and NSA, n260 NSA, & n261 NSA on the NR5G Band preference menu. 

18 minutes ago, S4GRU said:

Yet another reason to keep my LG V60. 

Robert

Hopefully T-Mobile keeps the *#2263# menu enabled. Honestly I use that more than the band selector app since the app used to be fairly glitchy. 

1 hour ago, jreuschl said:

FYI for the update coming any day now. The Samsung Band Selection app will no longer work. 

Can confirm, now my AT&T phone gives an error when opening the band selector app. 

My AT&T phone is downloading a 1715.86 MB update now.

On 5/23/2022 at 3:21 AM, dkyeager said:

n7 still appearing with latest version on samsung galaxy a32 5g with android 12. Swipe feature works. Log sent.

Samsung s21 ultra does show solid n41 connection on T-Mobile through Boost Mobile.

Note: fixed typo by removing "not".

Might be a samsung issue like the TA issue. My S22 Ultra is showing SA n41 as n7 also. Saw it for the first time today. 

2 minutes ago, red_dog007 said:

I just flipped over to 3G and my phone isn't picking up a signal.  That means all of 850MHz is only 5G now?  AT&T doing DSS on that or no?

Not sure on DSS since they haven't widened to 10x10 here yet. We'll see how long that takes, hopefully not another 3 months. I hope they enable SA on n5 soon, I get really good signal on n5 in my house but keep dropping to just b12 because the anchor signal is too weak.

Seeing 313-340 broadcasting n71 in Louisville now, so it appears Dish's network is now live here. My phone actually tried to connect to it briefly when I was forced to n71. 

Looks like everything is slowly recovering now finally.

So I'm currently experiencing issues with AT&T, T-Mobile, and Verizon around me in the south side of Louisville currently. It's been ongoing for at least 2 hours now. Multiple sites offline not broadcasting at all on AT&T and T-Mobile, Verizon is allowing my phone to connect but can't get any throughput. On both AT&T and T-Mobile I'm connecting to sites multiple sites over from my location and I don't see the closer sites in the neighbor lists on either. I'm wondering if it's an issue with a major network route or something. It has to be big to affect all 3 carriers across a mix of backhaul providers. Pretty sure it's not a local power issue as far apart as these are spread out.  On top of this I've also heard KY lottery is down in retail locations around here and they use a satellite connection to the lottery DC.

Is anyone noticing anything anywhere else right now?

Looks like AT&T finally killed 3G around here.

I finally found n66 in the wild. I'm on vacation down in the Gatlinburg TN area this week and noticed it in Knoxville and in Sevierville TN where I'm at now. Looks like they flipped the AWS1 5x5 carrier that centered at 1732.5/2132.5. 

Came across this on Reddit, its a T-Mobile site plan including n77 gear. Don't think I've seen this yet. Anyone else seen n77 gear in other parts of the country for T-Mobile? 

@mikejeepI've been noticing SCP freezing and unexpectedly closing a lot more recently since that latest beta update. It used to only do it after it had been running in the background for several hours. Now it's happening fairly frequently when I've got SCP on screen as I'm driving. Sometimes it will freeze but the system notification that it's not responding won't pop up for 15-20 minutes, or sometimes it's immediate. I have to go into settings-apps and force stop scp to get it to work again if I notice it before the system notification. 

On 6/4/2022 at 11:22 AM, Paynefanbro said:

T-Mobile sure hopes no one notices any difference with 5G VoNR

Looks like T-Mobile is done beefing up their LTE network. Now that CDMA is gone they're gonna use that 5MHz of spectrum for n25.

 

Currently n2 and n25 aren't enabled on my S22 Ultra on T-Mobile firmware. Hopefully they enable that soon if that is indeed their plan to use that spectrum for n25.

5 minutes ago, jreuschl said:

Anyone switch to eSIM for the S22 yet?  Any issues?  (Apparently it is supported for Sprint billing now)

I've been on esim since the day I got my phone back in February, no issues for me. But I'm also fully on T-Mobile too.