Trip

Good morning, I've just tried the update on my main phone and gotten a null pointer exception when I try to log in. Not really sure what else to do, but here's relevant screenshots. https://imgur.com/a/NvEQiDG And I checked and it does it regardless of whether the password is right or wrong. EDIT: I also tried removing the spaces from the device name (just "S21FE") and that didn't fix it. Interestingly, I'm looking at the website and I do see multiple "sessions" in my list there. So it looks like it may be logging in on the web site but then either failing to understand the acknowledgement on the app side since the next time I try it says I'm not logged in. I was going there to try to remove the non-alphanumeric characters from my password, as I know Cell Mapper has a problem with those, but can't figure out how to do it through the website. - Trip

It doesn't include T-Mobile because AT&T objected to the T-Mobile applications. The fact that anything at all was filed will add time. - Trip

https://i.imgur.com/mLIqTkL.png Try looking at the image direct; it has plenty of resolution. - Trip

I have something in one of my logs that I need additional opinions on. https://imgur.com/a/lVzbmGt This is from the SCP log database on my B26-locked Sprint SIM phone. That GCI definitely matches the B12/71 pattern for that tower, with the prior Shentel gear having been FE66E[19/1A/1B]. Am I correctly interpreting this as T-Mobile having deployed B26 on this site? - Trip

Okay, I wasn't sure if you knew any more than I did. I have a pair of Moto One 5G Ace phones and I can band lock LTE but not NR, which is frustrating since NR SA with Tello works on them but not on my NR-lockable A32 I bought specifically so I could band lock NR. - Trip

Off-topic question, but do any of these support NR band locking? - Trip

Ack, forgot to follow up. The n41 SA ended just after Frederick on I-70 headed west. I also saw n41 SA in Crystal City. - Trip

Same here, though I got all new phones back in May or June. I didn't think Unlimited Freedom was a particularly rare or old plan, either. - Trip

Do you have USB Debugging enabled? - Trip

The n41 SA followed me to Shirlington this evening. I'll be headed up toward Hagerstown this weekend and we'll see how far it goes in that direction. - Trip

On Saturday, I went down to Fredericksburg for the day. While previously I only saw n41 SA immeidately around Newington, I now had it from home all the way to the Prince William/Stafford County line on I-95. I assume it's now widespread through must of at least the Virginia side of the DC area. - Trip

Off-topic, but I just tried it on my S21FE (with updates after May disabled) and n25 is not available in the Selection tool, but is available via the dialer code. - Trip

As an FYI, the S21FE devices I got from T-Mobile back in June have the T-Mobile SIM and they connect to Sprint sites just fine, even those without 312250. If I open the service menu, I can see that despite what SCP tells me, I'm actually on 311490. Naturally, past performance is not an indicator of future results, etc. And I've been watching new gear fly into place in the parts of the Shentel region I'm most frequently in. It shouldn't be too terribly long before connecting to Shentel sites isn't really an issue. EDIT: And I'd consider taking a few T-Mo SIMs off your hands if you wanted to drop them in the mail. Can't hurt to have on hand for my phone collection... - Trip

Another weekend, another trip down toward Farmville. T-Mobile has been BUSY. These sites are now converted and operating: Burkeville Hooper Park (just south of the Burkeville tower) Raines Tavern A site in Cumberland county that I can't positively identify; possibly Ashby. Arvonia Radiant These sites aren't running T-Mobile bands yet, and either have new equipment observed awaiting activation, or lost B26 and thus are presumed to have new gear in place awaiting activation: Keysville Amelia East Sheppards Dixie Still waiting for more work to be done in Farmville proper as there are still three keep sites that haven't been touched, plus one T-Mobile site that still needs AWS and B41 added. Additionally, B66 is still tripping my phones up on some sites. Some just won't connect, but a select few actually kick my B66-locked phone off in such a way that it then refuses to connect at all to any site for some time afterward. My hypothesis is that I have to switch to a new TAC before it will reconnect, but I've not proven that. Not really sure what's going on. - Trip

Are there any devices on which NSG will lock 5G-NR? Doesn't offer the option on my Moto One 5G Aces or on my (now dead) One Plus N10 5G. And I didn't think the Snapdragon Samsungs could be rooted. - Trip

