Jump to content

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


mikejeep

Recommended Posts

Gotcha. I know I've seen B26, I just have yet to see B41 show up when I've looked. I might try disabling B26 and B25 today to force it to look for B41 just to see where it's available around here (Baltimore market).

When the S5 came out, it was not properly reporting the PLMN (numeric identifier) it was connected to; the Sprint variant always reported 310120, which is used for band 25 & 26 but not 41. This prevented SignalCheck from ever identifying B41. Samsung released an app that fixed several of the radio bugs, but I also heard that app might reset some of your settings. Newer baseband updates might have fixed the issue as well, but I don't have any notes on that. See the bottom of this page for more info: http://www.bluelinepc.com/signalcheck/known-issues/

 

-Mike

Link to comment
Share on other sites

When the S5 came out, it was not properly reporting the PLMN (numeric identifier) it was connected to; the Sprint variant always reported 310120, which is used for band 25 & 26 but not 41. This prevented SignalCheck from ever identifying B41. Samsung released an app that fixed several of the radio bugs, but I also heard that app might reset some of your settings. Newer baseband updates might have fixed the issue as well, but I don't have any notes on that. See the bottom of this page for more info: http://www.bluelinepc.com/signalcheck/known-issues/

 

-Mike

Lame Samsung. That's really annoying. I downloaded that app but not sure it did anything... Lol

 

Sent from my Galaxy S5 on the Sprint Network

Link to comment
Share on other sites

When the S5 came out, it was not properly reporting the PLMN (numeric identifier) it was connected to; the Sprint variant always reported 310120, which is used for band 25 & 26 but not 41. This prevented SignalCheck from ever identifying B41. Samsung released an app that fixed several of the radio bugs, but I also heard that app might reset some of your settings. Newer baseband updates might have fixed the issue as well, but I don't have any notes on that. See the bottom of this page for more info: http://www.bluelinepc.com/signalcheck/known-issues/

 

-Mike

Lame Samsung. That's really annoying. I downloaded that app but not sure it did anything... Lol

 

 

Sent from my Galaxy S5 on the Sprint Network

Link to comment
Share on other sites

Yea I saw I was connected to band 41 on the engineering screen but I didn't see it on signal check pro

 

Signal Check sometimes have issues reporting B41 correctly. Sometimes it will report B41 in the provider portion and sometimes it doesn't. In the MO market B41 towers start with a different set of numbers so that how we can identify B41 vs B25/B26.

  • Like 1
Link to comment
Share on other sites

Yea I saw I was connected to band 41 on the engineering screen but I didn't see it on signal check pro

Yeah, like I said, the S5 has an issue with that. If you try that "Samsung Refresh" app you might have better luck, I know it has worked for others. Its frustrating because the enginerring screens have the correct info, but its not reporting that same information to Android. I've been in contact with Samsung but they aren't very responsive. It has probably been a bug for years, but nobody noticed because you would never connect to another PLMN.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Signal Check sometimes have issues reporting B41 correctly. Sometimes it will report B41 in the provider portion and sometimes it doesn't. In the MO market B41 towers start with a different set of numbers so that how we can identify B41 vs B25/B26.

Oh yes I should mention the app is not perfect with B41 detection on several devices.. I was only pointing out that the specific problem on Samsung phones is their enginerrs, not me ;)

 

I have caught a few quick shots of B41 on my N5 in LTE-only mode this week, but it's still very rare and nothing near where I live yet, despite some Clear towers nearby. Makes it hard to troubleshoot. If I could even find a parking lot nearby where I could connect to it easily, I'd set up shop in my Jeep and figure it out!

 

-Mike

  • Like 4
Link to comment
Share on other sites

Oh yes I should mention the app is not perfect with B41 detection on several devices.. I was only pointing out that the specific problem on Samsung phones is their enginerrs, not me ;)

 

I have caught a few quick shots of B41 on my N5 in LTE-only mode this week, but it's still very rare and nothing near where I live yet, despite some Clear towers nearby. Makes it hard to troubleshoot. If I could even find a parking lot nearby where I could connect to it easily, I'd set up shop in my Jeep and figure it out!

 

