mikejeep

Yes, a reboot should fix it. The geocoding service will sometimes just stop working for no reason: http://www.bluelinepc.com/signalcheck/known-issues/ https://issuetracker.google.com/issues/36956130 -Mike

T-Mobile just touted it's Super Bowl plans, and showed Sprint downloads in the low 40's. However I did notice that Sprint's ping was the lowest. Of course that's only one test, I'd rather see the average of many tests.. https://www.tmonews.com/2018/01/t-mobile-network-upgrades-minneapolis-super-bowl-lii/ -Mike

I noticed that on my Pixel as well.. curious, but it probably doesn't mean much. -Mike

If force it my Pixel onto 3G, it won't let go of the 1x800 if it's connected to it.. but if I'm on the Airave's B41, it drops to the Airave 1X connection 100% of them time when I make a call. -Mike

Very happy with mine, at first it was hard to get my Pixel to use it for calls instead of the very weak 1x800 macro signal, but they must have tweaked something because it's great now. The B41 is great and it's also a WiFi router if you choose to use it. -Mike

You were roaming on band 12 for a few moments.. the PLMN (provider) usually doesn't update as quickly as the other data on any device I'm aware of, it takes a couple of seconds to catch up. If it stayed connected longer it would've updated (probably to AT&T or USCC I'm guessing). -Mike

Sounds like it most likely happened because your other device had an older version of Tapatalk installed that didn't have the fixes for this issue.. I'd update all your devices to the latest version and after 48 hours see how it goes. -Mike

I gave up and logged out of Tapatalk awhile ago.. but since it seems others are having fewer issues, maybe I'll try it again. I don't mind browsing the mobile site but I really miss Tapatalk's push notifications. -Mike

I swear I'm not trying to be a pain, but it was definitely a MB and not an Airave or S1000? Just want to be positive since it doesn't fit the range we've seen so far! -Mike

Is that definitely a MB? Closest to that I have is 0E8 for Airave 3/S1000. No MBs below 0EC until now.. -Mike

Finally got a SignalCheck Pro update pushed out yesterday afternoon! By now I'm sure many of you already grabbed it, but here are the version 4.47 highlights.. Added option to hide "Unknown" neighbor cells. If you enable this option, you will not see "Unknown" neighbors displayed individually.. instead the total number of unknowns (if any) will be mentioned in the neighbor cell header. "Unknown" cells are usually nearby cells that are on a different band than your active connection. Android used to handle these without an issue, but since 7.0 it's been broken. Resolved issue with missing signal information on GSM devices reporting 99% BER. There's a decent number of older Samsung devices (and possibly others) that report a bogus GSM bit error rate (BER) even when the connection is valid. This should work around that. Overhauled implementation of Android 6+ runtime permissions requirements. This has been a nightmare, but it's getting better. Essentially, you need to grant SignalCheck the location, phone, and storage permissions it asks for if you want full functionality. There is still a glitch where you may not be prompted for every permission if more than one is pending in the background, but I'm working on it. There is an explanation of why these permissions are needed on the website FAQ, but please ask if you have any questions. Overhauled Wi-Fi channel and bandwidth routines. Wi-Fi channel/frequency/bandwidth information should be greatly improved for those who were lacking this information before. Still some occasional reports of issues with DFS, please let me know if anything doesn't look right. Changed AT&T LTE band 17 indicators to display as "B12/B17" if EARFCN cannot be obtained. I'm probably getting the technical explanation wrong here, but AT&T is deploying B12 and B17 together with MFBI. SignalCheck will now show either B12 or B17 if the EARFCN confirms one of those, or "B12/B17" if it's not sure. Added additional indicators for AT&T LTE band 2, 4, 5, 12, 17, and 30 cells. Added additional indicators for Sprint CDMA Airave cells. Added additional indicators for Sprint LTE band 41 Magic Box cells. Added Data/EPST and Debug/Engineering shortcuts for rooted Pixel devices. Added indicators for T-Mobile LTE band 71 cells (excluding East Coast & Western US). Added support for newest LTE bands in 3GPP spec. Reorganized Display Settings screen. Resolved force closes on devices with multiple user accounts. Resolved force closes when necessary permissions have not been granted on Android 6+. Resolved force closes with Send Diagnostics function when storage permission is not granted. Resolved issue with CDMA BSL display failing on Android 8.1. These should all be self-explanatory but feel free to ask if you want more information. As always, thank you to everyone for your support! There WILL be an update to SignalCheck Lite this month to catch it up to this release. I have been holding out because I was hoping to get all of the permissions issues ironed out before doing that, but my patience has run out. -Mike

