Jump to content

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


mikejeep

Recommended Posts

The carrier name comes from the 1X connection.. he's on Verizon 1X and Sprint LTE. Last I heard, there aren't any LTE roaming agreements yet, certainly not between the major carriers.-Mike

 

Maybe stop flashing PRLs that are not for Sprint. You kinda sorta need the records that tell your device to scan for LTE.
Thank you kind gentleman! I'll relay the message and also tell him to go pro and use it to keep tabs on the emerging market. :D*Oh, and to stop flashing non-Sprint PRL's. Sent from my HTC d3rpONE using Tapatalk 4 Beta
Link to comment
Share on other sites

Mike,

 

I notice the same issue but it occurs with other apps too. (Cdma Field, Netmonitor, Opensignal, RootMetrics).  

 

*This is concerning what WiWavelength Mentioned*

Link to comment
Share on other sites

Mike,

 

I notice the same issue but it occurs with other apps too. (Cdma Field, Netmonitor, Opensignal, RootMetrics).

Not sure what 'issue' you are referring to.. do you mean the name of the cellular provider? It's because the only standard methods and variables used to check the carrier name are all based off of the 1X connection. The latest version of SignalCheck actually does it better than any of others because it doesn't rely on the built-in method to pull the name, and instead checks the 1X network it is connected to, and looks it up in a database within the app. Folks like the guy who flashed a Verizon PRL to his Sprint phone would normally not show them as being on Verizon's network, but SignalCheck will.

 

-Mike

Link to comment
Share on other sites

 This is to what I was responding too, Sorry I didn't quote it earlier.

 

Ooooh that's not good.  Any other LG users seeing similar issues?  I just received one report of stale EVDO and LTE data not clearing off the screen when the connection is lost on an LG Viper, but that's the only other LG issue I've ever received.

 

AJ, I'm sending you a PM..

 

-Mike

Link to comment
Share on other sites

The HTC patch for LTE ECIs and TACs should be going into Cyanogenmod nightlies in the next day or so: http://review.cyanogenmod.org/#/c/45607/

 

What are ECIs?  Right now, SignalCheck will display any Cell Identity and Physical Cell Identity data pulled from API 17.  I have the code for TAC data commented out because it was causing crashes and it was not benefiting anyone.  If CM is going to start populating these fields, I'll try getting it working again.

 

-Mike

Link to comment
Share on other sites

So I'm not sure if it is the CM10.1 Nightly for my Note 2 and the RIL issues or a SignalCheck issue, but I seem to be having stale data for 1X and eHRPD.  I'll watch the screen and it just hangs for 20-50 seconds, then jumps around for 10 seconds, then hangs again.  Lather, rinse, repeat...

 

Sometimes it's both, most of the time it is just one or the other...

Link to comment
Share on other sites

ECI=E-UTRAN Cell Identity (aka "hex id").

 

Sent from my EVO using Tapatalk 4

 

You'll also see them referred to as GCI's in LTE documents, Global Cell Identity.  The 3 digit ones shown on Samsung debug screens are called PCI, Physical Cell Identity (only 504 combinations in the spec).

Link to comment
Share on other sites

So I'm not sure if it is the CM10.1 Nightly for my Note 2 and the RIL issues or a SignalCheck issue, but I seem to be having stale data for 1X and eHRPD. I'll watch the screen and it just hangs for 20-50 seconds, then jumps around for 10 seconds, then hangs again. Lather, rinse, repeat...

 

Sometimes it's both, most of the time it is just one or the other...

It is probably something with the phone; signal updates are broadcast all at once; i.e. any change in 1X, EVDO, or LTE signal will trigger fresh values of all 3. The app has no control over the frequency of data updates, the device is supposed to broadcast signal changes as they occur.

 

Is there a thread anywhere about Note 2 RIL issues? Are they CM-specific?

 

-Mike

Link to comment
Share on other sites

It is probably something with the phone; signal updates are broadcast all at once; i.e. any change in 1X, EVDO, or LTE signal will trigger fresh values of all 3. The app has no control over the frequency of data updates, the device is supposed to broadcast signal changes as they occur.

 

Is there a thread anywhere about Note 2 RIL issues? Are they CM-specific?

 

-Mike

Yes, CM Specific, they've been working on this RIL since May.  For over a month, due to RIL blobs, LTE would be lost after a reboot.  We had times where the signals didn't work at all.  I believe the root is the entire family of devices trying to be under a single RIL.

 

As always awesome app and thanks for the follow up

Link to comment
Share on other sites

4.07b seems to have reintroduced the stale LTE issues on the HTC One. I was fully resolved in previous beta. Sent from my HTC d3rpONE using Tapatalk 4 Beta

 

Hmm.. check the Preferences menu, make sure "Show Hidden LTE" is not checked?

 

EDIT: Ha.. actually, check it off.  See if that fixes it...

 

-Mike

Link to comment
Share on other sites

Is there any way to set the network scan interval? Or add this as a feature? I want to get onto a 4g signal asap.

 

