Jump to content
mikejeep

SignalCheck - Android app to monitor your 2G/3G/4G LTE signal strengths

Recommended Posts

56 minutes ago, Flompholph said:

Triband.

Triband antenas have been found where sprint puts what we guess could be their 4th carrier GCI ending. 

 

Didn't though they were doing that here.  So that's good

Share this post


Link to post
Share on other sites
5 minutes ago, jthawks said:

Didn't though they were doing that here.  So that's good

So should I investigate this? 

Share this post


Link to post
Share on other sites
51 minutes ago, jthawks said:

Didn't though they were doing that here.  So that's good

 

45 minutes ago, jthawks said:

So should I investigate this? 

This is standard second carrier for Samsung tri-band sites. As Denver is a Samsung market, it is to be expected.

Share this post


Link to post
Share on other sites
On 4/9/2018 at 4:25 PM, Dkoellerwx said:

This is standard second carrier for Samsung tri-band sites. As Denver is a Samsung market, it is to be expected.

I don't know if it's definitely the second carrier (that should be 03/04/05), but it is an additional carrier that varies by market.

-Mike

Share this post


Link to post
Share on other sites
6 minutes ago, mikejeep said:

I don't know if it's definitely the second carrier (that should be 03/04/05), but it is an additional carrier that varies by market.

-Mike

Based on the EARFCN and it's from the Denver area, it is the second carrier. As far as I've seen, that is the typical ending for a second carrier tri-band antenna site in a Samsung market?

Share this post


Link to post
Share on other sites

I have received a lot of messages over the past 3 weeks regarding improper LTE band identification for T-Mobile users. There is an Android bug that causes EARFCNs assigned to newer LTE bands (>46) to be reported incorrectly, such as Band 66 and Band 71. SignalCheck is showing Band 2/3/5/6/7/etc. because that is what the OS is reporting.

For more details, please see this bug report; I encourage everyone to 'star' it and/or adding your own report to try getting it more attention: https://issuetracker.google.com/issues/37136986

I am trying to implement a workaround that will at least help T-Mobile users until Android fixes the issue.

-Mike

 
  • Like 1

Share this post


Link to post
Share on other sites
2 minutes ago, Dkoellerwx said:

Based on the EARFCN and it's from the Denver area, it is the second carrier. As far as I've seen, that is the typical ending for a second carrier tri-band antenna site in a Samsung market?

I have Samsung B41 second carriers as 03/04/05, but perhaps things changed? The "TB" indicator was implemented (and has been discussed a few times) because it wasn't consistently deployed as a specific carrier.

-Mike

Share this post


Link to post
Share on other sites
2 minutes ago, mikejeep said:

I have Samsung B41 second carriers as 03/04/05, but perhaps things changed? The "TB" indicator was implemented (and has been discussed a few times) because it wasn't consistently deployed as a specific carrier.

-Mike

Yes, on a normal 8T8R site, 03/04/05 is the normal second carrier. On 4T4R tri-band antennas in Samsung markets, 09/0A/0B has been used fairly regularly. I do not know off the top of my head what is done with the 3rd carrier on the tri-band antenna sites (normal 8T8R being 06/07/08, which is already covered).

Share this post


Link to post
Share on other sites

Mike,

1) As indicated previously, in my area (DC) which I believe is a Samsung Clear market, 03/04/05 are third carrier, but SCP currently doesn't note it as anything other than standard B41.

2) Yesterday, I finally managed to send you diagnostics showing "LTE" without a band indicator while connected to a Clear site.  I sent it having watched it not have a band indicator for more than 30 seconds.  Hopefully you got it and maybe it'll tell you something you didn't already know about the issue.

3) I don't yet have a B71 phone, though once a cheap Motorola one comes out, I plan to replace my T-Mobile 700 phone with one.  What kind of work-around are you considering?  Perhaps it could make sense to allow people to select which bands their phone actually supports or which bands they expect to see so you could work around obviously-incorrect data, even if it were in some kind of hidden menu.  (In my ideal world, there would be a hidden menu with lots of advanced functions to tweak the behavior of SCP in ways the average user may find unhelpful or confusing.  Like forcing all LTE to be identified as LTE 700 on my phone that is locked to 700.)

4) Is there any chance you could add a third mode to the neighbor cell notes beyond matching to PLMN and not matching to PLMN?  I'd like to merge my four SCP databases together (Verizon, AT&T, T-Mobile, and Sprint/USCC) but if I do that, then on my Sprint/USCC phones with the PLMN matching disabled, I'll get a bunch of neighbor cell notes that are clearly not correct since they'll match non-Sprint values.  And, of course, if I enable PLMN matching, then if I'm on Sprint, I'll miss Clear notes, etc.  It would be nice if there were a "Sprint" mode that matched only to PLMNs associated with Sprint when connected to a Sprint-associated network.  For example, if connected to PLMN 310120, have it match also PCI values for 311870 and other Clear PLMNs, but not to other PLMNs.  Or if connected to 311870, match to 310120, etc.