New SCP beta update went out yesterday afternoon coinciding with the public update.. just a couple minor changes since the last beta, most notably 0F2 and 0F3 added as Magic Boxes. Time to start working on more new stuff.. -Mike

So I was having issues with my Pixel refusing to grab the CDMA side of the Airave 3 at my house when there was even the slightest 1x800 macro signal to connect to.. suddenly those issues are gone. As long as I'm connected to the LTE side of the Airave, when I make a call it grabs the CDMA side instead of dropping back to the weak macro site connection. Oddly, if I force my Pixel into 3G mode, it still typically grabs the 1x800 macro site (but EV-DO is definitely coming from the Airave) and doesn't want to let go. I'm guessing there was an Airave software update that changed this behavior recently. It's so much better now! -Mike

That's not too far from me.. I can check my logs and/or take a drive if you're looking for something specific, just let me know. -Mike

Perhaps see if another messaging app works better? That would at least rule out your current app as the source of your problem. -Mike

I just got blocked again.. definitely a new block because I'm 800 miles away from home on Wi-Fi. I had just powered on my Pixel and when it finished booting I had a Tapatalk notification for a new post.. I clicked on it and got the Tapatalk error showing I was blocked, same via the web. Signed out of Tapatalk and disabled Wi-Fi to post via Sprint data. -Mike

Oh that's right.. I have never seen one in New England so I always forget about that. Carry on! -Mike

Oh excellent!! That's a great sign. Although PCI 0 should show as Unknown.. [emoji848] -Mike

On the latest beta, check the Unknown Neighbor Cells option to show them, but even if you have them hidden, they are still included in the summary of how many cells were observed. Make sure you have the Show Neighbor Cells option enabled too. Neighbors only tend to show up when your active connection has a weak signal, or there are others with similar/stronger signals in range. Site density obviously plays a role.. if you're only in range of one site, you'll only see neighbors if you are within coverage of one of the other sectors or another band from that site. Urban areas may see over a dozen at a time. On Android 7 and 8, neighbors on other bands are shown as Unknown. I'm hoping they fix that in 8.1 but no sign of that yet. -Mike

This has dragged out a bit so I want to keep everyone else in the loop.. just about everything is ready for release. However, I discovered a significant bug in a permissions library that SignalCheck uses. I am working with the developer of that library to get it fixed before I push out a public update. Without the fix, some of the ongoing issues with Android permissions will continue to persist. -Mike

I have B5 as 17/27/37/47/57/67 (dec) from @Trip but that's the only confirmed B5 data I have received. The 15.. 16.. 18.. 19.. examples do not conflict with anything else I have noted, so all of those might be accurate. Have you definitively confirmed each of those? I can't wait for the day when every device reports EARFCNs.. @david279 mentioned above that Samsungs are reporting on the Oreo 8.1 preview which is huge. Keep me updated.. I just have to be careful to assume that something deployed in one market is going to hold true elsewhere (i.e. T-Mobile's mess). NSG is not a good comparison, because they do not use native Android API methods, they communicate directly with the modem using routines not available to anyone else. It results in great data, but for now it's not the type of information within my reach. But I should be able to do anything CellMapper is showing -- could you give more details? SCP should show the same data. Sure, so GCI like FAxxxxxx / FBxxxxxx? Can you confirm any other details? PLMN 311480 I assume? Nobody has mentioned them. -Mike

I'm going on 48 hours without being blocked.. hesitantly optimistic.. -Mike

No, only on my Pixel.. it's rooted but otherwise nothing crazy installed on it. I got another Tapatalk update to 7.1.8 this morning but I haven't tried using S4GRU with it yet because my home IP is still blocked and I want to wait until that clears just in case I get blocked again I will know it's something new. I replied to the support email I had going but now they're not replying to me. I had the Pro version before they changed everything to VIP, didn't realize you could ask to get it back.. I'll have to do that. -Mike

Is the macro site 1x800? This happens with my Airave 3. I force it to 3G mode, then go in a corner of my basement where the 800 macro site completely loses signal.. once that happens, it will flip to the Airave and won't let go until you go out of range. It's disappointing. The old Airave had a 1x800 beacon that prevented this issue. -Mike

I tried this, and was hopeful since I was able to browse for a solid half hour last night with no issues.. buuuuut when I woke up this morning, I was blocked again. ? -Mike