Jump to content

PedroDaGr8

S4GRU Sponsor
  • Posts

    713
  • Joined

  • Last visited

  • Days Won

    46

Posts posted by PedroDaGr8

  1. 14 hours ago, mikejeep said:

    When you say you "can see" those bands but "can't connect" do you mean you see them as neighbor cells? I'm not completely sure I understand what you're interpreting as seeing vs. connecting..

    Not as a neighboring cell, the information fully populates in SignalCheck (see image below), I just don't have a data connection. 

    9tTuYj3.jpg

    Furthermore, despite driving around for a while and seeing multiple n5-SA cells, nothing is available for upload 

    Also, I'm still investigating the gNB. I thought all the Cell IDs for SignalCheck we're consistent: 1049/1073/1097 for n5-SA, 1050/1074/1098 for n2-SA, and 1051/1075/1099 for n66-SA. Said above image also shows a two digit Cell ID. It appears this is also a set 25/49/73 which are n5-SA.

    If it helps, device is a Samsung Galaxy Note 20 Ultra running Android 11 (Nov. Security). I sent you a diagnostic report a week or so ago while seeing an AT&T cell. 

    Edit:

    So I ran some calculations and it appears that CellMapper is using 24-bit gNB for AT&T, while SignalCheck is using a 25-bit gNB. Not sure which is correct yet since I can't find a screen to show me said info (my radio data doesn't populate since switching to a TMo sim).

    Edit2: Actually, using more NCI data from CellMapper, I think both SignalCheck and CellMapper are calculating gNB wrong. Based on the NCIs I have access to, if you use 26-29bits to calculate the gNB then you get a very consistent pattern for the Cell IDs:

    n5: 25/49/73

    n2: 26/50/74

    n66: 27/51/75

    n78: 28/52/76

  2. 19 hours ago, RAvirani said:

    When you say don’t upload, what do you mean? Can you send me the file the app spits out on failure?

    There's no failure or error. Based on my testing today it appears that it never records the cells. I tested it today while driving around and despite seeing a dozen cells, nothing was recorded.

  3. On 12/30/2021 at 5:05 PM, PedroDaGr8 said:

    Hi Mike, a question about gNBs to which you don't connect? I noticed if I band lock my phone to n5 or n66, I can see AT&T n5-SA and n66-SA bands. I can't connect to them but I can see them in CellMapper and in SignalCheck. That being said the IDs are different, the CellMapper gNB appears to match the eNBs in the area a bit closer than SignalCheck does (the first digit is the same).

    Additionally, the Signal check results don't upload while the CellMapper results do.

     

    Ignore what I said about the gNB, yours seems to be more consistent than CellMapper when it comes to the Sector IDs. My guess is they don't have the right number of bits set for the gNB. That being said, the sites still don't upload.

    • Like 1
  4. Hi Mike, a question about gNBs to which you don't connect? I noticed if I band lock my phone to n5 or n66, I can see AT&T n5-SA and n66-SA bands. I can't connect to them but I can see them in CellMapper and in SignalCheck. That being said the IDs are different, the CellMapper gNB appears to match the eNBs in the area a bit closer than SignalCheck does (the first digit is the same).

    Additionally, the Signal check results don't upload while the CellMapper results do.

     

    • Like 1
  5. On 10/1/2021 at 7:55 AM, iansltx said:

    Yesterday Boost released the Celero 5G, made by WIngtech. Has a MTK Dimensity 700, a 6.5" screen, a big battery, and is $280 + tax including a year of unlimited Boost service. The current revision of the phone supports T-Mobile NR bands, precisely zero of which AT&T uses at the moment (unless AT&T is using n66 now and I missed it), and two of which (n66, n71) DishNet will use. There will be AT&T and DishNet specific versions of the Celero later.

    I took this opportunity to grab my dad a new phone...and this will move him back from US Mobile on VZW on a Moto e4+. If the phone works well, I'll get one for my brother before the intro deal expires, upgrading his Moto G fast. I'll grab the DishNet variant when it's available, assuming that'll be the first phone that can do n70 (I assume it'll be able to do n26 and n29 as well, but we shall see).

    FYI, if I lock my phone to n66, I can see AT&T n66-SA (same with n5-SA) but can't roam on it.

  6. Ok either some glitch in my phone cleared or they activated n41-SA on a bunch of towers for about 10min. I was heading home for lunch, forgetting I had my phone locked on n41 and suddenly  I'm getting it everywhere. Places it never worked before (like home). Now it's back to not working.

    Edit: And heading back towards Woodinville it started again but only for some towers. Very strange 

  7. On 9/2/2021 at 6:12 PM, mdob07 said:

    I just noticed, after the update SA N41 is missing now. It's just NSA N41 and SA/NSA N71. Wonder why they removed it. 🤦‍♂️

    FYI, it seems like the band listing in service mode is not accurate. My N20U has n41-SA missing as well but I just connected to n41-SA on a new tower that went live this morning. 

  8. 6 hours ago, mikejeep said:

    Sorry about this; I'm unable to replicate this issue, but it's certainly possible given the current state of things. I'm halfway through overhauling all of the file routines; when I'm done, my intent is to display the native Android file picker instead of the custom one in SCP. New Android security rules really limit what third-party apps have access to without explicit user input.

    I have a Samsung device (Android 11, November security update) and think I can replicate the issue. I'm not sure why but for some reason, I can't browse the ..\Android\data\folder from my phone; it just shows up as blank. This is true whether using the built in file browser or using SCP. The weird part: if I plug my phone into my computer then I can see all of the subfolders and files in ..\Android\data\

    As such, my work around is to manually move the files to a location which I CAN see.

     

     

  9. 14 hours ago, PedroDaGr8 said:

    Looks like the National Glass site went live broadcasting 311-490 PLMN and some strange split eNBs: 505921, 506063 for 4G and 4198118 for 5G. I'll investigate it more tomorrow to verify.

    Confirmed, B2/12/41/66/71 are on 505921 and B41 is on 506063. Have not seen this format of eNB in the Seattle area before. Usually when they split eNBs, it is because they have more than 3 sectors.

  10. 18 hours ago, RAvirani said:

    Oh boy. Let me see if I can pull the azimuths. 

    I'm interested to see what you figure out. That area and the 85th St. Kirkland exit are getting absurd with tower density.

    For others, came across the first Dish permit for the Woodinville area. Looks like they will colo on the AT&T tower.

     

    https://aca-prod.accela.com/WOODINVILLE/Cap/CapDetail.aspx?Module=Building&TabName=Building&capID1=BLD21&capID2=00000&capID3=00611&agencyCode=WOODINVILLE&IsToShowInspection=

  11. On 12/4/2021 at 8:36 PM, RAvirani said:

    The team down there might have done more planning before site builds or they may take a more ANR-focused approach when it comes to neighbor relations.  You'd be surprised how differently teams in different regions operate.  

    You would think they would have done extensive planning in advance when selecting to keep a site. Maybe that's being presumptuous.

  12. On 11/29/2021 at 10:21 AM, RAvirani said:

    I stopped by this site and was surprised to see that they disabled lowband carrier aggregation after the upgrade (midband was moved to the 300,000 offset eNB). I thought that site’s lowband and midband footprints almost entirely overlapped. 

    I wonder if they’re anticipating increased lowband load from n5 usage…

    I wouldn't be surprised if they intend to do similar to TMo with the low-band (b71 in TMos case) being the primary carrier and mid-band providing the high data throughout (n41 for TMo). 

    The warehouse district site is complete. I snapped some pics of the work in progress last week. Weather hasn't complied with snapping a final finished shot. 

    None of the conversion sites I have come across are live yet. I have no idea why because they are all 100% complete. Hope it's soon because a bunch of coworkers who are T-Mobile customers have been complaining about how bad the signal has gotten recently. It's essentially non-existent at the back of our Woodinville location.

     

×
×
  • Create New...