Jump to content

Trip

S4GRU Staff
 View Profile  See their activity

  • Posts

    2,269

  • Joined

  • Last visited

  • Days Won

    88

 Content Type 

Everything posted by Trip

  1. Trip
    55052. From the file provided by UPdownLoAD. - Trip
  2. Trip
    Not a clue. I just found which Geo my SID was in and went from there. - Trip
  3. Trip
    The bug where 1X and LTE appear at the same time occasionally (usually after changing between the two) and LTE information doesn't fully populate. My Verizon phone on 5.1 gets it now and then. - Trip
  4. Trip
    Here are the changes I see: In Geo 3, the preferred roaming partners are now SIDs 6498, 21625, and 6499, with EV-DO. (6498 is United Wireless, 6499 is Nex-Tech Wireless. 21625 isn't in the list I have.) In Geo 4, Sprint native service now includes SIDs 4166 and 22424, the roaming priority of 4305 was increased, and 1211/1465/6488/152 were added. (See Geo 9 below.) In Geo 5, 1382 and 1996 were added as preferred roaming partners. (C-Spire.) In Geo 6, 4305 was increased, but also added to roaming are 264/1394/2094/113. 2094 comes with EV-DO. (113 is Verizon, 264/1394 is C-Spire, 2094 is not in my list. 4305 is SI Wireless.) In Geo 7, 4305 was increased, but 1280/6490/6492 were added. All three come with EV-DO. (All three are Bluegrass Cellular.) Geo 9 is now gone, having been merged into Geo 4. 5911 is the only roaming SID not to make the jump. The other geos are renumbered accordingly. (5911 is US Cellular.) In the former Geo 12, now Geo 11, 193 and 318 are added. (US Cellular and Alltel, accordingly.) In the former Geo 14, now Geo 13, 4305 was increased. - Trip
  5. Trip
    Well, I was going to try to look at it at work this morning, but the software I normally use isn't working. I'll have to try it at home (slower, but should function in any case). EDIT: Right after posting, I figured out what was wrong. Will have something shortly. - Trip
  6. Trip
    Understood. Kind of disappointing but not your fault in the slightest. Here's hoping Android N takes care of this once and for all. - Trip
  7. Trip
    I did respond to your response to Overstew, but it was still relevant because I hadn't gotten the second update before I left for work that morning. I more or less figured out that was what it did. Not to make more work for you, but is there any way to have an option to allow it refresh again as soon as the EARFCN becomes available? In the general case that probably doesn't matter, but given that this phone in particular sometimes goes 20 seconds between updates otherwise, it can be quite the waiting game. And I agree, I'd rather have no data than bad data. - Trip
  8. Trip
    Mike, It seems you were right. I updated again and now the EARFCN is much more consistent. It doesn't pop up right away, but after the first update of a connected cell, I see the EARFCN. (My T-Mobile phone is the one that has a really slow update frequency.) - Trip
  9. Trip
    Can anyone tell if the 6.0.1 update includes the 1X/LTE bug with SignalCheck Pro? If it does, I think I'd rather stay on 5.0. - Trip
  10. Trip
    I just confirmed /dev/smd0 is actually invalid on my device; I needed smd11. So I've switched that back and, at the moment, I have EARFCN. I'll keep an eye on it on the walk to the Metro and see if it behaves. Also, just in case you missed this: https://code.google.com/p/android/issues/detail?id=195574 - Trip
  11. Trip
    Mike, Thanks first for dealing with the text color issue. It was really causing me a problem over the weekend when I was driving around in the bright sunlight. Second, my T-Mobile phone has shown me the EARFCN a handful of times, but otherwise shows nothing, including right now as I sit at work on the DAS outside my door. I had to switch it to smd0 before it showed anything. This despite Cell Mapper showing it consistently. Is this the sort of thing sending a report back to you would be helpful with? - Trip
  12. Trip
    Other than Nextel conversions, I haven't seen much new lately. No permits on file with Fairfax County for Sprint, for example. - Trip
  13. Trip
    Very quick note about Verizon. Two weeks ago, I suddenly noticed my Verizon phone would no longer connect to LTE. It would only connect to 1X and EV-DO (note, not eHRPD). That was approximately three months from the time my Verizon phone was first turned on. I tried rebooting and other things (other than putting money on it) and didn't get a satisfactory result. On a hunch, this week I bought a new Verizon SIM for it. It came in the mail today. I turned off the phone, popped out the old SIM, put the new one in, and it jumped right onto Verizon LTE when I turned it on. So it seems that Verizon may deactivate LTE access on SIMs that aren't activated for three months. But, again, having to throw a few dollars at it every few months to be able to record where Verizon cell sites are seems like a good deal, much like the AT&T deal. - Trip
  14. Trip
    Mike, I've e-mailed it to you. - Trip
  15. Trip
    You're in Albuquerque, according to your profile information. The FCC has announced that no stations need to be bought in Albuquerque. But the list of participants in the auction is confidential. Stations that "win" and go off air or move to VHF will be published immediately after auction, but non-winning participants are kept confidential for at least two years. - Trip
  16. Trip
    As I said, it won't be as neat and tidy as I stated. The estimates range from 400 to 1200 stations changing channels, not counting several hundred going off the air. - Trip
  17. Trip
    My question is, what building materials are used in Houston? I ask because that could certainly account for differences in experience. I see this in OTA TV; parts of the country, particularly in the west, use stucco for building construction, and it murders signal level in buildings in general. Various building materials have different levels of penetration and thus different experiences result. In my personal experience here in the eastern part of the country, B41 works well in most buildings as long as the tower isn't too far away, except the ones with low-E glass (like my workplace, which has a DAS instead). I almost never see B25 though; my phone tends to connect to only B26 or B41, (unless B41 isn't available) which I think speaks to the reliability of the B41 signal. - Trip
  18. Trip
    Yes, if, using Chattanooga as an example, WFLI on 42 does not sell in the auction, but WELF on 16 does, then the FCC will shuffle the channels around so that, perhaps, WFLI goes on 16 but WELF goes off the air. It almost certainly will not be that neat and tidy, but the concept is right. - Trip
  19. Trip
    Mike, I installed it on two phones this morning, my main (Sprint) phone and my T-Mobile phone. While this doesn't really let me do much with many of the new features yet (I need to test my Verizon phone for the 1X/LTE bug over the weekend), I don't like the new color scheme. It highlights the one row I don't use very often while making the text of all the other rows a dull gray color that's harder to see. Not good when trying to see my phone on the go, or even in general. (Sitting at my desk at work with my T-Mobile phone at an angle, I can see "LTE AWS" clearly but nothing else is legible, when I used to be able to read all the rows in this position.) Can this be undone? Or at least be switchable? - Trip
  20. Trip
    SCP guesses the band based on the sector number and PLMN, which works great for Verizon, Sprint, and AT&T. T-Mobile, by contrast, is not nearly as neat about it. For example, where I live, 01/02/03 are AWS, while near where my parents live, those same sectors are PCS (but IDed as AWS in SCP). Some sites have four sectors instead of 3; the ones with three sectors have 04 as 700, while the ones with four sectors have 04 as AWS (or, I suppose, PCS is also possible) with 05-08 as 700. (Which is why 04 sectors are "LTE" and not "LTE 700" or "LTE AWS".) Once the new build is released, rooted phones that support retrieving the EARFCN should properly show the band. I've rooted my T-Mobile phone in preparation. Mike can correct me if I got any of that wrong. - Trip
  21. Trip
    It's strange how I keep hearing that AT&T's LTE rollout is "complete" but that's complete nonsense. Many rural cell sites do not yet have LTE with AT&T. In fact, the only carrier that seems to have universal LTE is Verizon. On the flip side, in this area at least, AT&T seems to be the densest of the four, followed by T-Mobile, and then Sprint/Verizon are very close to each other, but Verizon has a TON of open permits for densifying which I assume we'll see this year. Despite that, Verizon and T-Mobile are basically tied for first while AT&T is last, according to RootMetrics. I really don't know what AT&T is doing wrong around here, because their spectrum holdings are pretty comparable to the other carriers. - Trip
  22. Trip
    The app does have an "exit" function in its menu... - Trip
  23. Trip
    http://www.businesswire.com/news/home/20160311005110/en/Sprint%E2%80%99s-Network-1-Denver - Trip
  24. Trip
    I don't really know enough about how King Street Wireless is set up to be able to say, but my guess is that it's similar. - Trip
  25. Trip
    Don't forget that chamb is in Shentel territory. In Shentel territory, things tend to be better managed than in native Sprint territory. I have to think that Shentel will be densifying as needed, independent of the larger Sprint effort. - Trip
×
×
  • Create New...