mikejeep

Excellent!! Don't worry about posting in here.. you are on a beta OS, so it's on-topic..

I see it (although very rarely) on my Pixel 5, and I can't figure out why or when it happens either. It's often combined with a second incorrect/ridiculous value. I am working on improving the validation of those fields so it will show "?" for anything that is invalid. I can't force the data to be accurate, but I can at least hide it when we know it's wrong!

Rough translation:. The cell you are connected to is reporting 310120. The network is reporting 312250. Your phone's "home" PLMN ID is 312530. Sprint owns all three of those IDs (and several others). Most providers only have one.

A recent Samsung update did break 5G-NR reporting on many of their devices, it's no longer reporting any signal strength (RSRP). I've tried a few workarounds but it's not going to be resolved until Samsung fixes it on their end. Please alert them to the issue through whatever beta feedback channels they offer!

I think I'm just going to add a "Trip" menu to the app, where I put all of your special tweaks in one spot.. 😜

I am using a physical Sprint SIM right now. I initially had eSIM on my Pixel 4, but I accidentally discovered that was preventing me from activating an LTE plan on my a Samsung Galaxy Watch. When I switched to a physical SIM, the watch plan was able to be activated.

New versions of SignalCheck Pro and SignalCheck Lite were pushed out late last night and are now live on Google Play! This release has a lot more changes behind the scenes than new features, but there are some improvements. The most significant changes are improved 5G support for Lite, and GCI pattern matching and offset rules for site notes on PLMN ID 312250, which is popping up on Sprint sites that are expected to stay in place. This release was squeezed in minutes ahead of last night's deadline imposed by Google Play requiring app updates to target Android 10 or newer. Many will remember that I tried to do this last spring, but it caused a lot of headaches and it was rolled back. Hopefully I can produce better results with the next attempt!

New SCP beta was launched yesterday and went live on Google Play overnight! This is a fairly minor update from the last beta, some small bugfixes and Sprint 312250 should now follow the same pattern matching and offset rules for site notes as other Sprint PLMN IDs. This release (version 4.63) was also rolled out to the public SignalCheck Pro and Lite channels overnight. The primary reason for this release was to beat last night's deadline imposed by Google Play requiring app updates to target Android 10 or newer. Complying with this is going to be difficult, as when I tried to move the target version last spring, many users experienced problems with the app. Resolving these issues will have to be my priority for now. Anyone with a critical need for SCP should probably pay close attention to this thread and/or release notes to make sure they don't lose functionality they can't live without. As always.. thank you for all of your help!

Gotcha. I see the "Connecting.." sometimes on my inactive test devices, but not consistently. It's more when I'm on fringe signal, whether or not the device has an active line or not. I was just trying to come up with a direction to think about how to solve the underlying issue. Some devices report LTE connection values via GSM methods (and nothing via the LTE ones), especially older phones.. so it kind of makes sense that you might see those type of log entries occasionally. It took awhile for me to perfect it, but by now SCP does enough wizardry in the background to make it impossible to notice any difference as to where the source data is coming from. Maybe I could add an option to force-log "Connecting" entries as LTE automatically.. perhaps set a flag that indicates it's questionable. I'll play with some ideas when I get close to finishing 5G logging.

When it's showing "Connecting..." are any of the signal metrics on the screen changing? I'll have to double-check the code to confirm, but I don't think it will log anything because that displays when the device doesn't "know" what the connection type is.. that's why it doesn't say LTE. Even if the metrics appear to indicate LTE, the device isn't reporting that -- so SCP patiently waits for it to get sorted out. The logger won't know how to save any information it might be getting during that state. That label usually does not persist improperly, although sometimes when your connection is changing it may display briefly. Are these phones on active lines?

Sorry, missed this from a couple weeks ago. It just indicates the sector like you said.. happy to make it an option, hex/decimal/disabled.

I haven't noticed a difference, better or worse. It is a tricky comparison because my P4 preferred Sprint, and the P5 prefers T-Mobile.. since each network has different LTE bands, it's not apples-to-apples. Nothing has stood out that makes me believe that performance is worse.

Sprint owned many different PLMN IDs.. in the app, I tagged any that were dormant with the ** in the hopes that if they somehow started being used, it would be noticed and we could figure out why. It apparently worked! My goal is to come up with a label that not only makes sense to the most-informed users (you and many other S4GRUers) but also the least-informed, who might have no idea what is going on. Certainly worthy of being labeled somehow. Fantastic idea! I'll work on getting that added. FWIW, I have not seen this PLMN in New England yet. Android reports PLMN IDs in up to 7(!) different methods depending on your connection type. On most providers, it does not matter, because they only use one ID. Sprint is an exception to this. After many many hours of research, trial and error, digging through logs, and asking for opinions, I chose what I determined to be the most reliable value to implement in the app. The exact value chosen depends on your Android version and the connected provider, but on most devices running Android 7.0 and up it uses the value being reported with the primary connected cell information. With up to 7 different options, it is not surprising that other apps may show different data. There's a chance it could vary by device too, if the vendor implemented something differently in the radio firmware.

