Jump to content

Trip

S4GRU Staff
  • Posts

    2,265
  • Joined

  • Last visited

  • Days Won

    88

Everything posted by Trip

  1. B66 is a superset of B4 (AWS-1 only), which contains both AWS-1 and AWS-3 spectrum. So downlink spectrum below 2155 MHz is AWS-1 while downlink spectrum above 2155 MHz is AWS-3. It looks like SCP just assumes that B66 = AWS-3, and that's not correct, only a certain range of EARFCNs are actually AWS-3. 66886 looks like the dividing line. EDIT: But it occurs to me that someone could own the top 15x15 of AWS-1 and the bottom 5x5 of AWS-3, and then set up a 20x20 in B66 that technically has an EARFCN centered in AWS-1 but is actually AWS-3 since it covers AWS-3 spectrum. Not really sure there's a good way out of that, were it to come up. (I, personally, had no problem with it just saying "AWS" as it did previously.) So, wait, is dual SIM enabled by default? Considering most devices do not support dual SIM, maybe it should be disabled by default? In any event, for me, dual SIM is grayed out, as my e5 Play runs Android 8. See here: https://imgur.com/a/BefJJEo Note that I couldn't get SCP to stay open without putting my phone in Airplane Mode. Even after rebooting, it just kept crashing over and over otherwise. - Trip
  2. Mike, I've upgraded a subset of my devices to the latest beta. I sent you diagnostics on two separate issues this morning. 1) Less serious, but on at at least two devices, I'm seeing "LTE AWS-3" on GCIs that clearly have EARFCN values placing them in AWS-1. Whatever EARFCN-checking code is in place is clearly not working correctly. 2) Far more serious, the e5 Play I upgraded (I have several) crashes all the time with this build. The Pixel 3a and the Moto One 5G Ace each crashed once and then stayed running consistently for the rest of this morning's shopping, but the e5 Play crashes any time it changes status. So, going from signal to no signal, or vice versa. So, amusingly, hitting the "Reset Connection" button proceeds to immediately crash SCP as soon as Airplane Mode kicks in. And after doing that as a test, I couldn't get SCP to reopen without immediately crashing again until I rebooted the device. I tried to send some diagnostics but I'm not sure whether they went through or, if they did, whether or not there will be anything useful in them. Let me know if there's anything more I can do to help track down that particular issue. - Trip
  3. As best I can tell, the site chamb is referring to is using all new gear. The GCI pattern is the same as the 600/700 values on that site. I've got one just like it down in Buckingham County, VA, a site that had T-Mobile on it prior to the merger. Same story, the GCI pattern is that of the 600/700 T-Mobile gear and not that of the retired Shentel gear. https://imgur.com/a/gm5qTaa They may be doing it to make sure the licenses remain valid pending sale. - Trip
  4. It is. If I'm barrelling down the highway and glance over, I can check both timestamps at once if they're together at the top. If they're scattered into random places along the way, not so much. - Trip
  5. This please, for people who aren't using dual SIM devices. - Trip
  6. Mike, I'm holding off on updating per your previous suggestion about potential breakage from the dual SIM support changes. I'm returning from my next trip out of town on Sunday and should then be home for the next two weekends, so I'll plan to upgrade my devices once I return. Thanks so much in advance for the auto-reset functionality. I had assumed it would only work for devices with root access, which is all but two of my regular devices as of right now. The issue, for what it's worth, is that I have band-locked phones on T-Mobile, and sometimes when the connection is lost on a particular band, it takes a few minutes before it comes back. It must stop scanning to save power or something. Resetting the connection can bring it back if the signal is present when the reset occurs. EDIT: Separately, I just sent a donation your way. Thanks, as always, for all you do! - Trip
  7. I personally use SQLiteStudio. Got it open right now, trying to rush through data from a trip on Tuesday before I go out of town again tomorrow morning. I have 48,000 rows in sites_lte and 5,000 in sites_nr, most (not all) of which have proper labels on them. - Trip
  8. Is Dish really green/purple? I know Genesis is, but aren't they going to be selling their service to the general public under the Boost Unlimited brand, which appears to share the orange theme of Boost Mobile? - Trip
  9. Green is used for US Cellular because its blue color is a very similar blue to AT&T. What about an orange color like Boost Mobile uses? - Trip
  10. I have mine set to 2 seconds across all of my devices. Of course, my devices also have Tower Collector and Cell Mapper running at the same time as SCP... - Trip
  11. T-Mobile, historically, built out tower sites to fill the map rather than serve people. In one case, they actually built a tower in the middle of nowhere, an island of service surrounded by miles of "no service" which, of course, was greatly exaggerated on the map. Today, that tower has B41 on it to serve a bunch of forest land. As best I can tell, that strategy has changed now, at least here in Virginia. I think they're building out easiest sites first; trying to get as much online as fast as they can. - Trip
  12. I have 10 phones (9 of them solely for logging purposes) and all of them show me the notification when it starts and again when it finishes, and then leaves a notification in place until I dismiss it. Oh dear. That sounds ominous. - Trip
  13. Oof. Stay safe! We dodged the bullet in the DC area. It rained but the high wind dried the roads before they froze. - Trip
  14. I know it's Service Mode RIL, which appears to be something like: com.sec.android.RilServiceModeApp No idea beyond that. (*#73# I had to enable manually with the steps found in the link in the S22 thread. *#2263# works by default on T-Mobile, and is just a submenu of *#73# so I generally just use *#73#) - Trip
  15. I love the idea of the action button, though most of the actions don't work on my S21FE or aren't particularly helpful. I'm wondering if it would be possible for it to open the *#2263# or *#73# menu. - Trip
  16. The annoying thing is that I'd been sending him databases with that column removed, and forgot to do it last time I sent it because I was in a rush. Naturally, that's the time it caused a problem! I just tried to send you diagnostics but I'm not sure if it shows anything. It's kind of sporadic on the WiFi here because the modem is sitting at values around -17 dB RSRQ so it comes and goes. But just by turning off the WiFi while I have no service here I was able to get it to fail immediately to the log-in screen with the same toast message. Here's a screenshot: https://imgur.com/a/5MZffuP Understood. The "Validating" message does help, but an app locking always creates the perception of a problem even when none exists. - Trip
  17. Er, sorry. I know this is my fault. 😅 Separately, I wanted to flag that the new log-in feature for uploading could probably use a bit of tweaking when it doesn't work properly. I'm currently in my standard Poor Reception Area™ and I've had it prompt me to login when the connection was bad. It even pops up a message indicating that it's an Unknown Host Exception or something along those lines. Seems like it should just say "unable to connect" or something. It also seems to hang the app while trying to figure that out, though I'm not sure there's much you can do there. - Trip
  18. I've been locking my S21FE to n25 for several weeks now. Granted, I did the steps in the S22 thread to unlock the bands that the phone supported but weren't enabled... Separately, I'm on Unlimited Freedom and got migrated to the T-Mobile billing system today. Got the text during the day, and just now set up my account. I have to say I liked the old Sprint interface better, but it's not a complete disaster. Poking around to see where things are as it seems to be scattered all over the place. - Trip
  19. Yes! It works for me now as well. Just uploaded 3006 points. - Trip
  20. Still no luck. Diagnostics sent. - Trip
  21. I also sent a new report a while ago. - Trip
  22. I'm now also getting the [null] error. Previously I was getting the null pointer exception. Definitely seeing my device (multiple times) on the web page. - Trip
  23. I sent diagnostics on the new update as well a little while ago. - Trip
×
×
  • Create New...