mikejeep

Sure.. or it can just leave it blank or zero, whatever is easiest for you.

If the TAC is missing, an entry is still recorded in the log, but it would not be included in uploads.. so you could probably manipulate a trail log export to add the data to the map if you were able to nail down the sites without the TAC. EDIT: Sites with a missing TAC are only recorded in the log if the option to do so is enabled (Logger > Log Sites with Missing TAC).

Unfortunately I'm not seeing it either. LG must have broken something with that Android update.. there is no NR TAC in the LTE+NR report you sent. As you saw, it does report a valid TAC in NR-only mode. There isn't much I can do with no TAC being reported -- however, I recently discovered that a new telephony callback method was quietly added in Android 12. I am looking into it, but it's going to take me some time to get a beta with it included. Not much is published about it yet and I don't have much time at the moment. But I'll try to see if I can get something put together specifically to at least try resolving this.

A new version of SignalCheck Pro is finally being released and should become available on Google Play within the next several hours! Version 4.71 includes MANY bugfixes and new features. To view the full changelog, visit this link or go to About > Change Log from within the app. Please feel free to post feedback or questions, and thank you for your support!

New SCP beta rolling out now, fixes the issue with the pending web upload count missing from the popup window. A public release will finally be rolling out with this version as well!

I completely agree on both points. The article says T-Mobile/Sprint is down 5,500 jobs -- yet AT&T and Verizon are down 114,500. How is T-Mobile the problem here? And covid is not mentioned at all.. and that is undoubtedly a massive factor.

Oh wow, you're right! That was not intentional.. and I didn't notice because I've been testing the new option from the main screen. Thanks, I'll take a look.

Another SCP beta is rolling out now, mostly bugfixes and cleanup.. very close to being stable enough for a public release. Thanks for all the help!

Another SCP beta is rolling out now! This release includes bugfixes. Beta Crew members (and any other users who would like to help facilitate app development), I would appreciate it if you could please add a username or e-mail address on the Send Diagnostics screen and send one report (*if you've never done so before), even if you do not need to send diagnostics. This will save your info to be automatically included in crash log reports. That way if I see an automated report and need feedback, I can contact you. Thanks!

I have never been able to duplicate it, and it seems to be rather random. It's something at the OS level.

Thanks -- unfortunately that is an Android bug introduced in Android 10 and resolved in Android 11 that has no known workaround. I have thousands of identical errors logged.. it drives me crazy. Wish I could do something about it, but I have yet to figure out a way. Here's the issue tracker entry if you're curious: https://issuetracker.google.com/issues/141438333

Another SCP beta is rolling out now -- bug fixes and a new Beta Crew option to display your pending web upload points on the main screen, updated every time your screen refreshes. Click on the number and an upload is triggered!

This thread is specifically about Super Bowl mobile coverage. From a tech standpoint, it's pretty cool to see what can be accomplished. I would suggest skipping over it in the future if you're not interested.

How is the latest beta (4.691b) from over the weekend handling these scenarios.. are they resolved?

A new SignalCheck beta release is rolling out now, version 4.691b. It resolves the missing web upload usernames and should fix some LTE and NR band identification issues. Please update and see if recent issues have been resolved! Thanks.

I get what you're saying, but how about this for crazy perspective.. we're at a moment in technology history where 76mb/s is not "too impressive" for a mobile device. It's not a start, we have come a long way. Looking back at the device and network capabilities mentioned in early S4GRU posts makes me chuckle.

Can you send a diagnostic report next time you see that? Was it reporting n41 before this version? Thanks.

Another SCP beta is rolling out now.. band identification has been improved for both LTE and 5G-NR on newer devices (including C-band n77/n78). Also adjusted the plain new "<connection type>" field to now display as "Restricted <connection type>" to help communicate that the mobile connection might not be fully in service. Fully active connections will continue to display "Connected to <connection type>".

This is a result of the change I mentioned above, sparked by @PedroDaGr8 trying to log AT&T cells with a non-AT&T SIM that was reporting "out of service" but still capturing cell info. For the moment (subject to change as I keep testing and getting feedback), the "Connecting to" prefix will disappear when you connect in a scenario like that. I may adjust it to show a special prefix like "Limited LTE" or "No Data LTE" to make it more clear what is going on, but I also need to make sure that's only appearing at the proper times. When you were seeing just "LTE" in your screenshots, was there anything unusual about your connection? I see the app indicated you couldn't make calls; could you transfer data? Can you send a diagnostic report next time you see that? I'm seeing this more frequently, unfortunately -- it has something to do with Android's power saving efforts I believe. Was the app in the foreground when it happened? When the screen updates, the notification and home screen widget are also updated -- but as seen with the widget for the past couple of years, Android doesn't always execute the update. I'm constantly trying to find ways around these limitations, since the app is useless if it's displaying stale data.

The latest SCP version is almost done working its way through beta testing, and a full release might be ready next week. In the meantime, I'd appreciate it if users could take a moment and 'star' this Android bug that directly impacts the reliability of 5G-NR info that SignalCheck (and similar apps) tries to display. It only takes a moment, and helps prioritize what gets looked at by Android engineers.. thanks! https://issuetracker.google.com/issues/215232946

A new SCP beta is rolling out now and should be available shortly! This update should fix the GCI and NCI issues on exported site logs mentioned above, as well as some cleanup of unused log columns and tables. I also changed the method the app uses to identify and report connections; when the device is reporting it is out of service but still seeing cell info, it should now still record that cell info in the log. This will need some testing; issues may arise while roaming or in fringe signal areas, but we will see. If this proves to be stable over the next several days, it will become a public release next week. Fingers crossed!

Thanks for heads up, will fix that!

Another SCP beta rolled out yesterday afternoon.. more bugfixes and improvements. NR NCI formats have been adjusted as discussed above.

Are you running the public release or a beta? Sprint/T-Mobile site note matching was improved in 4.681b and should resolve the issue you're experiencing. It's coming soon to the public version.

T-Mobile sent me a CellSpot to replace my Airave. First one would not activate.. replacement unit works great, just like the Airave.