Cellular, Wi-Fi, GNSS

Let’s talk about cellular on the Nexus 4, which is for many people the main point of contention with the device. Google didn’t do itself any favors by initially posting incorrect specs for cellular compatibility, when in fact the Nexus 4 was capable of much more. Initially, that spec table showed inclusion of only HSDPA 21.1 (single-carrier WCDMA with 64 QAM), when in fact the Nexus 4 supports pentaband WCDMA up to HSDPA 42.2 (dual-carrier WCDMA with 64 QAM) courtesy of MDM9215. Of course, what gets left out is LTE support, and the reality of that choice is a device completely detached from carrier involvement. The realities of engineering hardware to support both LTE Bands 17 and 13 (for both AT&T and Verizon in the USA, respectively) basically necessitate at least two SKUs, and I have a feeling that Google just wasn’t ready to make that commitment. Band 4 (AWS) could essentially be supported with the power amplifiers and transceiver that already are onboard the Nexus 4, but again it ultimately comes down to a particular OEM choice whether these get supported. The rest of the LTE band support situation is similarly complicated, to say nothing of the political involvement required to support LTE and whatever CSFB (circuit switched fallback) or legacy hard handover is required for each carrier at present. I have a feeling that Google wanted to get the Nexus 4 out the door quickly and without making a million and one models it would have to build images and OTA delta updates for, and the result is a pentaband WCDMA phone with DC-HSPA+ support.

When I heard that LG would be making the next Nexus, I also heard that it would be WCDMA only. Honestly I thought it was obvious that those two go hand in hand to minimize carrier involvement in Google’s purest form of Android. The original goal of Nexus was to change the way that users shop for handsets, primarily in the USA. The goals were lofty at that time and the reality was that Google didn’t yet have the necessary infrastructure (like the Play Store) to do it, nor was hardware at the level required to deliver a single-SKU solution for all the UMTS bands out there. Galaxy Nexus was the first pentaband Nexus, thus it only makes sense for the follow up to likewise be pentaband WCDMA.

Internationally, DC-HSPA+ has widespread support, the reality is that in the USA AT&T’s lack of support for DC-HSPA+ is more of an aberration than the norm for UMTS networks across the globe. Not having LTE support would be much easier to stomach for AT&T subscribers if the carrier enabled DC-HSPA+. T-Mobile has always been something of a silent (or not so silent) target for Google’s Nexus phones, with the G1, Nexus One, and Nexus S all coming in AWS-flavors before 850/1900 (Cellular/PCS) flavors for AT&T, and T-Mobile has had DC-HSPA+ rolled out to nearly all of its WCDMA footprint for months now.

In reality, the cellular and RF architecture of the Nexus 4 is a dramatic improvement over the Galaxy Nexus, which was based on the still-ubiquitous Intel XMM6260 65nm baseband and lacked receive diversity or interference cancelation in its implementation. I was never really fully satisfied with RF performance on the Galaxy Nexus, and although I carried it as my daily driver for months, I could never shake that thought at the back of my head that I could definitely be achieving higher throughput with almost any of my other handsets even on AT&T (up to HSDPA 14.4, single carrier 16 QAM).

Google Nexus 4 - Network Support
GSM/EDGE Support 850 / 900 / 1800 / 1900 MHz
WCDMA Support 850 / 900 / 1700 / 1900 / 2100 MHz
Baseband Hardware Qualcomm MDM9215M + WTR1605L
UE Categories HSDPA Category 24 (43.2 Mbps), HSUPA Category 6 (5.76 Mbps)

Anyhow, the Nexus 4 is a dramatic improvement. It includes the latest and greatest 28nm Qualcomm baseband (MDM9215M), their flagship transciever (WTR1605L) and includes full receive diversity on all WCDMA bands.

