Jump to content

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


mikejeep

Recommended Posts

My battery has been draining quickly and under battery stats, it says SignalCheck Pro is the cause @ 48% drain. Any idea what happened? The only difference is now my phone is on 4.4.2. Same locations and apps.

Whoa.. are you leaving the Site Logger and/or Location Service within the app on? Other than that, you should see hardly any battery usage; it is a very passive program. Nobody else has reported similar issues. Which device is that?

 

-Mike

Link to comment
Share on other sites

Whoa.. are you leaving the Site Logger and/or Location Service within the app on? Other than that, you should see hardly any battery usage; it is a very passive program. Nobody else has reported similar issues. Which device is that?

 

-Mike

 

I had the same thing happen once on my Nexus 5.  I then restarted my phone and the battery usage went back to normal (1%ish), and I always have the Site Logger feature turned on.  I never use the Location Service though.

Link to comment
Share on other sites

Whoa.. are you leaving the Site Logger and/or Location Service within the app on? Other than that, you should see hardly any battery usage; it is a very passive program. Nobody else has reported similar issues. Which device is that?

 

-Mike

Location and Site logger are off within the app settings. The only thing I've done differently that I can think of is adding a note to my home site. I'll wipe data and see if that helps.

 

Sent from my LG-LS980

Link to comment
Share on other sites

I keep getting this while I'm at work. There is B26 present in the area and the store has a booster in the back room but it's a for 3g only so I have a strong signal all the time.

 

In your engineering screens does it show you as connected to LTE?  That is pretty weird...  Maybe it glitched out in the transition between the two?

Link to comment
Share on other sites

In your engineering screens does it show you as connected to LTE? That is pretty weird... Maybe it glitched out in the transition between the two?

I haven't checked. It's a consistent thing and doesn't come and go so I'll check next time it pops up and I'm able to take a minute to investigate.
Link to comment
Share on other sites

I keep getting this while I'm at work. There is B26 present in the area and the store has a booster in the back room but it's a for 3g only so I have a strong signal all the time.

Hah that is interesting! Certainly an issue with the app getting stuck, not a problem with your phone. Shoot me a diagnostic report next time you see that if you can. There are still a few specific situations where B26/B41 still needs some polishing.

 

Unfortunately a can of Sprite decided to kamikaze my laptop keyboard earlier this week (I swear my hand never touched it) so I haven't had a chance to finish up the Lite update or do any more work on the app. Hopefully I will be up and running in the next couple of days.. :(

 

-Mike

Link to comment
Share on other sites

I wiped data and all is well again. :-)

Good to hear. I've recently noticed that clearing the app cache (from Settings > Apps, not the BSL cache within the app) resolves force closes and frozen screens. I'm looking into it.

 

-Mike

Link to comment
Share on other sites

Has no one else noticed that after the KitKat update Signal Check on the GS3 now shows the GCI? For an aging Samsung phone, this is nothing short of a miracle!

  • Like 5
Link to comment
Share on other sites

Has no one else noticed that after the KitKat update Signal Check on the GS3 now shows the GCI? For an aging Samsung phone, this is nothing short of a miracle!

 

Only thing that could make it better is if you could get the PCI on that screen also.

Link to comment
Share on other sites

I was successfully hunting Sprint 8t8r band 41 TD-LTE and I observed a dichotomy between Signal Check Pro results, which I was using to reset the signal and observation, and Signal Detector, which I was using for signal tracking.  Previously these two products have always matched in terms of the MCC and MNC. With Signal Detector, the MCC of 310 and the MNC of 120 stayed 100% constant, unlike my Band 25 and Clearwire Band 41 according to Signal Detector.  Later I looked at Signal Checker Pro log and it had its usual issues of seeing both 310 120 and 311 490 (note I do have a G2 using ZVA which may have issues in properly reporting MCC and MNC). 

 

I am wondering if perhaps Signal Check Pro is not blanking its MCC and MNC variables when the reset button is pushed.

 

Further details here if needed: http://s4gru.com/index.php?/topic/4825-columbus-market-mapspreadsheet-premier-edition/page-19&do=findComment&comment=321397

 

Thanks!!

Link to comment
Share on other sites

I was successfully hunting Sprint 8t8r band 41 TD-LTE and I observed a dichotomy between Signal Check Pro results, which I was using to reset the signal and observation, and Signal Detector, which I was using for signal tracking.  Previously these two products have always matched in terms of the MCC and MNC. With Signal Detector, the MCC of 310 and the MNC of 120 stayed 100% constant, unlike my Band 25 and Clearwire Band 41 according to Signal Detector.  Later I looked at Signal Checker Pro log and it had its usual issues of seeing both 310 120 and 311 490 (note I do have a G2 using ZVA which may have issues in properly reporting MCC and MNC). 

 

