mdob07

My AT&T Ultra is downloading an update now, 3518.56MB.

Edit: It was the Android 13 update! Wasn't aware it was officially rolling out yet.

15 hours ago, dkyeager said:

Wi-Fi 5 works. N7 nr2600 still exists. Sent diags. *#0011* shows n41.  Will test other Wi-Fi later.

Not sure which phone you're using by my s22 on the beta reports n41 in SCP. The last time I saw n7 was before I got the Android 13 beta. Just wanted to point that out that it is working for me.

2 hours ago, PedroDaGr8 said:

FYI, I'm having an issue with uploading my data points to the server. It tries and fails, saying "Internal Server Error" but it isn't exporting the files for inspection. I send a Diagnostic Report from right after a failed upload.

I'm seeing the same. If I go out and back in to upload again it still shows my pending web entries. 

3 hours ago, mdob07 said:

Looks like SA N41 was enabled in Louisville today. Phone switched to it and held for awhile without me having to force it. Once it did switch I was able to lock to n41 and it connected again.

I was able to connect all over Louisville, southern Indiana, and held it all the way home to Bardstown KY. 

3 minutes ago, PedroDaGr8 said:

Awesome! Do they have the full B41 spectrum in L-ville?

140 MHz n41 and 40MHz B41 currently.

Looks like SA N41 was enabled in Louisville today. Phone switched to it and held for awhile without me having to force it. Once it did switch I was able to lock to n41 and it connected again.

1 hour ago, Trip said:

Do you have USB Debugging enabled?

- Trip

Yeah, ended up switching to my laptop and doing the exact same steps including installing the Samsung drivers and it worked on the first try. 

I can't get past the waiting for DIAG step. I've got the Samsung drivers installed and i did the setting in the *#0808# menu. Not sure what I'm doing wrong...

I don't know if T-Mobile pays the tower crews by the hour or what. A crew has been working on adding 2500 gear to a site that already has everything else upgraded, and they've been working on it for 2.5 weeks. Verizon is doing complete rip and replaces in 2-3 days and I've seen new Dish installs going up in less than a day. T-Mobile work seems to take longer than work for the other carriers around here for some reason. Couldn't ask for better weather for this time of year either. 

Does anyone have an S22 on AT&T using esim? I've tried looking up how to switch but the directions I've found online my AT&T account doesn't have the option to request esim. Was hoping to avoid a store visit. For T-Mobile it was a very quick and easy process.

18 hours ago, chamb said:

Just installed the September update on my S-22.  STILL no n-25 showing in the *#2263# NR5G band preference menu. bands 2, 4 & 12 are not there either but 66 is.  Using the TM version of the S-22.

Thats funny, my S22 on the android 13 beta is still saying up to date with August update. 

Just checked my T-Mobile and AT&T phone and both still say up to date with August update for now. I'm hoping T-Mobile enables n25 finally this month but not holding my breath. 

Just got a 1.2GB update on my AT&T phone, still says August for security patch level so I wonder what all was in this update. 

With n25 being spotted now what are the odds T-Mobile finally enables it for the S22s in the Sept update? 

I forgot to mention that the TA: 0 bug carried over to the Android 13 beta on my S22 Ultra. Was hoping that and some of the weirdness in the service menu would get cleared up but doesn't look like they touched any of it. 

On 7/29/2022 at 6:11 AM, mikejeep said:

Did you send a diagnostic report after that happened (before you exited) by any chance? If not, could you try to replicate that scenario and do that? Would like to see what's getting stuck.

It just happened again and I sent a report before closing and reopening SCP. Works fine after restarting SCP. The is the first time it's happened since my earlier post about it.

And I wonder if they'll ever fix the service mode screen before the next android release, still says "code review required".

2 hours ago, jreuschl said:

Nothing new added to the 2263 menu in August unfortunately. 

 

How can N77 not even be supported given that they are starting to test this? 

Still no n2 or n25 either. Really surprised on that one since they've publicly shown tests results using an S22 and n25+n41+n41. To me it kind of takes away from the validity of that test since they used some sort of custom firmware, makes you wonder what else they might have modified. Its not really a "stock" device at that point.

I think it might have already been reported on here but I found a Sprint keep site broadcasting the T-Mobile B2 carrier today. No sign of the Sprint B25 carriers. Was weird to see Sprint B2 in SCP. 

Edited to add screenshots. I also didn't think to check if B41 was still broadcasting from this site or not, if it is I wonder if they also moved that to match T-Mobile's B41.

I had a weird issue on both of my phones this morning. Went to upload data after driving to the office and after tapping upload web data nothing would happen. I had to exit out and reopen SCP to get the data to upload. 

16 minutes ago, PedroDaGr8 said:

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. 

So if you force n41 it works? I've only been able to get it to work when I get handed off from n71 to n41 and it usually only last a couple seconds. If I try to force to n41 via the 2263 menu it just says no service. 

n77 up to 100MHz in Louisville now. Speeds haven't been great compared to what it is capable of, mostly around 400-450 down. Didn't see much difference when it widened from 60 to 100MHz. Assuming backhaul needs to catch up. Verizon has a ton a c band gear already installed here.

Looks like c band and DoD deployment is imminent in Louisville!

15 hours ago, dkyeager said:

This will be rough for most to see.  My Samsung A32 5g locked to T-Mobile only has n41 and n71. My Factory unlocked could do it if it is public. Could certainly see n25 if rooted and using NSG. Otherwise a spectrum analyzer is needed.

It's not enabled on the s22s yet either. They'll need to update a bunch of their models to support it once it goes live. 

3 hours ago, IrwinshereAgain said:

OK.  Looks like the Samsung band selector app does not work, which everyone  knew already.  The *#2263# menu comes up but I have not tried to actually force any band changes.

Is that menu working for anyone on Tmo?

Works fine for me.