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

[Ascertion]

Hey Mike,

 

Any word on the No Connection bug for WCDMA on GS7, GSM variants?

[SturgeonGeneral]

 

Any ideas? GS7EDGE

 

 

Sent from my SM-G935P using Tapatalk

[Trip]

Mike,

 

I have a BLU R1 HD (Amazon Prime model).  It's a dual SIM device but if I try to enable the second SIM for phone calls, all of a sudden LTE data vanishes from SCP.  It's not the only thing wrong with how SCP works with the device, but it's the most annoying.  When I look at Diagnostic Mode, I can clearly see the LTE data still present, but not showing up.

 

Additionally, getting under my skin is the fact that it shows GSM and LTE at the same time whenever LTE is connected, but the GSM data is dummy data (which then gets logged in the GSM log incorrectly, too).

 

I'm sure you're busy, but if you have a chance to give it a look, let me know what I can do to help you piece it together.  I don't remember if I've sent you diagnostics yet.

 

- Trip

[SuzieTuesday]

So hopefully it's ok to ask a SCP question as it relates to T-Mobile on this forum.  Question is which should I believe, SCP telling me "LTE 700" or the EARFCN?  Clearly they disagree.  I suspect this really wasn't Tmo band 12 in Phoenix as TV channel 51 has not moved yet.  This is a Nexus 6P.

 

[Trip]

Is it a rooted device?

 

My gut feeling is to trust the EARFCN.  The "700" indicated by SCP is a guess since T-Mobile's sector IDs are wildly inconsistent.  (In some places I travel, the sector 01/02/03 that's listed as "LTE AWS" is actually on PCS, for example.  In my area, 04 can be either 700 or AWS, depending on whether or not the site has 3 or 4 sectors.)

 

- Trip

[SuzieTuesday]

Is it a rooted device?

 

My gut feeling is to trust the EARFCN.  The "700" indicated by SCP is a guess since T-Mobile's sector IDs are wildly inconsistent.  (In some places I travel, the sector 01/02/03 that's listed as "LTE AWS" is actually on PCS, for example.  In my area, 04 can be either 700 or AWS, depending on whether or not the site has 3 or 4 sectors.)

 

- Trip

Yes it is rooted.  Thanks for the info.  EARFCN was sort of my gut feeling as well, I assume that's sort of "unprocessed data"  taken from the modem commands available at /dev/smd11.

[Trip]

If it's a rooted device, then the EARFCN is coming straight out of the modem, which it sounds like you already know.  As such, I would consider it to be reliable.

 

- Trip

[BlueAngel]

Is it possible to change the status bar icon to match the system theme? I've noticed and just haven't said anything but on my Note 5 that since the marshmallow update I can't really see the text in the stock messaging app, it's white on white more or less. This is really the only app I have seen issues with. I can provide a screenshot if needed.

 

Sent from my SM-N920P using Tapatalk

[Dkoellerwx]

Is it possible to change the status bar icon to match the system theme? I've noticed and just haven't said anything but on my Note 5 that since the marshmallow update I can't really see the text in the stock messaging app, it's white on white more or less. This is really the only app I have seen issues with. I can provide a screenshot if needed.

 

Sent from my SM-N920P using Tapatalk

The icon changes color on my G5. When I open LG apps, the bar turns white and the text turns black.

 

Sent from my LG G5

[BlueAngel]

The icon changes color on my G5. When I open LG apps, the bar turns white and the text turns black.

 

Sent from my LG G5

Mine doesn't.

 

Sent from my SM-N920P using Tapatalk

[Dkoellerwx]

Mine doesn't.

 

Sent from my SM-N920P using Tapatalk

Maybe a Note issue rather than a Signal Check issue?

 

Sent from my LG G5

[Tengen31]

I didn't know upgraded to the LG G 5.

[dkyeager]

Mike, we have discovered a new type of Sprint site which is only being identified as LTE in SCP. These new sites are Clear Conversion sites operating on B41 yet have the standard market three character prefix. This is then followed by a 9 or an A in the dozens of cases that we have confirmed in Cincinnati, Columbus, Cleveland, and Sacramento. The easiest way to identify them is likely by the GCI sectors, 31, 32, 33 for first carrier, 39, 3A, 3B for second carrier

 

