mikejeep

@mdob07 and any others who had the issue with the blank/invalid 5G-NR blocks appearing -- is that resolved in the latest update? @Trip are the color adjustments working how you hoped? Accent color goes by PLMN first then falls back to the provider name if it's not in the list, and added Shentel. Tweaked the text color options to hopefully make them more visible too.

I don't even know what to suggest.. I didn't touch any logging code. I changed some colors and a few display adjustments. This is maddening! Your report shows an error trying to create one of the database tables, which I believe is similar to what you were seeing before. I'll dive into it later on and see if there's anything new showing. Really wish I could figure out what the issue is here.. and why it's so inconsistent..

Another new beta is rolling out now, hopefully will be available this afternoon.. includes fixes for all of the issues mentioned above! Text colors have been added and others adjusted to maximize visibility. Also, the accent line(s) will now appear by default, and will be displayed on any mobile connection blocks when connected to one of the major US providers (it can still be disabled under Preferences). Feedback appreciated as always.. hopefully this version proves to be stable enough to be ready for public release.

Ugh. Getting there! I will keep working on it. It was invalid on your device before.. you should only see it if it is within the valid range now.

Another beta rolling out now! It should fix the issue with unnecessary GSM and 5G-NR display blocks appearing. If it's still not fixed, please send me diagnostics as usual. Thank you as always!

Yeah it's happening to several users -- my guess is it's on devices native to non-CDMA networks. My "fix" was clearly a "break" haha.. please send me a report, I hope to get it resolved by tomorrow morning.

Thanks.. can you send me a report when you're not connected to 5G but seeing that block?

If you have SignalCheck (Pro or Lite), try sending a diagnostic report (About > Send Diagnostics) with WiFi off. If it fails, connect to WiFi and try again, it'll save the previous report and send both. Maybe I'll be able to see something in the background that could be helpful.

Thanks! Does that unnecessary "GSM" block always appear? Or only when connected to 5G? Or something else? If it's only when connected to 5G, that was a hiccup I was trying to resolve with this update. Thanks for sending that report! At the time of your report, your phone wasn't reporting any 5G info -- keep an eye on it and see if it starts populating later?

Another new SCP beta rolling out now.. it should be available sometime in the next 1-48 hours. This update includes more 5G improvements and a couple of other minor bugfixes. Getting close to the finished product for 5G, at least visually.. once I am satisfied the data is accurate and reliable, I'll start adding logging and site note features. Has anyone noticed/confirmed any NCI patterns? Are the last two characters the sector, similar to GCI? Thank you for all of your 5G diagnostic reports and screenshots, it is greatly appreciated!

Yes, there are at least two OnePlus 8 TMOs on the beta.. and all reports are helpful, especially when there's context as to what the user thought they were seeing at the time (ie "My phone was showing 5G but SCP wasn't"). I receive a lot of reports, but more data is better so please feel free to send whenever you like.. especially after firmware or app updates. Some users run different OS/firmware versions and that helps me learn what issues might be my fault vs. what issues are resolved by system updates that I can't control. When you see 5G info in SCP, do those readings fluctuate? Or do they seem to remain stagnant? If they are changing, that's a strong indicator that it's valid data.

Thank you for the fast response! I do not have 5G access yet, so user feedback is the only way I can make progress.. I sincerely appreciate it. I will move the 5G block above the LTE info since I expect that to be a higher priority for most users. Will also resolve that extra display block appearing.. that's a side effect of some of the data being reported multiple ways. Will also continue adding support for logging/alerts/neighbors/etc as I go along. Please keep an eye on the band/frequency data to make sure the calculations are correct. I was getting errors that your n71 ARFCN was invalid, but your enginerring screen was reporting the same data.. (Also, I am still working on Dual SIM support, bug fixes, and everything else.. 5G support has become a priority at the moment since it's an active rollout and OS support for it is finally improving.)

The latest beta update finally went live at 5:09AM (Eastern) today.. let me know!

