Jump to content

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


mikejeep

Recommended Posts

My phone was 2 feet from the antenna.

 

haha crazy.  i was in the car at least 25 yards out in front of the antenna and got -30 to -34.

Link to comment
Share on other sites

-40 eh?  The few rare times you have that great of a signal there isn't a need to look at the icon ;)  I think it is due to the app not having the icon with a number for that high of a signal. 

 

Listen, if you yahoos are going to resort to climbing towers to create "bugs" for me to fix, I'm going to give up!!

 

Yes, digiblur is correct, each signal level icon is not text, but a graphic that had to be created individually.  I created icons to cover -139 through -40.  I will come up with something creative in a future release for readings better than that.. :)

 

-Mike

  • Like 4
Link to comment
Share on other sites

I created icons to cover -139 through -40.  I will come up with something creative in a future release for readings better than that.. :)

 

For greater than -40 dBm, maybe the icon message should read:  PUT THE PHONE DOWN AND STEP BACK FROM THE ANTENNA!

 

AJ

  • Like 3
Link to comment
Share on other sites

A SignalCheck update has [finally] been released!  Version 4.06 should be available from Google Play within the hour for Pro users.  Lite users will receive their update in a few days.  Here are the changes:
 
Added LTE connection frequencies on HTC devices.
Not sure how useful the exact freqs are, but the uplink and downlink center frequencies will be displayed.  Feedback would be appreciated.. I found a way to get the info, so I figured I would share it.
 
Added menu shortcut to hidden system menu on Samsung devices. (Pro)
A step in the right direction for the Samsung folks!  Figured out how to get something working at last.. this will bring up a menu with many system functions, including engineering mode.  Still trying to get more functionality for Samsung devices, but it's painstakingly slow.
 
Added option for users to set the Reset Data Connection delay time. (Pro)
The default period of time the radio goes offline has been increased to 4 seconds, but now users can set it however they like (0-15 seconds) in the Preferences screen.
 
Improved BSL feature; map link is active even if the address cannot be displayed. (Pro)
The map uses the latitude/longitude, not the street address, so it should work just fine.  The street address will likely display in your mapping app once it loads.  Changed the "failing" message, since the site was being located, the app just can't connect to the geocoding server to determine the address.
 
Improved display of CDMA mobile carrier names; will now show carrier names at all times, including while roaming or otherwise connected to another mobile network.
The carrier name will now reflect whatever 1X network you are connected to; even if you are roaming or using a custom PRL that "fakes out" your phone, it should accurately show what carrier you are connected to.  No more memorizing SIDs or needing another app to check who you are roaming on.
 
Improved Reset Data Connection feature; only the cellular radios will now be reset. (Pro)
Only the cellular radios should reset now when you use the RDC function.  There is a known bug in Android that might cause your Bluetooth to continue to reset.  If so, restart your device and it should be ok.  You must activate the RDC feature at least once before rebooting for this to work.
 
Resolved issue with Google Maps 7+ displaying an error when mapping the BSL. (Pro)
The new version of Google Maps broke a lot of stuff, but I got it working again.  The BID will no longer display on the map, but I hope to implement maps in the app itself soon anyway.
 
Resolved issue with stale LTE data displayed on the HTC One after LTE connection is lost.
I am working on fixing the underlying issue with HTC's engineers, but in the meantime, a temporary fix is in place for One users.  No more bogus LTE readings frozen on the screen!
 
Resolved issue with widget always displaying GSM connection type as “N/A”. (Pro)
The widget was not displaying GSM connection types.. it will now.
 
Updated EV-DO labels to display eHRPD if connected to eHRPD or LTE.
Just trying to keep everything consistent, accurate, and simple.
 
Updated help screen to reference the online FAQ page.
This hopefully makes my life easier.  If you have questions, please look there first.
 
Updated LTE CID field to display in hex format.

CyanogenMod 10.1 users running the latest nightly on some HTC devices are now seeing the CID field implemented in Android 4.2.  Please let me know if this is not displaying properly after the update.

 

