mikejeep

It's kind of kooky, isn't it? Sprint was the only network provider that I'm aware of that actively used multiple PLMN IDs.. curious if T-Mobile will have everything on 310-260 when the merger dust settles. For those not following the main SignalCheck thread, I'll be adding an option to use an alternate PLMN method if you prefer.. that will make 312-250 appear when applicable.

I can't remember if I posted it here or elsewhere, but Android reports PLMN IDs several different ways. Right now, SCP uses the one reported by the cell you are connected to. Back in the day, I chose this ID because it proved to be more reliable than the other methods. I realize why seeing 312250 would be useful (I have an alert set for it myself and haven't seen it). It definitely seems like T-Mobile has not configured the cell method to report this, for whatever reason. So, I am willing to add an option to use an alternate PLMN method. The app already recognizes 312250 as synonymous with all other Sprint PLMN IDs so site notes should not be negatively impacted.

Last update didn't quite get the job done.. another beta rolling out now, should be available within a few hours. More 5G (standalone) information is included in the notification pulldown in this release -- please test that out! Also improvements to the 5G Lost alert and hopefully resolved the problem with 5G provider names missing.

I'm guessing that the DRL partnership costs a small fraction of what the NASCAR or NBA deals did too..

Hi there, welcome to S4GRU! Glad that you found the forum. I replied to your email last night a few minutes after you sent it with some troubleshooting questions. I know there are many SignalCheck users with Moto devices on Android 7, so we should be able to get things working for you. If you didn't receive my email, shoot me a private message on here and we can communicate that way. Thanks!

ANOTHER update rolling out to the beta crew now.. I did not intend for this week to have nightly builds, but here we are! Hopefully this wraps up all the bugfixes for this cycle.. maybe.. 🤞

So it's kind of technical/complicated, but there's 2 things going on here.. 1) your device is (incorrectly) reporting -24 dBm via one method and 2) it's loosely tied to an Android bug I reported 2 years ago that the development team disagreed with. Best bet is hope Samsung fixes the radio glitch.. if not I can try to come up with a creative workaround. But that might have a negative impact on a device that's properly reporting..

Busy week for the beta crew.. and me.. ANOTHER update has been pushed to Google Play and should be available within a few hours! These bugs were squashed this time: * No information at all was being displayed on pre-Android 10 devices. Fixed! * Connecting to 5G with the 5G band alert enabled but not configured was causing the app to crash. Fixed! * Some 5G bands (n41, most notably) were displaying improperly in some instances. Fixed! Hopefully getting very close to a stable release for everyone.. please let me know. Feedback has been awesome this release cycle, thanks!

Another SignalCheck beta is in Google's hands and will hopefully be available shortly. This update includes numerous bugfixes and also two significant pieces that I have been working on for awhile: * A new "Trail Logger" feature -- it saves one "crumb" to this log each time there is a signal update. It can be backed up and exported just like the existing Site Log. For reference, I drove around testing it for about an hour, and ended up with about 900 LTE entries. Not everyone will find it useful, but it opens up a lot of potential. * New 5G alerts based on bands or plaintext matching, same as what is already available for LTE alerts. Select "all bands" under the 5G band alert if you want to be notified of non-standalone 5G connections that do not report a band. Feedback is always appreciated.. thanks!

USCC has great coverage in Northern New England, where Sprint has almost none (and never planned to, based on my conversations with them over the years). When LTE roaming onto USCC went live it was fantastic.

Thank you to those who have provided feedback about the latest SignalCheck beta so far, I appreciate it! I have identified a bug where the app will crash in some instances if you attempt to add a 5G site note when there is an invalid NCI. It does not happen every time. It will be fixed in the next update, which I intend to roll out very soon. In the meantime, don't try to add a site note when the NCI is missing or invalid! Some have asked why they cannot see any identifying information for 5G cells when also connected to LTE. This is "non-standalone" (NSA) 5G mode, and for whatever reason, cell identity information is not reported in that mode, only signal data. "Standalone" (SA) 5G mode has no simultaneous LTE connection, and seems to reliably report cell identity information. This mode should become more prevalent as 5G deployment evolves. SignalCheck is more useful with SA 5G connections than NSA, but it is reliably reporting everything it can in both modes.

Excellent! Some of those occasional hiccups when switching networks and 5G is involved will take awhile to sort out, it was the same when LTE was rolling out. Fringe scenarios confuse the app sometimes. Glad it's working for you!

