Jump to content

RAvirani

S4GRU Staff
  • Posts

    3,457
  • Joined

  • Last visited

  • Days Won

    159

Everything posted by RAvirani

  1. It looks like the phantom NR connection when my second SIM has gone to no service is still an issue .
  2. I’m also seeing NR bands on my VZW Galaxy.
  3. Oh—this is the new CC site. I’m surprised they’re moving so fast!
  4. Which tower are you referring to? Did you snag any pictures?
  5. T-Mobile and Sprint both had racks on this tower. They’ve permitted to take over the Sprint rack, although there were some question marks about breaking the original T-Mobile lease. My understanding is they are reevaluating whether the increased RAD center would appreciably impact 2500 layer coverage. Not sure if a verdict has been reached there...
  6. Yup. It keeps GPS info up to date while logging.
  7. A few bug screenshots: https://imgur.com/a/eue3BVj
  8. When I’m connected to NSA NR and I have time stamps set to each cell block, the NSA NR connection has a blank line at the top. Any ideas why that may be?
  9. Service mode shows the SIM as having no service, so I would think the device should report that. I believe I sent a diagnostic report a little while back—can you check to see if you have it?
  10. Hey Mike—another dual SIM bug. If one SIM loses service, it doesn’t disappear from the app. I’ve seen this a couple times—my Dish SIM will lose service (confirmed in service mode), but SCP won’t stop displaying -115 or so. And it logs a data point at that signal every time the location updates. Along the same lines, I have a custom trigger set up for 313340 (Dish), and the custom trigger keeps firing when this is happening.
  11. Hey Mike, another feature request—could we have to option to set a maximum number of neighbor cells to display? I like being able to see neighbors, but when there are 15+ neighbors, I can’t see my second SIM. Also, I’m still experiencing the NSA 5G band bug. After connecting to SA 5G, NSA 5G incorrectly displays the same frequency/band as SA. For example, when I first open SCP, AT&T NSA 5G shows as “5G-NR”. But if I connect to Dish SA 5G 600, all subsequent connections to AT&T NSA 5G show as “5G-NR 600”. Restarting the app is what I usually have to do to fix it.
  12. It’s down for updates currently. I was originally planning to have them done by tomorrow morning, but it looks like I might be able to wrap them up tonight.
  13. That’s what I’ve noticed and been doing .
  14. I see this bug a lot. For some reason, my devices will start to count points in twos or threes sometimes. I’ve seen it count as high as twelves each time the display updates. Not sure what could be causing that.
  15. If you’re only using a single SIM, it’s really just that line moving into the signal info block…although I suppose it’s easier to read when it’s at the top.
  16. Hey Mike, another request. Right now, the timestamp displayed at the top of the screen seems to update whenever there is a signal update. But with dual-SIM devices, it’s unclear when each SIM’s signal info was last updated. Could we scrap the timestamp at the top and instead add a line in the text under each connection reading something like: ”Updated: Jan 13, 2023 1:24:00 PM”
  17. The app reported it as Dish NR. The PLMN was 313340.
  18. Sent diagnostics for both of these. I couldn’t get a diagnostic of this today, but I can confirm the app is still doing a simple remainder/division by 1024 on Dish.
  19. Thanks! Looks like I didn’t update the hex calculation on the website, only the decimal one. Can you validate against the decimal ID until I can get that done? Yes—I’ll try to send both of these today. Thank you! And yes, the triggers are functioning correctly.
  20. The Verizon 5G cell ID to sector/site should be remainder/division by 16384.
  21. Couple bugs I’ve noticed this morning: Dish IDs appear to be unchanged…there are some examples of the calculation on the map in Houston, TX. After connecting to Dish SA 5G 600, AT&T NSA 5G incorrectly displays as 5G 600. ServiceMode confirms AT&T 5G is n77. 5G custom triggers don’t obey the site ID format. For example, I have my format set to decimal but this is what I see on my alerts: https://imgur.com/a/XeCVvDE There seem to be a lot of 313340 entries getting identified as AT&T and a lot of 310410 entries identified as DISH…any idea what could be happening there?
  22. Everything but the icon would be great. Thank you!
  23. I’ll get this one sorted out on my side today. EDIT: There’s a problem with the app implementation—sent you a PM.
×
×
  • Create New...