mikejeep

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!

No, unfortunately I haven't seen any useful 5G info from your phone (or anyone else's LG) yet. If you get a software update and happen to find 5G before they shut it down, please try reporting again! The accent color is still in its infancy and only appears on LTE for now. I've had it on my version of SCP for several weeks, initially I didn't think anyone else would like it. Figured I'd offer it up and see what the feedback was.

I accidentally broke the Samsung menus when I compiled the latest release; it will be resolved in next update. Thanks, I'll look into that.. it's all a work in progress, glad we are making some headway! The current display format is temporary, it is just to get the data displaying reliably.. once that happens, it will get its own "block" like the connection other technologies have.

Another beta is rolling out now, 4.613b.. I am trying something new with this release. It will only go to some of the Beta Crew, but those who get it should see it on Google Play much faster, perhaps within a few minutes. I targeted many of you who have provided recent 5G feedback. It contains fixes for color accent, 5G, and Samsung shortcuts that were part of last night's beta update. Please try all of the Samsung menu items and let me know which ones (if any) are useful! If there are bugs, send a diagnostic and note what's going on.. thanks!

Hey thanks!! 🍻 I already saw your report and have been looking into it, I'm trying to get another release pushed out this morning to give you guys another try at everything for me.. the Red Pocket SIM caught my eye as the only oddity, although SCP identifies it as T-Mobile so it should show a magenta line. Did you try restarting the app after enabling the option, just in case? (You shouldn't have to do this but who knows). I'm adding some extra logging that should show me some more details why this might be missing. Stay tuned.

Doh.. your diagnostic reports are one of the things that helped me identify how to extract more 5G data. I only saw one new report from you but I'll see what I can tweak and hopefully get things working..

New SignalCheck beta release was rolled out tonight and went live a couple hours ago.. some new goodies: A shortcut to the Samsung Band Selector was added; I have no ability to test it myself so please let me know if it works. A new option allows you to add a thin accent line to the LTE info block, which will be colored based on which provider you are connected to. I was trying to add something discreet to be able to quickly tell if I'm on Sprint or T-Mobile.. any feedback to improve this would be appreciated. The best change is a significant increase in the amount of 5G information that the app can discover! Some recent diagnostic reports are showing some useful information, it looks like the latest Samsung update began reporting some new things. Please test and let me know if anything appears. Diagnostic reports are always useful because of the backend details I get. Hopefully these all work well, let me know..

I didn't know that had changed, thanks.. very good to know for testing!

I wish Google would release the RCS API so third-party messaging apps could take advantage of it..

Shoot me a diagnostic if you can catch this again! Invalid signal levels should automatically be filtered out. Yeah, B66 and B71 are natively reported wrong on many devices due to an Android bug. SignalCheck tries to catch these and report them as B66/B71, but it's tricky because in some instances the incorrect band is actually a possible valid result. I'm not aware of B7 showing up, if someone catches that please send a diagnostic.. it is likely B66/B71 being reported incorrectly but not getting caught.

The report you sent showed the app was displaying B2 and the icon at the time was also B2--I checked the graphics to make sure the B2 icon didn't actually say B71, LOL.. if it happens again send another report! I don't recall any recent reports of the notification icon falling out of sync with the app itself.