Welcome
This is the forum where you give a shout out to the S4GRU forum and say that you have arrived!
150 topics in this forum
-
- 8 replies
- 1.5k views
-
- 7 replies
- 2.2k views
-
- 4 replies
- 1.7k views
-
- 12 replies
- 2k views
-
- 8 replies
- 1.2k views
-
- 2 replies
- 1.6k views
-
- 6 replies
- 1.3k views
-
- 3 replies
- 1.1k views
-
- 7 replies
- 1.3k views
-
- 3 replies
- 714 views
-
- 5 replies
- 730 views
-
- 3 replies
- 703 views
-
- 4 replies
- 577 views
-
- 2 replies
- 701 views
-
- 11 replies
- 1.1k views
-
- 4 replies
- 717 views
-
- 2 replies
- 651 views
-
- 1 reply
- 522 views
-
- 6 replies
- 904 views
-
- 3 replies
- 617 views
-
- 2 replies
- 794 views
-
- 1 reply
- 657 views
-
- 4 replies
- 842 views
-
- 0 replies
- 479 views
-
- 13 replies
- 1k views
-
-
New Topics
-
-
Recent Posts
-
Well you officially fried my brain. Many of these topics are well beyond my very rudimentary amateur knowledge.. this has my head spinning even more than usual. When someone figures it out, just let me know what I need to do with the app! 😂 -
By PedroDaGr8 · Posted
Confusingly, there are two different types of Cell IDs, the NR Cell ID (NCI) and the Local Cell ID, which I will call the LCID from here on out. From my understanding, @Trip is trying to get the LCID from the NCI but the same gNB is showing up for multiple sites in the app. Some background for those that don’t know about NCIs (NR Cell ID) and how they relate to gNBs and LCIDs. Just like the E/GCI which is comprised of the eNB + LCID with the eNB denoting the site, the NCI is comprised of the gNB + LCID with the gNB denoting the site. A major difference is that the eNB is a fixed number of bits in the E/GCI but the gNB can vary between 22-32 bits (out of 36) in the NCI and there is nothing transmitted which tells you what the length is. The reason for the mentioning LTE sites is that Verizon’s gNB numbering scheme in most of the USA is based upon the sites eNB (using the rules I mentioned) and a 22-bit gNB. Additionally, their LCIDs start at 25 and increment by compinations of 16 and 1. Basically, it is common to see LCID sets of 25/26/27, 41/42/43, and 57/58/59. Looking at Trip’s data and some other data from the area, they are not following the format used in the rest of the USA. From what I can tell, they are using a 29-bit or 30-bit gNB (that gives LCIDs that follow Verizon’s standard patterning). 29-bit shares the same gNB across the two locations, while 30-bit splits the two sets: 18504107674 - gNB 144563341 + CLID 26 (29-bit) or 289126682 + CLID 26 (30-bit) 18504107690 - gNB 144563341 + CLID 42 (29-bit) or 289126682 + CLID 42 (30-bit) 18504107691 - gNB 144563341 + CLID 43 (29-bit) or 289126682 + CLID 43 (30-bit) 18504107706 - gNB 144563341 + CLID 58 (29-bit) or 289126682 + CLID 58 (30-bit) 18504107707 - gNB 144563341 + CLID 59 (29-bit) or 289126682 + CLID 59 (30-bit) 18504107738 - gNB 144563341 + CLID 90 (29-bit) or 289126683 + CLID 26 (30-bit) 18504107739 - gNB 144563341 + CLID 91 (29-bit) or 289126683 + CLID 27 (30-bit) If true, this is a problem for SignalCheck and other mapping apps because this means they are using at least two different gNB lengths depending on the location in the USA. -
Yeah I can confirm that the status bar is updating correctly and as often as the main app! Great to have that back after so long. Waiting on the app to pick up the 5G data. I'm on AT&T and I find that it only reports the 5G signal data a fraction of the time. Once I can get it to pop back up I'll send a report with the LTE RSRP showing up in the status bar instead of the NR RSRP. I am not sure if it is new behavior with the Beta because I had it set to just show the Band since I couldn't display the band and signal at the same time. Edit: Sent a diagnostic and here's a screenshot:
-
-
Recently Browsing
- No registered users viewing this page.
