Jump to content

dkyeager

Honored Premier Sponsor
  • Posts

    9,459
  • Joined

  • Last visited

  • Days Won

    268

Everything posted by dkyeager

  1. Try this one: https://www.fiercewireless.com/wireless/dish-frontier-cwa-others-lead-opposition-to-sprint-t-mobile-merger related: https://seekingalpha.com/news/3386206-dish-altice-usa-weigh-sprint-t-mobile-merger https://www.multichannel.com/news/dish-files-petition-to-deny-t-mobile-sprint-merger https://www.multichannel.com/news/altice-usa-files-in-opposition-to-t-mobile-sprint-merger
  2. Some required core updates, prerequisite upgrades, Samsung sites may have required special modules and then changing the GCI sectors (Sprint tends not to go ahead until all three of its vendors can do something. Latest example - Massive MIMO). Another huge factor was likely the cost of backhaul. They also had to get Son's approval and raise the capital. 5G represents a leapfrog opportunity for Sprint. Most people don't understand how close to bankruptcy Sprint was before Marcelo took over.
  3. I should have explicitly said cheaper. 4G will be around for a while with the average phone life at 3 years, meaning some keep their phone for 4 or 5 years or even longer.
  4. Quite a number of us have been looking at this issue for months, which I call Sequential GCI Sectors (SGS). For those unfamiliar it eliminates the special 8T8R market GCI and reorders all GCI band sectors first by sector then by band. Without software help this is uncomprehensible to most people. It took a while to get a reasonable sample of data from all sectors from various sites in various tracked markets. Sprint was also making changes and initially had various models in different markets. This has only been seen in Samsung markets, although I have looked at data from ALU and Ericsson markets. It should be noted that Mini Macros and B41 small cells are not affected. It now seems to have stabilized for a while around what is shown in ingenium's chart: Implementation is growing and is getting faster. Through the many logs I analyze I have seen it pop up in more and more markets. Still uncertain as to the reason. The latest theory is for 4x4 MIMO and 256 QAM with a long line of failed theories behind that one. There are areas of uncertainty surrounding 1) counties with portions of various b41 radius on different frequencies and 2) the handling of 4th and 5th carriers. We are hoping that Sequential GCI Sectors (SGS) in Columbus and Cincinnati will soon spread to such areas so we have a better data sample. Currently we only have the area around Youngstown to work with in this regard. Joski1624 has been key in this along with ingenium. I have handled this with a cutover date for GCIs and tracking expired b41 GCIs. Early on implementation stretched out over a couple of weeks, but it now seems entire sites are done at once. I process logs first to find any Sequential GCI Sectors (SGS) sites which are ranked into Yes, Maybe, and No. "Yes" is determined unique GCI endings which can be increased if you have detailed spreadsheet data on the site that is reasonably current. These become Approved SGS sites with the earliest one becoming the cutover date which is stored for future use. "Maybe" are unique GCI endings that don't have an expected EARFCN. Many of these are transition errors but a signification number are for sites where more data is needed. These become possible SGS sites and are flagged for followup. The approved SGS site data is then processed for new carriers and missing/changed PCIs. B41 is converted back to its old GCI including GCI sectors for this purpose plus to provide data for the expired B41 sites. The expired b41 sites is also used for Mini Macro GCIs that have been replaced with 8T8R in case they appear elsewhere in the future. This effort allows old spreadsheets to be retained. Should a market fully convert (none found so far) to Sequential GCI Sectors (SGS) it will be worth revisiting this multi-step process to simplify it. The unresolved issue of sites in counties with portions of various b41 radius on different frequencies is the most difficult for SCP. Sheets may have to track earfcns for those areas and/or store the SGS sectors for them to be properly rebuilt for SCP "national" logs. Markets with sheets will want to let SCP know the approved SGS sites as users may not be on the right band or sector to know independently. This way regular sites could be stored in their compressed format while only the SGS sites would need more entries. SCP may need to track SGS sites for markets without sheets based on past key GCI sectors. This may also be the right time for SCP to allow the direct importation of true site lat/longs as RSRP allows for easier detection of EARFCNs in transition. Another issue that would help is a more resilient error handling (retries) for rooted modem earfcns. Currently this is often tripped by other apps such as LTE Discovery (used for its airplane mode like ability) or Network Signal Guru (for bandwidth, MIMO and QAM detection). Presently you must exit and restart SCP to regain EARFCN detection in such cases. Based on past history, it is safe to assume that Sprint will not totally upgrade all sites in a market to Sequential GCI Sectors (SGS), but it will likely dominate -- it will just take a while in true Sprint fashion. Many of us S4Gru folks have retained older phones (I have 4) for assigning to different signal tracking purposes. The general public often has older phones just like these as their main phone. Without Sequential GCI Sectors (SGS) support older phones in SGS areas may soon become worthless for interactive signal detection and learning.
  5. It is disappointing that Sprint does not have a not Massive MIMO 5G option. I assume the price would be significantly less for less robust solution that would allow for both 4G and 5NR. This would allow more places to have 5NR sooner.
  6. I have been having an issue with Sensorly mapping on Android Oreo which is new to my V20. Trips map fine (when it does not crash), but results do not appear on map for new area of Sprint coverage. Next time I will try on an older phone.
  7. Various reports have stated since February That the LG G5 is to get the Android O "Oreo" update. On July 4th versions were released for Korea. Then the Sprint LG V20 got the update. A few hours ago T-Mobile said this: https://support.t-mobile.com/docs/DOC-37249 My guess is Sprint is not far behind.
  8. 5G is the truly unique item for Sprint. Do they have enough cash to make it fully work in a few markets? Ideally you would want all sites with Massive MIMO, which would be best done in a market where Sprint has all the B41 spectrum. If they do just a handful of sites in each market, people will quickly see through that and only the innovators will buy 5G phones.
  9. The nail that sticks up gets hammered down. Within 6 months both Verizon and AT&T will have answered this*. Sprint improves in so few places that it does not cost the duo much to answer each one before the public catches on and Sprint can reap significant rewards. Such a reply is much more difficult with T-Mobile since they have significant cash flow. * I have seen this happen many times over the years. Still improvements like this should be celebrated by us Sprint users!!
  10. So far we have found a grand total of one Massive MIMO iirc.
  11. Sprint often poorly covers nearby rural towns or rest areas (Shentel does a much better job with this). These rural areas are likely where much of the site reductions will be made because you can not afford too many sites given lower subscriber density. This will also work the other way in terms of expansion. Twice as many users will make a site viable. The urban areas will have site reductions just given the bulk of the sites are located there. Co-sites will likely be consolidated on one rack if possible and re-aimed. Same with the other retained sites. Small cells for coverage will need to be moved, possibly true for those providing better indoor coverage.
  12. If Sprint had more cash, I am sure they would be deploying 5G ready B41 equipment instead of 8T8Rs.
  13. Yes please. I and most other users in Ohio have turned off logging and/location at one time or another just by handling our phones. Quite frustrating/humiliating for those with only one phone. Embarrassing for those with more.
  14. Personally liked Ingenium's idea that liberal LTE roaming should only be used while on VoLTE to keep a call from dropping.
  15. Perhaps they are using the Clearwire PLMN because it is B2 rather than B25. Sent from my LG-LS997 using Tapatalk
  16. For me it will depend on price, the s9+ reduced price, versus waiting for 5g phones in January.
  17. Some small cells are for extended coverage while others are for rf shadows including building interiors. Look for hospitals, big box stores, and resturants. One of ours is for an extremely popular candy factory store. Also try to get out of the path of the host b41 signal. We have also had small cells not turned on for many months even after the electric meter is installed, so check the meter to see that it is drawing power between visits (the amount of power used is very small so it is unlikely you will notice a change while standing there). It can take 15 minutes for your phone to notice a small cell. Once found, your phone will then find it quicker in the future.
  18. My issue was on August 1. Sent from my LG-LS997 using Tapatalk
  19. Great job. Finding Massive MIMO deserves its own Premier Thread for the first few sites of each type. Sent from my LG-LS997 using Tapatalk
  20. Trade you a 2.5 for it. Sent from my LG-LS997 using Tapatalk
  21. One issue I saw with aggressive LTE roaming was AT&T 700 LTE would not let go as I drove through a Sprint town with triband LTE. Sent from my LG-LS997 using Tapatalk
  22. I keep looking for T-Mobile in all the Ohio logs I do. So far only a few snippets in unlikely roaming places. Sent from my LG-LS997 using Tapatalk
  23. If it is the product description that those are good or you ask a question on that and say they are good, you can get a refund based on the product not being as described.
×
×
  • Create New...