Jump to content

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


mikejeep

Recommended Posts

The update is awesome! But is this normal?

 

LT4QtEK.png?2

 

Are the site's different sectors identified under different PCIs? 'Cause that's 5 PCIs for one site, one of which is displayed twice. And the "352" PCI is at -97 yet its not part of the site I'm connected to.

This is not app related, but can you please investigate what site/band/carrier you're connected to!? I've never seen a Sprint GCI ending in 32.

 

Unless I've missed something? Edit. Yes I did.

 

Sent from my LG G3

  • Like 2
Link to comment
Share on other sites

This is not app related, but can you please investigate what site/band/carrier you're connected to!? I've never seen a Sprint GCI ending in 32.

 

Unless I've missed something?

 

Sent from my LG G3

 

All of the screens I've seen of Sprint (8t8r) B41 has an odd market id - 009 in this case; and a sector id of 3X (X being 0-3? - and for that matter all of the B26 I've seen is 1X sector id).  It seems like a legit Sprint B41.

  • Like 1
Link to comment
Share on other sites

All of the screens I've seen of Sprint (8t8r) B41 has an odd market id - 009 in this case; and a sector id of 3X (X being 0-3? - and for that matter all of the B26 I've seen is 1X sector id).  It seems like a legit Sprint B41.

 

I wasn't disputing the validity, but it would appear I've been spending too much time in Samsung market threads. For those markets, 8T8R GCIs (so far) have been ending in 0x, not 3x. But now I see that in Nokia and ALU areas the GCI are ending in 3x. 

  • Like 1
Link to comment
Share on other sites

