mikejeep

Yes, a return kit with prepaid label was included in my package.

Unfortunately no errors are on any reports or crash submissions from you or anyone else. I'm going to have to add some temporary extra logging to try debugging the issue. I've been slammed with other stuff the past couple of weeks, sorry for not being able to devote much time to this issue lately. I will get to it.. and several other things filling up my inbox!

I am still a Sprint account, and did the 5G Trade-In on both of my lines online without any trouble on the 18th.. arrived today. No idea about the Trade-Up portion though.

Ugh.. mdob07 your report did not show any problems. I am stumped at the moment, as I can't replicate this. I will do some research to see if I can figure out what might be causing this. What devices is everyone seeing this problem with? Also, what Android version? Sorry for the trouble!

Anyone with previous crashing issues seeing any improvement with latest SCP beta? Eerily quiet on the feedback front, hopefully that's a good thing..

I have a SCP user who reached out to me with what appeared to be valid T-Mobile standalone n66 in use in New Jersey.

From the official T-Mobile press release: "The Great Free 5G Phone Upgrade and Great Unlimited Trade-Up start April 18 and last all year long."

A new SCP release for the Beta Crew is rolling out now, version 4.672b. No new features; it is all bugfixes and internal improvements -- those of you experiencing various crashes and freezes, please let me know if this update is better, worse, or about the same. Thanks!

I'd actually prefer to switch that line to TNX so I can get a different experience from my Pixel 5 on TNA, especially since it's just a testing/logging/backup device.. but I also don't want to lose my free line or SWAC. I'm sure it will be a headache no matter what, but we'll see.

It works great.. it's my "how does SCP work on older phones" test device, although it is so slow I don't use it for anything else. Would be far more beneficial to have a newer Samsung in the testbed. Next hurdle, would I have to give up my SWAC account..

Soooo they will take my HTC EVO 4G I have on a free line (not kidding), and give me the Samsung..?!

I received your diagnostic reports, thanks! Unfortunately they do not show anything out of the ordinary, and I have no automated crash reports either. Do you have battery optimization for SCP disabled? Some others have reported that improves their stability on newer Samsung devices. I am not sure what to suggest other than an app uninstall/reinstall, since I don't have other reports of this or an error message to look into. If you do that, make sure you back up your log database before uninstalling, and then restore it on the new install.

As long as you've previously saved your username on a report, try a long-press on the "Connected to LTE" text... 😉

When it freezes, does the screen keep updating? Can you send a diagnostic next time you notice it happens please.. thanks!

A new SignalCheck Pro update is now available for download, version 4.67. It includes the following changes: Added one-time popup to comply with Google Play background location policy. This popup is a policy mandate, there are no changes to existing app behavior. The popup will only display on first launch after a brand new installation. Changed location accuracy precision to one decimal place. Changed location accuracy to display in feet if metric units are not enabled. Improved PLMN ID validation. Resolved force closes on some devices when connected to GSM/WCDMA networks. These should be self-explanatory but feel free to reach out if you have any questions. Thanks for your support, feedback is always welcome!

Another SignalCheck beta is rolling out now. There was a bug that had location accuracy being improperly saved as feet instead of meters in logs. Please do not upload any web data with version 4.66, or data points with accuracy worse than 75 feet (instead of 75 meters, approximately 3x more forgiving) will be excluded! This version also changes location accuracy precision to one decimal place, and aligns with a public release rolling out now. Thanks for all of your testing and feedback!

Another SignalCheck Pro beta was released this morning! The most visible change is a message displayed at startup explaining the app's use of your location. It will only appear once per app install; you will never see it again unless you uninstall/reinstall. This is to comply with Google Play policies; there are no functional changes to the location features. Location accuracy will now be displayed in either feet or meters, depending on your app settings. There are also some bugfixes in this release. Invalid PLMN entries in logs should be reduced, and a frequent cause of crashes when connected to WCDMA/GSM networks should be resolved. Feedback always appreciated!!