As always, please let me know if you discover any bugs, and a huge thank you to my beta testers, especially mrrogers1 who put a lot of time into this release conducting tests and providing feedback!

 

-Mike

  • Like 19
Link to comment
Share on other sites

Mike you are the man. Thanks for the hard work.

 

Sent from my EVO using Tapatalk 4 Beta

 

 

  • Like 2
Link to comment
Share on other sites

Added LTE connection frequencies on HTC devices.

Not sure how useful the exact freqs are, but the uplink and downlink center frequencies will be displayed.  Feedback would be appreciated.. I found a way to get the info, so I figured I would share it.

 

I take it you are pulling the EARFCNs, then running the calculations to produce the center frequencies.  Or did you find the device is reporting center frequency data directly?  Either way, good work.

 

And it becomes important as Sprint starts refarming its PCS A-F block spectrum for LTE.  The first time that a single band LTE device user encounters an EARFCN other than the PCS G block 26665/8665 (1912.5 MHz x 1992.5 MHz) will be a notable occurrence.  I wonder if you could incorporate a user alert into the app or even have "E.T. phone home" with a log sent back to you on such an occasion.

 

I wrote an article a year and a half ago about a second 5 MHz FDD LTE carrier in PCS A-F block spectrum.  It identified the most feasible candidate markets.

 

http://s4gru.com/index.php?/blog/1/entry-27-spectrum-analysisdoes-sprint-have-more-options-for-additional-lte-carriers/

 

AJ

  • Like 3
Link to comment
Share on other sites

Mike you are the man. Thanks for the hard work.

 

Sent from my EVO using Tapatalk 4 Beta

AGREED!

 

Sent from my HTC d3rpONE using Tapatalk 4 Beta

 

 

  • Like 3
Link to comment
Share on other sites

I take it you are pulling the EARFCNs, then running the calculations to produce the center frequencies.  Or did you find the device is reporting center frequency data directly?  Either way, good work.

 

And it becomes important as Sprint starts refarming its PCS A-F block spectrum for LTE.  The first time that a single band LTE device user encounters an EARFCN other than the PCS G block 26665/8665 (1912.5 MHz x 1992.5 MHz) will be a notable occurrence.  I wonder if you could incorporate a user alert into the app or even have "E.T. phone home" with a log sent back to you on such an occasion.

 

I wrote an article a year and a half ago about a second 5 MHz FDD LTE carrier in PCS A-F block spectrum.  It identified the most feasible candidate markets.

 

AJ, I thought you might chime in when you saw that feature!  I discovered how to pull the DL channel, and was trying to figure out how useful it might be.  Then a little birdie (coughdigiblurcough) reminded me of your article showing how to do the calculations, I learned what an EARFCN was, and I was off to the races.

 

I'm laying out the groundwork for some sort of basic logging component with a possible cloud implementation, but its still in the very very very early stages right now.  I have some ideas that might dovetail into your thought about keeping an eye open for new LTE channel activity.

 

-Mike

  • Like 1
Link to comment
Share on other sites

Can someone post a screenshot of a HTC device that shows the LTE connection frequencies.  I am curious what this looks like on the app.  I hope there is a way to get this same functionality on Samsung and LG devices.

Link to comment
Share on other sites

Lol. Not the usual 1912.5

I have not been able to reproduce this though.

 

Forget SMR 800 MHz. You got the 7000 MHz band.

 

;)

 

AJ

  • Like 3
Link to comment
Share on other sites

Speaking of that, I've been meaning to upload this for a couple days...

 

2z4e3bl.jpg

 

Any idea what in the world happened there? That SID in the 100k range, and my signal strength jumped up significantly compared to normal conditions in that area, but nothing was usable. I'd wager it was just the AOSP/CM RIL freaking out, but I wonder. I doubt it was a bug in Signalcheck.

Link to comment
Share on other sites

Any idea what in the world happened there? That SID in the 100k range...

That looks like a Canadian SID on steroids.

 

:P

 

AJ

Link to comment
Share on other sites

Lol. Not the usual 1912.5 I have not been able to reproduce this though. Sent from my HTCONE using Tapatalk 2

 