Network scan interval?  As in to force a re-scan for LTE?  There is no method for third-party developers to do that, other than toggling airplane mode.  SignalCheck Pro has a 'Reset Data Connection' button that will let you toggle it manually whenever you would like, but another S4GRU member wrote an app called "LTE Discovery" which automatically does it for you at a specific interval.  I've never tried that app, but I have read very good things about it and it is recommended by others around here quite often: http://s4gru.com/index.php?/topic/2864-lte-discovery-app-for-s4gru/

 

If that wasn't what you were looking for, please clarify.

 

-Mike

Link to comment
Share on other sites

Mike,

 

In the screen shot, the bsl location for 1x800 showed my location, not the tower location.  I was at a Sonic when I saw this.  The only 800 tower that Robert shows is in Olathe.

 

rTooCXfl.png

Link to comment
Share on other sites

Mike,

 

In the screen shot, the bsl location for 1x800 showed my location, not the tower location. I was at a Sonic when I saw this. The only 800 tower that Robert shows is in Olathe.

 

rTooCXfl.png

There is def 800x in Overland Park, I screen shot it last weekend, I think I actually posted it earlier in the thread. I want to say it was on W. 91st and Metcalf.

 

Sent from my HTC d3rpONE using Tapatalk 4 Beta

 

Link to comment
Share on other sites

My EVOLTE was going crazy tonight, driving across the Delaware Memorial Bridge on I-295.  It kept vibrating and showing LTE on Signalcheck, but the RF Band said [Exception] and it would go back to eHRPD.  Then back to LTE.  And back ... and forth ... etc.  Was I probably just picking up a fringe signal and losing it repeatedly?  This isn't the first time I've experienced that, either.

Link to comment
Share on other sites

Mike,

 

In the screen shot, the bsl location for 1x800 showed my location, not the tower location.  I was at a Sonic when I saw this.  The only 800 tower that Robert shows is in Olathe.

 

Well the app has no GPS functions (yet), so if it happened to be your location, that was just by chance!  Each site broadcasts latitude/longitude coordinates indicating its location.  SignalCheck takes those coordinates and translates them into the nearest street address using a remote geocoding server.

 

Many sites that are broadcasting CDMA 800 are not listed as 800 accepted on the S4GRU maps.  Many sites in my area have been broadcasting 800 for several weeks but are not showing that on the map.

 

If there is no site at the address shown, it is likely because many Sprint markets do not broadcast the actual location of the site, but an offset instead; see here: http://www.bluelinepc.com/signalcheck/help/#bslwrong

 

-Mike

  • Like 1
Link to comment
Share on other sites

My EVOLTE was going crazy tonight, driving across the Delaware Memorial Bridge on I-295.  It kept vibrating and showing LTE on Signalcheck, but the RF Band said [Exception] and it would go back to eHRPD.  Then back to LTE.  And back ... and forth ... etc.  Was I probably just picking up a fringe signal and losing it repeatedly?  This isn't the first time I've experienced that, either.

 

Yes, most likely -- especially if you were driving across the bridge.  Being in such an open area over water, your EVO was probably grabbing sites that were too far to hold onto.  The "RFBand [Exception]" display is a bug that is fixed in the next version that is coming soon.  It usually pops up when an HTC device sees an LTE signal for a moment but does not connect because it is too weak.  That would make sense in your case.

 

-Mike

  • Like 1
Link to comment
Share on other sites

Yes, most likely -- especially if you were driving across the bridge. Being in such an open area over water, your EVO was probably grabbing sites that were too far to hold onto. The "RFBand [Exception]" display is a bug that is fixed in the next version that is coming soon. It usually pops up when an HTC device sees an LTE signal for a moment but does not connect because it is too weak. That would make sense in your case.

 

-Mike

That does make sense, since the signals that kept popping up were like -124, -127, etc.

Link to comment
Share on other sites

Mike,

 

In the screen shot, the bsl location for 1x800 showed my location, not the tower location.  I was at a Sonic when I saw this.  The only 800 tower that Robert shows is in Olathe.

 

 

AJ and Rickie are slowly identifying sites that are broadcasting 800 in the Kansas market. There are many more than are marked on the sites complete map. We're not getting 800 acceptance notifications at the same intervals we are 3G and 4G.

Link to comment
Share on other sites

Well the app has no GPS functions (yet), so if it happened to be your location, that was just by chance!  Each site broadcasts latitude/longitude coordinates indicating its location.  SignalCheck takes those coordinates and translates them into the nearest street address using a remote geocoding server.

 

Many sites that are broadcasting CDMA 800 are not listed as 800 accepted on the S4GRU maps.  Many sites in my area have been broadcasting 800 for several weeks but are not showing that on the map.

 

If there is no site at the address shown, it is likely because many Sprint markets do not broadcast the actual location of the site, but an offset instead; see here: http://www.bluelinepc.com/signalcheck/help/#bslwrong

 

-Mike

 Wow, that is such a coincidence that I was at sonic getting cheese covered tatter tots and sprint would use that area as there location.  I notice that when I moved from the east side of the tower to the ease, it changed the location of the tower. 

 

Looks like 800 is on for the tower at 151st and 69 Hwy in OP, ks.

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