Jump to content

jasonsteele

Honored Premier Sponsor
  • Posts

    323
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jasonsteele

  1. Hey Mike, after the new update I'm still showing stale data and timestamp. I have more observations as noted below on my Pixel 8: - I made a mistake, the timestamps at the top are stale just like the timestamps on band info. I was actually looking at the GPS timestamp, which refresh about every 3 or 4 seconds. - The issue does not manifest when stationary and the GPS isn't refreshing (i.e. stopped at a traffic light) . It only persists when in motion. The second I stop the data and timestamp refreshes every 3 or 4 seconds. - The issue seems to be more pronounced when on an NR-SA connection, anywhere from 1 to 12 minutes delay. - When on an NSA or LTE only connection, the delay seems to be a lot less...mostly refreshes every 4 to 15 seconds, but as long as 90 seconds. - I have a Galaxy S22 on AT&T and don't have these issues at all. Timestamp and data refreshes every 3 or 4 seconds. Haven't encountered any SA on AT&T yet so I can't compare.
  2. Timestamps for individual network types are frozen for anywhere from five to fifteen minutes, timestamps at top refresh every four seconds when I'm moving and every ten seconds when I'm stationary. I have no memory optimization used. I went through and changed a few settings: battery usage to "unrestricted", toggled modify system settings to "allowed", toggled unrestricted data usage to "on". I also just turned off adaptive connectivity. All permissions are allowed. Will test on my next drive.
  3. Not sure if this has already been discussed, but I have a Pixel 8 and it seems band info is slow to refresh. On my commute, the time, date and GPS will refresh every 4 seconds. Band info below it takes between 1 and 10 minutes to refresh and just seems to be stuck even though I've traveled miles and passed multiple towers. I owned a Pixel 7 previously that had the same issue, and my S22 seems fine. When I'm stationary, the issue does not seem to exist.
  4. I'm in Phoenix, seems like all of the very few Sprint sites left that are not converted or decommissioned are broadcasting B26. There is one of them about a mile and a half from my house, once every month or two between 9pm and midnight the T-Mo site two blocks away goes down and the Sprint B26 is all that works.
  5. Updated my AT&T S22 last night, NR bands show up now. https://imgur.com/a/qEZh0dN
  6. I tried it today on my 13PM, seems to be permanent SA mode when toggled. On my 32 mile commute, only saw UC barely a third of the time even though when on NSA it’s pretty much 100% of the time. Seemed to prefer n71, even though nearly every upgraded tower has n41. Can’t confirm because field test seems permanently borked. There are three B2/66 only towers along the commute it would not connect to, connecting to the next closest upgraded towers…therefore buffering my music streaming. Turned it off for now.
  7. AT&T finally starting to build n77 in Phoenix, a few towers already have have the dual antenna setup with DoD. Was able to get 10 MHz B30, 40 MHz n77 and 20 MHz B2 in my living room. Verizon has quite the headstart here though. https://imgur.com/a/dCEUJa5
  8. I can confirm band locking works using the Samsung Band Selection app on my AT&T S22.
  9. I think somebody just didn’t do their homework and missed/mixed everything up. There’s no reason n77 C-band, n77 DOD and n258 wouldn’t be there and enabled IMO. These will be crucial bands for T-Mo going forward for extra capacity, especially when dumb and dumber really get rolling. Maybe waiting to list and enable until after deployment begins.
  10. Beta 3 is live, new UC indicator has been added.
  11. Strange, because I have an S21 running the OneUI 4 beta with SCP beta and never had an issue. Could it be a market issue? I’m in Phoenix.
  12. A lot of those in my area (burbs of Phoenix), except the poles are steel and carry power lines. They put them on top like a finial. There are a lot of flagpoles too, I don’t see how they can squeeze a n71 antenna on/in them or even a n41 antenna. I’ll take n66 though, might have to wait awhile. Full builds are spaced way apart around here and these just seem like infill.
  13. Just got notified it will be here Monday. Yippee!
  14. Ordered my S21 two weeks ago, says shipping between 4/30 and 5/12. Not holding my breath.
  15. That’s what they’re doing in Phoenix to all the sites that can handle all that equipment. I wonder what they are going to do with flagpole sites and the small cap assemblies they put on metal power transmission poles. Those are usually only B66 because they are so skinny. I guess we will see, awful lot of those here in the suburbs for aesthetic reasons.
  16. Waze was running during the issues. I let it go for two days before I rebooted. Once done, no more issues. SCP location service at high accuracy, update interval 4000. So far so good, it was the first reboot after Android 11 update...I’m not that technical, maybe the phone was stuck on stupid and had to reset.
  17. PSA, after installing the Android 11 update last week on my S10+, SCP beta was giving me my actual home address every time I clicked “here” to get locations for notes (no matter where I was). A reboot fixed that.
  18. So far still three carriers in Phoenix, Sprint is at 2640, 2660 and 2680 for B41. Seems like only 2xCA as well. T-Mobile is at 2538 and 2558 for B41. I’m guessing everything in between is for n41, can’t tell for sure on my iPhone 12 because Field Test Mode is hot garbage and my other phone is an S10+.
  19. Good eye, I didn't catch that. If you look again, the date is also 14 days off. Darn, I thought I had discovered some cool stuff.
  20. Seems like one B41 20 MHz carrier from my Sprint keep site is being used as anchor band for NSA. https://imgur.com/gallery/XeyBty3
  21. SCP showing 310-120 but engineering screen showing serving PLMN as 312-250 and HPLMN as 312-530.
  22. Strange thing is I have an iPhone 12 and an S10+ both on ROAMAHOME. The PLMN on the iPhone 12 is 312-250 and the S10+ it’s 310-120. In the same spot, they’re both connected to the same Sprint tower but using different EARFCNs 41094 and 41292. Not sure what that means.
  23. Yep, PLMN 312-250 is handing off from 310-260 natively, without loss of coverage. That means it’s a keep site. Makes sense for my Sprint home site, as it is the fourth corner in a square of the nearest three T-Mo sites around me.
  24. My home Sprint site is a keep site! I’m on ROAMAHOME, been over a month since I’ve connected to it. I’m so relieved, it’s going to fill in a gap nicely. https://imgur.com/gallery/1uOQRhe
×
×
  • Create New...