Jump to content

WiWavelength

S4GRU Staff Member
 View Profile  See their activity

  • Posts

    18,133

  • Joined

  • Last visited

  • Days Won

    429

 Content Type 

Everything posted by WiWavelength

  1. WiWavelength
    You can try an online petition, but I doubt that it will have any positive results. Sprint has ostensibly made a business decision that roaming in the area is less costly than building out native coverage. That also tends to signal that Sprint has limited market share, so you may be overestimating the number of Sprint subs at Stennis. Otherwise, Sprint would likely be more interested in building at least a roaming mitigation site to retain subs like yourself who may be terminated for excessive roaming. Now, I have this question for you: why are you beating your head against the wall over this? Sprint does not sound like the right carrier for you at Stennis. Since multiple other carriers do offer native coverage there, why not go with a carrier that offers a better fit? AJ
  2. WiWavelength
    Bathed, huh? http://members.tripo...BB/batheher.wav I could not resist... (Try opening the clip in a new window.) AJ
  3. WiWavelength
    Nope, no offense, but you are wrong. The Joplin "metro" is in the Kansas City MTA per Sprint's PCS license and MSC. But it is in the Missouri market per Sprint's internal organization. Nearly a year ago, Robert and digiblur put together a superb county by county market map: http://s4gru.com/index.php?/page/index.html/_/articles/nationwide-sprint-market-map-is-here-r31 AJ
  4. WiWavelength
    Here is the easy solution to your agita: do not run so many speed tests. What are you trying to prove? You do realize that you are just wasting capacity. By running speed tests, you are just reducing capacity for others and yourself. AJ
  5. WiWavelength
    bananakeg, what you actually meant was "I don't know if this is just my experience..." The quality of your cellphone service has nothing to do with you, personally, so runagun was just making a good natured joke about that. AJ
  6. WiWavelength
    Not many FDD bands do have the uplink segment at a higher frequency than the downlink segment. The most notable one right now is VZW's Upper 700 MHz C block license, which is its exclusive LTE band. In uplink x downlink format, it is 776-787 MHz x 746-757 MHz. So, the uplink is 30 MHz higher than the downlink. That was done to place the Upper 700 MHz C block downlink and Lower 700 MHz C block downlink directly adjacent to one another. Had the Upper 700 MHz band followed a more traditional duplex, then the Upper 700 MHz C block uplink would have been directly adjacent to the Lower 700 MHz C block downlink. And, as discussed above, uplink and downlink on adjacent frequencies does not tend to work well. See the band plan: http://wireless.fcc.gov/auctions/data/bandplans/700MHzBandPlan.pdf AJ
  7. WiWavelength
    Wow, that "upgrade" will cause a lot of areas in the western US to lose OnStar coverage. AJ
  8. WiWavelength
    Come on, Eric, your rhetoric on the LTE band matter is really over the top. Tone it down. None of us are privy to the decisions made behind closed doors, yet you act as if Sprint and HTC are necessarily myopic or incompetent. If you believe that, get out, move on. Find another carrier and/or another device maker because I see neither Sprint nor HTC changing to please you anytime soon. Also, trust me, as soon as LTE 800 and TD-LTE 2600 capabilities are added to a device, some will eventually complain that their particular markets have neither LTE 800 nor TD-LTE 2600 -- just like many "4G" handset subs have complained about lack of WiMAX. It just goes to show that you cannot please everyone. AJ
  9. WiWavelength
    "[M]issing out big time?" Are you asking a question or making an assertion? I think "missing out big time" is an overreaction. Unless Network Vision deployment picks up dramatically, LTE 800 will likely still be a while in coming, and due to SMR 800 MHz spectrum issues, many markets will not get LTE 800 for years, if ever. So, Sprint needs to focus on finishing LTE 1900 rollout before doubling back for LTE 800. As for TD-LTE 2600, that is still under Clearwire's control. We may not see TD-LTE 2600 in any devices until the Sprint-Clearwire-Dish wrangling gets sorted out. Even then, TD-LTE may be limited at first to data only devices (e.g. hotspots, cards/sticks) that tend to use greater amounts of data and can actually take advantage of the higher speeds that the bandwidth of TD-LTE 2600 can offer. AJ
  10. WiWavelength
    No one "needs" SVDO, though you may want that feature. If so, you will likely need to hang on to your current handset or stick within the handful of handsets that were released with SVDO last year, as there has not been a new SVDO capable handset in the last six months. AJ
  11. WiWavelength
    One possibility, the orphaned 2180-2200 MHz downlink could be used for downlink carrier aggregation. A second possibility, it could be paired as downlink with 1755-1780 MHz uplink that is being bandied about for government/private spectrum sharing. It would be very similar to an extension of the existing AWS-1 2100+1700 MHz band. Gotta run, but I can dig deeper and elaborate more late tonight... AJ
  12. WiWavelength
    LightSquared's L-band 1600 MHz uplink is unencumbered; it was the 1500 MHz downlink that ran afoul of GPS. I think what Tim is getting at is the potential for pairing the LightSquared 1600 MHz uplink with the Dish 2000 MHz downlink (converted from uplink). Sale of LightSquared's uplink spectrum could also provide some relief for its lien holders. AJ
  13. WiWavelength
    We have had a variation on this discussion before. Recall that Dish's S-band/AWS-4 spectrum is 2000-2020 MHz x 2180-2200 MHz. The PCS G block is 1910-1915 MHz x 1990-1995 MHz, and the PCS/AWS-2 H block is 1915-1920 MHz x 1995-2000 MHz. In all three cases, the lower segment is the uplink, the higher segment, the downlink. The problem is that places G/H downlink and Dish uplink in very close proximity. And RF wise, uplink and downlink do not get along any better than Sprint and Ergen do. Now, if Dish were to convert its lower segment to downlink operation, then G, H, and Dish lower segment spectrum would all operate like an extension of the PCS band downlink segment. And there would be peace on earth. AJ
  14. WiWavelength
    The problem with Asus' original version of the Transformer Prime is that its back was fully aluminum with no RF window(s). That was changed in the TF700T version, which added a plastic strip across the aluminum back. As for the HTC One, AnandTech reports that isolated segments of the aluminum back actually are the antennas. http://www.anandtech.com/show/6754/hands-on-with-the-htc-one-formerly-m7 AJ
  15. WiWavelength
    greenvillesc, as Ian explains, SVDO capability affects only simultaneous CDMA1X voice and EV-DO data. It has no bearing on simultaneous CDMA1X voice and LTE data -- that is called SVLTE. Also, as I explained in the article, SVDO requires separate RF paths for CDMA1X and EV-DO. In Sprint handsets over the last six months, those separate paths have not been present. CDMA1X and EV-DO have shared a path, LTE on the other path, and that has precluded SVDO. Now, I am not sure why I did not notice this previously, but the SVDO capable handsets almost exclusively utilized the Qualcomm MSM8960, which is a processor and baseband modem rolled into one. Since the transition to a more powerful, standalone dual core or quad core processor plus a separate Qualcomm MDM9615 baseband modem, SVDO has gone away. So, not to mistake correlation for causation, but the MDM9615 may not support separate RF paths for CDMA1X and EV-DO. And the correlation is quite strong. AJ
  16. WiWavelength
    T-Mobile already has advanced backhaul at its urban sites. Raising new panels and base stations is not easy, but T-Mobile does not have to wait on backhaul for those sites. The problem that T-Mobile faces is that it has too many rural sites that not only lack advanced backhaul but also are still GSM only. AJ
  17. WiWavelength
    Yes, I know that site very well and have even had it on my spectrum analyzer. Sprint is co-located on it. The install was done back in the late summer or early fall, though I cannot recall if LTE is active on the site yet. AJ
  18. WiWavelength
    Sorry, children, the pool is now closed for "adult swim." It will reopen tomorrow. AJ
  19. WiWavelength
    How many people? Seriously? It should be everyone. But maybe not paying attention to thread titles is a Forum Bummer and Yabba-dabba-dootalk thing. AJ
  20. WiWavelength
    No app will consistently locate Sprint sites. That requires a little bit of know how and legwork. AJ
  21. WiWavelength
    Another good reason not to use those substitutes for the real thing... AJ
  22. WiWavelength
    I think it a bit strong to call this a "mistake." We really do not know the reasoning behind this decision and whether it lie with Sprint, HTC, or both. Only time will tell -- if we ever know. But to temper the emotions on both sides a little bit, I am beginning to believe more and more that it will still be a while before we see any significant LTE 800 or TD-LTE 2600. Many who tend to upgrade on a yearly basis will already be on to their third generation of LTE handsets by then, anyway. AJ
  23. WiWavelength
    VZW has also had major issues with its LTE and eHRPD/EV-DO networks not getting along and suffering major outages. So, I would not hold up VZW as a shining example of how to integrate LTE and CDMA2000. It is not as simple as you make it out to be. Regardless, as I stated previously, removable SIMs are upcoming on the internal Network Vision roadmap, but they were not implemented right away for a reason. Give Sprint the benefit of the doubt. AJ
  24. WiWavelength
    Difficult to say, but this is not exactly a new development. For about the past six months, most/all new AT&T handsets have included those four LTE bands. AJ
  25. WiWavelength
    Just be careful not to get too comfortable in that bathroom, John... AJ
×
×
  • Create New...