Jump to content

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


mikejeep

Recommended Posts



Op now it's working. Accept now the GCI disappers when I turn my GPS off. It never did that before


Significant changes were introduced with Android 6.0 that limited what cell and Wi-Fi info would be accessible without Location access. I believe the theory behind it was that you could use that information to deduce your location. I held off implementing those APIs in SignalCheck as long as possible because I knew it would create headaches, but they have been in place since version 4.43 of the app, which was released in June 2017. Perhaps Samsung didn't fully implement those changes in it's flavor of the OS until the new update you just applied.

-Mike
  • Like 3
Link to comment
Share on other sites

Mike, I'm on Pixel 2 (not XL) running Android 8.1 and there's a really annoying, consistently re-produceable bug with multitasking. Apologies if it's already reported, but I'm pretty sure it's been in multiple releases.

If you use the BACK button to back out of the app, and then switch back to it again later, you can exit the app normally. If you use the HOME or app switcher buttons instead, it's like the app creates a new activity view and pushes it onto the history stack. It's cumulative too, so sometimes you have to end up pressing BACK or menu -> Exit multiple times to back out of all the views before the app will finally close.

  • Like 3
  • Sad 1
Link to comment
Share on other sites

Sorry for the double post. Made a video of the bug in action:
To reproduce:
1. Switch away from the app without using the back button.
2. Use the notification to switch back.
3. Try to exit app.


Huh.. very strange -- I'm not able to reproduce this on my Pixel 3. One other person reported it to me a few months ago (I don't think it was you) but I was not able to reproduce that on my original Pixel. Do you have a custom launcher, memory management app, or anything else installed that you can think of that might play a role?

-Mike
  • Like 1
Link to comment
Share on other sites

On 1/6/2019 at 7:38 AM, mikejeep said:

Huh.. very strange -- I'm not able to reproduce this on my Pixel 3. One other person reported it to me a few months ago (I don't think it was you) but I was not able to reproduce that on my original Pixel. Do you have a custom launcher, memory management app, or anything else installed that you can think of that might play a role?


-Mike

 

Just Magisk/Xposed. I don't suppose it could be something with GravityBox? Pretty sure it happens even with that disabled, but I will confirm.

To re-produceable, make sure you're switching away from SignalCheck WITHOUT using the back button (e.g. with the home button, and then using the NOTIFICATION to switch back.

Sent two diagnostic reports just in case there's anything in there that might help. One is after following the above steps several times to trigger the bug (but BEFORE trying to exit), and the other is immediately after the first exit attempt (when the app just opens again instead).

  • Thanks 1
Link to comment
Share on other sites

29 minutes ago, JWMaloney said:

Just Magisk/Xposed. I don't suppose it could be something with GravityBox? Pretty sure it happens even with that disabled, but I will confirm.

To re-produceable, make sure you're switching away from SignalCheck WITHOUT using the back button (e.g. with the home button, and then using the NOTIFICATION to switch back.

Sent two diagnostic reports just in case there's anything in there that might help. One is after following the above steps several times to trigger the bug (but BEFORE trying to exit), and the other is immediately after the first exit attempt (when the app just opens again instead).

I was trying it without using the back button.. I tried exactly what you suggested, as well as many variations of that, using the recent tasks, home button, back button, notification icon, widget, etc.. I could not duplicate it. Please try it with Xposed and/or GravityBox disabled. I just checked out your diagnostic reports; the only errors I see are these, neither of which are being generated by SignalCheck; the third one referencing Xposed repeats numerous times over several minutes:

01-09 10:41:48.200 E/SpellCheckerSession(28997): ignoring processOrEnqueueTask due to unexpected mState=TASK_CLOSE scp.mWhat=TASK_CLOSE
01-09 10:41:48.200 E/SpellCheckerSession(28997): ignoring processOrEnqueueTask due to unexpected mState=TASK_CLOSE scp.mWhat=TASK_CLOSE
01-09 10:41:53.642 W/zygote64(29404): ClassLoaderContext size mismatch. expected=1, actual=2 (PCL[] | PCL[];PCL[/data/dalvik-cache/xposed_XResourcesSuperClass.dex*2802528989:/data/dalvik-cache/xposed_XTypedArraySuperClass.dex*708326108])

Let me know how it goes! Send diagnostics if you have issues, before and after are great -- you never know where an obscure error is going to get flagged and point me in the right direction.

Thanks,
-Mike

Link to comment
Share on other sites

Stock S8

I reported extra instances maybe a week ago through diagnostics.  When I use the notification and the app is already open and it opens another instance over top. Then I have to close or back how ever many times I opened +1 to get out of the app. Animation is a slide from right to the left when opening another instance and slide from the left to the right when closing an instance.

Also I see wifi calling in the app when only connected to wifi(Wifi+[null]) and nothing connected to something else and Wifi(Wifi+LTE or WiFi+cdma). 

  • Thanks 1
Link to comment
Share on other sites

17 minutes ago, Flompholph said:

Stock S8

I reported extra instances maybe a week ago through diagnostics.  When I use the notification and the app is already open and it opens another instance over top. Then I have to close or back how ever many times I opened +1 to get out of the app. Animation is a slide from right to the left when opening another instance and slide from the left to the right when closing an instance.

