WiWavelength

Maybe, maybe not. AT&T already has the largest PCS 1900 MHz and Lower 700 MHz holdings in the industry and has the WCS 2300 MHz band entirely to itself. AJ

I cannot get over Grain Management as the most oddly named licensee in the industry. Living in Kansas, we know a thing or two about "grain management." It looks like this: AJ

LTE is coming to the entire coverage area. So, LTE will cover your house sooner or later. But that should be the least of your concerns, as you should already have broadband Internet access with Wi-Fi at home. If not, then you are doing something wrong. As for a BBB complaint, that is just silly. You would have to show that your Sprint contract somehow specified that you would have LTE at your house within a certain time period. AJ

Jim Gaffigan: AJ

Sensorly should effectively tell the Galaxy Nexus, "Thanks, but no thanks," and discard its data. On second thought, I guess you could say that the Galaxy Nexus running Sensorly brings new meaning to the phrase "painting the town." AJ

Yes and no. AT&T is doing some token AWS LTE deployment right now, but that is only until AT&T further consolidates its Lower 700 MHz spectrum holdings and gets LTE up and running on Cellular, PCS, and WCS. Then, expect AT&T to bow out of AWS, selling off what little remains to VZW and/or T-Mobile. AJ

Hmm, interesting. I guess if you are a jealous boyfriend, you should become or pretend to be a wireless signal nerd. Then, you can check her handset for illicit SMS, and she will think that you are just geeking on the engineering screens. AJ

Do not worry. Just keep going down this path. Soon enough, you will no longer have a job nor a girlfriend who thinks you are weird. Then, you can walk the streets looking at panels full time. AJ

I always suspected the Prayer Tower served an ulterior purpose. It must be used for the coaches to scout the underground football team's secret practices. AJ

Really? I did not know that Oral Roberts plays football. AJ

Apparently, VZW is being advised by Leopold Stotch of Sanford Bernstein... AJ

Miss Sprint Cup, eh? What do you think of her "cup"? A, B, C, or D? AJ

Well, it was pseudo native coverage. Sprint disaggregated and partitioned the spectrum to Pioneer, which also owned the infrastructure. So, Sprint could do basically nothing when Pioneer stabbed Sprint in the back and shacked up with VZW. But that is all well established. In fact, it was the basis of the first article that I wrote for S4GRU last year. http://s4gru.com/ind...t-of-hypocrisy/ The issue here is that one member has claimed that, according to a recent Sprint coverage tool update, native coverage has decreased on the West Coast. But that member has been unable to substantiate what native coverage has disappeared. My eyes do not see it. The only problem that I notice is an inaccurately conservative mapping algorithm for the former Ubiquitel affiliate footprint in California's Central Valley. And that problem has shown up previously. So, right now, this situation is a bit like someone yelling, "Fire!" Then, others immediately try to determine the source of the fire. Yet, the fire may not actually exist. AJ

When I made those informal calculations of EV-DO capacity, I did so for a 16 hour day. I think using a full 24 hour day model is a bit unrealistic -- though, I do wish that wireless carriers would consider relaxing traffic shaping and/or caps for off peak data usage. So, per my 16 hour day estimates, the real world max for a 5 MHz FDD LTE carrier is somewhere closer to 3900 GB per month. Do you think my narrowing the scope to primarily the waking hours is reasonable? AJ

Wow, I had no idea that The Fantastic Four character The Thing's real name is Roger Entner. AJ

Agreed, that does suggest causation, rather than correlation. AJ

The Pioneer betrayal of Sprint was real. The problem here is that we have no solid evidence that any native or pseudo native coverage has been lost. AJ

Hmm, interesting. The Optimus G does use an in cell digitizer. The glass, touchscreen, and LCD panel are all sandwiched into one, thereby reducing depth and internal reflections. That seemed like a uniformly positive development, but it apparently does have downsides. AJ

No big deal. I am just trying to put to good use the network operation knowledge and spectrum licensing data that I have accumulated over the years. But I could not speak with any authority about sites on the Michigan/Indiana border 700 miles from me if not for the data extraction and mapping work that Robert and digiblur have so diligently completed. So, give full credit to the team here at S4GRU -- we depend upon and build off the work of each other. AJ

Network Vision may or may not make it better. Yes, you will be on all Sprint corporate Samsung infrastructure, rather than the iPCS affiliate legacy mix that you have now. But you will still live near a PCS 1900 MHz license boundary, not to mention an MSC boundary. For example, in Sturgis, you are in the Detroit MTA, where Sprint holds the PCS B block 30 MHz license. But across the state line, Howe is in the South Bend-Mishiwaka BTA, where Sprint holds the PCS D block 10 MHz license. That means your device must switch PCS carrier channels as it crosses the state line. Moreover, your site in Sturgis is backhauled to the Lansing_MSC_2, while the site in Howe is backhauled to the Fort Wayne_MSC_1. So, in the end, when you cross the state line, you experience an inter frequency, inter MSC hard handoff, and those are almost always hit or miss. You can observe the above phenomenon by watching your engineering screens as you cross the state line. You will see SID, NID, CDMA1X carrier channel, and EV-DO carrier channel change. Now, because of the transaction with USCC, Sprint will soon hold PCS B block spectrum in the South Bend-Mishiwaka BTA. So, the chances are good that your PCS carrier channels on both sides of the state line will be harmonized. Additionally, Sprint holds the same SMR 800 MHz spectrum on both sides of the state line. Thus, eventually, your CDMA1X 800 carrier channel will likely remain a consistent SMR 476. But the MSC handoff between Lansing and Fort Wayne (or vice versa) will remain. AJ

For all people, creating fallacious straw man arguments diminishes the rationality of their positions. AJ

Just a quick clarification, how do you know that the PN mismatch is due to Network Vision? Over the years, I have encountered a few rare sites that use different PNs for CDMA1X and EV-DO. But I have not encountered any PN changes associated with Network Vision. AJ

Well, the Lower 700 MHz D/E block 6 MHz licenses have made it into 3GPP standards. Classified as band 29, one or both are paired with band 2 PCS 1900 MHz or band 4 AWS 2100+1700 MHz using downlink carrier aggregation. AJ

I like the methodology, but as long as we are doing some back of the napkin math, I would adjust some of the figures. The 1.8-4.2 percent figure is derived from wired broadband data caps. But is wired broadband an appropriate parallel for wireless broadband? I say not. The number of subs that share a cable node, for example, is almost certainly much lower than the number of subs that share a wireless sector. I ran some informal calculations a month or two ago. See below: http://s4gru.com/ind...post__p__111617 Now, if we use the low end estimate of 600 subs per sector, the fair and proportional cap per sub would be 0.17 percent of the total. Admittedly, that would be a bit extreme, since it would not take advantage of the synergies that come from some using less, some using more than their fair share. But the 1.8-4.2 percent figure may be a bit extreme in the other direction, since only a relatively small number of the 600 subs would have to reach the cap in order to soak the sector completely. AJ

Actually, most other smartphones share this same limitation, and the FCC OET docs disclose it. For example, note the simultaneous transmission mode table in my HTC One article: http://s4gru.com/index.php?/blog/1/entry-342-updated-all-for-htc-one-htc-one-for-all/ Modes can incorporate either Wi-Fi or Bluetooth but simultaneous Wi-Fi + Bluetooth *transmission* is not supported. AJ