Jump to content

JWMaloney

Honored Premier Sponsor
  • Posts

    698
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by JWMaloney

  1. Nexus 5, stock Google Messenger. I disabled RCS after the issues started, and it hasn't made any improvement. Also tried profile and PRL updates as well as SCRTN programming reset. It's not any one tower either.
  2. Can confirm -- having ongoing intermittent issues with texting for the past few weeks, and I'm pretty mad about it. It will either be outgoing texts stuck sending or incoming texts not being received at all, both fixable only by reboot. Not sure why it's only now becoming an issue in 2017, but I would wager it's related to RCS rollout.
  3. EDIT: In case it was unclear, the press release was about a Sprint and Ericsson demonstration.
  4. Anyone else having issues with SMS/MMS recently? I've had an intermittent issue where all of my sent messages will get stuck in "Sending" state, and the only thing that will fix it is a reboot (also tried toggling airplane mode and forcing 3G unsuccessfully). Also had an issue this past Saturday where I didn't get any messages until I rebooted that evening (and then about 30 messages from 3 people all came in at once). This is on a Nexus 5 using the default Google Messenger app. I had RCS enabled at one point but disabled it after this first started happening frequently. It doesn't seem to have had any effect either way. The issue also doesn't seem to be isolated to any specific cell site.
  5. I expected a new GCI. I didn't expect a new GCI per sector (although it does make sense given the name mini macro). EDIT: These are using the same EARFCNs as the first 2 carriers on the 8T8R sites.
  6. Tracking these is going to be a nightmare. Is there really no way they can share an eNodeB ID on a macro site?
  7. The "Aggressive Wi-Fi to Cellular handover" setting under Developer options really helps with this. Note that it doesn't persist after reboot though.
  8. I don't know what that map depicts, but it definitely isn't their coax footprint. Take a look at southeast Louisiana which is majorly Cox Communications territory. They do have a fiber transport partnership with Cox, so maybe that's why Cox territories are depicted. Here's an alternative map: Source
  9. I haven't been able to successfully activate/swap a phone online in over 2 years. It fails every single time. What's worse though is that almost every manual activation I've had done has resulted in TEP being fraudulently added to my lines. No, I don't need or want $11/mo insurance on a 5-year-old flip phone that's temporarily replacing a relative's broken smartphone.
  10. The RRH has a limit to the number of carriers that can share a transmit path. For example, the Ericsson RRUS 35 supports a maximum of two LTE and six CDMA carriers simultaneously, but no more than 4 carriers can share any single transmit path. So to run the maximum number of carriers, you'll have two LTE and two CDMA carriers on one set of paths and four CDMA carriers on the other set. There's actually a site in Central, Lousiana that does run 4x4 MIMO with a single RRH and antenna, but it's only running one LTE carrier and presumably no more than 3 CDMA carriers. EDIT: I just noticed this was in the Samsung thread, so perhaps someone who is more familiar with that equipment could offer more details about its specific limitations.
  11. This happens to me all the time on busy sites. The network sends an RRC Connection Release packet to my phone with reason "other" and directs it to a specific CDMA channel. Often it's almost immediately after handoff to the site in the first place, and it usually only happens during peak hours. I'll have to see if I still have screenshots somewhere.
  12. Sprint's B41 holdings in Baton Rouge include BRS1, BRS2, E1-E4, F1-F4, and H1-H3. That gives them a 6 MHz orphan block (2496-2502), a 12 MHz contiguous chunk (2602-2614), and a 55.5 MHz contiguous chunk (2618-2673.5). FCC records show a new, "Special Temporary" license, WQYL886, has been granted for the K block (filed as the "old" F2 block under the pre-transition band plan). This bridges the gap between the 12 MHz and 55.5 MHz chunks for a total of 71.5 MHz contiguous. The first B41 carrier in Baton Rouge moved to new center of 40913 (2622.3 MHz). Based on the previous center spacing of 19.8 MHz, I expect the second and third carriers to now sit at 41111 (2642.1 MHz) and 41309 (2661.9 MHz) respectively, leaving 10 MHz free at the lower end and enough for a guard at the high end.
  13. Sprint was required by US authorities to remove all Huawei equipment from its network (more info). With payments coming due on the Clearwire debt, most of the new band 41 equipment went directly into Clearwire conversions to replace the Huawei gear. This further confounds the "70% of our LTE sites" figure. That said, Sprint has stated multiple times that they are taking a more "surgical" approach to network planning. They are not going to add band 41 macro equipment to every Network Vision site; rather, they are targeting specific sites which need additional capacity the most.
  14. It's a misleading statistic because there are thousands of LTE sites which only have band 41. Subtract all the Clearwire dual-mode and conversion sites, and the number is a lot lower.
  15. Any word on how Sprint is planning to do 2T4R for band 26? Are they just planning to add an A2 module to the RRUS 11 B26A radios in Ericsson land, or is something new showing up in FCC docs yet?
  16. Which Marriott? The one near the Convention Center is a block away from a B25/B26 macro site; the one on Canal St is facing a tri-band macro site with three band 41 carriers. You'll also see B25 on the . You should definitely see usable data speeds.
  17. It's supposed to be. I asked about that recently too, because when the third B41 carrier came online in NOLA, all three carriers changed to 2x2.
×
×
  • Create New...