Jump to content

ajm8127

Honored Premier Sponsor
  • Posts

    69
  • Joined

  • Last visited

Everything posted by ajm8127

  1. Thanks for that. I was unable to listen to the call this morning. That 125 number for the legacy network is likely a result of current market penetration and data demand. As those metrics increase I would be unsurprised to see that number of sites increase as well. Central PA is a very under penetrated market for Shentel, compared to their penetration in the Shenandoah Valley (something like 4x less penetrated in CPA). Also I expect them to equip almost all new sites built for capacity with B41. Another thing to remember is there are a lot of cows and corn in areas Shentel covers, so picking and choosing which sites get B41 instead of carte blanche deploying TDD makes a lot of sense. I am just excited to see 50 sites. It will make a huge difference in network performance. You can do a lot with three well balanced 5MHz carriers, but it is still only 15 MHz. I almost can't fathom what 40 or 60 additional MHz will be like on top of what Shentel already has. It is an exciting time to live in Shentel land.
  2. I do not believe Shentel has the necessary licenses to actually own spectrum. What Shentel gets is 225 million over five to six years, which could be viewed as compensation for the spectrum. I could not image this acquisition will slow down Shentel's B41 deployment. If anything it will have the opposite effect. nTelos owned the BRS 2.5 spectrum from around Winchester south to Harrisonburg among other areas, and now that Shentel will be handing it over to Sprint, Shentel should be able to deploy multiple 20 MHz B41 carriers in those areas, plus all others where Sprint controls the BRS spectrum. There is a ton of growth potential in Central PA for Shentel and they know this. They also know they are behind the eight ball with LTE spectrum having only three 5 MHz carriers in all markets, granted their hands are a bit tied by Sprint. B41 deployments will proceed full steam ahead - they have to. Otherwise the LTE network will practically collapse in on itself. Goals are set at around 10% of the network by the end of 2015. Also, Shentel's HQ is in Edinburg, not Harrisonburg. Not that I am complaining, this site is fantastic.
  3. B41 is coming. From some of the conversations I have had I gather Shetel has been given the OK to start putting 2.5 equpiment on their towers. I still do not think they can legally transmit yet. I think it has to do with Clearwire still being on-air until November.
  4. What you found was a DAS fed by a nearby macro site.
  5. I can tell you this annoucement was made to the company and the public at about the same time. There is no timeline yet though there will be signifigant discussion and planning before the deal offically closes so the deployment goes as quickly and smoothly as possible.
  6. Part of the advantage for Shentel is they can leverage their fiber network which is very complimentary to the nTelos acquisition. Shentel stands at something like 98% PCS 4G (G Block) with 95% 800 LTE which will very soon be augmented by 2.5 LTE in the major metro (if you can really call them that) areas. Expect the same level of deplyment in the newly aquired territory. The deal is set to close in early 2016 due in large part to the spectrum that needs to transition from nTelos to Sprint and the regulatory approval this requires. I really don't think this will be a problem, however. A lot of the spectrum is already used in Sprint markets.
  7. Those small B25 only "antennas" are actually ALU MCO (metro cell outdoor) small cells.
  8. As was posted above, Lancaster is not Shentel, but I can tell you almost all Shentel sites now have an 800 MHz LTE and voice carrier. Has anyone noticing the lack of eHRPD in the Shentel market noticed slower data performance? This would only be noticeable during the transition from EV-DO to LTE. Read the following for more information: http://s4gru.com/index.php?/topic/1819-what-is-ehrpd/&do=findComment&comment=52976
  9. This is correct, but I would like to expand on it a little. The last two digits of the GCI will tell you the sector and the band in Shentel's market. 01, 02, and 03 indicate sectors alpha, beta and gamma respectively for PCS G band LTE. 09, 0A and 0B also indicate sectors alpha, beta and gamma respectively. The represent PCS band A or B depending on if you are in the Philadelphia (B band) or Washington/Baltimore (A band) markets. 19, 1A and 1B again indicate the three sectors respectively and show you are currently connected to 800 MHz LTE (Band 26) I have also heard that Shentel was holding out to see how the Sprint/T-Mobile deal was going to work out before deploying any B41. I suspect now that it has fallen through, Shentel will be doing some evaluation with the 2.5GHz spectrum because they know Sprint will be holding onto this spectrum. Had the deal worked out, the resulting company may have had to sell that portion of the spectrum to satisfy the FCC.
  10. Interesting. I had the location setting set to use GPS only. When I changed it to use GPS and the network, everything works as it should. Thanks for your input.
  11. Mike, Sent you a report from my LG G3. I noticed I get no SID, NID, BID, BSL when I force the phone into CDMA mode. Come to think of it this may be related to another problem I have where I get a 0 byte CDMA log file. I don't even get column headers. I can see the LTE GCI/PCI fine and those logs appear normal. I reliaze this may be a limitiation of my device, and I have tried turning location services on. Let me know how the report looks when you get time. Thanks, Tony
  12. I have a G3 as well and I am having trouble accessing the engineering screen using SCP. The app tells me "Debug/Engineering screens may not be availible on this device" but I can enter ##33284# in my dailer and it enters the engineering screen just fine. Recording the RSRP and the PCI for LTE or the Ec/Io for 1X and EVDO independantly along with the PN (understand this might be impossible?) with the Lat and Long from the GPS reciever to do simple drive testing would be invaluable. CSV files would be alright, but KML files with color codes for the signal strengths would be even better. Setting a distance interval in feet for each data point would be most excellent, but a polling interval in seconds would work. I love the app. Keep up the good work, mikejeep
  13. ajm8127

    general

×
×
  • Create New...