Good thing... the FCC might start knocking on your door if you're using those kind of frequencies.. ;)

 

In all seriousness, you actually just gave me a bug to fix.  I know exactly what is causing it, I bet AJ already figured it out too!

 

You might see it once in awhile, but it's an invalid reading.  I'm guessing you will most likely see it immediately upon connecting to LTE or right as you lose the connection.  I stumbled across another post where someone else had similar readings with a Samsung device a year ago.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Speaking of that, I've been meaning to upload this for a couple days...

 

2z4e3bl.jpg

 

Any idea what in the world happened there? That SID in the 100k range, and my signal strength jumped up significantly compared to normal conditions in that area, but nothing was usable. I'd wager it was just the AOSP/CM RIL freaking out, but I wonder. I doubt it was a bug in Signalcheck.

 

If you're on a CM ROM with a Samsung device, there's a bug in SID and NID reporting that was introduced with this change: http://review.cyanogenmod.org/#/c/45784/  Yell and scream on that page and it may get fixed.

Link to comment
Share on other sites

Speaking of that, I've been meaning to upload this for a couple days...

 

 

Any idea what in the world happened there? That SID in the 100k range, and my signal strength jumped up significantly compared to normal conditions in that area, but nothing was usable. I'd wager it was just the AOSP/CM RIL freaking out, but I wonder. I doubt it was a bug in Signalcheck.

 

How long did it stay like that?  I doubt it had anything to do with the app, I don't mess with the SID/NID/BID, just display the raw values the phone is reporting.  Are you on a CM nightly?  They have been tweaking the code to improve LTE data reporting on HTC devices; I know there was a recent bug where they had messed up the SID/NID/BID.  Perhaps they are working on similar features for other devices (fingers crossed).  If you see it again, check your 1X engineering screen and see what it looks like.

 

EDIT: Nevermind, lordsutch is up at this crazy hour too, and he posted a better answer while I was typing!  Hah..

 

-Mike

Link to comment
Share on other sites

Call me Lil Troy...

 

Switched from a Motorola to a PrimeCo phone.

Well at least after some Googling I was able to figure out what the heck you were talking about..

 

Is that accurate, or an old entry that should be Verizon now?  I'm not going to fix it just for you, but I am curious. :P

 

-Mike

Link to comment
Share on other sites

Is that accurate, or an old entry that should be Verizon now?  I'm not going to fix it just for you, but I am curious. :P

 

Most anything PrimeCo has been VZW since the turn of the century. The exceptions would be in Chicago what became USCC, in Richmond what became nTelos, and in Honolulu what became Sprint.

 

AJ

Link to comment
Share on other sites

Well at least after some Googling I was able to figure out what the heck you were talking about..

 

Is that accurate, or an old entry that should be Verizon now?  I'm not going to fix it just for you, but I am curious. :P

 

-Mike

 

I did save you a bit of sanity by not posting the YouTube video ;)  I got a good laugh when I saw that name. 

Link to comment
Share on other sites

If you're on a CM ROM with a Samsung device, there's a bug in SID and NID reporting that was introduced with this change: http://review.cyanogenmod.org/#/c/45784/  Yell and scream on that page and it may get fixed.

 

 

How long did it stay like that?  I doubt it had anything to do with the app, I don't mess with the SID/NID/BID, just display the raw values the phone is reporting.  Are you on a CM nightly?  They have been tweaking the code to improve LTE data reporting on HTC devices; I know there was a recent bug where they had messed up the SID/NID/BID.  Perhaps they are working on similar features for other devices (fingers crossed).  If you see it again, check your 1X engineering screen and see what it looks like.

 

EDIT: Nevermind, lordsutch is up at this crazy hour too, and he posted a better answer while I was typing!  Hah..

 

-Mike

If you look at the screenshot, you can see Halo "hiding", so yeah, I was on some sort of CM-based nightly. Yay more broken. I'm already back on rooted stock, there's been too many issues with CM lately. Glad it was just that instead of Sprint going bonkers.

Link to comment
Share on other sites

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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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