Jump to content

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


mikejeep

Recommended Posts

It's not actually showing B25, if it was it would say LTE 25 or 1900 LTE. (Edit: I just saw that the provider does say Sprint B25. I believe that is the default for when SCP doesn't know what you are connected to. I was looking at the notification and the top line for LTE band).

 

5.1 devices for some reason continue to report a 1x value for some time after switching to LTE from 3G. This is an android bug, as this is what the OS is reporting to SCP. Notice Discovery continues to show a 1x connection as well, even though we know it shouldn't seeing as you are on a tri-band device. I'm not sure why Discovery is able to see the GCI buy SCP is not. This bug popped up just as Mike got busy (went on vacation?) So not sure he has had a lot of time to work on it yet.

 

Sent from my LG G4

 

 

On my LG G4, SCP often won't display GCI when it is displaying 3G and LTE 1900.  It only happens with certain sites. I think it may have something to do with the G4 3g look ahead issue where it makes a table of what GCI with which NID-SID-BID.  This could actually be a feature.  LTE Discovery displays both and I can sometimes see both move the RSRP/RSSI, but it often crashes.  Only Signal Detector seems to be working fine all the time.

Link to comment
Share on other sites

Have noticed Samsung S6 having issues showing B41 on SignalCheck Pro in San Diego market.  Anyone having this issue?  It always gets stuck showing 1X and B25 LTE.  I don't have any issues with LTE Discovery displaying between bands.

 

It's not actually showing B25, if it was it would say LTE 25 or 1900 LTE. (Edit: I just saw that the provider does say Sprint B25. I believe that is the default for when SCP doesn't know what you are connected to. I was looking at the notification and the top line for LTE band).

 

5.1 devices for some reason continue to report a 1x value for some time after switching to LTE from 3G. This is an android bug, as this is what the OS is reporting to SCP. Notice Discovery continues to show a 1x connection as well, even though we know it shouldn't seeing as you are on a tri-band device. I'm not sure why Discovery is able to see the GCI buy SCP is not. This bug popped up just as Mike got busy (went on vacation?) So not sure he has had a lot of time to work on it yet.

For some reason, SignalCheck is not getting any GCI information for some sites on Lollipop when LTE Discovery is. I reached out to those guys but they didn't seem to have any idea why their method was working and mine was not. I've looked at the raw data and as far as SignalCheck can tell, the OS isn't reporting a GCI.. it's very bizarre. I'm still working on it; I bought a Nexus 6 specifically for app testing purposes so I could have a physical Lollipop and Project Fi test bed instead of relying on everyone else for help. It's supposed to get delivered today so hopefully I can make quick progress!

 

When the app doesn't see a GCI, it doesn't give a band indicator, it should keep it as generic "LTE" or "Sprint". There must be a bug that's causing the "B25" part to stick on your screen in your situation, but as you can see the status bar icon doesn't show B25. I should able to fix that display issue easily.

 

That 1X glitch is a problem, but like David said, it's something with the Lollipop OS itself. I can't filter it out because the app doesn't know what is valid and what is not. If the values are within nominal ranges, it shows them.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Something is seriously wrong with the site logger, at least for me.  I turned it on before a drive today, and after returning home I found only 1 site logged from the drive, and I know I hit at least 6 sites.  I'm not sure if this was just my device or if it's an actual bug in signal check.  I'm running the latest beta version.

 

Evan, could you backup your log .db file and send it to me, support[at]bluelinepc.com? What device/OS version? Did you have the app's background service enabled? Was the app in the foreground the entire time, or background? Are your status bar icons enabled? Was it a brand new log, or additions to an existing log? Did the app appear to be acting normally otherwise?

 

Thanks!

-Mike

  • Like 1
Link to comment
Share on other sites

Only 'bug' I've seen on latest beta:

 

Is the 'bug' the BID 0? That's more of a new feature in the latest beta.. I was noticing that when in areas with poor 1X signal strength, my N5 could get a signal reading (that changes as you move) but the SID/NID/BID/Provider lines were missing. After some testing, I discovered that the reported BID was 0 in these instances. Since it appears to be a valid signal reading, and the SID/NID proved valid in my testing as well, I have the app now display that data. It has become handy for me when traveling in the boonies of NH where I'm often roaming, and I see it hopping between Sprint/Verizon/USCC while it struggles to maintain a stable connection.

 

-Mike

Link to comment
Share on other sites

Is the 'bug' the SID 0? That's more of a new feature in the latest beta.. I was noticing that when in areas with poor 1X signal strength, my N5 could get a signal reading (that changes as you move) but the SID/NID/BID/Provider lines were missing. After some testing, I discovered that the reported SID was 0 in these instances. Since it appears to be a valid signal reading, and the SID/NID proved valid in my testing as well, I have the app now display that data. It has become handy for me when traveling in the boonies of NH where I'm often roaming, and I see it hopping between Sprint/Verizon/USCC while it struggles to maintain a stable connection.

 

