Jump to content

WiWavelength

S4GRU Staff Member
  • Posts

    18,133
  • Joined

  • Last visited

  • Days Won

    429

Everything posted by WiWavelength

  1. "Dr. Strangelove or: How I Learned to Stop Worrying and Let the Tri Band Network Do Its Thing" AJ
  2. Is it still new in box? Is somebody just cashing out a subsidized upgrade? AJ
  3. No, we did not miss it. Both Milan in his comment and I in my article mention the likelihood of the Snapdragon X7 LTE (MDM9635) standalone baseband. The RDFs may lend some credence to that connection, but they also list the processor chipset as "Istor," which makes no sense. So, that calls the accuracy of the RDFs into question. AJ
  4. It happens on the 2014 Moto X, too. It is a glitch. I am not trying to be gruff with you. But too many wishful thinkers will take your screenshot to mean that SVLTE is making a comeback. AJ
  5. Simultaneous reception is not the same thing as simultaneous transmission. AJ
  6. That would be great. But be precise about location. Said engineering screen cap basically would need to come from St. Louis proper to be conclusive -- because the Chicago MTA extends surprisingly close to St. Louis exurbs on the Illinois side. AJ
  7. A few thoughts... EARFCN 26315 is the uplink. Focus on the downlink EARFCN, which would be EARFCN 8315. Generally, logging either is fine. But TD-LTE throws a wrench into the mix -- with invalid uplink EARFCNs. The PCS B block spectrum acquired from USCC is in the Chicago MTA. Parts of Northern Indiana, such as Ft. Wayne, and much of Southern Illinois are still in the Chicago MTA. So, reports of a second carrier in those areas with the same EARFCN as in Chicago are not exactly new info. Those areas are all part of the Chicago MTA. Now, St. Louis is a whole new ballgame -- to the cheers of insufferable Cardinals fans. The USCC spectrum acquired there is from the St. Louis MTA PCS A block license. It is not the same spectrum as in the Chicago MTA, so it cannot contain the same EARFCN. But Sprint itself has long held the PCS B block license for the St. Louis MTA. Thus, a second band 25 carrier in St. Louis with the same EARFCN as in Chicago would have to come from Sprint's own spectrum. AJ
  8. The makeover is not complete. S4GRU still needs exfoliation, eyebrow waxing, and maybe some Botox. Also, photograph S4GRU only on its good side. AJ
  9. Yes, you did not hear the news? Mighty Canada invaded. We were no match for the Mounties, and we lost Montana -- now known as South Alberta. AJ
  10. The gold one has to be delivered from Fort Knox. Get it? Gold. Fort Knox. Samsung. Knox. AJ
  11. An IKEA just recently opened in the Kansas City metro. I saw a DAS there. But to get coverage, you had to assemble it yourself. AJ
  12. Reddit has driven a significant uptake in recent traffic to this article. http://www.reddit.com/r/Android/comments/30jykd/cellular_radio_rf_comparison_samsung_s6_and_htc_m9/ AJ
  13. No, that is incorrect. For just two of several examples, the AT&T variant iPhone 6 supports band 29 Lower 700 MHz D/E block carrier aggregation, while the AT&T variant Galaxy S6 supports that and band 30 WCS 2300 MHz. Those are going to be important capacity bands for AT&T. Soon enough, lacking those bands on AT&T will be like lacking a tri band device on Sprint. And I, for one, am happy about that. A user should not be able to take a Sprint variant device to AT&T and have a great experience -- until AT&T reciprocates and makes its variant devices fully Sprint capable. AJ
  14. No, the RootMetrics methodology is fine. It may not be perfect, but it is the best available -- more systematic and rigorous than the assessments of any casual wireless users. And the east side was tested thoroughly and equally just as it should be. You are just fixating on an area where you have experienced service that you deemed less than satisfactory. http://www.rootmetrics.com/us/rsr/wichita-ks AJ
  15. Actually, it came from a decade old post at the anti S4GRU: SprintUsers. AJ
  16. ##DEBUG# If you do anything else first, you are not worthy. AJ
  17. More and more, ericdabbs, you are becoming a Sprint detractor. T-Mobile does not have generally more dense urban coverage. You are reflecting on just your own market, Southern California, which T-Mobile did not build. Cingular nee PacBell built it, and T-Mobile bought it in divestment. Cingular was focused solely on California and a sliver of Nevada -- it was just a regional operator in the West. Regional operators often do have more dense coverage because they can concentrate on just their limited areas. Plus, Cingular had no GSM roaming partners anywhere nearby to fill in gaps. So, Cingular had to build a dense network. In the end, get outside of Southern California. Travel the country. In many other major markets, T-Mobile has equal to or worse urban coverage compared to that of Sprint. Otherwise, T-Mobile would not have its bad reputation for in building signal. Sprint beats T-Mobile in that regard -- even before SMR 800 MHz. AJ
×
×
  • Create New...