I can't believe Samsung screws up something so simple on its phones.  I've got no PCI, no neighbors, and no B41 identification. :(

 

But I'm very glad to have the update if only for the "strongest signal" fields in the log--that's a huge deal!  I also see the "coming soon" option for a continuous log; also a huge deal.  I can't wait for the next one now!

 

Does anyone know if the Verizon 4.4.4 update fixed it for those customers?  Trying to figure out if I should be looking forward to 4.4.4 as a fix or not.  Otherwise, maybe 5.0 will help...

 

And one other thing, is it possible that the next version could clean out all the null entries from the database if that bug really is fixed now?

 

- Trip

Link to comment
Share on other sites

I can't believe Samsung screws up something so simple on its phones. I've got no PCI, no neighbors, and no B41 identification. :(

 

But I'm very glad to have the update if only for the "strongest signal" fields in the log--that's a huge deal! I also see the "coming soon" option for a continuous log; also a huge deal. I can't wait for the next one now!

 

Does anyone know if the Verizon 4.4.4 update fixed it for those customers? Trying to figure out if I should be looking forward to 4.4.4 as a fix or not. Otherwise, maybe 5.0 will help...

 

- Trip

I'm on an S4T and I get band 41 identification, but no PCI/neighboring cells. I'm still on the current 4.4.2 release, maybe a new radio with the next release will fix it. Previous radios didn't have TAC.

 

Sent from my SPH-L720T using Tapatalk

Link to comment
Share on other sites

I can't believe Samsung screws up something so simple on its phones.  I've got no PCI, no neighbors, and no B41 identification. :(

 

But I'm very glad to have the update if only for the "strongest signal" fields in the log--that's a huge deal!  I also see the "coming soon" option for a continuous log; also a huge deal.  I can't wait for the next one now!

 

Does anyone know if the Verizon 4.4.4 update fixed it for those customers?  Trying to figure out if I should be looking forward to 4.4.4 as a fix or not.  Otherwise, maybe 5.0 will help...

 

And one other thing, is it possible that the next version could clean out all the null entries from the database if that bug really is fixed now?

 

- Trip

I have B41 identification.  But no PCI or neighbors.

Link to comment
Share on other sites

My problem is that all my local B41 installations are on Clearwire gear which have a different PLMN that is not reported correctly to the app, so you guys are probably on 8T8Rs or just getting lucky and one of the other ID methods just happens to flag it for you.

 

- Trip

  • Like 1
Link to comment
Share on other sites

My Note 4 is showing the neighbor cells just fine.

Is the note 4 running 4.4.4 out of the box? Could be an update in 4.4.4 for the gs5 that could fix it.
Link to comment
Share on other sites

My problem is that all my local B41 installations are on Clearwire gear which have a different PLMN that is not reported correctly to the app, so you guys are probably on 8T8Rs or just getting lucky and one of the other ID methods just happens to flag it for you.

 

- Trip

All mine is 8t8r

 

Sent from my SPH-L720T using Tapatalk

Link to comment
Share on other sites

Is the note 4 running 4.4.4 out of the box? Could be an update in 4.4.4 for the gs5 that could fix it.

Any day now the 4.4.4 (NJ1) will drop for the S5, so let's hope! They've also fixed a ton of Bluetooth issues reportedly so maybe they worked up the radios and reporting good.

 

sent from an underwater dust storm with my Sprint S5

  • Like 5
Link to comment
Share on other sites

Any day now the 4.4.4 (NJ1) will drop for the S5, so let's hope! They've also fixed a ton of Bluetooth issues reportedly so maybe they worked up the radios and reporting good.

sent from an underwater dust storm with my Sprint S5

Yes but wonder if root will be impossible with 4.4.4?

Link to comment
Share on other sites

On my one max it not showing the neighboring nor the proper plmn ID. Not even a for close and restart fixes it.

Send me a diagnostic report and I will try to see what's going in. Make sure you have neighbor cells enabled in the Preferences also.

 

-Mike

  • Like 1
Link to comment
Share on other sites

I have no neighboring cell sites on my G2. FYI.  Must have the Samsung bug.

Nor do I.  Have it on my G2. hardware version 1.0

Link to comment
Share on other sites

Mike, I am starting to question the accuracy of the neighbor cells on my Nexus 5.

Because it is showing several different towers I have no idea where they are unless they are 15 to 30 miles away.

 

If only Android would report the GCI.

I love the neighbor cells I could run the battery down watching it.

Link to comment
Share on other sites

Mike, I am starting to question the accuracy of the neighbor cells on my Nexus 5.

Because it is showing several different towers I have no idea where they are unless they are 15 to 30 miles away.

 

If only Android would report the GCI.

I love the neighbor cells I could run the battery down watching it.

If it shows it then the phone sees it.

 

It's not uncommon for signals to go way farther than expected. It just won't be usable.

 

Sent from my Nexus 5 using Tapatalk

  • Like 3
Link to comment
Share on other sites

If it shows it then the phone sees it.

 

It's not uncommon for signals to go way farther than expected. It just won't be usable.

 

Sent from my Nexus 5 using Tapatalk

Is it the phone that sees it or is it the site that knows it.?
Link to comment
Share on other sites

Mike, I am starting to question the accuracy of the neighbor cells on my Nexus 5.

Because it is showing several different towers I have no idea where they are unless they are 15 to 30 miles away.

 

If only Android would report the GCI.

I love the neighbor cells I could run the battery down watching it.

 

Like Tim said, the app reports what the phone is seeing. I have all of my nearby sites noted, and still see a "rogue" PCI on occasion. It could be that you haven't yet connected to that specific sector on that specific band, so you don't have that specific PCI recorded yet. Or your device can see it, but for whatever reason it is not accepting connections. Many possibilities. Again, as Tim said -- it's showing you what the phone sees. Just because you've never hit it doesn't mean it's not out there.

 

As far as GCI goes, it might not be an Android limitation, it might be by design; I have no idea if the LTE neighbor cell protocol includes any more information than Android is offering. It's a moot point though, I can only show what Android decides to collect. :)

 

-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

    • I have my Dish phone locked to NR-only.  That keeps it on Dish and only occasionally will it see T-Mobile NR SA for brief periods before going to no service. I also don't have mine band locked beyond that, except that I have some of the unused bands turned off just to try to reduce scan time.  Fortunately, my Dish phone is the one with the MediaTek chipset, so it has NR neighbor cells, and I can usually see n71, n70, n66, and sometimes n29 (market-dependent) through those regardless of which band it's connected to as primary. - Trip
    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • 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.  
  • Recently Browsing

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