Jump to content

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


mikejeep

Recommended Posts

If Signal Check Pro what would show Carrier Aggregation what would it look like? Sometimes i see 1xRtt and LTE on the screen at the same time.

In a list of neighbor cells, while connected to B41, you'll see duplicate PCIs. This only works for B41, as B25/6 usually share PCIs.
  • Like 2
Link to comment
Share on other sites

Does B41 squared mean second carrier or carrier aggregation?

 

Sent from Moto X Pure via Tapatalk

 

B41^2 indicates the second carrier.

 

If Signal Check Pro what would show Carrier Aggregation what would it look like? Sometimes i see 1xRtt and LTE on the screen at the same time.

 

There is no way to indicate Carrier Aggregation at this time. The only way to see CA is to look at the engineering screen and see if the SCC PCI/RSRP fields are populating. 

  • Like 1
Link to comment
Share on other sites

Amy movement on disabling/hiding Lock Screen notifications on Lollipop & above? Also, is be happy to help test anything M-related on my Nexus 6. I've got preview 3 up and running.

On the Note5, I was surprised to see that you can restrict the apps that can have lock screen notifications. So I disabled it from the lock screen that way. Not gonna help you on the Nexus 6, but is nice for us with the latest Samsungs.

 

Sent from my SM-N920P using Tapatalk

Link to comment
Share on other sites

Without going back and wading through posts, has anyone figured out what the unknown 0dbm neighbor cells are?

No.. those just seem to indicate that the device is seeing a neighbor cell that it can't identify anything about. I wonder if its an Android bug but its hard to tell. I will probably have those filtered out in a future release as they have not proven to be useful as far as I know.

 

-Mike

Link to comment
Share on other sites

I wonder if they are Stingray devices or law enforcement fake towers. Could they belong to the other cell phone carriers?

Unlikely in this case. Those are (usually) used short-term and have limited range. They are also usually used for voice, not data, so there wouldn't be a PCI since that is for LTE. As mikejeep mentioned, it's most likely an Android bug.

 

Best way to be sure is to download the National SCP database notes in Premier forums that will show you the tower and where your neighbor cell is coming from for many markets. If anything shows up that isn't listed for the markets we have, it's either new or Stingray (or similar).

Link to comment
Share on other sites

Best way to be sure is to download the National SCP database notes in Premier forums that will show you the tower and where your neighbor cell is coming from for many markets. If anything shows up that isn't listed for the markets we have, it's either new or Stingray (or similar).

The "Unknown" sites won't correlate to anything in the national database because there is no PCI. If there is a PCI, you don't see the "Unknown" label in the app.

 

Besides a bug, my best guess would be the phone is seeing the neighbor cell before it finishes identifying it. Hard to know exactly, since most of these methods are not documented well.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Unlikely in this case. Those are (usually) used short-term and have limited range. They are also usually used for voice, not data, so there wouldn't be a PCI since that is for LTE. As mikejeep mentioned, it's most likely an Android bug.

Many Stingrays have now received the Hailstorm update. Allowing them to port into the IP standard of traffic. They are then fronthauled to the tower itself through the LTE connection now.

 

No more messy separate connection.

  • Like 1
Link to comment
Share on other sites

The "Unknown" sites won't correlate to anything in the national database because there is no PCI. If there is a PCI, you don't see the "Unknown" label in the app.

 

Besides a bug, my best guess would be the phone is seeing the neighbor cell before it finishes identifying it. Hard to know exactly, since most of these methods are not documented well.

 

-Mike

 

I have seen exactly what you describe.  A PCI may be identified at one point, not identified later, re identified an hour later, all from the same location.   This seems to be more likely where a large number of neighbors can be seen. 

 

Recently, another possibility has come to light: AT&T LTE sites.  SCP does not always see them as such, but rather as Sprint sites.  From a log from this morning:

 

Sprint 310120 00007EA7  361  17165 0  -77 40.49888  -83.9143

 

Similar situation has been observed with US Cellular.  Closer examination has revealed that you are unable to authenticate.  Mostly likely to happen in areas of weak Sprint signal when their site is nearby,

Link to comment
Share on other sites

When I'm on 1xrtt is that 2g? Would it be easier for law enforcement to capture my data if I'm on a 1xrtt connection? I only ask because my area is covered with B26 and B41 yet for some reason I'm always on 1xrtt until I update my profile. Then I hop onto B26/B41. What could cause my Note5 to keep dropping to 1xrtt when I'm covered by B26 and B41?

Link to comment
Share on other sites

running version 4.28,signal check pro largest user of battery right now on my galaxy S6.

 

 I have logging and location enabled, location accuracy set at 100m, have even bumped up to 10km, still just eating thru battery.  Have rebooted phone, i've uninstalled and reinstalled.

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

    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No specific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
    • T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.
  • Recently Browsing

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