mikejeep

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

These are the 5G networks supported according to the Pixel 5 official specs: "5G Sub-6: Bands n1/2/3/5/7/8/12/28/41/66/71/77/78 5G mmWave: Bands n258/n260/n261" I believe T-Mobile mmWave uses n260 and n261.

A new SignalCheck beta has been submitted, and will become available sometime in the next few hours (days?) depending on how long it takes Google Play to release it. They are still warning of delayed processing times. There are no big changes in this version on the end-user side, however there are extensive changes behind the scenes, including a new crash reporting service I am trying out. I did a lot of testing on my own, but as I mentioned last week, this release MAY be more unstable than typical beta builds because of the volume of code changes. I need help testing to ensure it is stable, but if you can't be without SCP, please don't update immediately. Hopefully after a few days there will be enough feedback here reporting it's all good.. hopefully.. EDIT: Update went live at 6:30am Eastern 9/30/20

Maybe the difference is simply organizational.. higher overhead costs and/or profit margin targets? I think it's safe to presume that the 865 chip costs more than the 765.. we'll find out for sure tomorrow when the official specs and official pricing is announced. OnePlus seems to be the leader in combining price and specs these days. I'm looking forward to the announcement. I've been using a Google phone as my daily driver since the Nexus 5.. initially because I loved the phones compared to the competition, and while I still am pretty happy with the phones, it's also easier to test SignalCheck. First in line for OS updates, no third-party OEM issues that might muddy the waters, unlocked for all carriers, and (usually) simple rooting methods makes for a very solid testbed. I can't afford to buy every LG, Samsung, and Motorola that comes out. I don't have many complaints about my Pixel 4, but I would love a larger battery and access to 5G (more for testing than my own personal needs). I didn't use Soli/gestures, and while I like face unlock there are too many apps that unfortunately still use the old fingerprint API (looking at you, Target!) so it'll be nice to go back to that. The slightly larger screen will be ok, but hopefully 6" is the ceiling for "smaller" devices moving forward. I want a phone, not a tablet!

Looks like you were on non-standalone T-Mobile 5G. The signal strength appeared to be quite strong, I'm guessing you were very close to the antenna site. You were using LTE band 66 as the anchor, along with 5G (unknown band). This is typically what SignalCheck is displaying on 5G NSA connections.. I have not seen any real-world examples of full 5G data being displayed except for on SA (standalone, ie no LTE anchor) connections.

I have been in contact with OnePlus support in an attempt to improve SignalCheck's 5G reporting. I was ultimately directed to make a forum bug post by their support team. I would appreciate it if I could get users to "Like" or comment on that post in an attempt to get it attention: https://forums.oneplus.com/threads/oneplus-devices-not-properly-reporting-5g-nr-cell-info-to-android-api.1312205/ Not sure if it will help, but it certainly can't hurt. Thank you!

B41 in this market always had the 0x145000 offset, until these oddball 000***** B41 GCIs started appearing on some sites. Currently everything either remains the same it always had been, or has switched B41 to the new 000-style. I have not seen any B25/B26 GCI changes on any sites I had previously identified in MA or NH.

You never know, sometimes the devices with the best engineering screens report garbage to the OS, and vice versa. I know @S4GRU was testing a V60 with SCP.. Robert, have you seen any 5G band info in SCP? It would likely only be seen with a standalone connection at this point..

Rumors about the Pixel 5 are flying, and it is expected to be officially unveiled next week, with availability starting October 8. Improvements over the Pixel 4 include 5G support, 8GB of RAM instead of 6GB, thinner bezels but larger (6") screen, and my favorite -- a 4080 mAh battery instead of 2800 mAh. Some are unhappy about the mid-range Snapdragon 765G processor, but that's probably what gets the price to $699.. $100 less than the 128GB Pixel 4 was and several hundred dollars lower than the new Samsung line. 5G and a much larger battery are worth the CPU sacrifice to me. It might impact gaming I guess, but that's not my thing. Sources: https://www.androidpolice.com/2020/09/01/it-sure-looks-like-the-pixel-5-and-pixel-4a-5g-just-passed-through-the-fcc/ https://9to5google.com/2020/09/22/pixel-5-render-leak/ https://www.tomsguide.com/news/google-pixel-5-just-fully-leaked-heres-the-final-design-and-specs https://www.theverge.com/2020/9/22/21450764/google-pixel-5-design-specs-leak-hardware-software-camera

I've been looking for someone else to notice this.. all summer, the Sprint B41 GCI's in my area have been slowly transitioning to new 000xxxxx ones that don't seem to correlate to anything. B25/B26 hasn't changed at all. Do we know if this is a temporary "work in progress" sort of thing, or permanent?

If your phone is reporting it, yes! Generally works on standalone 5G connections, but not on NSA (5G+LTE anchor). Hoping it improves as more device software updates come out. EDIT: See some examples in these posts from the Beta Crew thread.