Jump to content

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


mikejeep

Recommended Posts

Hello all,

I have been visiting S4GRU for quite some time, and one of the most common issues I see popping up is confusion from users--especially when they first get 4G LTE devices and/or LTE service--regarding their signal strengths. For some reason, the signal bars on many devices do not display what most users expect them to display. It seems strange that we have to enter special dialer codes just to see what our LTE signal is!

With that in mind, I started creating an Android app from scratch. I had never created an app before, so it took a few months before it was ready for the public, but its time has come. Robert and a few others have been beta testing it for me since October, and I recently released it onto Google Play. Robert gave me the go-ahead to give it a mention here on S4GRU, so here goes..

It's called SignalCheck, and it is available on Google Play here: https://play.google.com/store/apps/developer?id=Blue+Line+Computing
 
The "Lite" version is free; the "Pro" version has a small one-time fee but includes a bunch of extras, including signal bars in the notification area, a widget, the ability to alert a user when they pick up an LTE or 800 SMR signal, one-button instant connection reset, the street address of the connected 1X site, and menu shortcuts to some screens that are usually only accessible with dialer codes. I intend to offer S4GRU Premier Sponsors special benefits in the near future, as soon as I figure out a feasible way to do that.

This is the first app I have ever developed, so I'd appreciate any and all feedback, both positive and negative. I have been trying to educate myself as much as possible regarding cellular technologies, as I didn't know much before I started this project. My goal is to make this app as accurate and useful as possible for all the "nerds" on here.. myself included!

I intend to continue squashing bugs as they are reported, and adding features as they are requested. As I learn more about Android programming and cellular technology, I'll improve things. Please let me know what you would like to see, and I'll do what I can.

My "Beta Crew" helps test out the app before public updates are pushed out. Membership is by invite only but anyone is welcome to join in our discussions or get a sneak peek at what is going on (see thread here).
 
Links:  SignalCheck Help / FAQ  |  Change Log  |  To-Do "Wish" List  |  Known Issues  |  SignalCheck on Google Play

 
-Mike
 
Here are some screen shots from a previous version.. there have been tweaks since this release, but this is basically what you get:

http://www.bluelinepc.com/wp-content/uploads/2013/01/SignalCheck-2.0-main-168x300.png http://www.bluelinepc.com/wp-content/uploads/2013/01/SignalCheck-2.0-menu-168x300.png http://www.bluelinepc.com/wp-content/uploads/2013/01/SignalCheck-2.0-advanced-168x300.png http://www.bluelinepc.com/wp-content/uploads/2013/01/SignalCheck-2.0-pulldown-168x300.png

  • Like 31
Link to comment
Share on other sites

Very nice. hmm, should seperate the difference of eHRPD and EV-DO. I'm in the middle of having all of the towers upgraded around me and right now they are upgrading the tower i connect to most of the time when I'm at home. I can't wait till they switch it to network vision :D.

I think the app needs a tiny bit of work. Love it. I think the meter should be a speedometer. That' be awsome xD red all the way to the left, yellow middle fading to green.

Link to comment
Share on other sites

Nice!! I was looking to do something very much like this!

 

Any possible way to do what Sensorly did and get the LTE Cell Identity working on some phones?

 

I've also been reverse engineering how some the ##DEBUG screens work on the Note2 as the 1X PN and other info would be VERY helpful as well.

Link to comment
Share on other sites

Lite version: Sent you a crash report: I get 4gLTE only intermittently on my stock JB 4.1.1 GS3, and when I do, the app consistently crashes. Seems OK when LTE is not present. Now if Samsung would only update to a release that allowed access to the Sector ID info . . .

 

And, thanks for this, it will be very useful.

Link to comment
Share on other sites

I actually added LTE cell ID info to version 2.08, which I released late last night.. I suspect that is what is causing the crashes, since this is a brand new problem.

 

Any chance anyone with Jelly Bean got any cell ID info on LTE? Or anyone with Jelly Bean have it not crash while on LTE?

 

I also saw some crash reports come in for some of the shortcuts on the Advanced menu. I'll check everything out this afternoon.

 

  • Like 2
Link to comment
Share on other sites