- Trip

Share this post


Link to post
Share on other sites



Yes, on a normal 8T8R site, 03/04/05 is the normal second carrier. On 4T4R tri-band antennas in Samsung markets, 09/0A/0B has been used fairly regularly. I do not know off the top of my head what is done with the 3rd carrier on the tri-band antenna sites (normal 8T8R being 06/07/08, which is already covered).


Third carrier on triband sites (that use triband endings) has second carrier GCI endings. So:

Non-triband:
2nd carrier - 03, 04, 05
3rd carrier - 06, 07, 08

Triband:
2nd carrier - 09, 0A, 0B
3rd carrier - 03, 04, 05

I define second carrier as the middle earfcn, and third carrier as the highest earfcn.

Sent from my Pixel 2 XL using Tapatalk

  • Like 2

Share this post


Link to post
Share on other sites
On 4/11/2018 at 9:14 PM, Trip said:

1) As indicated previously, in my area (DC) which I believe is a Samsung Clear market, 03/04/05 are third carrier, but SCP currently doesn't note it as anything other than standard B41.

2) Yesterday, I finally managed to send you diagnostics showing "LTE" without a band indicator while connected to a Clear site.  I sent it having watched it not have a band indicator for more than 30 seconds.  Hopefully you got it and maybe it'll tell you something you didn't already know about the issue.

03/04/05 are coded as third carrier, and your report showed sector 00 which should have showed you regular B41. You are likely getting victimized by the bug that has been driving me insane for a couple of years where things go south when the PLMN changes on the fly. Some devices suffer more than others. Essentially the band stops appearing until the PLMN changes again.. something is getting hung up momentarily on the OS side, and SCP chokes on it. It's related to the glitch that causes the PLMN and GCI to fall out of sync when switching cells, which also wreaks havoc and creates duplicate (bogus) database entries. It's maddening and I have tried all sorts of hacks i in the background to address it -- and I will continue to try, because it's a priority.

 

On 4/11/2018 at 9:14 PM, Trip said:

3) I don't yet have a B71 phone, though once a cheap Motorola one comes out, I plan to replace my T-Mobile 700 phone with one.  What kind of work-around are you considering?  Perhaps it could make sense to allow people to select which bands their phone actually supports or which bands they expect to see so you could work around obviously-incorrect data, even if it were in some kind of hidden menu.  (In my ideal world, there would be a hidden menu with lots of advanced functions to tweak the behavior of SCP in ways the average user may find unhelpful or confusing.  Like forcing all LTE to be identified as LTE 700 on my phone that is locked to 700.)

I'm hoping to keep it simple.. essentially by checking if it's a T-Mobile connection, and if so, checking if it's a band that T-Mobile actually uses. If not, assume it's a glitch and add 65536 to the EARFCN. I've spent the past few weeks trying to bring SignalCheck Lite up to speed and I have to finish that first, but it's not going well since it's been 3 years since that was updated and a lot has changed since then.

 

On 4/11/2018 at 9:14 PM, Trip said:

4) Is there any chance you could add a third mode to the neighbor cell notes beyond matching to PLMN and not matching to PLMN?  I'd like to merge my four SCP databases together (Verizon, AT&T, T-Mobile, and Sprint/USCC) but if I do that, then on my Sprint/USCC phones with the PLMN matching disabled, I'll get a bunch of neighbor cell notes that are clearly not correct since they'll match non-Sprint values.  And, of course, if I enable PLMN matching, then if I'm on Sprint, I'll miss Clear notes, etc.  It would be nice if there were a "Sprint" mode that matched only to PLMNs associated with Sprint when connected to a Sprint-associated network.  For example, if connected to PLMN 310120, have it match also PCI values for 311870 and other Clear PLMNs, but not to other PLMNs.  Or if connected to 311870, match to 310120, etc.

Hmm, that's an interesting thought. It would only make sense for Sprint, since most other major providers stick with one PLMN.. I'll look into seeing how feasible that is. What device do you see Clear neighbors when connected to Sprint, and vice versa? My Pixel doesn't do that.

-Mike

  • Like 1

Share this post


Link to post
Share on other sites
On 4/15/2018 at 8:31 PM, mikejeep said:

03/04/05 are coded as third carrier, and your report showed sector 00 which should have showed you regular B41. You are likely getting victimized by the bug that has been driving me insane for a couple of years where things go south when the PLMN changes on the fly. Some devices suffer more than others. Essentially the band stops appearing until the PLMN changes again.. something is getting hung up momentarily on the OS side, and SCP chokes on it. It's related to the glitch that causes the PLMN and GCI to fall out of sync when switching cells, which also wreaks havoc and creates duplicate (bogus) database entries. It's maddening and I have tried all sorts of hacks i in the background to address it -- and I will continue to try, because it's a priority.

 