These sites actually have 3 "Nokia mini macros*" rather than RRHs, thus they have 3 unique site GCI, which have always been sequential so far. PCIs remain the same as the Clear Huawei sites they are replacing. The PLMN is pure Sprint rather than Clear or Clearwire. We understand from various Sprint contacts that these sites need to be replaced by the end of the year as part of the original Softbank buyout of Sprint.

 

For more detailed information, start here for Columbus: http://s4gru.com/index.php?/topic/4825-columbus-market-mapspreadsheet-premier-edition/page-108#entry485655 and here for Cincinnati: http://s4gru.com/index.php?/topic/6200-cincinnati-market-mapspreadsheet-premier-edition/page-44&do=findComment&comment=485752

 

This will likely affect the following markets which have Huawei*: Cleveland, Columbus, Cincinnati, Denver, (Northern) Los Angeles, Merced, Modesto, Sacramento, Salt Lake City, San Francisco - San Jose Bay Area, Seattle, Stockton, Visalia-Tulare-Porterville

 

*credit lilotimz

Edited September 9, 2016 by dkyeager

[kg4icg]

Sitting here in Chambersburg PA and I got this, band 25 CA

 

Sent from my 2PQ93 using Tapatalk

[kg4icg]

I guess just a anomaly, did a airplane mode reset and it's showing regular band 25 setup now

 

Sent from my 2PQ93 using Tapatalk

[jefbal99]

That's Band 25 second carrier, not Band 25 CA.  on Band 41 you might see a superscript 2 or 3 for a second or third carrier.

 

Only way to see CA active is in the engineering screens.

[Dkoellerwx]

Sitting here in Chambersburg PA and I got this, band 25 CA

 

Sent from my 2PQ93 using Tapatalk

 

As stated above, this is the second B25 carrier, but not CA. There will not be carrier aggregation on Band 25 anytime in the foreseeable future. Many markets (most?) now have a second B25 carrier live.

[BlueAngel]

I've yet to see a second B25 carrier, not sure if there are any around me however. Then again I hardly ever see B25, I am usually camped on B41 at all times and B26 when B41 won't reach me.

[kg4icg]

Now look at the next that I did saying it might have been a error on the same node but no 2nd carrier annotation

 

Sent from my 2PQ93 using Tapatalk

[Dkoellerwx]

Now look at the next that I did saying it might have been a error on the same node but no 2nd carrier annotation

 

Sent from my 2PQ93 using Tapatalk

 

It was probably not an error, you were seeing the second carrier as noted by the ^2 next to B25. We were just making it clear that SCP does not show Carrier Aggregation for any band, just simply tells you when you are connected to a second (or third) carrier.

[Flompholph]

Now look at the next that I did saying it might have been a error on the same node but no 2nd carrier annotation

Sent from my 2PQ93 using Tapatalk

B25 second carrier is live in shentel at least 110 plus sites. But CA is when the phone is using both at the same time. If you are using CA shorthand for the superscript 2 that may cause confusion.

[mhammett]

