mikejeep

Oh I have diagnostics from others with a OnePlus that is reporting n25 but at 2600 MHz. Because of the Android band reporting bug and all of the other evidence in the wild, I trust the ARFCN more than the reported band so I implemented a workaround.

Any that were reporting bogus info before.. 😁 Somehow some OnePlus devices are natively reporting n25 instead of n41. Totally different spectrum blocks, so I can't even figure out how the OS would get confused with that.. but it is happening..

A beta update is rolling out now, includes bugfixes that I hope to release publicly this week.

47 is pretty good.. but there is no set number. It just "helps".. allegedly.. 🤞

It's a known Android 13 bug.. not the app, and can't do much about it other than select a different icon type: https://github.com/bluelinepc/signalcheck/issues/18 Please give it a +1 on the Android Issue Tracker to help get it some attention: https://issuetracker.google.com/issues/244063666

I have discovered a bug in the latest release that is causing force closes for users who have not granted proper Location permissions to the app. I hope to have a fix implemented soon, and will get it rolled out after a brief testing window. In the meantime, impacted users can avoid the crashes by granting precise location permission to SignalCheck (the app is severely limited without it anyway, although it should not crash).

Haha yes it was.. but that's ok! I should've handled that scenario, it just never crossed my mind that a "Back to the Future" situation might come up.. 😁 Nice catches. I try testing all the possible scenarios and handle them gracefully, but it's tricky to plan for everything (see above). Did you happen to send a diagnostic when you got the funky error message? If you can make it happen again, that would help me identify exactly what I need to catch. Yes, this is something I know needs to be improved. I have it display the toast message that it's connecting to the server to let users know something is happening, because that was the quickest implementation I could get working. My goal is to display the login dialog box first, then some sort of animation placeholder while the network connection is working.

Rolling out a minor beta update right now.. will hopefully resolve issues for users who imported databases from newer versions of the app than they were running at the time.

A SignalCheck Pro update is finally rolling out to users right now and should be available on Google Play within the hour! This long-overdue update includes a tremendous amount of bugfixes and stability improvements, especially on 5G-NR connections. View the full changelog here, and feel free to reach out with any feedback by whatever means you prefer. Thank you all for your support and patience.

Another SignalCheck beta is rolling out now -- I was able to replicate an additional instance of n7/n38 appearing incorrectly and improved the workaround for that (hopefully that resolves it for you this time, @dkyeager). This update is being pushed out as version 4.731b to the Beta Crew and version 4.73 to the public!

One last beta update is rolling out now before it goes live for the public.. this includes minor code improvements and cleanup, and the removal of the [SCC] indicator on neighbor cells. For now, only the [PCC] indicator will appear (if applicable) on neighbor cells, as the SCC indicator is basically redundant. If anyone has seen the PCC indicator on their device (or sees it in the future), please let me know. This will likely only appear when you are in a dual SIM configuration and it should help me provide dual SIM support. Absent any new bugs appearing with this update, a parallel release will finally go out to non-beta users soon!

I believe I have finally tracked down the cause of the null pointer issue, it was a compiler issue -- which explains why I could not replicate it myself. New release is rolling out to Google Play now. Please test and submit diagnostics if you encounter any problems. Thanks for all of the help and feedback!

Ok, thanks (EDIT: I didn't get fresh diagnostics from you).. won't be able to get any other updates out tonight, but I'll be working on it again tomorrow. I would appreciate additional diagnostics from anyone who wants to try logging in and sending them. Any logged is still saved, and your device(s) are actually logging in, there's just something weird going on with processing the login response.. if I can't get it fixed by tomorrow afternoon, I'll push out an update that will bypass some things as a temporary fix.

Another update rolling out now.. very odd how I can't replicate this on my devices. Fingers crossed this does the trick..

Another beta update rolling out now, another attempted fix at the web login issues. As before, try to log in and please submit diagnostics if it fails. If logging in works properly, please attempt to upload your data, and also attempt to log out from within the app. Thank you!

Rolling out a new beta release now with some minor adjustments and additional logging. Please log out of the app (or remove your session(s) from the website if the app is not providing the log out option) and try to log in again. If you experience an issue, please submit a diagnostic report immediately after your attempt. Logs only capture a limited amount of information, and sometimes a delay causes the useful information to already be overwritten. I also sent an e-mail to the beta crew offering a faster way to receive beta updates, please let me know if you have any questions.

Yeah that change was a result of the null moving from one point in the code to another with the latest update, ha. I'm digging into it. Appreciate all the quick feedback from everyone! Hopefully can figure out what is going on and resolve it today.

Thank you both, not sure if there is a server issue (@RAvirani?) or I'm just completely missing something, I can see the error but cannot replicate it on my end. If others could chime in with their experience (positive or negative), it might help me narrow down a cause. Thanks!

Could you please try again and submit diagnostics immediately following so I can see what's up.. thanks.

Not sure what is causing that issue for some users (and not me!), but made some adjustments and rolling out another beta update now.. if you receive additional errors on the new version, please submit diagnostics immediately following your login attempt. Thanks!

Hmm, that is odd, I cannot replicate that on my end. Should not be any restrictions on spaces or special characters in any of the fields. Could you each try again, and submit diagnostic reports immediately after so I can see if anything is being logged? Thanks!

A new SignalCheck beta is rolling out now and should be available shortly! The most significant changes in this version are an overhaul of the web upload routines. Password authentication (signalcheck.net account) is now required. To upload data, go to the menu and select Logs > Upload Web Data. The upload shortcut (accessed by clicking on the pending points display on the main screen) still works, however you will need to use the menu option the first time in order to log in. Please test the upload functionality as much as possible and share any suggestions for improvement. You can have one web account for multiple devices; there is a "Client" field that users can configure upon login. This field defaults to your device make/model but can be any text. All of your active sessions are displayed on the Account page on signalcheck.net. Sessions can be deleted from the website or by logging out on the app. Overhauling the upload functionality and implementing secure login should open the door for more features down the road, perhaps some sort of logic to identify sites for Site Notes, etc.. there is a lot of interesting potential here. Known issues with this release: Once logged in, there is a delay in displaying the Upload Web Data window while the app contacts the server to validate your login. The delay varies depending on network conditions, but should only be a brief moment. I am working on improving the UI to make it more clear that the app is doing something and not freezing. Creating a new web account is not supported from within the app yet. There is a button for it, but you are simply directed to the website for now. Other notable changes: Added accent colors for additional wireless providers. Improved web upload processing and error handling. Resolved issue with delayed status bar icon at startup on Android 12+ devices. As always, I appreciate your support and encourage feedback, publicly or privately. I intend to release this version to the public (with upload features hidden, for now -- that is still in beta testing) if testing proves it to be stable.

I hear ya.. basically just casting/Chromecast for native support on a Pixel, not surprisingly they want to sell their own gear. The strategy works, because I've purchased several TVs over the past year, and as a Pixel fan, I limited my options to models that had Google TV as the OS. (FWIW, I've been very pleased with that interface for my needs, but that's a whole other topic). As such, it makes sense for Samsung users to stay with the Samsung ecosystem (and Apple with Apple, etc). Unfortunately not everything is universal, but I think we have come a long way overall. Looking forward to USB-C on the next iPhone to help ease that nuisance..

I feel like you sort of answered your own question here. Smart View is a proprietary Samsung feature, so it's only available on Samsung devices..

Remember when we used to track PRL updates like this back in the day with @digiblur.. ahh memories!