-Mike

 

Hey Mike I was in no way putting down the app. I appreciate all the hard work you put into SCP. Without it we would not half of the information that we have in most of the markets that are being tracked. 

 

Keep up the good work

  • Like 4
Link to comment
Share on other sites

If I could even find a parking lot nearby where I could connect to it easily, I'd set up shop in my Jeep and figure it out!

 

Wait, you have a Jeep?  No way.  That comes as a surprise.

 

AJ

  • Like 3
Link to comment
Share on other sites

Two local full build towers which had Band 26 launched last week or so i think are in optimization mode now.    They have been playing with the BSL coordinates...i think, on 1x800 and 1xRTT. Does this normally happen during optimizing?

 

As for signal check, when it sees new BSLs, does it bold them the first time it connects?  They are showing up bold now and then unbolded if i open it again.

Link to comment
Share on other sites

Hey Mike I was in no way putting down the app. I appreciate all the hard work you put into SCP. Without it we would not half of the information that we have in most of the markets that are being tracked.

Oh I wasn't taking it as a putdown, no worries! Just wanted to make sure I mentioned that I knew there were still some issues identifying B41 on non-Samsung devices.

 

Two local full build towers which had Band 26 launched last week or so i think are in optimization mode now. They have been playing with the BSL coordinates...i think, on 1x800 and 1xRTT. Does this normally happen during optimizing?

 

As for signal check, when it sees new BSLs, does it bold them the first time it connects? They are showing up bold now and then unbolded if i open it again.

Many (all?) of the sites around me had their BSL coordinates (offset here in the Boston market) tweaked during the upgrade process.. most were not significant, just a few blocks or so. I have read that in other markets, BSLs that were previously offset are now exact.

 

SignalCheck bolds the BSL if those coordinates were not saved in the cache, indicating a "new" site. If you leave the app and then bring it to the foreground again, it will no longer be bolded because it re-queries the cache and now sees it as a saved coordinate pair. By only caching the coordinates and not the site itself, you don't have to worry about stale BSL information being cached. If Sprint changes something, the app will reflect it immediately.

 

The only time SignalCheck uses any internet access is when you see a bold BSL, because it had to determine the address by submitting a geocoding query to Google. Non-bolded BSL addresses are pulled from the local cache. No reason for those on limited data plans to needlessly waste KBs on a geocoding query every single time they switch 1X sites..

 

-Mike

  • Like 4
Link to comment
Share on other sites

Mike, I know you are just bubbling over with spare time, so I have a question:  I just bought a shiny new LivePro projector.  I would like to know what bands it is connecting to, but Google Play refuses to load SCP, saying that it is incompatible with my device.

 

Any insights?

 

Thanks in advance.

Not sure if you had tried it or not, but SCP can be side loaded on the LivePro. It's a little awkward when you have the app open as it forces the screen in portrait mode like a phone so you have to hold it sideways, but the notifications and the status bar seem to work fine so far. I would be willing to bet the screen aspect ratio is the reason google play thinks it's incompatible, every other app I side loaded (speedtest, fcc speed test etc) all do the same thing and force portrait mode but still work perfectly fine.

  • Like 2
Link to comment
Share on other sites

Not sure if you had tried it or not, but SCP can be side loaded on the LivePro. It's a little awkward when you have the app open as it forces the screen in portrait mode like a phone so you have to hold it sideways, but the notifications and the status bar seem to work fine so far. I would be willing to bet the screen aspect ratio is the reason google play thinks it's incompatible, every other app I side loaded (speedtest, fcc speed test etc) all do the same thing and force portrait mode but still work perfectly fine.

Does SCP work any better if you go into Preferences > Display Settings > Enable Orientation Sensor?

 

-Mike

  • Like 3
Link to comment
Share on other sites

Does SCP work any better if you go into Preferences > Display Settings > Enable Orientation Sensor?

 

-Mike

That works, didn't realize that setting was even there. You end up having to scroll, but no more holding the device sideways.

 

