Jump to content

PedroDaGr8

S4GRU Sponsor
 View Profile  See their activity

  • Posts

    684

  • Joined

  • Last visited

  • Days Won

    39

 Content Type 

Everything posted by PedroDaGr8

  1. PedroDaGr8
    New PCS/AWS Spectrum swaps between T-Mobile and AT&T posted over at Reddit:
  2. PedroDaGr8
    January play system update is out.
  3. PedroDaGr8
    New Dish permit plans showing them using Samsung Radios for n26, n29, n66, n70, and n71:
  4. PedroDaGr8
    I posted a link in the NYC thread on how you can enable it.
  5. PedroDaGr8
    You may be able to enable it. This link is for the S22 but the process is the same for most Samsung models: https://forum.xda-developers.com/t/how-to-enable-all-bands-through-service-menu-on-us-ca-s22-series-including-sub-6-and-mmwave.4488435/
  6. PedroDaGr8
    Seeing similar speed drops. Towers that used to be 600+ any time of day are now 300-400.
  7. PedroDaGr8
    That actually would make a lot of sense! Oly reason I have seen that does make sense.
  8. PedroDaGr8
    I seem to remember that AT&T got permission to temporarily use some of Verizon's spectrum in some areas. Unfortunately, I can't find any direct articles due to all of the other "noise" around C-Band.
  9. PedroDaGr8
    By the way Mike, I have noticed that the map and the app report different gNBs for Verizon NR. From the map, it looks like Verizon is using 22-bit gNBs while the app is using a different value. You might want to work with @RAviranito get on the same page.
  10. PedroDaGr8
    Weird, two of the DEMO three permits (the Bridle Trails one and this one) have been withdrawn. Only the Mark Twain water tower one remains. Doesn't mean they aren't planning to demo them, maybe just not at this time (or they just plan to leave them). Still will be curious what, if anything, you find out about whether they do intend to upgrade that site or not.
  11. PedroDaGr8
    Yeah, that area is atrocious (especially up by the interstate where this would have helped the most. Thanks for looking into this. I look forward to hearing what you might find out.
  12. PedroDaGr8
    Wow, I love those images! My only thoughts are 1. They just don't care about that area for some reason. 2. This is a formality that is for some reason required due to the level of changes they are doing. 3. It has something to do with [this permit](https://permitsearch.mybuildingpermit.com/PermitDetails/PUB22-08613/Kirkland) which mentions servicing the the Kirkland Urban site. There are no other permits
  13. PedroDaGr8
    Weird, I just went to check the version number and there was a SECOND update available but still November 1, 2022 date. That's the Google Play Store, not the same as the Google Play System (despite the similar name). To update Google Play System, go to Settings--> About Phone -->Software information-->Google Play System update It should check for the update and restart if necessary.
  14. PedroDaGr8
    For the first time in forever, I just got a Google Play Sysyem Update. Brings the Play System Version up to November.
  15. PedroDaGr8
    A few more demo permits: That weird Sprint B25 only site near the tall tower in Bridle Trails: Image, Permit Mark Twain Water Tower by LWIT. This one is on the tower, as opposed to T-Mobile which is on the adjacent tower: Permit This one is weird, the Sprint site by 85th and I-405 which T-Mobile previously was going to convert now has a Demo permit. Not sure if they cancelled the conversion or what (@RAvirani any thoughts?): Permit
  16. PedroDaGr8
    Did you/she turn off battery optimizations for SCP? Samsung has really aggressive battery optimizations for background processes. If you don't turn it off, then the app won't log points like normal.
  17. PedroDaGr8
    Per someone over on Reddit: Android reports the ARFCN for the SSB of the NR channel. Unlike LTE which had this at the center, it can be any value within the frequency range of the channel for NR. I guess T-Mo is using a non-standard SSB location for some reason. This is really unfortunate because it means the recorded values for n41 are totally wrong.
  18. PedroDaGr8
    So, I posted a while back about it appearing like the two n41 carriers in my area were overlapping I now think that in some cases, the phone is actually posting totally wrong values for the ARFCN. I was looking at some screenshots I took of the 0011 menu while on a trip earlier this month. Two of them include ARFCN/BW combos which are 100% impossible. For example, this one: That NR ARFCN corresponds to center frequency of 2506.95 MHz with a BW of 100MHz. This would mean the n41 signal would range from 2456.95 MHz to 2556.95MHz. This is impossible because Band 41 only goes down to 2496 MHz. Not sure if this is a Qualcomm bug or a Samsung bug but it is very clearly in error. That or T-Mobile is violating loads of FCC regulations and the phone is totally ignoring an out-of-band signal at the same time. Also, I don't know if this issue is limited to n41 or exists in other frequency bands as well but this is very unnerving either way.
  19. PedroDaGr8
    As I am sure you know, the Field Test app on iPhone is FAR from reliable. If iPhone works the same as Android, if you see 5GUC in your notification bar then you are connected to n41.
  20. PedroDaGr8
    I was commenting about back before I knew about that method. I've fully unlocked the bands on my s22.
  21. PedroDaGr8
    That's pretty impressive! T-Mobile is so horribly backhaul limited in most areas. I really wish they would get to upgrading back haul on a bunch of their urban/suburban sites.
  22. PedroDaGr8
    This has been something I noticed a while back when n41-SA was rolling out. Just because a band doesn't show up in *#2263# doesn't mean the phone can't connect to it.
  23. PedroDaGr8
    Seems like it was saved but didn't send. Sent it and a new one now.
  24. PedroDaGr8
    Already did when I first saw it.
  25. PedroDaGr8
    SignalCheck was reporting n25-SA properly. The diagnostics screen shows "mBands = [2]" As an aside, I decided to test out n2 to see if that is what AT&T n2-SA reports. The diagnostic screen also shows "mBands = [2]". That being said, whatever you did to fix the issue with the reporting of bands now causes AT&T to report n25-SA instead of n2-SA.
×
×
  • Create New...