-Mike

I was in BFE (25 miles into IBEZ) trying to get LTE service while mapping. It did properly pull the SID after about 5-8 seconds. I assumed it to be lag with the large national Premier SCP note database, but I hadn't seen this 'feature' in previous builds.
Link to comment
Share on other sites

I was in BFE (25 miles into IBEZ) trying to get LTE service while mapping. It did properly pull the SID after about 5-8 seconds. I assumed it to be lag with the large national Premier SCP note database, but I hadn't seen this 'feature' in previous builds.

 

Sorry, I made a typo that might have confused things -- I meant BID 0, not SID 0. In any event, any delay in SID/NID/BID display is related to the network or device, not the app. SignalCheck will show it as soon as it has it. If there was a delay related to site notes, it would cause the note field to be delayed (but I don't think you should experience that, regardless of the size of your database). You wouldn't have seen this behavior until this latest build, I just added it. Previously, it would hide the SID/NID/BID/Provider if the BID was 0. It will still hide them if the SID is 0 of course.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Evan, could you backup your log .db file and send it to me, support[at]bluelinepc.com? What device/OS version? Did you have the app's background service enabled? Was the app in the foreground the entire time, or background? Are your status bar icons enabled? Was it a brand new log, or additions to an existing log? Did the app appear to be acting normally otherwise?

 

Thanks!

-Mike

Sent all the info requested!
  • Like 1
Link to comment
Share on other sites

While doing a survey in a nearby area I found something interesting that VZW is doing with the AWS/B4 sites. In most areas I found that when they add capacity they would use a different GCI on the same site. However, with these sites they're using the same GCI and PCI while using some offset of the sector.

 

First I thought it could've been that dreaded Android bug where it would give false information when I first seen this a while ago while in the area since the sector part of the GCI looked 'off'. I guess not! I've attached a sample file with a particular site. So far this seems to be only on AWS/B4 sites and not 700/B13. Thankfully it's not really doing anything else to SCP other than not identifying the correct band.

 

While I'm here, as a request, have you thought about adding a timestamp to the strongest lat/long? I would find it useful in areas I frequently visit.

 

And also regarding the strongest lat/long, it appears the entry doesn't change unless the RSRP is stronger, but my concern is that if the device accuracy isn't good and I capture a reading that will probably not get any stronger, the lat/long won't be accurate. I have several entries where the device's accuracy is significantly off (thousands of meters due to GPS failure). Of course I could manually edit the strongest_rsrp value to allow SCP to correct it for the next time as a workaround. I'm actually not sure how this could be addressed. It's not that important as I know there are other issues to address, but maybe something to think about later.

sample.zip

Link to comment
Share on other sites

 

For some reason, SignalCheck is not getting any GCI information for some sites on Lollipop when LTE Discovery is. I reached out to those guys but they didn't seem to have any idea why their method was working and mine was not. I've looked at the raw data and as far as SignalCheck can tell, the OS isn't reporting a GCI.. it's very bizarre. I'm still working on it; I bought a Nexus 6 specifically for app testing purposes so I could have a physical Lollipop and Project Fi test bed instead of relying on everyone else for help. It's supposed to get delivered today so hopefully I can make quick progress!

 

When the app doesn't see a GCI, it doesn't give a band indicator, it should keep it as generic "LTE" or "Sprint". There must be a bug that's causing the "B25" part to stick on your screen in your situation, but as you can see the status bar icon doesn't show B25. I should able to fix that display issue easily.

 

That 1X glitch is a problem, but like David said, it's something with the Lollipop OS itself. I can't filter it out because the app doesn't know what is valid and what is not. If the values are within nominal ranges, it shows them.

 

-Mike

 

 

FYI maybe this information will help.  If 1X is not displayed when connected to B25, it will switch over to the B41 just fine.  When it is displaying both 1X and B25, I will see LTE Discovery switch to B41 and seems like SignalCheck will switch over B41.  Only work around is to airplane cycle which will latch on B41 and SignalCheck will show B41.  

Link to comment
Share on other sites

We are now seeing SCP no longer  logging with logging fully enabled while using the "national" SCP database (6/24 and 7/27).  Wondering if it is too many records for some of your variables?  Various phones and firmware: imex99 N6, nowerlater G4 with latest firmware, dkyeager g4 with original firmware.  Diagnostics sent.

 

9:15 am: The three of us worked together.  National database was absolved first.  Then verified to be just a beta issue.  Bleeding edge of technology.

 

[is now a good time to put in a plug again for site_latitude & site_longitude so we can find small cells and have accurate neighbor info? ;) ]