Liking my Pixel 5 so far.. after finally getting used to face unlock on the Pixel 4, I catch myself staring at the Pixel 5 for a second before remembering to use the fingerprint reader.. no problems so far, the phone seems very snappy. I really like the matte back. Screen and camera are very good as always. The minimal front bezel and punch hole selfie cam is cool. I was a Sprint customer, but the Pixel 5 is preferring T-Mobile, while showing the roaming 'R' when connected to Sprint sites. I learned that this is because it's a newer 5G-capable device so ROAMAHOME was added. I have connected to T-Mobile NSA 5G, but no standalone yet. Looking online, is sounds like the only official response is that standalone is "coming soon" -- has anyone connected to SA with the Pixel 5 yet?

@RAvirani I didn't want to hijack the merger thread so I branched off over here. I would like to get some feedback from you (and anyone else) and with reliable knowledge of the PLMN situation. I want SignalCheck to display the most useful provider name, especially now with the network in flux. I know there are some regional variations, but I would love to get some opinions on what people think would be the best way to label things, at least for now. Thanks!

Release day! I received my pickup notification from Best Buy shortly after closing last night. I will be grabbing it today. Looks like many nearby stores are already out of stock.. hopefully due to demand, not supply.

Looks like that was not planned.. posted by a Tapatalk admin this morning: "An updated App will be submitted in the next couple of hours. Let's hope it gets approved and released quickly."

It looks like when I added a free line they offered me (that I haven't used and has never had a device attached), that doubled the "administrative charge" from $5 to $10 and the state 911 surcharge went up. Free is never free!

Speaking of taxes and fees, did anyone else's skyrocket over the last few months? My $40 plan now tacks on another $21 in fees and taxes.. that's a steep tax rate!

Anyone else having issues with Taptalk on S4GRU lately? I no longer receive push notifications, and I tried logging out and logging into my S4GRU account again and it says there is a network error. I have not run into any issues accessing other forums with Taptalk lately.

There is a small shopping plaza near me that has Sprint and T-Mobile next to each other, and AT&T and Verizon a few doors down. The Sprint store was re-branded in early August and both remain open today, literally right next to each other, their doors are inches apart but they remain separate. It is funny to see, but I assume there are leases involved that make it pointless to close one immediately. I don't think either one was a corporate store but I'm not positive.

Are you guys using a Samsung with the recent Android 11 update? That update is resulting in 5G details missing from SCP (and probably other similar apps), not sure if that is related. Samsung is not reporting 5G-NR RSRP in that update -- please let them know if they have any sort of beta feedback channels. I do have extra crash reporting in this latest beta update, so I have a lot of new information that I am still combing through. I have not found anything that includes MIMO info, although there area several new features in the Android 11 API that I am still pouring through. Those service/engineering screens typically use proprietary functions that are not part of the standard Android API.

I do get those Google reports, as well as similar ones from services I have embedded in SCP (as long as the app does not completely self-destruct before it can get sent). Always send the system reports if you are prompted and it's something new, and include email/notes when you can! I often need every angle I can to determine what the actual problem is.

Your database issues befuddle me.. I did make a minor SQL syntax adjustment in the latest beta in the hopes that it would eliminate that weird issue where the app crashes and reports that it can't create a table that already exists. That is the only relevant error I've seen from you--and I think I've only seen it from you. The API says my previous code shouldn't generate that error, but maybe this new way will completely resolve it. Please keep using the database functionality how you normally do and see if it's better on this latest version. You mess with it more than the average user so if it works for you, it'll work for anyone! I would like you especially to use the database stuff like you normally do.. export, modify externally, re-import, etc. That's one of the changes. Besides that it is generic instability. Changing a lot of deeply integrated routines and want to make sure I don't miss something. So far the testing has been surprisingly stable as far as I can tell. The only issues seem to stem from seemingly coincidental OS changes (see next post shortly). Awesome!! I have found it useful as well. Nearly everything originates from user suggestions, so keep them coming!

The "coming soon" is probably referring to something on the software side, or hardware choices that were changed at the last minute. As far as hardware goes there's only a Verizon model and an unlocked model -- but both reportedly have the same network capabilities. The article below pointed out that adding mmWave to the unlocked model added $100 to the price. Perhaps at some point Google was considering excluding mmWave from the unlocked model. https://www.androidcentral.com/google-had-option-launch-599-pixel-5-us