I'm hoping to keep it simple.. essentially by checking if it's a T-Mobile connection, and if so, checking if it's a band that T-Mobile actually uses. If not, assume it's a glitch and add 65536 to the EARFCN. I've spent the past few weeks trying to bring SignalCheck Lite up to speed and I have to finish that first, but it's not going well since it's been 3 years since that was updated and a lot has changed since then.

 

Hmm, that's an interesting thought. It would only make sense for Sprint, since most other major providers stick with one PLMN.. I'll look into seeing how feasible that is. What device do you see Clear neighbors when connected to Sprint, and vice versa? My Pixel doesn't do that.

-Mike

Mike,

I didn't mean to conflate the first two items.  In the first, when I'm connected to Clear B41 third carrier on sectors 03/04/05, I'm not seeing the "3" next to it.  That's what I was trying to say.  I would love if this could be corrected, since it's hopefully a small change.  I'll try to send you a diagnostic showing it, but here's a picture from my log:  https://imgur.com/a/7zw72

I separately sent you the data on the missing band indicator because you said it was causing you a problem that you were having trouble tracking down, but I had been unable to send you diagnostic data on it previously.  I finally tried and successfully sent you the data without getting an error message.  I was hoping it helped you track down the issue, as it was sitting there for a very long time with no band indicator.  Same thing happened yesterday, actually, on a different site.  In that case, it lasted for a long time, measured in minutes.

Sounds like an interesting fix, though I suspect you'll have some Band 66/Band 2 overlap.  For example, if T-Mobile held AWS-1 A-block, that would be EARFCN 66586, and 66586-65536=1050, a valid Band 2 EARFCN.  Not sure what you would do about that.

Yes, I agree it would have to be Sprint-only.  I think most of the phones I've had since moving to Sprint would show Clear and Sprint B41 in neighbor cells at the same time.  (LG G6, LG G5, Samsung S5.)  They do/did not, however, show PCI values for US Cellular or other networks.  I'll confirm and let you know for certain.

- Trip

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Trip said:

Yes, I agree it would have to be Sprint-only.  I think most of the phones I've had since moving to Sprint would show Clear and Sprint B41 in neighbor cells at the same time.  (LG G6, LG G5, Samsung S5.)  They do/did not, however, show PCI values for US Cellular or other networks.  I'll confirm and let you know for certain.

Mike,

Confirmed via picture.  https://imgur.com/a/ZWewf  I'm connected to a Clear site with two 8T8R sites appearing in the neighbor cells.  Couldn't get diagnostics before it dropped back to B26 on the DAS though.  I'm in too much pain to walk back to the window and try again for diagnostics.

