Jump to content

SignalCheck - Android app to monitor your Wi-Fi/2G/3G/4G LTE/5G-NR signal strengths


mikejeep

Recommended Posts

  • 4 weeks later...

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

  • Like 9
Link to comment
Share on other sites

  • 1 month later...
Mike I noticed on my S8 that the BSL isn't displaying, instead I get "click for map."  Is this a known issue?


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

Link to comment
Share on other sites

8 hours ago, mikejeep said:

 


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
 

 

Rebooting my device doesn't fix it, hopefully it gets fixed in Android since its a known bug.  

Link to comment
Share on other sites

8 hours ago, mikejeep said:

 


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
 

 

BSL has not worked on my essential phone...ever.

Link to comment
Share on other sites

41 minutes ago, JossMan said:

Rebooting my device doesn't fix it, hopefully it gets fixed in Android since its a known bug.  

11 minutes ago, swintec said:

BSL has not worked on my essential phone...ever.

Until now I do not think I had any reports of this not working. You do need an active data connection (it looks up the address using an unknown Google server) but otherwise it should just work. Can you try sending a diagnostic report after you are connected to a CDMA site for a bit? Maybe there's an error getting thrown in the background.

-Mike

  • Like 1
Link to comment
Share on other sites

5 hours ago, mikejeep said:

 

Until now I do not think I had any reports of this not working. You do need an active data connection (it looks up the address using an unknown Google server) but otherwise it should just work. Can you try sending a diagnostic report after you are connected to a CDMA site for a bit? Maybe there's an error getting thrown in the background.

-Mike

Will do I'll send a few reports from various sites.

  • Thanks 1
Link to comment
Share on other sites

7 hours ago, mikejeep said:

 

Until now I do not think I had any reports of this not working. You do need an active data connection (it looks up the address using an unknown Google server) but otherwise it should just work. Can you try sending a diagnostic report after you are connected to a CDMA site for a bit? Maybe there's an error getting thrown in the background.

-Mike

okay i sent one over.  just for reference, what needs to be enabled in the settings for BSL to display correctly?  i could have missed a setting migrating from my nexus device.

  • Thanks 1
Link to comment
Share on other sites

 

38 minutes ago, swintec said:

okay i sent one over.  just for reference, what needs to be enabled in the settings for BSL to display correctly?  i could have missed a setting migrating from my nexus device.

There's only one option (enabled by default); if you had it disabled, you wouldn't see the line at all.

I got your report and immediately see the issue.. the latitude and longitude are flipped. It's trying to geocode coordinates in Antarctica, not Maine. A bug caused this to happen on Android 8.0, so SignalCheck flips them back -- I wonder if the Essential folks implemented a fix on their end, so my "fix" is really breaking it. Ugh! I'll have to implement a smarter fix.

EDIT: Actually, something more widespread is going on.. @JossMan I just got your report, and your lat/long is flipped too. The "fix" must have rolled out in an interim 8.0 update for some devices. It wasn't fixed on the Pixel until 8.1 so that's what the app looks for.. ugh..

-Mike

  • Thanks 1
Link to comment
Share on other sites

48 minutes ago, mikejeep said:

 

There's only one option (enabled by default); if you had it disabled, you wouldn't see the line at all.

I got your report and immediately see the issue.. the latitude and longitude are flipped. It's trying to geocode coordinates in Antarctica, not Maine. A bug caused this to happen on Android 8.0, so SignalCheck flips them back.

EDIT: Actually, something more widespread is going on.. @JossMan I just got your report, and your lat/long is flipped too. The "fix" must have rolled out in an interim 8.0 update for some devices. It wasn't fixed on the Pixel until 8.1 so that's what the app looks for.. ugh..

-Mike

So is this just a fix to SCP Pro? 

Link to comment
Share on other sites

3 minutes ago, JossMan said:

So is this just a fix to SCP Pro? 

The initial release of Android 8.0 had a bug in the OS that switched the BSL latitude and longitude. When Android 8.1 came out for the Pixel, it was fixed. So SCP checks if you're on 8.0, and if so, it swaps the lat and long. Until now, it was working great as far as I knew. Your devices must have a flavor of Android 8.0 that does not have the original bug. Perhaps it wasn't fixed in time for the initial rollout to pure Android devices, but it was fixed for other devices (either by the Android developers or the individual OEMs).

@swintec and @JossMan can you confirm that the BSL stopped working once you moved to Android 8.0?

If anyone else is experiencing issues with the BSL display, please let me know; include your device and OS details. I am thinking I could just limit my workaround to Google devices, but I want to confirm no others are impacted.

Thanks,
-Mike

Link to comment
Share on other sites

21 minutes ago, mikejeep said:

 

@swintec and @JossMan can you confirm that the BSL stopped working once you moved to Android 8.0?

If anyone else is experiencing issues with the BSL display, please let me know; include your device and OS details. I am thinking I could just limit my workaround to Google devices, but I want to confirm no others are impacted.

Thanks,
-Mike

Yea Mike once I updated to Oreo (8.0) on my S8 the issue started. 

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, mikejeep said:

 

@swintec and @JossMan can you confirm that the BSL stopped working once you moved to Android 8.0?

 

Ive been on the Oreo 8 beta since essential came out with it..i cant remember when that was though, december?.  However, when I was on 7 for a little bit in the beginning, I want to say BSL was not working then either.  That is why i thought there was a setting ive been missing all along once i swapped to this device.  Dont attack this problem based off that though as I could be mistaken so hopefully someone in the essential post is still running version 7.

 

I believe 8.1 is coming out very soon though, if we can believe the essential team.

  • Thanks 1
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

SignalCheck Pro update was pushed out a few minutes ago! Not a huge update, but laying the groundwork to be able to raise the minimum Android version so I can move forward with new features I really want to add. Trying to tie up loose ends by fixing all significant bugs I am aware of. Grab the update on Google Play, should be available shortly if you don't see it yet..

Added additional indicators for Sprint LTE band 41 Magic Box cells (up to 0FC).
Magic Boxes are confirmed up to GCI prefix 0FA as of right now. This will continue to evolve as more Magic Boxes are deployed.

Internal development changes.
Stuff nobody would really notice without seeing the source code, but important nonetheless.

Resolved force closes on certain Android 7 devices with the 1X status bar icon enabled. (Pro)
Resolved force closes on some devices when Location Service is stopped before it finishes initializing. (Pro)
Resolved issue with CDMA BSL display failing on certain Android 8.0 devices. (Pro)
Resolved issue with missing Wi-Fi data on Android 8.1 when location permission was not requested.

Bug fixes, more bug fixes, yay bug fixes!

 

As always, please let me know if you have any issues, and thanks for everyone's support!

-Mike

  • Like 6
Link to comment
Share on other sites

  • 1 month later...

I was in a grocery store in downtown Denver across from Coors field.  I know that site next to Coors field gets killed so if it is that site then it's good to see this being a high capacity site now.  I assumed that's what hc stood for.  

Link to comment
Share on other sites

4 hours ago, jthawks said:

I was in a grocery store in downtown Denver across from Coors field.  I know that site next to Coors field gets killed so if it is that site then it's good to see this being a high capacity site now.  I assumed that's what hc stood for.  

Probably was a Clear site that was converted to Nokia mini-macro, and they did this to add capacity for the stadium area.

Link to comment
Share on other sites

Mike, I sent in diagnostics last evening for the last GCI showing an AT&T LTE site via Sprint Roaming from an hour before despite having passed many Sprint LTE sites which had been see by SCP.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...