Jump to content

Trip

S4GRU Staff
  • Content count

    1,336
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by Trip

  1. Follow-up note: Do not buy the Moto E4 if you're attempting to use it for network tracking as I am. Leaving aside the bad Band 66 EARFCN (which means I never see a valid EARFCN for AWS-1), it's also having issues with Network Signal Guru. The band lock doesn't seem to stick properly some of the time; if it can't find LTE in a particular band, it looks like it will sometimes override the lock and try the other bands anyway. I was also having trouble with the GPS power save being really aggressive and not providing coordinates at all; I had to change it to high accuracy. I may still keep it if Mike puts the override in for the bad EARFCN, but it's rather disappointing. - Trip
  2. Mike, I bought a Moto E4 to replace my Moto G4 Play that I use to track Verizon since the GPS is dying in it, and it has the bad EARFCN on Band 66. For Verizon (and I suppose AT&T), where we know that the sector number properly indicates the band in use, could a fast work-around be to check the sector ID and, if appropriate, add 65535 to the EARFCN provided by the API if it's an AWS sector but providing a non-AWS EARFCN? - Trip
  3. AT&T opened a bunch of permits around here that, I believe, are for Band 66 and/or 14. I know in Montgomery County, MD, I can see some of the actual application documents and they show those bands being installed. I just need to get a phone that supports Band 14 now. Waiting for one that's a bit lower in price than what I've seen thus far. - Trip
  4. Trip

    LG G6 to be Sprint's first HPUE-capable device

    Are there any changes in the way SCP behaves? - Trip
  5. For folks in the south Texas part of IBEZ: https://docs.fcc.gov/public/attachments/DA-18-542A1.pdf - Trip
  6. Interesting, it also appears to be giving you correct EARFCN values for Band 66, so maybe they've fixed that issue as well. - Trip
  7. Trip

    Sprint Tmobile merger Disc.

    Plus staff who should not take a position on it. - Trip
  8. I won't speak for Mike, but it sounds like they're specifically talking about network traffic, as in what websites you're connecting to, rather than which cell tower you're connected to. That information comes from an actual Android API which requests permissions, and what they're talking about here is direct access to /proc/net in the file system, which apparently does not. That said, it's vague enough that I, too, would like to hear more information on it. - Trip
  9. Trip

    Sprint Tmobile merger Disc.

    I'm not sure I understand how that works. Shentel builds out better than any other carrier. They are the leader in their region, they don't rest on their laurels despite that, and they continue building out and upgrading at a ridiculous pace. I'm not entirely sure how it is anti-innovation to want the company that clearly knows what they're doing to continue being able to do so. - Trip
  10. Trip

    Sprint Tmobile merger Disc.

    Old expression: If it ain't broke, don't fix it. Seems like it should apply here. - Trip
  11. Trip

    Sprint Tmobile merger Disc.

    You're not familiar with Shentel. In its region, Shentel beats out the other three or four carriers hands-down. In the recent state-by-state wireless company rankings, Sprint was tied for first place in exactly one state: West Virginia. https://www.rootmetrics.com/en-US/rootscore/map/state/west-virginia/2017/2H Shentel operates the network in almost all of West Virginia. Getting rid of Shentel would be a very bad decision, in my opinion. - Trip
  12. Trip

    Sprint Tmobile merger Disc.

    I took care of it. - Trip
  13. That has not been my experience at all. When roaming on US Cellular, the moment my phone thinks it sees 1X 800 from Sprint, it immediately ditches the US Cellular LTE signal and tries to connect to 1X 800 until it realizes there was nothing there after all. Very, very annoying. - Trip
  14. Not sure if you have a US Cellular phone, but on mine, it roams seamlessly onto Sprint LTE even while connected to US Cellular 1X. - Trip
  15. Trip

    Sprint Tmobile merger Disc.

    What I've been reading is that the combined network would have 120,000 sites, and they're planning to shut down 35,000 of them, leaving 85,000. That's about 30%. Going back to the Spotsylvania County example, counting it that way, there are 30 sites. 12 of the Sprint sites are co-located with T-Mobile sites. Turning those off would decrease the total number of sites by 40%, but there would be no change in coverage. - Trip
  16. Trip

    Sprint Tmobile merger Disc.

    To the earlier discussion about the number of cell sites being turned off, I did a little bit of an analysis. I used Spotsylvania County, VA as my example case, excluding the Shentel area. I put both the Sprint and T-Mobile sites on a map. The total number of sites is 18. Of those, 12 are shared between Sprint and T-Mobile. Of the remaining six, 5 are Sprint-only and 1 is T-Mobile only. While the 1 T-Mobile only site is kind of near one of the Sprint-only sites, both are on I-95 and AT&T is actually on both towers, so I would expect them to keep both. So even though 2/3 of the Sprint sites would presumably go away in Spotsylvania County, the actual change in service would be effectively zero. - Trip
  17. Trip

    Sprint Tmobile merger Disc.

    I've been in half a panic about this merger because there's been no word at all about what happens to Shentel. I found this article this morning, which is making me feel better, though I want to wait to hear something for certain: https://seekingalpha.com/article/4096992-real-winner-sprint-t-mobile-merger The link to the agreement being discussed in the article is here: https://www.sec.gov/Archives/edgar/data/354963/000114036115031058/ex10_2.htm The summary seems to be that in the case of this merger, Sprint either has to buy out Shentel at a premium, sell the T-Mobile customers and network in the Shentel region to Shentel at a discount, or shut down the T-Mobile network in the Shentel region. One of the latter two options would make me happy. - Trip
  18. Trip

    Sprint Tmobile merger Disc.

    There are an absolute boatload of sites shared by both Sprint and T-Mobile. There are additional sites that are at adjacent locations. I wouldn't be surprised if that number added up to 35,000. - Trip
  19. Trip

    Sprint Tmobile merger Disc.

    It just ended. - Trip
  20. Trip

    Sprint Tmobile merger Disc.

    Mostly taking questions about business synergies and other buzz words. I missed the beginning of the call so I missed any discussion about roaming. - Trip
  21. Trip

    Sprint Tmobile merger Disc.

    Call is still going on. - Trip
  22. Trip

    Sprint Tmobile merger Disc.

    I've asked on Twitter about the Shentel region and SprintCare already wrote back saying they don't know. I hope they address it on the call; I'm listening now. - Trip
  23. Trip

    Sprint Tmobile merger Disc.

    I am okay with this if, and only if, Shentel is left in charge of the areas they're currently in charge of. - Trip
  24. https://medium.com/@AjitPaiFCC/on-the-road-again-9a759494d85e Chairman Pai blogs about items on the May agenda for the FCC. Among them, an item about 2.5 GHz band licensing. - Trip
×