- Trip

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

    • By lilotimz
      Ericsson RRUS31 B25 + RRUS11 B26
      These are the newest and greatest remote radio units to come from Ericsson. 

      The new Ericsson RRUS31  B25 should be fairly distinctive compared to the earlier RRUS11s and now the RRUS12s being deployed by ATT and Verizon. One of these new RRUS31s can do the job of two earlier RRUS11s thus reducing deployment costs for Sprint and complexity in deploying new sites and making it easier for users to spot as there are now 4 jumpers coming out of one RRUS31 rather than two from each RRUS11 that Ericsson originally deployed. 

      All future deployments will be utilizing the new Ericsson RRUS31s. In addition Ericsson are sending crews to their original deployments and swapping out older RRUS11s for these new RRUS31s due to the aforementioned fact that one RRUS31 can do the job of 2 RRUS11s. Weight savings will be significant at sites where there are 4 or 5 RRUS11 B25s that can be replaced by one or 2 RRUS31s. The Ericsson RRUS31 deployment project is known as the 65 Mhz Project. 

       

      Ericsson RRUS11 B26 top and RRUS31 B25 bottom

       

       
      Ericsson High Capacity / 4x4/2 MIMO Deployment
      Note the additional antenna + PCS radio.
      Previously Ericsson utilized additional PCS radios and used RF combiners for high capacity setups where they utilized three or more PCS radios. This new setup will utilize a completey new antenna + radio set just like Samsung and run 4x2 MIMO on the LTE antenna / radio set. 
       

       

       

       
      Ericsson RRUS11 B25 [EOL'd] and B26
      A standard Ericsson Network Vision 1.0 site with 3 RRUS11s where two are dedicated to PCS and one to SMR.  

      This type of setup is no longer deployed or utilized in new sites. Existing sites will be slowly converted to newer RRUS31 B25 via the Sprint 65 mhz project. 


       
      Ericsson NV high capacity site [EOL'd]
      3 or 4 PCS RRUs are present for a total of 4 or 5 RRUS11s per antenna. 


       

       

       
      Close up of Antennas
       

       
      Ericsson cabinets 
      (center)



      All credit to those who took the photographs. They know who they are!
       
    • By danlodish345
      Hey guys I found another newsletter about Sprint and Cox. I'll be posting the article here.
      http://www.kansascity.com/news/business/technology/article195339874.html
    • By Handyman
      Just installed the 8.1 update on my Pixel.  Still no Sprint Wi-Fi / LTE calling
       
      But ... I did get the mandatory Google Search button added to my launcher.
       
    • By lilotimz
      Here are the Alcatel-Lucent (ALU) Network Vision equipment for Sprint. Their equipment consists of 2x base stations, 6 or 9 Remote Radio Unit (RRU) setups, and 1 standard NV antenna of with connectors on the bottom (4x PCS, 2x SMR). 

      Below are images of Alcatel-Lucent equipment. In these images, you will find Alcatel-Lucent base stations, Sprint Network Vision antennas, PCS 1900 & SMR 800 RRUs, and their configurations.
      Alcatel-Lucent 4x40w 25 MHz PCS 1900 B25 RRUs (Panasonic) [old]

      Alcatel-Lucent  4x45w 1900 MHz B25 RRU 

      ALU 2x50w B26 800 MHz RRU [KMW Communications]

      Older Panasonic Setup [4x40w 25 MHz B25]




      Standard Alcatel-Lucent Setup 
      Utilizes 2x50w 800 MHz B26 RRU and 4x45w 1900 MHz B25 RRU and compatible antennas. 



      Closer Look at the connectors on the bottom of the antennas

      Special Case Mexican IBEZ Setup
      Note the lack of 800 MHz RRUs though the antennas are capable of 800 MHz. 


      High Capacity Setup


      High Capacity no SMR 800 IBEZ setup


      * Credits go to those whom took the images of these equipment. You know who you are."
    • By danlodish345
      hello everyone i m starting a thread for sprint network predictions for 2018. i am wishing sprint and s4gru a happy holidays and new years. 
       
      regards Daniel
  • Posts

    • I started working on the Raspberry Pi 3b Plus tonight with an Sierra Wireless em7565. This one has all those cool features that I was describing up top. Not bad for ~39 bucks. I was waiting for a few open source firmwares to get through the compilebot6k's toobs; this one is built now. Some use modem manager or openWRT for the router side. This LTE radio is band(s) 2/26/41 capable on the Sprint side. Band 25 did not make the cut, but was on previous Sierra builds. This is a tester radio so there is a slight chance it will appear down the road. It has just about every other LTE band.  

      This is an example of the debug screen. GMO is nearest so we only get 26 from a far site. No 41 in our zip yet. 
      The best part is I can plug an MC7455(that would be Modem#2) or another EM7565 in and it can hop over to that or I can direct load balancing. I just wanted to show the EM7565 authenticated below. Another shot of my terrible reception. Here it is out of the armor.

      So, we have a stable software image. I will get it built and add some GPS features, then test on band 41 in Myrtle where present. We have one site w 8t8r gear to test 3xCA on, so it might be a minute. I am in 2xCA MM areas through the week. I will see how it likes the Magic box too. 

      I should have a true GB ethernet router to massacre in the next couple of weeks with software images already set to go. I can embed the radio beyond a USB adapter. It still requires m.2>mPCIe but that is one less failure point and better throughput. This was a great breakthrough in affordable and small solutions for us.  I have to go to bed and then work now.

      Have a great week everyone.
    • Thank you so much for bringing light to this! I would have never known about it had you not posted it! You've saved me a lot of money and lowered my bill moving forward! It wasn't an easy process, but well worth it. Unlocking the phones was surprisingly easy. But the small hiccup came with my final bill. When I received it, I thought I was screwed when I saw that the ETF was included. I almost paid for it too, but the frugal in me decided to call Sprint (couldn't hurt, right?). After an hour on the phone with a US supervisor, my account was credited for the full amount of the ETFs. I walked away Scot-free!! Thanks a bunch OP! I'm trying Verizon's throttled unlimited data plan. Excellent reliability in the city, but there are certain key spots where I need my phone that aren't great. I don't know if it's the throttling or the network.
    • I see more mass upgrades by TMO on 600mhz -- it seems they did an amazing and fast roll out. If I recall folks here thougt TMO wouldn't be able to see much strides for a year plus.

      Reason I bring it up is TMO can't have much more free cash than Sprint. Yet can operate fast and lean.

      Positive note Sprint has rocked it's upgrades this past year...

      Sent from my XT1635-02 using Tapatalk

  • Recently Browsing

    No registered users viewing this page.

×