Jump to content

WiWavelength

S4GRU Staff Member
  • Posts

    18,133
  • Joined

  • Last visited

  • Days Won

    429

Everything posted by WiWavelength

  1. The Upper 700 MHz D block was deeded to Public Safety about a year ago. It will never be auctioned now. AJ
  2. T-Mobile does not have enough AWS spectrum on its own anywhere to deploy 20 MHz FDD LTE. That would require at least 50 MHz of AWS in order to continue one HSPA+ carrier and at least 25 MHz of PCS in order to redeploy DC-HSPA+ and continue GSM. AJ
  3. There is no MetroPCS in any of the Oklahoma markets, thus no additional AWS spectrum. AJ
  4. But, but, but what about that great "4G" HSPA+ fallback that all the tech bloggers are writing about? AJ
  5. Yeah, from memory, DFW is about the only market where T-Mobile-MetroPCS has enough AWS spectrum that 20 MHz FDD LTE would be feasible anytime soon, and even that is several years off. Do not believe all the hype that you read. When it comes to spectrum, I know the nitty gritty. AJ
  6. What do I think? Wishful thinking. NYC will not see 10 MHz FDD LTE from T-Mobile anytime this year, potentially not anytime next year either. Here are the real facts. T-Mobile holds 30 MHz of AWS spectrum in NYC, while MetroPCS holds 20 MHz. T-Mobile is currently running DC-HSPA+ (20 MHz) and deploying one 5 MHz FDD LTE carrier. That occupies T-Mobile's 30 MHz AWS bandwidth. MetroPCS, meanwhile, is running several CDMA1X carriers (10 MHz) and one 5 MHz FDD LTE carrier. That takes care of MetroPCS's AWS bandwidth. In order to combine T-Mobile and MetroPCS AWS spectrum to deploy 10 MHz FDD LTE, MetroPCS will have to reprogram all devices to use T-Mobile LTE instead of MetroPCS LTE, shut down its own LTE in the AWS C block, push out new PRLs to all subs, and relocate its CDMA1X carriers from the AWS D block to the C block. Only then can T-Mobile extend its bandwidth from 5 MHz FDD LTE to 10 MHz FDD LTE. In other words, it is a mess. Not gonna happen quickly... AJ
  7. Fine by me. Samsung plastic handsets are for the throngs of commoners. AJ
  8. No, it does not. Announcing a market does not mean that T-Mobile has "finished converting the whole market." Where in the world did you ever get that idea? AJ
  9. Worried about the camera seeing your "o-face" while you are browsing mobile porn? AJ
  10. No, the chipset has effectively nothing to do with band/band class capability. AJ
  11. Not yet. However, if Sprint is going to maintain unlimited data in the face of profligate use/abuse, do not be surprised to see traffic shaping in the future. AJ
  12. But than weez woodnt know if da carriers wuz throttlin us after 2 secs. Oh noes! AJ
  13. Does it use any less data? That would be a major improvement. AJ
  14. No, on the EVO LTE that is impossible, since EV-DO and LTE share a radio path. That, by the way, allows for SVDO. AJ
  15. At least, AT&T is finally getting close to having all native GSM overlaid with W-CDMA. It has taken only seven freaking years! AJ
  16. As big as the Note 3 is purported to be, it might be all over you. AJ
  17. You can keep knocking on that door, Josh, but SVDO doesn't live here anymore. No, that is band class √100. AJ
  18. https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=612557&fcc_id=ZNFLG870 AJ
  19. So, you are seeing something. That is good news. AJ
  20. Yeah, that would be a solution if SoftBank were not such a stupid name. AJ
  21. And there is your answer. LTE (and other 3GPP) networks use MCC-MNC, but CDMA2000 (3GPP2) networks do not. The primary Mobile Country Code for the US is 310, and Sprint's LTE Mobile Network Code is 120. So, 123456 is null data for both MCC-MNC, while 310000 is correct for the US but null data for the Mobile Network Code. AJ
  22. The two phones hashed to different carrier channels. http://s4gru.com/index.php?/blog/1/entry-318-can-toggling-airplane-mode-actually-improve-your-3g-data-speeds/ AJ
×
×
  • Create New...