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
    I am not sure that the casinos on The Strip would allow RootMetrics to waltz in with its multi handset test gear. The casinos want people gambling, not talking and idling time on their cellphones. There are business reasons why casinos tend to be daylight and RF black holes. AJ
  2. WiWavelength
    No, as far as I know, firmware updates were not distributed, were not necessary. The hardware always was capable of carrier bandwidths other than 5 MHz FDD. It just was not tested and authorized for those other bandwidths -- because they were not expected to be used. FCC authorized handsets contain latent capabilities out the wazoo. Remember the Nexus 4 from three years ago? It was supposed to be a GSM/W-CDMA only handset, but band 4 LTE worked, though it was not tested and authorized. AJ
  3. WiWavelength
    We do? We know how the complicated 600 MHz incentive auction is going to play out? I think that it has the prospects to and hope that it does fail spectacularly. We just are throwing way too much spectrum at a problem in the hopes that the free market will solve it. I have been saying that for years. And if the auction does produce little more than a whimper, I may never stop laughing. AJ
  4. WiWavelength
    Not really nationwide. But it is getting there. However, what is the purchase price? I bet the spectrum holding companies are making a nice profit. T-Mobile, if you want to be the pied piper, you have to pay the piper. Or, more accurately, pay to be the piper. And will these Lower 700 MHz expenditures affect participation in the problematic 600 MHz auction? AJ
  5. WiWavelength
    Your setup has become tiresome. Now is ze time on S4GRU vhen ve dance! AJ
  6. WiWavelength
    AJ
  7. WiWavelength
    No, those early single band LTE devices that seemed limited to 5 MHz FDD always were capable of at least 10 MHz FDD. They just were not tested and authorized for other LTE carrier bandwidths. Since then, all have received Class II Permissive Change filings in the FCC OET database. AJ
  8. WiWavelength
    To be clear, USCC EV-DO roaming works fine, just no LTE roaming at this time. We shall see if that changes. AJ
  9. WiWavelength
    Yes, talkative people. Sad. One feels sorry for them -- but there it is. AJ
  10. WiWavelength
    And that unpaired band 29 is worthless to anyone but AT&T. Not even that valuable to AT&T. AJ
  11. WiWavelength
    Yes. This is old news. The Sprint coverage tool has shown and some S4GRU members have reported LTE roaming on USCC since late last year. http://s4gru.com/index.php?/blog/1/entry-401-psa-lte-roam-if-you-want-to-plus-it-may-count-as-native-coverage/ AJ
  12. WiWavelength
    I am sorry to bust your balls, but you need to read more of this thread. This SignalCheck Pro feature/bug in recent Android builds has been thoroughly discussed. The Nexus 5X -- like all single RF path handsets -- is incapable of being connected to CDMA1X and LTE simultaneously. That causes the issue. AJ
  13. WiWavelength
    AJ
  14. WiWavelength
    Yup. Saw that yesterday. Shocking, just shocking that this "unlimited" plan shortly proved unsustainable. https://en.wikipedia.org/wiki/Tragedy_of_the_commons AJ
  15. WiWavelength
    And that extra 2.3 makes all the difference in the world. AJ
  16. WiWavelength
    Uh, decades more network site development, tens of millions more subscribers, and billions more dollars. AJ
  17. WiWavelength
    Does LTE roaming actually work, though? We have not had any reports yet of LTE roaming on the three unlocked BYOD handsets, only on Sprint branded handsets. AJ
  18. WiWavelength
    The Sprint-AT&T spectrum transaction seems directed mostly at problem markets, those with band 25 and/or band 41 limitations. Phoenix does not have a band 25 PCS problem. It has a band 26 SMR problem. Thanks, Joe Arpaio! Phoenix already has a band 25 second carrier at 5 MHz FDD. In the relatively near future, that will expand to 10 MHz FDD. So, Phoenix will have the band 25 first carrier at 5 MHz FDD, the band 25 second carrier at 10 MHz FDD, the band 26 carrier at 5 MHz FDD, and at least two band 41 carriers at 20 MHz TDD. Phoenix will be fine. AJ
  19. WiWavelength
    T-Mobile handsets do not support SVLTE. They do simultaneous voice/data via VoLTE or e/CSFB fallback to W-CDMA. AJ
  20. WiWavelength
    Yes, most/all of these markets will not add a band 25 second carrier. Instead, they will expand the band 25 first carrier to 10 MHz FDD. It will be the only band 25 carrier. The other carriers will be all band 26 and/or band 41. AJ
  21. WiWavelength
    Marketwise, it is largely a matter of location and circumstance -- where AT&T has spectrum that benefits Sprint and vice versa. AJ
  22. WiWavelength
    So, you are going to leave the shit just lying there on your phone? And who shit on your phone in the first place? AJ
  23. WiWavelength
    Shh, do not tell the others about the band 41 second carrier. They can stay on the slowed down first carrier, and you can have 2x CA all to yourself. AJ
  24. WiWavelength
    And I believe I quoted one of your previous posts, you quoted one of my previous posts, or both. But for me to be clear, too, I was not trying to call you out -- or anyone in particular out. Sometimes, I quote posts just to serve as examples. I digress. To address the bits/bytes issue above and in your previous post, I think that you are making too much of it. It clearly is a typographical error. An executive, engineer, or PR person screwed up when writing that release. People who should know better still use MB/s or MBps when they really mean Mb/s or Mbps. The total data transfers were measured in TB. The average data speeds were measured in Mbps. Despite any typographical error, that really should be obvious. AJ
  25. WiWavelength
    Yes, this is off topic, but as you are a first time poster, we can answer here. And the answer is that it depends. Do you want to be a technician or an engineer? If you want to be a technician, you probably can pursue an associate's degree at a two year community college or vocational/technical school. Then, you may need additional certification training. If you want to be an engineer, the road is considerably more difficult. You need at least a bachelor's degree, possibly even a master's degree in engineering or computer science. To even consider that, you should have a strong aptitude for math and science in high school classes (AP Calculus, AP Physics, etc.), high GPA, and high standardized test scores. Without those attributes, you are unlikely to succeed in an engineering program. Then, to go to a top engineering school (MIT, Stanford, Georgia Tech, etc.), especially for graduate studies, you need to have a high GPA and standardized test scores among the best in the nation. AJ
×
×
  • Create New...