The G2 does have issues; it seems to pick and choose when it wants to refresh the PLMN (MCC+MNC). I'm not entirely clear on what you're trying to say above; I think perhaps you wrote Signal Detector somewhere you meant to put SignalCheck. I think you are saying that the engineering screens, Signal Detector, and SignalCheck do not show the same information? I am aware of some issues, but thought they were due to problems with the phone's radio software, not SignalCheck.. if you are seeing more accurate results with other apps, that would mean it's me, not the OEM's. Let me know!

 

-Mike

Link to comment
Share on other sites

The G2 does have issues; it seems to pick and choose when it wants to refresh the PLMN (MCC+MNC). I'm not entirely clear on what you're trying to say above; I think perhaps you wrote Signal Detector somewhere you meant to put SignalCheck. I think you are saying that the engineering screens, Signal Detector, and SignalCheck do not show the same information? I am aware of some issues, but thought they were due to problems with the phone's radio software, not SignalCheck.. if you are seeing more accurate results with other apps, that would mean it's me, not the OEM's. Let me know!

 

-Mike

Let me try again, For the first time SignalCheck Pro and SignalDetector differ on PLMN (MCC+MNC) types reported.  This occurs with the new Sprint band 41 from the 8t8r RRHs and Antennas.  Signal Check Pro reports two PLMNs: 310120 and 311490, while Signal Detector reports only 310120 100% of the time. I only saw 310120 on engineering screens. While the G2 has issues, in this particular instance I would analyze SignalCheck Pro first.  I will try to "send diagnostics" later this week and will let you know if anything changes.

 

Thanks!!

Link to comment
Share on other sites

I noticed on your "known issues" page that the GS5 should show PCI but I am unable to see it in the app. Am I missing a setting or is this an issue? Diags sent

 

I rely on reports from users for most of the info on that chart; I was led to believe that the S5 was showing PCI, but that could be wrong. Samsung devices did not report any LTE cell identity information until these KitKat updates, so this is their first attempt at it. It's more likely to be a radio firmware issue than a SignalCheck issue; the app shows everything it can see. No PCI means it's not being given a valid one to display.

 

EDIT: I just looked at your diagnostic report; your S5's radio is not reporting a PCI, which is why SignalCheck has nothing to show you. Hopefully Samsung keeps moving in the right direction and gets this fixed; I will update the chart.

 

-Mike

  • Like 1
Link to comment
Share on other sites

I keep getting this while I'm at work. There is B26 present in the area and the store has a booster in the back room but it's a for 3g only so I have a strong signal all the time.

 

Thanks for your reports! I think I found the bug; the routine to check the provider is still seeing the last GCI you connected to and using that to identify it as B26. The next update will be mostly B41/B26 bugfixes, I should be able to get this included.

 

-Mike

  • Like 1
Link to comment
Share on other sites

Let me try again, For the first time SignalCheck Pro and SignalDetector differ on PLMN (MCC+MNC) types reported.  This occurs with the new Sprint band 41 from the 8t8r RRHs and Antennas.  Signal Check Pro reports two PLMNs: 310120 and 311490, while Signal Detector reports only 310120 100% of the time. I only saw 310120 on engineering screens. While the G2 has issues, in this particular instance I would analyze SignalCheck Pro first.  I will try to "send diagnostics" later this week and will let you know if anything changes.

 

Aha.. well I'm guessing that SignalCheck is catching at least a glimpse of 311490 at some point; there is nothing in the code that would arbitrarily choose that PLMN. Hopefully the reports will show something, but like I said, the G2 does have some issues reporting PLMNs consistently. Signal Detector probably uses a different command to pull the PLMN (there are several) that the G2 always reports 310120 on.

 

-Mike

Link to comment
Share on other sites

Thanks for your reports! I think I found the bug; the routine to check the provider is still seeing the last GCI you connected to and using that to identify it as B26. The next update will be mostly B41/B26 bugfixes, I should be able to get this included.

 

-Mike

Cool! I was going to post something similar to that yesterday but was tired from being out all day.

I was down in Schaumburg and kept seeing the glitch happen and figured it must just be holding old data somewhere.

Glad you got it figured out!

  • Like 1
Link to comment
Share on other sites

I rely on reports from users for most of the info on that chart; I was led to believe that the S5 was showing PCI, but that could be wrong. Samsung devices did not report any LTE cell identity information until these KitKat updates, so this is their first attempt at it. It's more likely to be a radio firmware issue than a SignalCheck issue; the app shows everything it can see. No PCI means it's not being given a valid one to display.

 

EDIT: I just looked at your diagnostic report; your S5's radio is not reporting a PCI, which is why SignalCheck has nothing to show you. Hopefully Samsung keeps moving in the right direction and gets this fixed; I will update the chart.

 

-Mike

Ok thanks for checking into it!

Link to comment
Share on other sites

