mikejeep

Another SCP update rolling out now.. beta-only for the moment, but pending any last-minute hiccups, the same version will roll out as a public release within a day or so. The only change for beta users is a minor bugfix related to the Recent Apps screen. Appreciate all the feedback! EDIT: Google Play pushed the public release out with the beta and there's no way for me to pause it.. hopefully all is well!

Another SCP beta is rolling out now. It includes more bugfixes for web uploads and Android 14 hiccups. Thanks for your support!

A new SCP beta is rolling out now! The most notable addition is 5G-NR Timing Advance (TA) display on compatible Android 14 devices. It is not displaying on the latest Android 14 Beta release on my Pixel 7, but when the functionality is added, the values should appear in the app. It will probably take some time before it is displayed on most devices. Beyond that, there are many bug fixes and improvements, including ongoing dual SIM improvements (slowly getting there!) and numerous changes in preparation for the upcoming launch of Android 14. Full changelog is available here as always, or inside the app. Look forward to feedback!

USCC has a very good network in central/northern NH and Maine.. probably better than the Big 3 in most areas. I hope that if anything changes hands, that coverage remains accessible to T-Mobile customers in some fashion. It was more of a big deal pre-merger when Sprint had NO coverage in those areas, but they still beat T-Mobile in many areas, especially when you get away from the larger cities.

I'm not sure if I can make an option to pick any shortcut the user wants, but I will look into it. I'm happy to add anything anyone wants, but dialer codes were blocked several Android releases ago. I need the actual name of the shortcut (using one of those apps is the best way to find that).

My account was switched over today. Both of my regular lines as well as my watch all appear to be displayed correctly. FWIW, my billing cycle ends in 11 days so I'm not sure that has anything to do with it.

As someone who followed and was somewhat involved in the construction of Fios (and who has had Fios for over a decade), I agree.. it's a lot more complicated when you get into residential business like that. Lots of red tape and individual agreements with every individual municipality.

Me too!

The website (https://signalcheck.app) has a Known Issues page on the Wiki tab. If you want to report a bug, the Issues tab is a good place to check to see if it's already reported. If not, you can report it there. You can always just post, PM, or email too.. I get to it all eventually. Sending diagnostic reports when you see an issue is definitely helpful. Feel free to share info even without a report, you can always send it next time you see an issue.

Thanks all, I was able to figure out the issue, it was a compiler problem -- new beta update is rolling out now that resolves it!

Hmmm can't replicate it myself, but I know that means it's a compiler issue.. will dig into it shortly. I received your diagnostic @mdob07 but @dkyeager and anyone else if you have a chance this morning please send one after trying to upload also, can't hurt. Thanks!

A new SignalCheck Pro update is rolling out to all users now; it should become available on Google Play within the next several hours. This release includes numerous bugfixes, including: Resolved force closes when phone permission was not granted on some older devices. Resolved issue with incorrect 5G-NR bands displayed on many devices due to Android bug. Resolved issue with internal crash reporting library initialization errors on some devices. Resolved issue with missing icons on some devices. Resolved issue with Wi-Fi info only updating on connection/disconnection. Dual-SIM support remains in development and is not included in this public release. Testing continues to go well but there are still a few more bugs being worked on. I appreciate all of your support!

Another beta release is rolling out now, includes additional improvements to 5G-NR band identification. This version is also rolling out as a public update to all users.

Back at it with another fresh beta release, containing several bugfixes.. most notably, Wi-Fi information was only updating upon connection and disconnection. Still working on ironing out the last few hiccups on Dual-SIM devices..

I believe that Sprint had several 2-sector sites along Alligator Alley that provided coverage on the highway.. did T-Mobile take those down? Or were you elsewhere?

A brand new SignalCheck Pro update is finally rolling out to all users today! The number of changes and improvements is significant, see here for the full list: https://signalcheck.app/changelog Dual-SIM support is still in the final phases of testing and is not included in this public release. I anticipate it to be ready soon, testing is going very well but there are still a few more bugs to iron out. I appreciate everyone's support and look forward to feedback! EDIT: Update has been processed and is now available for download from Google Play.

Another SCP beta is rolling out now -- should hopefully resolve the issue with the new NR NSA band display missing on some devices. To clarify, this new field will only appear if the NR frequency is identified (i.e. the app is showing "5G-NR 2500"). If the frequency is not displayed, that means it is not available.. this information is not widely reported on NSA connections yet, although it is becoming more common. @chamb your S22 was not reporting the information at the time of your report, that is why you are not seeing it.

Hmmm interesting.. it's working on my Pixel 7 and A32, you should see something similar to below. I will add some extra logging and get another update out tonight.

Still good news on this front?? 🤞

Another SignalCheck beta update is rolling out now.. NSA 5G-NR band is now displayed on the main screen, network connection type in dual-SIM configurations will be more reliable (on some devices, the secondary SIM would overwrite the "Connected to" display on the main screen), and other minor bugfixes are included. Pending any new bugs that pop up over the next few days, this version will roll out as a public release at the end of the week..

That's good news, I just checked the API reference and see the added method. I will certainly add support to SCP, but as you mentioned it all depends on if the phones will support it. My Pixel 7 does not report LTE TA on my T-Mobile eSIM, and only reports inconsistently on my AT&T physical SIM.

As others have mentioned, I can't take credit for the phrase, and it has been mentioned for over 3 years just on S4GRU posts. There was a discussion about what to label 312250 as when it started popping up.. the consensus was "Sprint Keep" worked best. It's nice because it gives a little bonus insight into your connection.

Awesome, glad to hear that -- thank you for sharing, that's the first shot I've seen mmWave in the wild! What does the SCP status bar icon show? Can't make it out clearly in that screenshot.

How are we looking with the latest update.. any improvement? 🤞 Anyone else seeing stale NR after connection is lost? This is the primary hurdle remaining that is keeping fron rolling this version out to a wider audience.

I get dozens of random reports daily with no name or issue listed.. not a problem at all! I review most of them anyway, to see how the app performs on various devices and networks.