Lite version: Sent you a crash report: I get 4gLTE only intermittently on my stock JB 4.1.1 GS3, and when I do, the app consistently crashes. Seems OK when LTE is not present. Now if Samsung would only update to a release that allowed access to the Sector ID info . . .

 

And, thanks for this, it will be very useful.

 

The sector info is there but not by a normal api. You have to request it from the baseband then parse it out.

 

-- "Sensorly or it didn't happen!"

 

 

Link to comment
Share on other sites

I am very curious what total set of info is accessible by this API or what additional info can be readily fished out the baseband, as digiblur notes above. I am not sure that a single third party app can ever replace the internal debug/engineering screen apps on some handsets. But those debug/engineering screens are being removed from many more recent devices on many carriers -- Sprint seems to be the holdout thus far, thankfully. Regardless, it would be quite nice to have a third party app that could provide at least as much detail as the debug/engineering screens. Then, the exclusion of debug/engineering screens in a handset (e.g. Nexus 4) would not be a deal breaker.

 

I have much knowledge of CDMA service options, PN offsets, channel assignments, neighbor lists, carrier bandwidths, UARFCNs, etc. My full assistance is at your disposal.

 

AJ

  • Like 3
Link to comment
Share on other sites

Just got the Pro version and will give it a shot. Not much LTE in the Raleigh/Durham area yet, but that's why this app will be nice to have so I can tell when I hit a 4G connection. Great job, will let you know if I find any issues.

  • Like 1
Link to comment
Share on other sites

Crashes on my S3 when I go to Advanced.. Battery Info, and also Advanced.. Radio Info. I reported one of the crashes from my phone just in case it gives you any useful info.

 

What are the "Field Trial" and "EPST" options? Field Trial says it's not available on my device and EPST is greyed out.

 

Can't wait to test out when I get a chance to visit where some of the completed RDU towers are.

Link to comment
Share on other sites

The sector info is there but not by a normal api. You have to request it from the baseband then parse it out.

 

That sounds easy . . . :twitch:

Link to comment
Share on other sites

The LTE sector IDs are available in the Jellybean 4.1.1 API. But according to what the devs at Sensorly say, so far there are few devices that populate it.

 

Then it sounds like it was blocked in the programming on many devices.

Link to comment
Share on other sites

Then it sounds like it was blocked in the programming on many devices.

 

I doubt that it is blocked, exactly. More likely many OEMs just failed to implement all the Jellybean API. I have read that implementation of the whole Android telephony API was imperfect in earlier versions, too.

Link to comment
Share on other sites

Ec/Io is also missing a decimal point. Measurement lower limit is -31.5 dB.

 

AJ

  • Like 2
Link to comment
Share on other sites

Crashes on my S3 when I go to Advanced.. Battery Info, and also Advanced.. Radio Info. I reported one of the crashes from my phone just in case it gives you any useful info.

 

What are the "Field Trial" and "EPST" options? Field Trial says it's not available on my device and EPST is greyed out.

 

Can't wait to test out when I get a chance to visit where some of the completed RDU towers are.

 

Worked the first time for me. Looked nice. Now crashes on my s3 every time. Even after a reboot.

 

Sent from my SPH-L710 using Tapatalk 2

Link to comment
Share on other sites

Crashes on my S3 when I go to Advanced.. Battery Info, and also Advanced.. Radio Info. I reported one of the crashes from my phone just in case it gives you any useful info.

 

What are the "Field Trial" and "EPST" options? Field Trial says it's not available on my device and EPST is greyed out.

 

Can't wait to test out when I get a chance to visit where some of the completed RDU towers are.

 

Thanks for the report. It appears that many Samsung devices either do not have these screens, or do not allow access to these areas by third-party applications. I have improved the error-checking routines in the latest version (2.09, should be available on Google Play within the hour) to handle this.

 

Field Trial and EPST are diagnostic screens normally accessible by entering special dialer codes, at least on HTC devices. I intended to allow these shortcuts to save people the hassle of knowing the dialer codes, or possibly accessing these screens on devices without a dialer (such as a tablet). If the function is not supported by a device, there is not much I can do. This part of my app is meant to provide a shortcut to pre-existing screens, not create new functionality.

 

-Mike

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...