Thanks! Unfortunately Google Play doesn't pass on any user info or comments, so it's difficult to pinpoint those.. but one of my other crash reporting libraries caught it (the username from diagnostic reports is included on those). That crash is something I've been working on, it just recently started over the past couple of months and only impacts GSM/WCDMA connections. Looks like you were on HSPA at the time of the crash. I added some additional error tracking in this version so your report was very helpful.. hopefully I can squash it.

That is great news.. but do those of us with a Sprint SIM but on the T-Mobile network (TNA) not already benefit from it? That page doesn't mention anything specific about Sprint customers on the network.

The accuracy is in meters (m) because that's what Google refers to in all of its location setting descriptions. Miles would not be terribly useful, but I do plan to add feet as an option.

Awww man I planned on reaching out to you to see if this update resolved your issues. I am still stumped -- feel free to send me another diagnostic report on the new version if you still have it. If you're moving on, PM me your Google Play order number and I'll refund your purchase.

Do you have the timestamp display on? Try enabling that.. it should end up on the same line as the IP, and that puts the location info on the line below it. I will try to come up with a better alternative. Screen space is getting tight.

An update to SignalCheck Pro is ready for all users and is rolling out on Google Play now! It should be available shortly. You may be prompted to update when you open the app; if not, you can check Google Play. There are a LOT of bugfixes in this release, and a lot of groundwork for future improvements. As always, I love to hear feedback -- especially in the form of a Google Play review. SignalCheck Lite will be updated to this version soon. Those of you asking about the references that have popped up regarding "web data uploads".. stay tuned. Something really cool is in the works! Below is the full changelog of this version (4.66) with some details as needed.. Added toggling of Location Service, Site Logger, and Trail Logger features by clicking on the icons on the main screen. (Pro) Changed site note lock option to also lock Location/Site/Trail buttons. (Pro) The icons along the top row of the main screen are now clickable to enable/disable each feature. If you want to prevent accidental toggling of these options, you can enable the lock option under Preferences > Display Settings. Added option to display location accuracy on the main screen. (Pro) Changed location coordinates to update on main screen in real-time, independent of mobile signal updates. (Pro) The display coordinates can now show the accuracy (in meters) of your calculated location, either all the time or only when the Trail Logger is enabled. The coordinates will also now update as they are refreshed, regardless of how often your mobile signal information updates. Changed pending diagnostic reports to use app cache; eliminates need for Storage permission to send reports. Users who choose not to grant Storage permissions to the app can now send diagnostic reports. Other storage-related features still require the permission to be granted. Bugfixes/self-explanatory changes: Changed LTE band 13 to display as LTE 750. Code optimizations and enhancements. Resolved force closes on some Android 10 devices. Resolved force closes on some devices when attempting to update site notes. (Pro) Resolved force closes on some devices when connected to a WCDMA network. Resolved force closes when root modem functions were enabled. (Pro) Resolved issue with CDMA 1X BSL remaining on screen after 1X connection is lost. (Pro) Resolved issue with cell ID format on alert notifications not matching user preferences. (Pro) Resolved issue with invalid signal strengths displayed on some devices when connected to a WCDMA network. Resolved issue with older log database imports failing. (Pro) Resolved logcat warnings when inserting geocoded addresses. (Pro) Resolved SSL errors when sending diagnostic reports on older devices. Resolved Wi-Fi errors on some Android 11 devices. Thanks for all of your support!

Most have already noticed a new beta rolled out several hours ago.. only a couple of minor changes compared to the last beta. The big change was a public version was released, catching up with all of the betas over the last several weeks. Web data uploads are still limited to beta versions for now. Thanks for all the help, I appreciate it! More improvements coming soon..

Ugh. Did you recently get any device software updates? Please try sending a diagnostic right after it crashes just in case.. unfortunately that hasn't included anything useful so far but who knows. There are a lot of bugfixes coming in the next update, possibly rolling out as soon as tomorrow. Maybe/hopefully it will resolve these issues I'm not getting any crash reports on. I'm lost without any error messages or specific behavior patterns.