PedroDaGr8

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.

16 hours ago, xmx1024 said:

This one seems to be an upgrade
 

Also, it's been a while since I have been up there but I am having trouble locating it on Google Maps street view. The only site visible appears to be an AT&T site due to the raycap visible just above the fence line & gate signage.

https://www.google.com/maps/place/16001+124th+Ave+NE,+Woodinville,+WA+98072/@47.7437861,-122.1749942,3a,19.2y,224.2h,80.66t/data=!3m6!1e1!3m4!1sT9h59Sj7l0YRZH8PxCBWqA!2e0!7i16384!8i8192!4m5!3m4!1s0x54900dda6f2be3cb:0x31061dfdc68aa722!8m2!3d47.7438019!4d-122.1753217


 

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. 

8 minutes ago, chamb said:

Apparently the s-22 STILL has access to band lock enabled via the #*2263# service menu after installing Android 13????

I want to be sure I can still lock out certain bands at times.  What I hear appears to suggest this is still working but I want to be positive before allowing the update.

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

On 10/29/2022 at 1:13 PM, PedroDaGr8 said:

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

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

4 hours ago, gr8nuguy said:

The T-Mobile update is out today

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

15 minutes ago, mikejeep said:

FYI the latest T-Mobile A32 update appears to remove the Samsung band selector app.

EDIT: *#2263# menu still works.

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

On 10/20/2022 at 4:45 PM, PedroDaGr8 said:

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.

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

12 hours ago, mikejeep said:

Another new SCP beta is rolling out now. It has additional adjustments to the web upload error handling and another(!) attempt to work around the n7/n41 bug. It should be available within the hour. If you have been experiencing these issues, please send diagnostic reports after checking the same things on the new version.

Also, it has been determined that the issues with n41 appearing as n7/n38 and n25 appearing as n2 (and probably other similar issues on other networks) are bugs with the Android OS, and are not manufacturer-specific. Please visit the link below and add a "+1" on it, this will help attract attention for it to be properly fixed by the Android development team:

https://issuetracker.google.com/issues/253539094

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. 

1 hour ago, dkyeager said:

Thus start with n7 for T-Mobile plmns is always n41. T-Mobile has no n2 but rather is using n25. Then work through the other items in order where possible. Asterisk what is uncertain.

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.

40 minutes ago, mikejeep said:

Thanks for the report, it doesn't tell me what is wrong but it gives more direction as to where to look for the problem. The exported files do not go in the normal SCP directory, they will be in /Android/data/com.blueline.signalcheck/files/weberrors -- did anything new get saved there?

In any case, I will be rolling out another update tonight with some more adjustments to try capturing exactly what is happening here.

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

6 hours ago, dkyeager said:

1) Does s22 have SCP n7 problem instead of n41? Curious if so, does android 13 fix it?

2) Curious if band selector app or other method allows band selection. Does latest samfw method still work with 13?

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. 

5 hours ago, mikejeep said:

New SignalCheck beta is rolling out now.. many bugfixes, hopefully they all fix the bugs they intend to!

Those of you experiencing the Internal Server Error upload issue, please try uploading with this new version; if it fails again, send a diagnostic report so I can see if additional information is captured. Also, it should now export log files for inspection; that may help determine what the issue is.

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.

28 minutes ago, mikejeep said:

Sure, that could be possible, it's tough to know from my end because nothing is being logged on the app side. @RAvirani is looking into it from the server side. If anyone knows exactly when they experienced this issue (perhaps try another upload now and note the time), please share your web username and attempted upload time.. thanks!

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

1 hour ago, mikejeep said:

I haven't been able to pinpoint what causes the "Internal server error" response, otherwise I'd be handling it a lot more gracefully..

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

15 minutes ago, mikejeep said:

I will take a look. I've run into that once or twice and the only way I could resolve it was to select the Discard Web Entries option to reset the upload timestamp. That will cause you to lose any data you had not uploaded yet though.

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?

2 minutes ago, mikejeep said:

No.. couldn't on the Pixel 6 either, even when rooted. My guess is they don't exist?

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.

16 minutes ago, Paynefanbro said:

New T-Mobile site in Sterling, CT with 180MHz n41 and 1.6Gbps speeds. Absolutely insane!

 

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

9 hours ago, S4GRU said:

Can't stand not being able to connect to SA n41 and n25.  I ordered a new Pixel 7 Pro.  Should arrive today. I am hoping it will connect!  

Robert

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.