Anritsu recently loaned me an MD8475A signaling tester base station emulator for testing devices, and I decided to go and check out the maximum theoretical performance difference between the Galaxy Nexus and Nexus 4 just for illustrative purposes. In this test I corded up the Galaxy Nexus (since it has external antenna ports) and placed the Nexus 4 on top of an antenna, and setup a simulation running an HSPA+ 3GPP Release 8 network running on UMTS Band 4 (AWS). I tested using UDP over iperf on this simulated network. There were additional cabling losses due to me not being able to cable up the Nexus 4 so I adjusted Tx power appropriately.

Galaxy Nexus - HSDPA 21.1


Nexus 4 - HSDPA 42.2 (Dual Carrier)

Corded up, the Galaxy Nexus can eek out just over 19 Mbps on 64QAM single carrier WCDMA which is the maximum that hardware supports. Moving to dual carrier on the Nexus 4 buys the device unsurprisingly roughly double the throughput at just shy of 40 Mbps. This is of course in basically an ideal signal environment for both devices.

In real world performance testing I turned to speedtest.net and running a bunch of tests, then making a few histograms of the resulting data. I’m still a big fan of the fact that T-Mobile has always been first to these upgrades to WCDMA, first with 64QAM, then with dual carrier (DC-HSPA+).


Stats Download Throughput (Mbps) Avg: 11.28, Max: 23.43, Min: 0.01, StDev: 6.98


Stats Upload Throughput (Mbps) Avg: 1.52, Max: 2.99, Min: 0.05, StDev: 0.48


Stats Latency (ms) Avg: 627.98, Max: 1577.00, Min: 117.00, StDev: 553.65

The speeds I see out of the Nexus 4 on T-Mobile are on par with my expectations for that network. The maximum downstream throughput we see at just shy of 24 Mbps is essentially the result of the maximum bitrate with two 16QAM WCDMA carriers aggregated together. Again getting to 64QAM on the downlink can be quite difficult, I’ve seen breakdowns where 64QAM only gets used sub 10% of the time in the real world for WCDMA. At cell edge the improvement that receive diversity brings should be dramatic for users upgrading from Galaxy Nexus to Nexus 4.


GNSS (Global Navigation Satellite System) is supplied courtesy MDM9215 on the Nexus 4, which offers GPS and GLONASS support. I’ve talked at length about this in other reviews, and like other implementations based around Qualcomm’s GNSS, the Nexus 4 locks very fast even indoors. There’s really nothing more to add about GNSS on the Nexus 4 except to note that it performs very well just like other MDM9x15 based devices I’ve played with.

There’s an Avago 3012 GNSS front end with LNA and filters for GPS and GLONASS on the Nexus 4 PCB that I was able to identify as well right near the GNSS antenna feed.


The Nexus 4 includes dual band (2.4 and 5 GHz) Wi-Fi support, which as far as I can tell is supplied by the Qualcomm “WCNSS” solution leveraging the digital baseband onboard APQ8064 and some external RF. I have no doubt the actual package is hidden under the last remaining EMI can I couldn’t remove on the Nexus 4 PCB right near the Wi-Fi antenna feed.

I noted that there’s an optimization toggle under Advanced for the Nexus 4 which changes some things around. There still is a band preference toggle as well. I tested the Nexus 4 the same way I always do with iperf on my myriad 802.11n networks and made some graphs.

WiFi Performance - iPerf

What’s curious to me is that the 5 GHz support for Nexus 4 doesn’t include 40 MHz support, instead the Nexus 4 attaches at 72 Mbps (the 20 MHz, short guard interval rate) on both 2.4 and 5 GHz. Likewise we see similar throughput on both bands. I have no complaints about range, the Nexus 4 is on par with my expectations.

Inside the Nexus 4 Speakerphone, Noise Rejection, Audio


