mikejeep

I finished testing a workaround for the n7/n38 bug a couple days ago! It'll be included in the beta I'm planning to release in the next 1-3 days.. just depends on how my final testing goes. Need to take a few drives to check out certain issues. I greatly appreciate your generosity.. it's not necessary but it goes a long way! Thank you!!

Rolling out a new website for SignalCheck at https://signalcheck.app (which redirects to the new site on GitHub) -- check it out! This provides the opportunity to use a public-facing issue tracker as well as a wiki. If anyone is interested in adding to the wiki, I would graciously accept the hand. I believe I will need to grant permission to trusted users for this; send me a message with your username and I'll get you set up. I know the documentation for the app has always had a lot of room for improvement, hopefully together we can make it much better. SignalCheck is not going open-source, but GitHub offered the best collection of tools in one spot that I was looking for. The website is still a work in progress, but hopefully it will prove to be useful. I think the issue tracker and the wiki will be great tools.

I know this is an old message, are you still having issues? I don't see any unanswered e-mails that old but I apologize if I missed you. Please feel free to send it again if needed. I did work with OnePlus on that display issue a few years ago; this is the first I've heard that it is occurring again. If so, it's on OnePlus to resolve it, apps have no control over the color of the text in the status bar. It's supposed to adjust automatically if there is a light background.

I like it too -- but I believe that feature is contributing to the app instability that many users are experiencing. I don't intend for it to be permanent; I'm working on overhauling it with a different approach. My first few attempts have not produced a great alternative, I just don't want to hold up releasing an update just for this. If I don't have a replacement working when I'm ready to release an update, maybe I'll try to continue offering the current option with a warning about potential issues. Ah, that is annoying. The only reports I found were both from you, but they were LTE-only and every cell was identifying itself as AT&T. EDIT: I found one other Dish report from another user -- SCP was identifying it as AT&T LTE with Dish NR.. so who knows.

Working on crushing all of the latest bugs, but I need more data to help improve the app for Dish users. Please submit diagnostic reports when connected to Dish, especially NR. In the report, I can see what the app is displaying, but please include in your note what you think is wrong (ie should be Dish NR, etc). Thanks!

Still working through catching up on PMs, e-mails, and posts.. but just a quick note to update 2 things: 1) If you are experiencing crashes/freezes, disable the Show Pending Web Entries setting under Preferences > Beta Crew Settings. New beta coming soon that removes that and updates some internal libraries that seems to have resolved all issues on my devices. 2) New website is coming online tonight, transitioning to GitHub to provide issue tracking and a Wiki that I will invite everyone to contribute to.

That is from the 1H22 Boston market test -- that is a statistically significant jump and massive lead by T-Mobile.. yet they finished #2 in the market for network speed. Kind of funky.

Not sure how it happened, but I missed all the posts in this thread for the past several weeks. I've been busy but certainly didn't mean to ignore everyone.. will start working on catching up today.

SCP should record whatever NR cells it identifies with PLMN+NCI (similar to LTE, which requires PLMN+GCI). I know you're not getting TAC; are you seeing an NCI?

Identification of 1x800 and the 1x800 alerts.. I didn't realize there was still any value to it, but since it's still out there, I'll put it all back in for the next update.

Isn't the Sprint CDMA shutdown going to be finished by 5/31? The 1x800 features only work(ed) on Sprint. I used to camp on it at home; haven't been able to connect in weeks/months.

They've become far more responsive on the Samsung Developer portal than they had been in the past; they now have a support ticketing system that they actually utilize. It's usually tricky for me to pursue anything unless I have the device in question in-hand, but I can try submitting something on your behalf if you can provide me with what they might ask for. Or you can check out https://developer.samsung.com/dashboard/support and try yourself. FYI I reported TA=0 on the A32 last night; I'll add a note that it happens on your device as well, I have all the info I need from your diagnostic reports.

I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung. EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.

I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.

I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.

Did the app report any errors, or did it seem to go through ok? Be curious to see what @RAvirani sees on the server side.

Could you elaborate on this, not sure what you mean? Try going into Preferences > Beta Crew Settings > Web Data Timestamp and setting your timestamp in the past to re-upload entries missing a TAC and see what happens! I just need to improve it more on my end. It's just a crude "if location hasn't changed in 10 min, restart" at the moment which uses unnecessary resources when your device is legitimately idling in one spot. Going to try making it a little smarter moving forward. Please keep an eye on it though, because I rarely see the issue myself and I want to make sure this actually solves it.

A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! Some notable changes: New "swipe to refresh" -- flick down on the main screen, and the data will "refresh" -- I put this in quotes because it will *not* force the modem to be polled (that's unfortunately not possible), but it will 'wake up' the app and display the latest information if for some reason your screen did not automatically update. I am still working on improving this. New cell identification methods for Android 12+ devices -- new routines are available in Android 12 and this is my first attempt at implementing them. I have not seen any changes positive or negative on my Pixel 6, but hopefully someone sees improvements. I will continue exploring these methods and adding new features as I get them working. Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing. Missing/invalid TAC values included in web uploads -- this will need some testing, because I can't replicate it myself. The option to log cells with missing TAC must be enabled for this to have an impact. Feedback welcome as always!

I looked into it a few times, but it was never allowed per the Android Auto guidelines. AA apps had to be related to media, messaging, or navigation. I can understand why they wouldn't want to explicitly permit an app like SCP that encourages users to look at their dash instead of the roadway. With the increased reliance on in-dash apps, I wonder if the rules have been relaxed at all. I'll look into it again.

No problem, I hadn't looked too closely but you are right, 0 is valid (and recognized by the app as such) -- internally, I set it to -1 unless a valid value is returned anyway, so that shouldn't be too bad. Let me know when you get your side ready, no rush. The current alpha build I'm working on is half-broken as I try to implement this new TelephonyCallback stuff I'm working on.

Sure.. or it can just leave it blank or zero, whatever is easiest for you.

If the TAC is missing, an entry is still recorded in the log, but it would not be included in uploads.. so you could probably manipulate a trail log export to add the data to the map if you were able to nail down the sites without the TAC. EDIT: Sites with a missing TAC are only recorded in the log if the option to do so is enabled (Logger > Log Sites with Missing TAC).

Unfortunately I'm not seeing it either. LG must have broken something with that Android update.. there is no NR TAC in the LTE+NR report you sent. As you saw, it does report a valid TAC in NR-only mode. There isn't much I can do with no TAC being reported -- however, I recently discovered that a new telephony callback method was quietly added in Android 12. I am looking into it, but it's going to take me some time to get a beta with it included. Not much is published about it yet and I don't have much time at the moment. But I'll try to see if I can get something put together specifically to at least try resolving this.

A new version of SignalCheck Pro is finally being released and should become available on Google Play within the next several hours! Version 4.71 includes MANY bugfixes and new features. To view the full changelog, visit this link or go to About > Change Log from within the app. Please feel free to post feedback or questions, and thank you for your support!

New SCP beta rolling out now, fixes the issue with the pending web upload count missing from the popup window. A public release will finally be rolling out with this version as well!