Jump to content

Trip

S4GRU Staff
  • Posts

    2,274
  • Joined

  • Last visited

  • Days Won

    88

Posts posted by Trip

  1. The map has been updated and shows new B41 in Charlottesville.  Hard to tell with certainty which tower or towers it is, but it appears to be some combination of the T-Mobile site at the Darden School, the T-Mobile power line site behind La Quinta, the Shentel site at Barracks Road Shopping Center, and the Shentel site where Rose Hill meets Westwood.

    I also note that they show the Lake Louisa tower, which previously had only 600/700, as now running B41.  That is rather unexpected.  I note the "Personal" map does not indicate the presence of AWS or PCS there yet.

    In a different part of the Shentel region, I spent much of the past week in and around Luray, and saw the Luray B41 before it appeared on the map.  Also verified a number of B41 sites in and around Harrisonburg, as well as the ones in Front Royal and Strasburg.

    - Trip

    • Like 3
  2. I don't anticipate returning for a long time.  I made that trip specifically because there was otherwise no reason for me to ever go there.

    I can clearly see some bad points on a number of sites.  I've located some (not all) of them, particularly in/near Luray, Front Royal, and Strasburg.  Up to you what you want to do with them.  I can make edits which I'm capable of making, or you can make changes as you see fit.  Whichever.  I'm fine either way.

    - Trip

  3. So this is bizarre, and I'm not really sure what to say about it or how it could have even happened.

    My AT&T phone (FreedomPop) is a rooted Pixel 3a.  Somehow, it appears that in both the trail log and the site log, the GPS somehow lagged the cells yesterday.  I noticed it because we went through Detrick, VA.  On my new S21FE, the logs are correct.  I see Shentel's 0FE18Fxx at Detrick, as expected.  Meanwhile, AT&T is on that same tower.  It got recorded with correct TA numbers, but coordinates that were probably 20-30 minutes out of date.  They clearly follow the route that we took, and are even spaced correctly from what I can tell, but they're just clearly mismatched.

    I salvaged the data by using the timestamps to match with my S21FE logs, and used those coordinates to locate anything I had issues with, so I didn't lose anything personally, but you can see the incorrect locations on the SignalCheck Map site.  Look at AT&T LTE, 09FB11, and you'll see that the 0x10 and 0x11 sectors are placed very wrongly, while the 0x0F sector as a few points that are right only because one of my other phones managed to connect to it by accident along the way.

    It looks like others were impacted too; that's just the one that's most obvious.  I didn't notice it along the way because I had my dashboard phone holders dedicated to various T-Mobile devices, and my AT&T phone was out of my line of sight.

    Later in the log, things appear to be correct again.  Utterly bizarre.  Any thoughts?

    - Trip

    • Confused 1
  4. So I just, uh, sidegraded? I guess? to a Samsung S21 FE.  Certainly not an upgrade, but it's fine, I suppose.  Biggest winning feature: I can now band lock my primary phone.  Biggest losing feature?  Can't decide.  No SD card slot, no headphone jack, can't double-tap the notification bar to sleep, volume and power on the same side...

    Anyway, right after waking, several times over the past few days that I've had it, it's told me that SCP has stopped responding and asked me to close or wait.  If I say close, it automatically restarts, which is good.  I need to try to get you a report from right after it happens; haven't thought of it when it was happening yet.

    EDIT:  Just happened.  It offered "Close", "Wait", and "Send Feedback".  Send Feedback then took me to a message indicating that the feedback app had crashed, so close or wait.  Sigh.  So I sent you diagnostics after it started back up again.  Not sure there'll be anything helpful.

    - Trip

    • Like 1
  5. 6 hours ago, chamb said:

    I do not know but I sure would like to find out.  I am still on the sprint biller and was offered two s-22 phones to replace my two s9 phones.  I took the deal. 

    Had to pay taxes and shipping cost.  Great deal. Almost Free.  This all went down about a month ago. So far, it looks like it all went as advertised.

    I have still been unable to figure out why I can't seem to get this deal, even though your phones were older than mine.  Yesterday the Sprint site popped up a big warning when I logged in telling me to upgrade, and when I went to the phone page, it said $0/mo, right up until I got to checkout, at which point the number increased back to the $16.67/mo I had seen previously.  Chat was clueless--first person suddenly disconnected when I asked after they initially ignored my question and went into a spiel, and the second basically talked in circles.

    - Trip

  6. Around me, there appear to be sites in small groups where n41 SA is available.  For example, it appears the sites in and immediately surrounding Tysons Corner have n41 SA, but get outside of that group and it drops right back to n71 SA.

    - Trip

    • Like 1
  7. I was just about to ask what 1x800 features were removed, since I still see 1x800.  Actually, I've had to reboot my phone twice in the past week or two due to it dropping VoLTE and falling back on very weak 1x800 from who knows where.

    - Trip

     

  8. 9 hours ago, mikejeep said:

    Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing.

    Thank you so much for this one.  I'll be giving this a try--this is something that has caused me a ton of grief in the past.  When you're running 9 or 10 phones like I am, it's hard to make sure they're all getting updated locations.  This should be massively helpful.

    Let me know what information I can prove to help you optimize this.

    - Trip

    • Like 2
  9. Mike,

    I saw a video taken last night of someone drive testing the Dish Wireless network and at one point they pulled up SCP.  When they did, the accent line appeared to be in the magenta color of T-Mobile.  Not sure what color to suggest but if it's native Dish and my vision caught it correctly, it seems like it should have its own color.

    https://imgur.com/a/kOZmBuL

    EDIT:  Found another frame where it appears there was no accent.  Huh.

    https://imgur.com/a/USbB4Zq

    - Trip

  10. 3 hours ago, dkyeager said:

    Interesting notes:

    Acquired customers, net of base adjustments (1)(2) 12 806 (558)
    (1) Customers impacted by the decommissioning of the legacy Sprint CDMA network, who did not migrate to the T-Mobile network, have been excluded from our postpaid customer base resulting in the removal of 212,000 postpaid phone customers and 349,000 postpaid other customers in the first quarter of 2022. In connection with our acquisition of companies, we included a base adjustment in the first quarter of 2022 to increase postpaid phone customers by 17,000 and reduce postpaid other customers by 14,000.
    (2) In the first quarter of 2021, we acquired 11,000 postpaid phone customers and 1,000 postpaid other customers through our acquisition of an affiliate. In the third quarter of 2021, we acquired 716,000 postpaid phone customers and 90,000 postpaid other customers through our acquisition of Shentel’s Wireless Assets.
     

    I assume other customers is from MVNOs (perhaps old Dish customers, since most MVNOs are prepaid, including current Dish.) Other clarifications are welcome.

    Could "an affiliate" in #2 be Swiftel?  Trying to puzzle out who it could be and that's all that really makes sense to me.

    As far as #1 goes, I'm finding it hard to believe that there were so few.  Or is that only customers who are already cut off from service entirely via the CDMA retirement on 3/31?  Like, I still have service that works fine since I have a VoLTE through Sprint, and I have to imagine there are a lot more like me.

    - Trip

  11. We're like a month and a half from the deadline.  I was really hoping to see some availability by now.  I'm itching to get a device (possibly the Moto G 5G 2022, which should have n70 support, though that doesn't come out until next month and may be too pricey for now, so maybe the Celero if that can be band locked) and the $100/year plan to track the network.  Lots of deployment around Richmond, which tracks with their announcements, but I've also seen permits appear around here and at least one deployment. 

    - Trip

    • Like 2
  12. 3 hours ago, RAvirani said:

    The two big reasons for this are site density disparities and the complexity associated with the spectrum transition 

    Quoting because your whole post is relevant.  I just got back from a miserable drive (it poured the whole way) through Lynchburg and Charlottesville.  I found that several Shentel sites which are co-located with T-Mobile are now flagged 312250, new since the last time I was there, presumably because they desperately need the spectrum to be in use until they can get the associated T-Mobile gear upgraded. 

    - Trip

    • Like 6
  13. They've been turning off sites around here for some time now.  My home site was one of the first decommissioned--gear is long gone.  After initially having blocked ROAMAHOME on my account, which also blocked MOCN when that came along, around the time I realized the gear was gone, I had them add MOCN back to my account so I could use T-Mobile sites without dropping to roaming.  I'm still on a Sprint SIM but mostly live on T-Mobile towers in this area.

    Sites running 312250 are still going strong.  And very little has happened in the Shentel region where the T-Mobile network is the inferior partner.  I spend a lot of time on 312250 from Shentel in those areas.

    - Trip

    • Like 2
×
×
  • Create New...