Thanks for the heads up! You nailed the problem, but the real issue is I forgot to update SignalCheck Lite -- it's still a few versions behind. The bug that popped up in the Chicago thread has been fixed in the latest version.

 

It took a lot longer than I planned thanks to an unfortunate accident with a can of Sprite (the keys on my keyboard are sticking to the board and very difficult to type on, but at least it works again!), but I have finally finished getting SignalCheck Lite up to speed! It should be available on Google Play within the hour. It includes all of the pertinent updates that Pro users received between January and April, including bugfixes, Sprint B26/B41 identification, and enhanced WiFi information.

 

The full changelog is online here: http://www.bluelinepc.com/signalcheck/change-log/

 

-Mike

  • Like 2
Link to comment
Share on other sites

It took a lot longer than I planned thanks to an unfortunate accident with a can of Sprite (the keys on my keyboard are sticking to the board and very difficult to type on, but at least it works again!), but I have finally finished getting SignalCheck Lite up to speed! It should be available on Google Play within the hour. It includes all of the pertinent updates that Pro users received between January and April, including bugfixes, Sprint B26/B41 identification, and enhanced WiFi information.

 

The full changelog is online here: http://www.bluelinepc.com/signalcheck/change-log/

 

-Mike

Did it spill like this

 

 

 

Sent from my iPad using Tapatalk

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

    • Throwed Roll Lambert's Cafe 
    • I've now seen how things work in Kobe, Hiroshima, and Osaka, as well as some areas south of Osaka (e.g. Wakayama, Kinokawa), and tried three more SIMs. The two physical SIMs (different branding for each) both use IIJ, which provides a Japanese IP address/routing on NTT, aleit LTE-only, so latency is ~45ms to Tokyo. The catch with NTT is that it uses two frequency bands (B42/3500 MHz LTE, n79/4900 MHz NR) that you're not going to get on an Android sold in the US, and I'm guessing that B42 would be helpful speed-wise on that network, as it doesn't have B41. I also found one place that doesn't have cell service: a vending machine in the back of the Osaka Castle tower. Or, rather, the B8/18/19 signal is weak enough there to be unusable. Going back to 5G for a moment, I saw a fair amount of Softbank n257 in Hiroshima, as well as in some train stations between Osaka and Kobe. 4x100 MHz bandwidth, anchored by B1/3/8, with speeds sometimes exceeding 400 Mbps on the US Mobile roaming eSIM. Not quite the speeds I've seen on mmW in the States, but I've probably been on mmW for more time over the past few days than I have in the US over the past year, so I'll take it. My fastest speed test was actually on SoftBank n77 though, with 100 MHz of that plus 10x10 B8 hitting ~700 Mbps down and ~80 Mbps up with ~100ms latency...on the roaming eSIM...on the 4th floor of the hotel near Shin-Kobe station. Guessing B8 was a DAS or small cell based on signal levels, and the n77 might have been (or was just a less-used sector of the site serving the train station). I'm now 99% sure that all three providers are running DSS on band 28, and I've seen 10x10 on similar frequencies from both NTT and SoftBank IIRC, on both LTE and 5G. I also picked up one more eSIM: my1010, which is different from 1010/csl used by US Mobile's eSIM unfortunately, as it's LTE-only. On the bright side, it's cheap (10GB/7 days is like $11, and 20GB for the same period would be around $15), and can use both KDDI and SoftBank LTE. It also egresses from Taiwan (Chunghwa Telecom), though latency isn't really any better than the Singapore based eSIMs. Tomorrow will include the most rural part of our journey, so we'll see how networks hold up there, and from tomorrow night on we'll be in Tokyo, so any further reports after that will be Tokyo-centric.
    • I think the push for them is adding US Mobile as a MVNO with a priority data plan.  Ultimately, making people more aware of priority would allow them (and other carriers) to differentiate themselves from MVNOs like Consumer Cellular that advertise the same coverage. n77 has dramatically reduced the need for priority service at Verizon where the mere functioning of your phone was in jeopardy a couple of years ago if you had a low priority plan like Red Pocket. Only have heard of problems with T-Mobile in parts of Los Angeles. AT&T fell in between. All had issues at large concerts and festivals, or sporting events if your carrier has no on-site rights. Edit: Dishes native 5g network has different issues: not enough sites, limited bandwidth. Higher priority would help a few. Truth is they can push phones to AT&T or T-Mobile.
    • Tracfone AT&T sims went from QCI 8 to 9 as well a couple years ago. I'm pretty neutral towards AT&T's turbo feature here, the only bad taste left was for those who had unadvertised QCI 7 a couple months ago moved down to 8. In my eyes it would have been a lot better for AT&T to include turbo in those Premium/Elite plans for free to keep them at QCI 7, while also introducing this turbo add on option for any other plans or devices. As it stands now only a handful of plans can add it, and only if you're using a device on a random list of devices AT&T considers to be 5G smartphones.
  • Recently Browsing

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