Jump to content

WiWavelength

S4GRU Staff Member
  • Posts

    18,133
  • Joined

  • Last visited

  • Days Won

    429

Everything posted by WiWavelength

  1. WiWavelength

    EVO LTE Heat

    (the angle of the dangle) ÷ (the sag of the bag) - (the mass of the ass) = the coefficient of Odell's shame AJ
  2. If I am not mistaken, this link seems relevant. If so, "Buy Up" is being put down. http://insidesprintnow.wordpress.com/2012/06/08/early-upgrade-buy-up-replaced-by-upgrade-now/ AJ
  3. The Galaxy Nexus engineering screens line up quite consistently with the EVO LTE engineering screens. That has not always been the case. So, both are likely utilizing the same signal diagnostics embedded into Android 4.0. AJ
  4. With a -44 dBm signal, that handset could be practically humping an Airave. AJ
  5. kckid, you were not connected via eHRPD, which is just a variation on EV-DO. The data speeds that you measured -- both uplink and downlink -- are impossible for an eHRPD/EV-DO Rev A single carrier. So, you were connected via LTE. I investigated the site at 135th & Black Bob last night. Here is a screen cap of my EVO LTE connected via LTE: AJ
  6. Robert, will you post some screen caps of the ICS debug screen? I would be very interested to see the fields contained within, as every debug screen/engineering screen/field trial app presents signal diagnostics a bit differently. AJ
  7. Ah, but I got you to try it. My work here is done. AJ
  8. WiWavelength

    HTC EVO 4G LTE

    Or it could just be that both of you are slumming with your non Qualcomm LTE chipsets... AJ
  9. WiWavelength

    EVO LTE Heat

    The angle of the dangle is inversely proportional to the heat of the meat. AJ
  10. WiWavelength

    HTC EVO 4G LTE

    The basic difference is that Rev 0 retains the standard CDMA1X uplink structure, while Rev A uses a new EV-DO TDM uplink. So, when you get Rev 0 on a Rev A network, that just indicates that the handset could not establish a Rev A uplink. AJ
  11. Well, damn, I was in KC nearly every day this week. But it looks like I am going to have make another trip over to the city today to do some testing. AJ
  12. Robert, 135th St and Nieman Rd is about 2 miles due east of this site: KC03XC133. AJ
  13. Yes, that would be multi band carrier aggregation supplemental downlink, which is supported under LTE Advanced. I proposed the same idea about nine months to a year ago. I have quoted my proposal on several sites, including here at S4GRU in the post linked below. http://s4gru.com/index.php?/topic/770-lte-network-buildout-a-comparison-between-carriers/page__view__findpost__p__12777 AJ
  14. Yep. That is the mark. I mean, why else do you think that the letters VZW type out 666 on a standard cellphone keypad? You just cannot make this stuff up. AJ
  15. The advantage of a floating cell site is that it would not use satellite backhaul. It could use wireless backhaul to a terrestrial site ~100 miles away. AJ
  16. Does your Galaxy Nexus ever get very warm while you are browsing S4GRU? It may be trying to burn this into your hand. AJ
  17. Guys, a COW may be a viable alternative but only if it has access to backhaul. AJ
  18. Ryan is looking up Sprint coverage on a VZW iPhone. Sacrilege! Look out, everybody, that thing is apt to burst into flame any minute. AJ
  19. Lake Erie is part of the issue -- no obstructions, signals can propagate a long way. Plus, the spectrum sharing zone extends from the international boundary, which is in the middle of the lake, not at the shore. So, Cleveland is really only ~20 miles from the border. Interesting aside, US cellphone users along the south shore of Lake Erie have been known to pick up unintended international roaming charges from Rogers or Bell sites on the north shore. Not as far as you think. You are forgetting Vancouver Island. And, again, the international boundary is in the middle of the Strait of Juan de Fuca, not at the shore. AJ
  20. TheComputerMaster from San Antonio is visiting Puerto Rico, where he has another uncle who works for Sprint. AJ
×
×
  • Create New...