Edited by dkyeager
  • Like 3
Link to comment
Share on other sites

What is the little "2" behind the B25 in the provider line?

That indicates 2nd carrier band 25. Check your engineering screens to get the EARFCN and confirm that it's actually 2nd carrier. Signal Check can be wrong depending on market
Link to comment
Share on other sites

...

 

[is now a good time to put in a plug again for site_latitude & site_longitude so we can find small cells and have accurate neighbor info? ;) ]

Found a few new sites over the last couple of weeks in my market including small cells, so this would be very helpful. I'd prefer not to have to opt out of accurate neighbors for the national db, but it's quite a trade off with losing location information of new and sometimes unknown to anyone sites (I know, I want my cake and eat it too) . ;)

  • Like 3
Link to comment
Share on other sites

Found a few new sites over the last couple of weeks in my market including small cells, so this would be very helpful. I'd prefer not to have to opt out of accurate neighbors for the national db, but it's quite a trade off with losing location information of new and sometimes unknown to anyone sites (I know, I want my cake and eat it too) . ;)

Small cells? Where?

 

Sent from my LG G4

Link to comment
Share on other sites

Small cells? Where?

 

Sent from my LG G4

Complete answer against rules in a public forum. In Ohio.

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

Complete answer against rules in a public forum. In Ohio.

 

Sent from my LGLS991 using Tapatalk

Why is it against rules...not premier or put out by s4gru....his find!

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

Why is it against rules...not premier or put out by s4gru....his find!

 

Sent from my Nexus 6 using Tapatalk

 

 

THE RULE:  It is not permissible to post content obtained from the Sponsor section of S4GRU in a public forum (whether S4GRU or otherwise).  It can only be posted within S4GRU Sponsor forums.  To post info obtained from S4GRU Sponsor forums is a violation that may result in actions being taken against your membership.

 

 

 

 

 

source

  • Like 3
Link to comment
Share on other sites

You can still post the information...just minus the "illegal" content... Cross streets , etc of a new find by driving around and finding is fair game!

 

Sorry to clutter the thread, everything doesn't have to be secret squirrel.

 

Sent from my Nexus 6 using Tapatalk

  • Like 1
Link to comment
Share on other sites

We are now seeing SCP no longer  logging with logging fully enabled while using the "national" SCP database (6/24 and 7/27).  Wondering if it is too many records for some of your variables?  Various phones and firmware: imex99 N6, nowerlater G4 with latest firmware, dkyeager g4 with original firmware.  Diagnostics sent.

 

9:15 am: The three of us worked together.  National database was absolved first.  Then verified to be just a beta issue.  Bleeding edge of technology.

 

[is now a good time to put in a plug again for site_latitude & site_longitude so we can find small cells and have accurate neighbor info? ;) ]

Found a few new sites over the last couple of weeks in my market including small cells, so this would be very helpful. I'd prefer not to have to opt out of accurate neighbors for the national db, but it's quite a trade off with losing location information of new and sometimes unknown to anyone sites (I know, I want my cake and eat it too) . ;)

 

Sorry for not getting back to everyone sooner, but I'm aware of the Site Logger issue in the latest beta. I have been mostly off the grid for the past week because I've been moving.. starting to get settled in now. I'm looking into the issue -- and I'm adding those columns soon, I know it would be a huge benefit to you guys!

 

 

That indicates 2nd carrier band 25. Check your engineering screens to get the EARFCN and confirm that it's actually 2nd carrier. Signal Check can be wrong depending on market

 

I might already have it noted somewhere (see above, nearly all of my stuff is still in boxes!), but could you refresh my memory as to when the second carrier indicator might be wrong?

 

-Mike

  • Like 2
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

    • 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.
    • https://www.phonearena.com/news/t-mobile-older-rate-plan-prices-june_id157821 We're on Sprint Max for our seven phone/two Apple Watch (with Cellular) family plan... Because it doesn't make sense to switch to anything else, especially if we can't even finance all of our devices. Some of you may recall that T-Mobile suddenly cut our credit limit to $1,500 (which is barely more than one iPhone 15 Pro) with no notice at all. I escalated it to the Office of the CEO and was told to pound sand, even though I have 800+ Credit as a longtime customer and was suddenly being treated as a deadbeat. I ultimately upgraded my three iPhone lines directly through Apple and they're Unlocked. I haven't bothered to check on whether my Credit Limit has updated, but I don't plan on upgrading them through T-Mobile again. I guess we'll find out if "Sprint Max" counts as "older" soon enough.
    • From just under a week ago: https://www.t-mobile.com/news/network/t-mobile-announces-163-million-in-completed-network-upgrades-for-arkansas Progress!
  • Recently Browsing

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