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
    If you do a lot of roaming, be careful with your streaming, as even streaming over CDMA1X can easily transfer 15-60 MB per hour. And that can eat fairly quickly into the 300 MB per month roaming quota. AJ
  2. WiWavelength
    What I am referring to? This... http://s4gru.com/index.php?/topic/3100-verizon-sells-700mhz-ab-blocks-for-19b/page__p__97563#entry97563 It is just a joke, a reference to a relatively famous movie monologue: AJ
  3. WiWavelength
    Hmm, you will need to post some engineering screen caps for us to diagnose fully what you are seeing. AJ
  4. WiWavelength
    My guess is that Craig got wind of my admonition that I posted the other day and got out while he still could... AJ
  5. WiWavelength
    That EV-DO Rev A indicator references the PCS carrier (e.g. PCS 0650 that you listed earlier). Network type indicator usually reflect the highest protocol revision network to which you are connected. EV-DO Rev A is a higher protocol revision than is CDMA1X. If you were connected to LTE, it would indicate that instead. AJ
  6. WiWavelength
    Norfolkin' way, Sprint has LTE in Norfolk? AJ
  7. WiWavelength
    Yes, CDMA1X and EV-DO have to be on different channels and can be in different bands. AJ
  8. WiWavelength
    No, as long as Ec/Io (signal quality) from a more distant CDMA1X 800 site remains above a certain threshold, your handset will not likely handoff to the closer CDMA1X 1900 site, not even if you are sitting on one of the panels. AJ
  9. WiWavelength
    I think that, if Sprint pursues carrier aggregation, it will be between the PCS G block and H block, especially since they are contiguous. For non contiguous aggregation, it could be between a 5 MHz FDD LTE carrier that Sprint has refarmed from its traditional PCS A-F block holdings and the 3-5 MHz FDD LTE carrier in SMR 800 MHz. But that is all predicated on Sprint actually electing to use carrier aggregation. And I am not sure that it will be necessary. As long as Sprint-Clearwire gets some 20 MHz TDD LTE up and running, then that will offer the cheap thrill peak speeds that many may be craving. AJ
  10. WiWavelength
    I am not sure why I find this slightly amusing, but in many parts of the country, 2000 square miles would not be thought of as a small area. And it would probably include 3-4 counties. I guess John has some San Bernardino County envy... AJ
  11. WiWavelength
    Jim, Joan, Bob, this is Craig... AJ
  12. WiWavelength
    Yes and no. This is somewhat similar to the Sprint-Dish interference issue, but I have not heard as much concern over the G block and H block uplink separation from the A block downlink. That is probably because the separation here is at least 10 MHz, while the separation between Sprint downlink and Dish uplink is at most 10 MHz and could be effectively zero. With carrier aggregation, though, the issue becomes exacerbated because, as I tried to describe, transmitter and receiver interference would be within the same mobile device. In other words, transmitter and receiver operating only 10 MHz apart would be also located only inches apart. And for reducing the negative effects of out of band emissions, distance is your friend, proximity your enemy. AJ
  13. WiWavelength
    I somehow missed this question a few weeks ago. The answer is, yes, Sprint probably can use carrier aggregation with two carriers in the PCS band, definitely if those two carriers are contiguous, probably if those two carriers are non contiguous. In the latter case, a problem could arise if Sprint were to aggregate the PCS G block with the PCS A1 block, or even worse, the PCS/AWS-2 H block with the PCS A1 block. The problem is that the G block and H blocks are at the very high end of each of the uplink/downlink segments, while the A block is at the very low end of each of the uplink/downlink segments. That brings the G block and H block uplinks within 10-20 MHz of the A block downlink. To illustrate, I have notated the following band plan diagram: If Sprint were to aggregate A1+G blocks or A1+H blocks, a mobile transmitting on the G block or H block uplink and receiving on the A1 block downlink would possibly interfere with itself -- the frequency separation between the uplink and downlink may not be enough. Think of it a bit like placing a speaker (transmitter) too close to a microphone (receiver). Now, the potentially unfortunate reality is that Sprint does hold a lot of PCS A block licenses (e.g. Los Angeles, San Francisco, Miami, Pittsburgh, Denver, Kansas City, et al.) because these, along with the PCS B block licenses, are the large MTA based licenses that Sprint won at the first PCS auction to go from zero to a nearly nationwide footprint in one stroke. AJ
  14. WiWavelength
    At least, we are not in the woods... AJ
  15. WiWavelength
    Yeah, it is interesting that DC-HSPA+ downlink speeds are pretty much on par with those of 5 MHz FDD LTE. Of course, DC-HSPA+ requires twice the spectrum bandwidth to achieve those speeds, so it is not as efficient as LTE, which also pulls way ahead in uplink speeds. AJ
  16. WiWavelength
    DC-HSPA+ peak uplink speeds will be no greater than those of HSPA+ because both are limited to HSUPA (max 5.76 Mbps). In other words, though DC-HSPA+ uses both carriers on the downlink, it still uses only one of the two carriers on the uplink. AJ
  17. WiWavelength
    At least the lower 25 MHz of this spectrum will likely be paired with 2155-2180 MHz to form the AWS-3 band -- essentially, an extension of the existing AWS-1 band. So, this spectrum makes the most sense for T-Mobile and VZW, since they are the most heavily invested in AWS. I doubt that Sprint will be a major player, if at all. AJ
  18. WiWavelength
    Actually, it makes sense. See, in T-Mobile's "network modernization" endeavor, W-CDMA 1900 deployment is not really separate from LTE 2100+1700 deployment. The antenna integrated radios being installed support both. AJ
  19. WiWavelength
    And just FYI, nothing from BlackBerry on the CDMA2000/LTE front yet. I did check. AJ
  20. WiWavelength
    And another... https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=616004&fcc_id=L6ARFF90LW AJ
  21. WiWavelength
    Okay, so I decided to do some digging through the FCC OET database. Here is an AT&T and/or T-Mobile LTE BlackBerry: https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=201077&fcc_id=L6ARFK120LW AJ
  22. WiWavelength
    The used bento box is a good idea, but judging by the stately appearance of that house, I think that Son might prefer a chicken bone chandelier. You probably have at least one of those that you can spare, right? http://www.comedycentral.com/video-clips/g544ez/chappelle-s-show-dave-on-mtv-cribs AJ
  23. WiWavelength
    Okay, I got about "tree fitty" to contribute to the cause. And speaking of pool, this house appears to have two of them, though one may be just for decoration. Now, what I want to know is when does the S4GRU invitation to the housewarming party arrive? Of course, we will need to bring some wine or chocolate babka... AJ
  24. WiWavelength
    Not to toot my own horn, but I think that I already posted 10 days ago the definitive evidence of T-Mobile LTE in KC. AJ
  25. WiWavelength
    That house is so big, it is going to require multiple Airaves. Good luck, Son, getting all of those on your account. In all seriousness, though, I am about $117.4 million short of the $117.5 million selling price, but I would not have paid a dollar for that house. From the outside, it really looks rather dowdy. The allure has to be the property and the location. AJ
×
×
  • Create New...