Jump to content

jasonsteele

Honored Premier Sponsor
  • Posts

    323
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by jasonsteele

  1. On 11/8/2023 at 12:54 PM, mikejeep said:

    If you are still experiencing this issue, could you please send a diagnostic report (from within the app, select Help > Send Diagostics) and include a brief note about the issue so I can dig into it further? Thanks!

    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.

    • Sad 1
  2. 3 hours ago, mikejeep said:

    Hmm.. my primary daily device is a Pixel 8 (and was a Pixel 7 for the year prior) and I have not seen this. Do you have any sort of memory optimization app running? Do you have timestamps enabled for the individual network types (not at the very top of the screen, but within each "block" of signal information) and are they updating at all?

    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.

    • Like 1
    • Thanks 1
  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. 

    • Confused 1
  4. 2 hours ago, Trip said:

    They're running B26 on a handful of protection sites, essentially.  I'm not sure that they don't need extra equipment to pull that off.  I've only confirmed four T-Mobile sites running B26 total.

    - Trip

    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. 3 hours ago, Paynefanbro said:

    I wonder if the toggle will allow you to permanently be in standalone mode or if it's just a switch that lets the network put you in standalone when necessary but still prefers NSA.

    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.

    • Like 4
    • Thanks 1
  6. 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.

  7. 1 hour ago, Paynefanbro said:

    Recently I've been confirming the location of a lot of the split eNBs in Cellmapper along with locating unconfirmed sites and one thing I've noticed is that T-Mobile seems to have some sort of deal with PSEG (the ConEd of Long Island) to put up towers at their substations. The towers are always wooden poles with one set of 2/66 antennas. My guess is that T-Mobile is in no rush to upgrade these towers or they won't get 5G until they start deploying n66 here.

    Some good examples are:

    eNB 45864: https://goo.gl/maps/eCAMm6TrH29tiEr5A

    eNB 45861: https://goo.gl/maps/Ci7rddeezcwa33jq5

    eNB 49541: https://goo.gl/maps/47YMWeXECuMMzb92A

    eNB 50419: https://goo.gl/maps/U41aS2UptSr9stFc6

    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.

    • Like 1
  8. 11 hours ago, Dkoellerwx said:

    That was the same window on my dad's S21, but got notice that it was going to ship last night, arrived here this afternoon. Hoping they get it out to you soon!

     

    11 hours ago, PythonFanPA said:

    Same here, was originally at order time slated to be 2-3 weeks out before even available (and mine's a 256gb version), next thing I know a shipment notification came in email later that night and it was on my doorstep the next day.

    Just got notified it will be here Monday. Yippee!

    • Like 2
  9. 15 minutes ago, Dkoellerwx said:

    Got my dad's S21 activated today. Seems like a pretty good device, and he's happy to have a new phone instead of a second-hand one from me ha.

    Still waiting on the Ultra. Going on 20 days since the order. No estimated shipping date...

    Ordered my S21 two weeks ago, says shipping between 4/30 and 5/12. Not holding my breath.

  10. 4 minutes ago, Dkoellerwx said:

    Fully modernized T-Mobile site colocated with Sprint in Denver, CO. 694Mbps with 80Mhz of N41. Not bad.

     

    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.

  11. 58 minutes ago, mikejeep said:

    Interesting.. the location is provided by an API that shares device location information between all apps that request it. What are your location settings in SignalCheck? Did you happen to try opening another app that uses location features (Google Maps, Waze, etc) when you were having that issue?

     

    9 minutes ago, mikejeep said:

    Thinking a little more about this -- the geocoding feature that translates coordinates to a street address is separate from the actual location service that gets the coordinates. There are limits on geocoding requests (the specifics are not published), but I had never run into them and I expect if that was the issue, it would display an error instead of an address.

    Having one address constantly returned makes me think your coordinates are not changing, so the geocoder is working but not getting any new information. If it happens to pop up again, and you have the coordinates displayed on the main screen, try driving around to see if they change or if they are frozen.

    There are some minor improvements coming to the location service in the next update; not sure if it would be something that corrected an issue like this though.

    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.

    • Like 1
  12. 3 hours ago, superbluepsd said:

    Lower Sprint B41 carrier is gone here in the Portland market as well.    The remaining 2 B41 carriers have also been moved up higher to 2660 and 2680 Mhz.   

    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+.

  13. 48 minutes ago, Dkoellerwx said:

    Noticed that yesterday I was handing off to a local Sprint site instead of sitting on T-Mobile, and it seemed seamless. Checked and it was 250. Very interesting to see.

    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.

  14. 2 hours ago, shaferz said:

    How do you know if your home Sprint site is a keep site?

     

    2 hours ago, stlman314 said:

    I believe it is based on the plmn showing 250

    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.

    • Like 1
×
×
  • Create New...