The new diagnostic report is the same as yesterday, just says "null" -- very odd. I don't see how targeting Android 10 would cause that, as it's working fine on other older devices. Many apps have been targeting it for 2 years, I literally waited until the last moment to make the move. We will keep chatting over email and get it figured out. Saw your report this morning, thanks! It's working for others, but you oddly have that "no connection" block above the 5G info that is a red flag.. is that always there? If you toggle airplane mode does it go away? Please try saving a note again and sending a report right after, I want to compare the info.

New beta rolling out now.. hopefully will become available on Google Play within a few hours! It has another pile of bugfixes, but more fun than that.. 5G logging and site notes! Just like LTE, you will need a minimum of a PLMN and a site ID (NCI) to save entries, which means you will need to have a standalone connection. I have not seen any non-standalone connections provide any cell identity information, so those will not be able to be logged. I do not have access to 5G SA, so those of you who do, please test it thoroughly and let me know how it goes. Another new feature is a somewhat hidden "shortcut" to send a diagnostic report -- long-press on the "Connected to [whatever]" line in the top right corner and it will send. It will use the username that was included on the last report (if any), but you can't include any details. This should come in handy for those of you trying to report certain situations or issues. You can always send a shortcut report, then follow it up with a regular one if you want to include a note. The last significant change in this release is a new column in the log database, "hits". It is a running counter of how many times an entry is logged.. so it's how many times you have "hit" a cell. Right now it doesn't display anywhere in the app, but you will see it browsing the database or if you export your log. If there's somewhere in the app that you think would be useful to display it, let me know. I have some ideas for it in the future. Thank you for the help!

I saw your diagnostic report.. it's just null. That's it, null. Nothing else at all.. it literally just says the word null! The only devices I've ever seen do that were non-phone tablets like a Kindle fire. Impressive! I don't have APKs, I deploy with bundles that Google Play determines how to handle on a case-by-case basis.. but I'll try to figure something out for you.. check your e-mail. Did previous versions work on these phones? New beta is rolling out now, give that a try in a few hours.

I have to ask.. what did the entire state of Nebraska do to T-Mobile to earn that glaring hole in the center of the country? 😆

That's what I thought, but I have gotten feedback from several users recently who think the CA display is wrong because the site they are hitting only offers one band. Thank you!

I always appreciate diagnostics from the field, but it's not something I can probably improve on if the CA bandwidths appear to be valid -- the phone is reporting it like that. Serious question: can multiple carriers on the same band be aggregated? No info is reported on NSA other than signal strength. That 5G 600 indicator was stale data that got stuck when switching from SA to NSA in certain circumstances. It should be resolved in this beta, thank you for confirming! 😉

Is anyone else having trouble with the regular website too? My "activity stream" never shows accurate info about new posts.

New beta rolled out a couple days ago, tons of bugfixes (and one small new feature). Those if you who were experiencing intermittent crashes or closures, please let me know if this new version is an improvement. Also, is anyone experiencing information updating slower than usual in the app? It was an issue back in the spring when I tried to target Android 10; this beta is my first attempt at trying that again. Thanks!

😜

Yes.. it sends the crash report to Google Play, where there is a dashboard I can review to monitor crash information. I also use two other crash reporting services that send similar crash information when there is a problem. The three different systems often report varying information, so they all have value. In addition to those services, the user-triggered diagnostic reports I often ask for provide me with different data. Combined, all of these options give me a decent amount of behind-the-scenes information to help keep the app running smoothly as new devices and software updates are released.

It happens on my Pixel 5 sometimes as well, but I believe it also happened on my Pixel 4 shortly before I upgraded. I've been trying to track it to see if it's crashing at some point, or if something is killing it off. My crash analytics are showing that Android 11 is causing a surge of new force closes, so my guess is it's related to the new OS. Disabling battery optimization is a requirement for more and more apps, and I'm afraid it's getting close to that point for SignalCheck. I've going through the crash reports to see what I can resolve, but many are obscure and point to system processes and nothing directly related to SignalCheck. There is one crash that points to one part of my code (which was never a problem until Android 11), so I am testing a new approach for that to see if it resolves the problem.

Anyone have an update? My stream of most recent active subscribed threads is also no longer updating on S4GRU.com itself. The threads are updating, but the stream shows old posts as most recent. I'm seeing this error on some pages: [[Template forums/front/topics/activity is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

I used the one from my Pixel 4. It is a Sprint-branded SIM, the ICCID begins with 89312530, and the other string printed on it is SOI0003a. A rep at a T-Mobile store installed it so I don't have any packaging or paperwork showing anything else.