PedroDaGr8

Still works on my end but I might not the best example.

Got it as of this morning. All of the bands I unlocked are still there.

Still not showing up for me. Maybe by the end of the weekend I'll have it.

Samsung is gradually killing this app across all product lines. Doesn't seem like they are killing *#2263# or *#73#

Got my answer, n25 is now 15 MHz as of today.

I think we are on to something. This time, when the upload fails, the error message states a file doesn't exist: "File NR_20221020-163832-1.scp not found." Diagnostic report sent. From my understanding, that's what he is doing until it gets fixed properly in Android. My phone, Samsung S22, and others now show n41 and n25 despite Android very clearly reporting n7 and n2 respectively. I think the banging his head against the wall is because he can't figure out why it isn't working for you too.

Yes, there are a bunch of files in that folder but only one since this mornings update. I will upload a handful of the most recent ones to a Google Drive folder and send the link to you in PM

1) Mike's recent changes have fixed that issue for me. That being said, the real cause is the underlying code that assigns bands in Android. Rather than polling the baseband to determine the band, it looks at the ARFCN and compares it to a list of ARFCNs and band assignments. This was a reasonable process in the LTE days because ARFCNs were unique between bands. So a B41 ARFNC was totally different from a B7 ARFCN which was totally different from a Band 40 ARFCN. NR does away with this practice and makes the ARFCNs frequency specific rather than band and frequency specific. As a result, the function now returns the first result it encounters (basically the lowest band). At this time, Google has not fixed this issue in Andorid though CellMapper has opened a ticket. 2) Supposedly Beta 5 ended up being the Stable and SamFW still works on that. Until I receive an update that I am for sure is a stable release, I won't know for certain. As for the Band Selector app, it is unfortunately permanently dead. The only way to select bands from here on out is via the ServiceMenu (*#73# or *#2263#).

Interesting. I did a bit of logging this morning on the way to work and the new beta was able to send the new cluster that I had logged while still not sending the 18 original clusters that are part of the issue. EDIT: Hmm I logged a bit more and it appears to only be able to send one cluster of fresh data. So it now says 0 of 19 sent.

The beta changed something because now it says "0 of 18 clusters sent" instead of "Internal Server Error". It does not export a log file or notice that an error occurred. I sent a Diagnostic Report. Can confirm that n25 reports correctly.

9:32PM and my web username for the app is the same as here PedroDaGr8

Not sure if it helps but I did lose signal during an upload a bit before this happened. Maybe that's part of it?

If that's the solution, so be it. It would be nice if it could skip over the first block(s) until it reaches blocks which it can upload.

Android 13 Stable update is out today for Verizon. Nothing for TMo yet.

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.

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

Likely they don't. Most of those screens (*#0011#, *#2263#, etc.)from Samsung phones are actually Qualcomm menus which have access to the baseband

B2 shifted down to 1890/1970 MHz that leaves 15MHz free. Curious what they plan to do, maybe reactivate the second B2 channel or expand n25 to 15MHz.

Second fastest speeds I have seen other than those posted by falconhand on the Bellevue Greg's Bicycle Site

Good luck to ya! Hope you like it! The Motel 6 site was live this afternoon. That means all 5 sites in Totem Lake are now live and fully upgraded.

Lots of changes in the Totem Lake area: For a brief period of time today, I connected to the second n41 carrier as the PCC. For those that care, it appears that T-Mobile is using Sectors 311, 312, 313, ... for the second n41 carrier. This was on the second 124th/Willows tower up on the hill: gNB 1853382. On that note, that tower has been upgraded to include b41/n41 and NR in general. The Totem Lake office building they co-lo with AT&T now has B41/n41. Additionally, I have picked up a couple of other stray gNBs over the past week. One I think was the Motel 6 but the n41 channel was weird (the old EARFCN) and I didn't get a chance to map it more. It is off today. Another, I have NO CLUE where it is located. I only picked it up on n25 once and it isn't ANY of the nearby stations which are ready for upgrade. The only one I can think of is the tower over by LWIT but when I drove by it today, that tower isn't broadcasting anything extra.

For a brief period of time today, I connected to the second n41 carrier as the PCC. For those that care, it appears that T-Mobile is using Sectors 311, 312, 313, ... for the second n41 carrier.

Interesting permit from AT&T, looks like they are going to be moving their downtown Kirkland site on the Marina Park Building to the notably taller WestWater Apartments building across the street: https://permitsearch.mybuildingpermit.com/PermitDetails/PRE22-00727/Kirkland IMHO this is a very good move for them because the location on the Marina Park building was EXTREMELY LOW and really limited their signal propagation in the area. TBH they didn't really have a good high elevation location to cover most of downtown Kirkland.

This is correct, the purpose of the Enable Secret Code portion is so that you can use the *#73# code. This code is the one that allows you to move back into the desired Service Menu.

Which code? *#73#?