View All Comments

  • hulabaloo - Tuesday, November 13, 2012 - link

    "We now have a form factor of device for every two inches of diagonal difference. "

    Should be three inches?
  • kyuu - Tuesday, November 13, 2012 - link

    Thanks for the in-depth review, Mr. Klug. Greatly appreciated.

    Question: Is there a review for the Lumia 920 in the works? I'd really love to see a thorough review on it like this one from yourself or Anand.
  • aryonoco - Tuesday, November 13, 2012 - link

    Thanks Brian, you've outdone yourself yet again. There is literally no reason to read any other Nexus 4 review.

    And also, a huge hats off to Anand for employing the very talented Brian and giving him a platform to show of his talents. You guys rock!
  • tuxRoller - Tuesday, November 13, 2012 - link

    I suppose the end result explains how thry achieved the price of $300.
    About the SoC, is there anyway AT could do a more detailed review of the s4 pro? Perhaps something like what you did for Swift?
    There is something seriously wrong with the s4 pro. Singke threaded performance shouod be really similar to the s4 but it is always as good bit slower. The memory performance has likewise regressed.
    Has there been actual architectural changes made that causes this or is it something software releated (perhaps core affinity is nonexistent causing processes to keep moving between cores thus harming single thread performance).
  • Slaps - Tuesday, November 13, 2012 - link

    ""First, audioflinger is set to 48 kHz which results in software resampling causing artifacts for 41.1 kHz source material.""

    I think you mean 44.1 kHz not 41.1 kHz :)
  • Conficio - Tuesday, November 13, 2012 - link

    Hi Brian,
    thanks for all the hard work that flowed into this review. Your drive to put out the best reviews is evident and you are succeeding when measured in the amount of data and information.

    However, I'm considering this phone for my wife, and wanted to send it to her for a read. That is until I realized the enormous amount of comparisons to other phones, to other chips, etc. make it a really hard read. Somehow the text is a review and a history lesson mixed in one. I'd wished there would be a structure like the following:
    * Introduction
    * Form factor, feel, usability
    * The phone's innards and benchmarks
    * Comparison to phone X
    * Comparison to phone Y
    * The good, the bad, the ugly and conclusion

    Funny that I'm as ambivalent about the phone. On the one side it looks great on price and basic features and independence of carriers and phone companies and their skin shenanigans (Why don't they compete on useful social or productivity software or at least make the skin removable). And I don't even need LTE, and can live w/o more memory. But then there is the thermal throttling going on and that just makes me uneasy. While it may not mean that much in today's real world applications, it is unnerving, that performance is something not reliable. It is there, but when you really use it it disappears. Reminds me of the unlimited ISP plans with speeds depending on your neighbor's usage and caps set so that they'll hurt in three years. I hope for really useful apps in three years to actually catch up to four cores.

    What also bother's me is the camera. The low light performance is xoxo. But this horrible yellow tint is not something I'd appreciate. Can anybody recommend PC/ Mac OS X software to correct this? Can one set up something like a monitor calibration profile?
  • Conficio - Tuesday, November 13, 2012 - link

    For a few years now we had the death grip test in every phone test. Has this problem disappeared altogether? How do we know? Due to tests or any other characteristic? Reply
  • staticx57 - Tuesday, November 13, 2012 - link

    Not a problem with the review itself, but chrome is so far behind on Android that it absolutely kills the experience. If you compare AOSP browser vs chrome, not only does the AOSP browser faster in feel but kills chrome in benchmarks. It is pathetic that the Nexus 4 with krait scores 1800 ms sunspider but the Gnex on AOSP scores much better says something about the software Google chose to ship with. Reply
  • Impulses - Tuesday, November 13, 2012 - link

    Google really needs to address this... Whether they need to start optimizing for the most popular SoC or simply update faster, it should not be that hard for them to improve on it. Reply
  • thesavvymage - Wednesday, November 14, 2012 - link

    is there a way to just install the AOSP browser on the nexus? mine should be arriving friday if they ship on time and on my dad's gs3 i wasnt too impressed with chrome either Reply

Log in

Don't have an account? Sign up now