crw-rw---- 1 system    system       230,   0 1970-03-21 05:14 /dev/smd0
crw------- 1 root      root         230,   1 1970-03-21 05:14 /dev/smd1
crw------- 1 root      root         230,  11 1970-03-21 05:14 /dev/smd11
crw------- 1 root      root         230,   2 1970-03-21 05:14 /dev/smd2
crw------- 1 root      root         230,  21 1970-03-21 05:14 /dev/smd21
crw------- 1 root      root         229,  11 1970-03-21 05:14 /dev/smd22
crw------- 1 root      root         230,  27 1970-03-21 05:14 /dev/smd27
crw------- 1 root      root         230,   3 1970-03-21 05:14 /dev/smd3
crw------- 1 root      root         230,  36 1970-03-21 05:14 /dev/smd36
crw-rw---- 1 system    system       230,   4 1970-03-21 05:14 /dev/smd4
crw-rw---- 1 system    system       230,   5 1970-03-21 05:14 /dev/smd5
crw-rw---- 1 system    system       230,   6 1970-03-21 05:14 /dev/smd6
crw-rw---- 1 bluetooth net_bt_stack 230,   7 1970-03-21 05:14 /dev/smd7
crw------- 1 root      root         230,   8 1970-03-21 05:14 /dev/smd8
crw-r----- 1 radio     radio        229,  25 1970-03-21 05:14 /dev/smd_cxm_qmi
crw------- 1 root      root         229,  28 1970-03-21 05:14 /dev/smd_data_0
crw------- 1 root      root         229,  27 1970-03-21 05:14 /dev/smd_logging_0
crw------- 1 root      root         229,  30 1970-03-21 05:14 /dev/smd_pkt_loopback
crw------- 1 root      root         229,  24 1970-03-21 05:14 /dev/smd_sns_adsp
crw------- 1 root      root         229,  21 1970-03-21 05:14 /dev/smd_sns_dsps
crw------- 1 root      root         229,  26 1970-03-21 05:14 /dev/smd_test_framework
crw------- 1 root      root         229,  12 1970-03-21 05:14 /dev/smdcnt_rev0
crw------- 1 root      root         229,  13 1970-03-21 05:14 /dev/smdcnt_rev1
crw------- 1 root      root         229,  14 1970-03-21 05:14 /dev/smdcnt_rev2
crw------- 1 root      root         229,  15 1970-03-21 05:14 /dev/smdcnt_rev3
crw------- 1 root      root         229,  16 1970-03-21 05:14 /dev/smdcnt_rev4
crw------- 1 root      root         229,  17 1970-03-21 05:14 /dev/smdcnt_rev5
crw------- 1 root      root         229,  18 1970-03-21 05:14 /dev/smdcnt_rev6
crw------- 1 root      root         229,  19 1970-03-21 05:14 /dev/smdcnt_rev7
crw------- 1 root      root         229,  20 1970-03-21 05:14 /dev/smdcnt_rev8
crw-r----- 1 radio     radio        229,   0 1970-03-21 05:14 /dev/smdcntl0
crw-r----- 1 radio     radio        229,   1 1970-03-21 05:14 /dev/smdcntl1
crw------- 1 root      root         229,   9 1970-03-21 05:14 /dev/smdcntl10
crw------- 1 root      root         229,  10 1970-03-21 05:14 /dev/smdcntl11
crw-r----- 1 radio     radio        229,   2 1970-03-21 05:14 /dev/smdcntl2
crw-r----- 1 radio     radio        229,   3 1970-03-21 05:14 /dev/smdcntl3
crw-r----- 1 radio     radio        229,   4 1970-03-21 05:14 /dev/smdcntl4
crw-r----- 1 radio     radio        229,   5 1970-03-21 05:14 /dev/smdcntl5
crw-r----- 1 radio     radio        229,   6 1970-03-21 05:14 /dev/smdcntl6
crw-r----- 1 radio     radio        229,   7 1970-03-21 05:14 /dev/smdcntl7
crw------- 1 root      root         229,  23 1970-03-21 05:14 /dev/smdcntl8
crw------- 1 root      root         229,   8 1970-03-21 05:14 /dev/smdcntl9

Did you figure out what device to use?

[jthawks]

clearwire site with new anntenas

 

Sent from my SM-N920P using Tapatalk

[mirskyc]

I'm connected to my local site with B25, the site also has B26. I use the note feature. Under more available signals a site with the name note pops up but with a weaker signal than the B25, could that be B41? or is it B25 from another sector so its weaker. normally a stronger signal shows up which is B26 when connected to B25, and a weaker B25 signal shows up when connected to B26. Don't know why that's not happening now. 

 

[nowerlater]

I'm connected to my local site with B25, the site also has B26. I use the note feature. Under more available signals a site with the name note pops up but with a weaker signal than the B25, could that be B41? or is it B25 from another sector so its weaker.

 

You would be correct. You are connected pci 339 and in the notes below it is seeing pci 170. So yes it's different sectors.

 

Sent from my SM-G928P using Tapatalk