Well, I saw a good deal on a factory unlocked A32 5G on eBay and was able to convince the seller to show me the software info screen--and it was May. So I jumped on it. Stuck one of my Tello SIMs in it, and while my Moto One 5G Ace would connect to n71 SA, this phone refuses to do so. And with only 0 for the TA value, it's less useful for LTE than my older devices. Oh, and the *#2263# menu doesn't work properly for NR. So definitely glad I'm able to disable updates. - Trip

T-Mobile gear continues to fly into place at a rapid clip. Over the weekend, I saw that these sites that are now fully upgraded since the last time I went by, including B41 (all in Virginia): Jeffersonton Amissville Merrimac Stanardsville Quinque Charlottesville Downtown Lancer Park (Farmville) Keysville Bypass (!) Orange Water Tower (yes, in addition to the existing T-Mobile site. B12/71 antennas are present but not yet operating) Plus, Gear Mountain was now converted and running all bands except B41. And none of this includes sites I've spotted with new gear that has yet to be turned on. I was by many of these sites a month ago. I was by some of them two weeks ago. Crazy how fast this seems to be happening. Some of them have a weird issue where AWS spectrum is clearly running, but none of my phones will connect to it, including my S21FE on T-Mobile post-paid. I somehow convinced my S21FE to briefly connect to AWS at Lancer Park once, but was less successful at the newly-converted Culpeper West site I passed a few weeks ago and tried again today. Same problem I noted at Red House in my 8/27 post. - Trip

I don't see how it can wrap up this quarter (which I assume ends in two weeks) when there are still heaps of keep sites floating around right now that have yet to be touched, especially but not entirely in the Shentel region. - Trip

Just added a feature request in the issue tracker! EDIT: Sigh, I somehow have two accounts on Github... - Trip

In Virginia, I noted that US Cellular won only three licenses, two of which are in Charlotte and Prince Edward Counties, which are directly relevant to me. US Cellular is easily the most dominant carrier in Charlotte, but is limited to a single 850 MHz CLR block and a 5x5 AWS-3 block. I think they've recently won some spectrum in C-band or 3.45 GHz, but I'm not sure how useful that will turn out to be given how rural it is. Winning C1 here should help with their capacity issues a lot. T-Mobile got C2 and C3, so hopefully that means they'll be coming back and deploying B41 sooner rather than later. - Trip

I've done that before. When my AT&T data first went bad back in June, I used a different phone to plot the locations for my own purposes--but there was nothing I could do on the SignalCheck map. - Trip

Yep. Closing and reopening SCP resolves it, but it's annoying because you can't tell it's going to happen until you're moving, and then you have to ditch any data prior to that point because it's not accurate. Here's the bug report on the tracker: https://github.com/bluelinepc/signalcheck/issues/16 - Trip

Ouch: https://www.wvnstv.com/news/t-mobile-customers-have-minimal-reception-in-beckley-seek-more-coverage/ - Trip

From the "things not on my bingo card for 2022" department, it looks like the T-Mobile site in Red House, VA is now fully upgraded. I drove up to it this morning to confirm, and it now has B2/71/41, where previously it had been B71-only. AWS appeared to be present but not accessible, as any phone locked to B66 would fail to connect to anything, even though it's on high ground and should have seen AWS from sites 10 miles away, as my AT&T phone was doing. Notably, it also failed to connect to US Cellular B66 on the same tower, implying they have blocked roaming on it, which is also new. The Shentel gear on the tower was not operating as best I could tell; B26 would connect to more distant sites if chosen. I assumed backhaul would be a massive problem at the site, but maybe that's been resolved. In any case, assuming they ultimately offer home internet, it'll be a big deal for people around who have never had great options in the past. I got pictures of the upgraded setup which I'll post on Reddit next week. - Trip

Neat! Thanks. Most of my issues at the moment are from inexperience. I've never used AT commands and I'm bad at Python. I'm not really sure what the best way is to send AT commands to the modem; socat seems to work, and there are Python libraries that should do it, but I don't really know what I'm doing. - Trip