Also I see wifi calling in the app when only connected to wifi(Wifi+[null]) and nothing connected to something else and Wifi(Wifi+LTE or WiFi+cdma). 

Hmm.. just dug out your report too, I don't see anything specific that might cause multiple instances. Any recollection which version this started with?

Regarding your Wi-Fi Calling icon, at the time of your report your device was reporting the voice side was connected to the 1X macro site, not Wi-Fi Calling. I have discovered that many phones do not reliably report Wi-Fi Calling status to the OS in the only manner I can access it. As you have seen, in certain instances it shows properly, but sometimes it does not. I'm still trying to find better ways to access this info.

Also, I do see you have the root EARFCN method enabled, perhaps unnecessarily? It's logging lot of errors, are you seeing any error messages on your end? You can turn that off under Preferences > General > Enable Modem Commands if you're not using it; it would save some system resources.

-Mike

Link to comment
Share on other sites

SCP has been reopening on me as well on occasion. I've had it happen on all of my devices including my unrooted stock Pixel 2XL and Nexus 6P running LineageOS 15.1. It usually happens when I access SCP through the notification.

Sent from my Pixel 2 XL using Tapatalk

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, mikejeep said:

Also, I do see you have the root EARFCN method enabled, perhaps unnecessarily? It's logging lot of errors, are you seeing any error messages on your end? You can turn that off under Preferences > General > Enable Modem Commands if you're not using it; it would save some system resources.

-Mike

Just trying to break your app:devil:. But only 2 toast messages on start up. But I will turn it off and restart phone to give you a clean log. I did not think it would fill the cat file with errors.

  • Haha 1
Link to comment
Share on other sites

2 minutes ago, Flompholph said:

Just trying to break your app:devil:. But only 2 toast messages on start up. But I will turn it off and restart phone to give you a clean log. I did not think it would fill the cat file with errors.

Hey it doesn't bother me, you're the one wasting battery for no reason.. 😉

-Mike

  • Like 1
Link to comment
Share on other sites



. . . Also I see wifi calling in the app when only connected to wifi(Wifi+[null]) and nothing connected to something else and Wifi(Wifi+LTE or WiFi+cdma). 


Aha! This explains my issue.

Sent from my 2PZC5 using Tapatalk

Link to comment
Share on other sites

I managed to get my old HTC EVO LTE test device to duplicate the multiple instances bug. I can't figure out why it's not impacting my Pixel 3, but I guess that doesn't matter. I think I see what is causing the issue.. can anyone confirm that this behavior started with version 4.49 (released October 2018)? Or did it not appear until the most recent release from last month, 4.51?

-Mike

Link to comment
Share on other sites

4 hours ago, mikejeep said:

I managed to get my old HTC EVO LTE test device to duplicate the multiple instances bug. I can't figure out why it's not impacting my Pixel 3, but I guess that doesn't matter. I think I see what is causing the issue.. can anyone confirm that this behavior started with version 4.49 (released October 2018)? Or did it not appear until the most recent release from last month, 4.51?

-Mike

Fairly sure the old version had the issue too. Can you send me a copy to confirm?

Link to comment
Share on other sites

2 hours ago, JWMaloney said:

Fairly sure the old version had the issue too. Can you send me a copy to confirm?

I loaded an old version myself after I posted, the issue appears to be related to the change in October that I suspected.. thanks! I think I've already got a fix working.

-Mike

  • Like 3
Link to comment
Share on other sites

Can you add a feature to allow users of the app to change the max-min of the bars on the Status Bar Notifications from SignalCheck?
I would like to set them so I know what true strength I have...a2fc765c6adee6dbca1ee369aa881a22.jpg

Sent from my LG-M150 using Tapatalk - S4GRU

Link to comment
Share on other sites

40 minutes ago, DesotoTyler said:

Can you add a feature to allow users of the app to change the max-min of the bars on the Status Bar Notifications from SignalCheck?
I would like to set them so I know what true strength I have...

Sent from my LG-M150 using Tapatalk - S4GRU
 

The true strength is best represented with the RSRP option. (Network Type and Signal strength).

Link to comment
Share on other sites

The true strength is best represented with the RSRP option. (Network Type and Signal strength).
I meant the signal bars. There should be a setting to change how many bars display at a certain strength...

Sent from my LG-M150 using Tapatalk - S4GRU

Link to comment
Share on other sites

  • 2 weeks later...
6 hours ago, jthawks said:

Saw this come up but not seeing a small cell near byc7d9c788a5bbf340198790c279652cd1.jpg

Sent from my SM-N960U using Tapatalk
 

All small cells that we have seen in Ohio have a PCI of 450 or greater.

Link to comment
Share on other sites

Saw this come up but not seeing a small cell near byc7d9c788a5bbf340198790c279652cd1.jpg

Sent from my SM-N960U using Tapatalk


Its basically a mini mac. We do have a small cell in the Cincinnati market that is broadcasting 2 signals with different pci and gci. Mike did that just incase its discovered somewhere else also.

Sent from my SM-G965U 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

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