mikejeep

Google Play has been slow at approving releases lately, but I did see it finally got cleared around 9:15 Eastern this morning. Those seem like low duplicate numbers, that is good. Mine were worse but I also intentionally try to force behavior to trigger bad logs for testing purposes. If you run the "Clean up duplicate GCI" entry from the Logs > Clear menu, it will eliminate them.

Neighbor notes have been available for a long time.. many years. Sorry if my post wasn't clear, I was saying I made improvements to that feature.. fixed some bugs and overhauled how the app looks for notes that may be recorded under a different PLMN (like T-Mobile/Sprint Keep sites/etc). NR sites can be tricky depending on the provider because some use multiple NCIs per site.. and in my area, T-Mobile has changed a lot of them. For T-Mobile, I have not identified a pattern between old and new NCIs, so until you save a note under a new NCI, it's going to be blank. If you long-press on the "Connected to [LTE|NR]" label, it will send diagnostics immediately. There's no ability to add a comment to that report but you can send a few when you're seeing an issue and then send one with a comment referring to the other reports so I know what I'm looking for.

A SCP beta update is rolling out now.. it includes more adjustments to site note features including saving notes and displaying neighbor notes. If you are seeing odd behavior with notes (especially those of you 'missing' notes that you know should be appearing), please send a diagnostic report soon after you observe this behavior. I have added additional logging that should capture what is going on (it can be seen on the Diagnostic Mode page). A major improvement to the function to clean up duplicate LTE GCIs is included in this release. Instead of deleting all duplicate entries, it will now save the entry that has the highest 'hits' column value, and delete all others. It is not perfect, but should be a huge improvement over deleting all of the entries. Please keep in mind if you have duplicates, this could impact site note display. Duplicate GCI entries are typically a product of quickly-changing PLMNs that the OS does not report in sync with other data, resulting in some information being logged with the wrong PLMN. Similar issues are happening on dual-SIM devices that I have not been able to resolve yet. Keep in mind that dual-SIM functionality is still in testing, and even the new option to disable dual-SIM logging is still buggy. I'm working on it! Thanks for all of the feedback, keep it coming...

Thank you Robert, that means a lot -- especially coming from you. I appreciate everything you have done to host this site, notably allowing me to make it the de facto discussion forum for SCP. Thank YOU! To be clear, I am not ending my efforts or looking to hand the app off.. just figured a user with more skills than me might be interested in lending a hand with some of the issues I haven't succeeding in resolving. It's more fun to add new features, but I find myself spending more and more time chasing bugs instead of doing cool stuff!

Another beta is rolling out now with some more adjustments and additional diagnostics. The last two beta releases have taken 48+ hours for approval, hopefully this one clears quicker but that's up to Google Play..

As many of you know, SignalCheck is a side hobby for me. I taught myself Java when I began this project over a decade ago and I am still learning. I am far from a professional programmer, but I have figured enough things out along the way to get the app this far. Lately, I have been struggling to find the amount of spare time necessary to keep up with app development and bugfixes, but I am still enthusiastic about pushing SCP forward. If someone with experience in Java and Android app development would like to lend a hand, especially to help eradicate some of the most challenging issues I have been unable to resolve, please message me. Thanks!

Ahh then it sounds more like yet another dual-SIM bug! Thank you, that is a big help.. I've been working on trying to figure this out.

Did they previously hop between n38 and n41 in prior version of SCP, or have you always seen n41 displayed properly?

That's not good. Please back up your log databases in case an app bug is doing something to erase your existing notes.. with the changes made in that version, I suspect it's more of a search query issue, but it can't hurt to be safe. Strangely I'm not seeing the same issue myself. Could you send me 1) screenshots of instances where notes are missing, a 2) backups of your log databases? PM or email is fine.

No, the beta is completely independent of that.. Google Play's review processes are just unpredictable. I don't see any specifics, other than the time I submitted it and the "In Review" status. This release took longer than usual to be approved, but it was not out of the normal range. New beta is rolling out now with some more adjustments to the NR band correction algorithm as well as some other NR bug fixes.. please let me know if it resolves this issue.

Depends on if you are in the standard Beta group or the Internal Test group. I roll all releases out to both groups simultaneously, but Beta releases get screened/analyzed/reviewed by Google Play first, in the same manner that production releases are. Internal Test releases become available immediately. When they came out with the Internal Test option (which has a limit on number of users), I offered it with the caveat that they're slightly riskier because of the lack of review and let users decide which group to be in.

Looks like the standard beta hasn't cleared Google Play's review process yet. Sometimes it clears within an hour, sometimes it takes over a day.

A new SignalCheck beta is rolling out now and should be available on Google Play shortly. It includes some new user-suggested features and several bug fixes. One change that should be noted is that secondary SIM cells are no longer logged by default; there is a new option under the Beta Crew menu to re-enable it if you prefer. I have not been able to get Dual SIM logging to be reliable yet, random entries mix and match the provider details and SIM number. Hoping this at least resolves the issue with inaccurate log entries for the primary SIM. Will continue to work on that.. it remains the final hurdle to open up Dual SIM support for all users.

I have workarounds that essentially do this, but it has taken some time to catch every instance in the code where things need to be adjusted, especially with dual SIMs in play. I have been making further improvements in a soon-to-be-released beta. I see this frequently as well on my Pixel 8.. unfortunately, I have yet to come up with a workaround because the OS is still reporting it as a valid connection; at least the timestamp freezes so you have a clue that something is up. I'm still trying to find the best way to handle this. I overhauled the site note editing/saving/querying functions in the aforementioned beta in progress.. "coming soon" Appreciate all of your feedback as always!!

Sorry for the delayed reply, I missed the notification.. SignalCheck doesn't really 'control' how quickly the information refreshes. To oversimplify it, the app listens for signal changes, and displays them as soon as they happen. The rate depends on many variables, including device configuration, power status, radio programming, etc. The biggest driver of updates is flowing data -- if your device is idle and also not moving, not much will change because it's not going to "waste" effort updating signal metrics. But if you are sending/receiving data (streaming audio or video is a big trigger), or your location is significantly changing (drive faster for more frequent updates.. just kidding), you should see more frequent updates. I don't know the inner workings of Cellmapper, but it's likely designed in a similar fashion; there is no native accessible "force the modem to refresh the information" command that I am aware of, but there could be. If you notice quicker updates when you have Cellmapper running, it could be because Cellmapper is sending/receiving data (I know there is an auto-upload function), or Cellmapper is configured to use more precise location information, so your device is more sensitive to smaller movement. You can adjust SCP location settings under Preferences > Location Settings; if you increase the priority or decrease the update interval, you will get more accurate and more frequent location updates, but be aware that this may increase battery usage. Hope all that makes sense! Feel free to let me know if I can clarify anything further.