RAvirani

It looks like the phantom NR connection when my second SIM has gone to no service is still an issue .

On 3/11/2023 at 6:57 PM, jasonsteele said:

Updated my AT&T S22 last night, NR bands show up now.

https://imgur.com/a/qEZh0dN

I’m also seeing NR bands on my VZW Galaxy. 

On 2/27/2023 at 5:59 PM, PedroDaGr8 said:

Found the permit for it! Looks like it will be Verizon, T-Mobile, and AT&T at minimum on the tower. The bottom rack is described as "future antennas by others", which makes me think Dish will be on there as well. 

Oh—this is the new CC site. I’m surprised they’re moving so fast!

Which tower are you referring to? Did you snag any pictures?

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...

4 hours ago, cjauregui said:

Was wondering if you guys can give some insight into something. In Puyallup there is a tower that was approved to be upgraded in Jan 2022. It's now Feb 2023 and the upgrade has not been done. The city sent a letter telling them they have 60 days to start the work or lose the permit. Is this normal for T-Mobile to wait this long to upgrade a tower?

Which site?

16 minutes ago, PedroDaGr8 said:

Looks like GPS Status and Toolbox

Yup. It keeps GPS info up to date while logging. 

A few bug screenshots:

https://imgur.com/a/eue3BVj

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?

7 minutes ago, mikejeep said:

Interesting, that doesn't happen on my P7. Can you send me a diagnostic report the next time you see that please? Hopefully the phone isn't actually reporting the -115, that will be tricky.

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?

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. 

5 hours ago, mikejeep said:

A fresh SCP beta is rolling out now.. mostly bugfixes, but also includes a new option to display the cell timestamp at the top of each mobile connection "block". 

Thank you for this!

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. 

10 minutes ago, CrackedLCD said:

Is there an issue with the web upload server tonight? I'm getting an immediate failure when attempting to upload points. I've tried on data and two different WiFi connections.

After exiting and restarting the app, it not only failed again but then the entire app became non responsive. Diagnostics sent about an hour ago. 

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. 

3 minutes ago, mikejeep said:

I will continue to make adjustments to it, but in the meantime if you do a swipe-down refresh, that will always poll the database to get an accurate pending count.

That’s what I’ve noticed and been doing .

51 minutes ago, dkyeager said:

Counter on screen was showing significantly higher number than web upload.

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. 

1 hour ago, Trip said:

This please, for people who aren't using dual SIM devices.

- Trip

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. 

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”

5 minutes ago, mikejeep said:

Was it happening when the app saw it as Dish NR, or when you knew it was Dish but the app was showing AT&T?

The app reported it as Dish NR. The PLMN was 313340. 

9 hours ago, mikejeep said:

Can you send a diagnostic report next time you see this?

Hmm that is weird -- can you send me some log exports (and diagnostic reports if you see it wrong on the fly) that show that so I can try looking into it?

Sent diagnostics for both of these. 

9 hours ago, mikejeep said:

I was using sample data from those Houston sites to confirm my math -- do you have your cell ID preference set properly in the app? Check Preferences > Display Settings > LTE/NR Cell ID Format, I believe you will want "Decimal w/Sector" to have the app match the map.. if that doesn't work, try a different setting just in case. Shoot me a diagnostic if you're still not seeing them.

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. 

29 minutes ago, mikejeep said:

I'll change Verizon to 16384 in the next update.

Thanks!

29 minutes ago, mikejeep said:

I was using sample data from those Houston sites to confirm my math -- do you have your cell ID preference set properly in the app? Check Preferences > Display Settings > LTE/NR Cell ID Format, I believe you will want "Decimal w/Sector" to have the app match the map.. if that doesn't work, try a different setting just in case. Shoot me a diagnostic if you're still not seeing them.

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?

29 minutes ago, mikejeep said:

Can you send a diagnostic report next time you see this?

Hmm that is weird -- can you send me some log exports (and diagnostic reports if you see it wrong on the fly) that show that so I can try looking into it?

Yes—I’ll try to send both of these today. 

29 minutes ago, mikejeep said:

You are right, looks like the notification is hard-coded to display hex format -- I will fix that. Are the triggers themselves working properly?

 

 

Thank you! And yes, the triggers are functioning correctly. 

13 minutes ago, PedroDaGr8 said:

By the way Mike, I have noticed that the map and the app report different gNBs for Verizon NR. From the map, it looks like Verizon is using 22-bit gNBs while the app is using a different value. You might want to work with @RAviranito get on the same page. 

The Verizon 5G cell ID to sector/site should be remainder/division by 16384.

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?

8 hours ago, mikejeep said:

Missed this earlier.. I added it to the request list. I initially kept it all "AWS" because squeezing in "AWS-3" on the status bar icon was difficult to read. Would it be sufficient to change everything but the icon, or were you hoping for the icon also?

Everything but the icon would be great. 

8 hours ago, mikejeep said:

Another attempt to fix web data points that are failing validation when dual SIM mode is enabled. This issue is caused when data points on both SIMs are simultaneously recorded at the same location, which is causing the mapping server to interpret them as stale.

Adjusted cell ID formatting for DISH Wireless 5G-NR connections.

Thank you!

6 hours ago, mikejeep said:

A fix for web data points that were unnecessarily failing validation when dual SIM mode was enabled. Wanted to get this rolled out quickly to minimize the impact on mapping efforts by the dual SIM crowd.

I’ll get this one sorted out on my side today. 

EDIT: There’s a problem with the app implementation—sent you a PM.