Sent from my Nexus 5 using Tapatalk

  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

Oh yes I should mention the app is not perfect with B41 detection on several devices.. I was only pointing out that the specific problem on Samsung phones is their enginerrs, not me ;)

 

I have caught a few quick shots of B41 on my N5 in LTE-only mode this week, but it's still very rare and nothing near where I live yet, despite some Clear towers nearby. Makes it hard to troubleshoot. If I could even find a parking lot nearby where I could connect to it easily, I'd set up shop in my Jeep and figure it out!

 

-Mike

I was wondering this about a mth ago when i got the G3.....sometimes it tells me 41 other times no (and i know it is)

 

Hey per chance is there a way to have a notification ring when we connect to 26???

Link to comment
Share on other sites

I was wondering this about a mth ago when i got the G3.....sometimes it tells me 41 other times no (and i know it is)

 

Hey per chance is there a way to have a notification ring when we connect to 26???

You might see the opposite too.. earlier tonight I was all excited because I was driving around and it was showing B41. After a little bit of time I realized it wasn't true. Must have caught a quick blip of it somewhere, and the app never flipped back. :(

 

B26 notifications aren't in there yet, but hopefully will be soon. I pick and poke at the code whenever I have a chance, it just isn't too often lately. But, good news on that front.. as of Monday I will have a much lighter workload, at least a few weeks.. that means I can spend some serious time on new updates!

 

-Mike

  • Like 8
Link to comment
Share on other sites

Hey, Mike, Llama has been acting up lately, and I'm thinking it's due to network issues. Here's a screenshot, and I notice the utter lack of data other than signal strength. I'm hoping this is due to nTelos network changes (upgrades?)

f233946fda3c5527bfd5e6a27932fe92.jpg

 

Thoughts?

Thanks

Link to comment
Share on other sites

Hey, Mike, Llama has been acting up lately, and I'm thinking it's due to network issues. Here's a screenshot, and I notice the utter lack of data other than signal strength. I'm hoping this is due to nTelos network changes (upgrades?)

 

I don't know much about Llama, but isn't it an app that automates tasks based on your location? And missing SID/NID/BID information is a sign that you have mobile location features disabled on your device, so the two issues go hand-in-hand. Go into your device's Settings menu (not SignalCheck's), and ensure that you have the option to determine location by mobile/cellular networks enabled. This is usually separate from the satellite/GPS option, which is not needed by SignalCheck.

 

-Mike

Link to comment
Share on other sites

Mike,

 

In the "Error in Custom LTE Discovery Apps" thread, you say:

 

"Are you sure it's on Band 41 (i.e. confirmed thorough engineering screen)? SignalCheck uses the PLMN to identify B41, it should be 311490 or 311870. Band 25 and 26 use PLMN 310120."

 

The new 8T8R B41sites apparently also use the 310120 PLMN, but offset the B25/B26 GCI.  This has been illustrated in the "TDD LTE 2600 . . ." Premier thread, and I have also seen it in the Chicago market.

 

Just another happy Sprint idiosyncrasy to drive you totally insane as you try to get Signal Check to report the truth. :wall:

 

And you thought you'd have time to watch football . . .

Link to comment
Share on other sites

The new 8T8R B41sites apparently also use the 310120 PLMN, but offset the B25/B26 GCI.  This has been illustrated in the "TDD LTE 2600 . . ." Premier thread, and I have also seen it in the Chicago market.

 

Just another happy Sprint idiosyncrasy to drive you totally insane as you try to get Signal Check to report the truth. :wall:

 

And you thought you'd have time to watch football . . .

 

Ah! That is very interesting, I wonder if Sprint is going to eventually transition everything onto 310120. It's not all bad news.. yes, it's more work for me, but identifying the PLMN has proven to be very unreliable. That's why SignalCheck isn't great at B41 identification yet. Is there a confirmed GCI pattern? I thought I follow all the relevant threads, I will go do some digging. The app would actually work much better if it only had to rely on GCI patterns (see Band 26 and AT&T band identification).

 

There's always time for football!! :)

 

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