Thanks for the update, glad you got it figured out! I tried messing with some of my database routines this week trying to replicate your issue, but couldn't generate similar problems. Never hurts to go back and check my work once in awhile!

Pre-pandemic it was usually an hour or less, but there's no explanation or ETA given. Since March, Google has posted warnings of extended processing times but nothing specific. This is the longest delay I've experienced.. it's still pending, 18ish hours after I submitted it.

New beta rolling out now, should be available within the next few hours. Major work on the 5G routines.. fingers crossed for some great improvements. 5G-NR information will now be displayed in its own block on the main screen like other connections, and standalone 5G connections have their own status bar icons. There is still a lot of work to do, but hopefully this is a big step forward.. let me know! EDIT: Google Play is taking longer than usual to process this update. I will add a post when I get notified that it has gone live.

Your phone is reporting some GREAT details.. signal info, ARFCN, PCI, NCI.. I've been working on it! Will take me some time, but I have what I need. First time I have seen such complete information, thank you!

There is not anything within the app that deletes database rows, except for the function that clears duplicate GCIs.. but the user has to manually run that from the menu. Keep me updated please! -Mike

The widget is downright flaky on Android 7 and up. Android intentionally restricted the update frequency and I have yet to find a way around it. If you get in the scenario where it won't open SCP, it was probably shut down and killed from memory.. you'll have to re-launch from the menu, then you should be good for awhile. Happens to me as well. I really found the widget useful so I spend a lot of time trying to fix it.. zero success so far. I can't speak for S4GRU data sources, but on a similar note a I do know that T-Mobile LTE GCI patterns are nowhere near as consistent as Sprint's. Different markets have different rules, and many conflict with each other. Thankfully most phones report frequency info, but that's why you might not see secondary carrier info as much, or if you pay attention to patterns it might confuse you.

Trip, glad it started working (wish we knew why/how.. grr) and thank you for the suggestions about the accent color. I've gotten a lot of positive feedback and other similar suggestions.. honestly it caught me by surprise. I added the coloring on my personal version but didn't think it would be well-received so I kept it out of releases. I will expand it more and try to add as many options as I can get working!

I checked out your report; it all looks good, nothing to indicate that logging might not work. These logging glitches are very odd and difficult to reproduce across devices sometimes, and it drives me mad. As Robert mentioned before me, his Motorola had similar issues. I couldn't find anything wrong on my end but a couple of reboots did the trick. I have no idea how or why that would fix anything, but please give his suggestion a try and let me know..

I think I have been experiencing that with low-numbered Verizon 1X IDs (I never connect to Verizon LTE). I assumed it was something on my end, but maybe it's related.. I'll have to try getting some specifics and monitor that thread.

Another SignalCheck beta update rolling out now, should be available when "normal" people start waking up! Mostly more 5G fixes.. stale data, missing values, ugly text, etc. Please keep those relevant diagnostic reports coming, it is a huge help as I do not have a 5G device yet.

SignalCheck does not currently use either one of those codes, I have another method in place that is slightly different.. although maybe if my method fails, it should try those as a backup.. (EDIT: I forgot.. newer versions of Android no longer permit apps to make direct shortcuts to dialer codes.) Working on the stale info -- thanks for your diagnostics! I'm flying blind without you guys sending me data, so I sincerely appreciate it! Once it's reliable, I'll move it into its own "block" like the other connection types, and add full logging/alerts/icons/etc. We're slowly getting there. Unrelated note.. thank you to @S4GRU for the LG V60 reports tonight.. after a software update, it's now reporting 5G info in SCP as well! Hopefully more devices follow suit..

Another beta update to SignalCheck Pro is rolling out! Version 4.614b will appear on Google Play sometime over the next several hours. More 5G improvements, the accent color should be fixed, and several Samsung shortcut menus were added. Samsung users, please try all of the new shortcuts and let me know which ones are useful and what they lead to. Thank you!