Jump to content

ingenium

S4GRU Premier Sponsor
 View Profile  See their activity

  • Posts

    1,717

  • Joined

  • Last visited

  • Days Won

    17

 Content Type 

Everything posted by ingenium

  1. ingenium
    Time Warner *should* have the capacity in place to upgrade them. B41 antennas and radios cost more money. Increasing backhaul capacity is much cheaper by comparison. That being said, if there isn't much load on the sites, they may keep some carriers off and lower the backhaul bill. Then turn them on as usage increases. In a lot of markets though (SF, Pittsburgh, and I believe Columbus), during peak hours even with 10x10 B25 (or 2 5x5 or in the case of Columbus, a 5x5 and 10x10) and 3 41 carriers, sites are getting over capacity. In SF I found a test site near Napa that was running at least 5 carriers (likely 6). My guess is that if backhaul and spectrum isn't an issue, they'll jump straight from 3 to 6 carriers (but still only allow 3 to be aggregated at a time). Sent from my Pixel XL
  2. ingenium
    It depends how it was provisioned and how much capacity their supplier has. It may be as simple as calling up the backhaul provider and asking for more bandwidth (akin to upgrading your home internet speed). That was supposedly the point of NV 1.0, get (usually fiber) backhaul in place that can be easily upgraded for more capacity. No site visits or additional cables. Sent from my Pixel XL
  3. ingenium
    If it's a new deployment, they'll do 3 carriers from the start (assuming backhaul is in place). CA will be enabled by default, at least 2xCA. It sounds like they have 3xCA enabled on a lot of sites, but haven't flipped the master switch yet allowing consumer devices to actually use it. From what I've seen, if the site supports 3 carriers, and the backhaul is there, they turn on all 3. No reason not to. Sent from my Pixel XL
  4. ingenium
    Which Android devices? Sent from my Pixel XL
  5. ingenium
    Oooo, I have one of those too, 0129EA39. Also the same route, so in Manhattan as well. It could be a bug in SCP because I was connected to them so briefly, but [0129EA39] shows an EARFCN of 41474, and [012A8D31] an EARFCN of 41276, which matched up with the regular macro EARFCNs. Like I said though, i was connected to each for only less than a second, so it's likely SCP just logged stale EARFCN data and they're really 40072 like the other small cells.
  6. ingenium
    The ones I have in Manhattan are [012A3131], [012A7B31], [012A8D31], and [012A9631]. The first is near Battery Park, and the others were along FDR starting from Midtown down through Battery Park to the tunnel.
  7. ingenium
    I don't have an exact address, but these are my SCP logs with 012A as the starting GCI (EDIT: Removed due to mangled formatting) I found 4 in Manhattan, and one in Brooklyn. That one has a strongest rsrp of -84 near Prospect Park at Caton Ave and Rugby Rd.
  8. ingenium
    Hmm I didn't think to check NSG, since the ones in Ohio are only a single carrier (at least the LTE backhaul fed ones I checked out are). It's possible it's a new install that isn't 2xCA yet? I'll look through my logs tomorrow and see what earfcns I found for your market. Almost all the B41 was Clearwire lol. This particular site with earfcn 40072 was in Flatbush, I think I saw the antenna on a street light post but didn't take a picture (was very hungover lol), just a screen shot: Sent from my Pixel XL
  9. ingenium
    Add in SF Bay Area and Pittsburgh city. I never see 3G drops unless it's an actual dead spot for CDMA too. Now non-B41 may be unusably saturated (*cough cough* SF...), but QoS makes that a non issue for VoLTE. I just wish they'd roll it out and make it a secret dialer code to enable (and BYOD wifi calling...). And reset it with a profile update (to ease tech support). It lets people use it who want to, and gives Sprint valuable data. Plus no complaints since it's not an official feature yet. It just seems like a no brainier. It'd only be power users using it at first anyway Sent from my Pixel XL
  10. ingenium
    Was in your market the last couple days. The small cells seem to be using the same earfcn as the ones in Ohio, 40072, despite the first and second B41 earfcns being different. So that might be an easy way to distinguish them from the macros. Sent from my Pixel XL
  11. ingenium
    Yup, I just laid down the purple on Sensorly a few days ago [emoji39]. Drove from Ohio to NYC. Unfortunately I forgot to start mapping on Sensorly until after I passed Clarion (going east), so I missed the western portion of I-80. Logs were submitted for processing tonight. More detailed info with GCIs is on CellMapper (that was logging the whole time, along with SCP, so it shows the western portion of I-80). It seems in some stretches they upgraded every other site to GMO LTE (CDMA often showed -60 while LTE was -110ish as I passed some sites). Overall pretty solid coverage for most of I-80, I was surprised. It's 2x2 MIMO too surprisingly, so it's not limited to half the usual 5 Mhz B25 capacity like 1x1 would be. I guess the antennas had enough ports for it. NSG showed TM3 MIMO, at least in Clarion and to the west. I didn't test after that, so it could drop to 1x1 further east. Some stretches had B25 on Sprint but HSPA for ATT (no LTE). EDIT: Actually it looks like Clarion is Pittsburgh market based on the GCI. Western PA starts just east of there.
  12. ingenium
    Wait is that just for new lines? Can people who already have the Pixel qualify? Sent from my Pixel XL
  13. ingenium
    I think if it doesn't detect the other end is also on RCS, it falls back to SMS. If you were to send the message to an RCS enabled number it likely would have gone through. If I have time I'll try to get a packet capture of an RCS message. Likely it's wrapped in TLS or ipsec, but it might yield some interesting information. Sent from my Pixel XL
  14. ingenium
    They actually just released an update today. Not sure if it does anything to address that issue, it's mostly to deal with a bug that prevented MMS on a UK carrier. No other changes are mentioned. They also released an out of cycle update to fix Canadian band 4 connectivity last month. So I'm hoping from now on they'll be more likely to release out of cycle bug fixes. Sent from my Pixel XL
  15. ingenium
    Yup same with FiOS in Pittsburgh. Never below 150 down. Up is usually 165 or so. I don't think I can ever go back to unsymmetrical internet long term, it's nice being able to host things from a home server (media, VPN, etc). Now if they would just roll out IPv6... Sent from my Pixel XL
  16. ingenium
    I actually didn't get the confirmation text in Messenger, but I've tested it with someone and it indeed works. Maybe the newer version of Messenger is intercepting it similar to the way voicemail notifications work. Sent from my Pixel XL
  17. ingenium
    So I cleared data for Messenger (this does NOT delete your messages), and when I opened it it asked me to enable enhanced messaging again. This time the settings appear and it's actually enabled. Sent from my Pixel XL
  18. ingenium
    It appears they maybe intend to roll it out on the stock Samsung messenger http://eguides.sprint.com/support/eguides/samsunggalaxys7edge/content/samsung_galaxy_s7_edge_ug/use_enhanced_messaging.html Sent from my Pixel XL
  19. ingenium
    Yeah, I'm not even sure exactly where it shows up in the settings. If you put a non Sprint SIM in the device it should show you the setting, but with a Sprint SIM in it's hidden unless GSM/UMTS roaming. Sent from my Pixel XL
  20. ingenium
    It just asked if I wanted to enabled enhanced messaging, then asked me to exclude Messenger from battery optimizing. And that was it. I think you're supposed to get a confirmation text from Sprint but I never got it, nor did another phone that got the same notice a few days ago. So it's not actually enabled... Sent from my Pixel XL
  21. ingenium
    I got the alert just now and enabled it. But it's still not showing up in advanced settings. And messages to people I know have it enabled are showing as sending with SMS still... Grrr Sent from my Pixel XL
  22. ingenium
    Disable data roaming first. Then when they get to a country go into settings, mobile networks, more, and there should be a way to select which network the phone is connecting to. It doesn't show up when you're on Sprint native service. Once you've connected to a network that is part of Open World, reenable data roaming. The phone will be locked to that network then and won't switch unless you manually select a different one. Sent from my Pixel XL
  23. ingenium
    Supposedly LTE roaming costs more than HSPA roaming. But considering Sprint doesn't even have domestic LTE roaming on Nexus devices yet, I wouldn't hold my breath... Sent from my Pixel XL
  24. ingenium
    Still nothing on my Pixel XL. Even updated to the new version of Google Messenger. I wonder if it's an account by account toggle, rather than a line by line toggle. Sent from my Pixel XL
  25. ingenium
    Pretty much. That's what we observed on the relay small cells in Akron, Ohio. They were using a different earfcn from the nearby macros (40072 in this case). Sent from my Pixel XL
×
×
  • Create New...