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

    • Today I was driving over in Bothell/Kenmore area. I noticed the site which used to host Sprint eNB 745953 (where Waynita Way NE turns into 100th Ave NE) before it was fully decommissioned last year is now hosting all new T-Mobile gear. The gear isn't live yet but is fully installed. My guess is they plan to decommission the T-Mobile B2/B66 (enB 84647) only site a few blocks up the hill. This is a great move because decommissioning that old site would reduce interference with eNB 84740/175124. At the same time, the new location should notably improve coverage in the geographically shielded area along Waynita/100th.  The weird thing is I can't find a permit for this anywhere!
    • Mint and Ultra: Welcome to the T-Mobile Family! https://www.t-mobile.com/news/business/t-mobile-closes-acquisition-mint-and-ultra-mobile
    • https://www.t-mobile.com/2023-annual-report Most items s4gru members will be aware of, but an interesting read.
    • I've now seen 100 MHz n77 from SoftBank and 100 MHz n78 from NTT. NTT seems to be a bit better south of Osaka, though in some cases it drops down to B19 LTE as some areas around here are pretty rural. SoftBank has n77 around, but it's flakey enough that I switched eSIMs earlier this morning.
    • I'm currently typing this from a bullet train headed from Tokyo to Osaka. Using a roaming eSIM rather than T-Mobile as it's a lot cheaper, but I'll start with T-Mobile's roaming experience. Since I have a business line, I can't add data packs online, so I'm just using the 256 kbps baseline service you get by default. That service runs on Softank 4G. SoftBank has a well-built-out LTE network though, with plenty of B41, falling back to B1/3/8 as needed. 5G roaming from T-Mobile doesn't appear to exist though. I've seen 20+10 MHz B41 when I've looked, generally speaking. WiFi calling works well, and voice calls over LTE work fine too (I forgot to turn WiFi back on after doing some testing, so I expect my bill to be a dollar more next month). I want to say I even got HD voice over the cell network for the VoLTE call I did. I have a bunch of eSIMs and a couple of physical SIMs to try out. I've gotten the eSIMs up and running, but last I checked the physical SIM wasn't working even after activation so I'll run through eSIMs for the moment and update this thread with pSIM info and details on not-Tokyo in the coming days. First off, there's US Mobile's complimentary East Asia eSIM (5GB) that I grabbed before my unlimited plan Stateside expired. That SIM uses SIM Club, routing through Singapore, running on SoftBank LTE and 5G. I've seen 40 MHz n77, as well as 10x10 n28, and have seen download speeds in excess of 200 Mbps with uploads of more than 50 Mbps, though typical speeds are slower. Routing is via Equinix/Packet.net. 5G coverage is rather spotty, but LTE is plenty fast enough; either my phone doesn't want to use the 5G band combos that have more coverage or 5G coverage is just spottier here than in the US (at least on T-Mibile). Latency is as low as 95ms to sites in Singapore (usually closer to 120ms), which is pretty great considering the 3300 mi between Tokyo and Singapore. Next there's Ubigi. It also routes through Singapore via Transatel (despite being owned by NTT), and sites on top of NTT docomo's network. I didn't see NTT 5G in Tokyo when I tested it, but since then I've seen 10x10 n28, and have seen B1/B3/B19 on the LTE side. So far it's not the fastest thing out there, but I'm guessing coverage will be a little better...or maybe not. This was $17 for 10GB. Latency is a bit higher to Singapore, but still under 150ms it seems. Then there's Airalo, which was the cheapest when I bought it at $9 for 10GB. It also routes through Singapore (on Singtel), but on my S24 I have my pick of KDDI (au) or SoftBank. KDDI has extensive B41 coverage and I've seen 20+20 with UL CA. While waiting for the train at HND Terminal 3 (Keikyu line) I hit 250+ Mbps down and 10+ Mbps up...over LTE...with pretty respectable latency numbers (not much above 100ms). This is in adition to supporting SoftBank, also on LTE (my S24 defaulted to KDDI, while my wife's Pixel 8 defaulted to SoftBank and didn't seem to want to connect to KDDI). Of the various carriers mentioned, I'd say this was the best pick, though prices have bumped back up to $18 for the 10GB plan...but it's probably still what I'd pick if I had to pick just one carrier. Then there's Saily, which uses Truphone out of Hong Kong. I haven't used this as much, as I only grabbed 3GB for $7. It runs on NTT but doesn't seem to have 5G access and doesn't seem to have as good speeds. Yes, Hong Kong is way closer to Japan, but latency didn't seem to be any better, at ~150ms. In all cases, I've had reception even in train tunnels and even at high speed on the bullet train, on all three carriers I've tried (I don't think I'll be able to play with a Rakuten SIM, which is rather disappointing). There have been cases where service has degraded, but it looks like you'd have reasonable cell service no matter which of the big three carriers you picked...and since T-Mobile roams on one of them, that's good enough if you're content to buy day passes.
  • Recently Browsing

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