WiFi

The Galaxy Nexus uses Broadcom’s BCM4330, which is starting to pick up steam and become just as ubiquitous as the BCM4329 it replaced. The Galaxy Nexus’ BCM4330 includes both 2.4 and 5 GHz WLAN connectivity, just like the SGS2 in fact. What’s particularly notable is that Android 4.0.x now includes the proper prioritization for each WiFi band, and also includes the ability to set preference for one band for the other. By default, when faced with the same SSID on both 2.4 and 5 GHz, the Galaxy Nexus correctly chooses the 5 GHz AP if the signal is favorable, then falls over to 2.4 GHz when its link quality on that band would be better. Other than this notable change, the remainder of the WiFi settings panes are unchanged. The WiFi sleep preferences and the main scan and connect page does get a minor facelift and change, however.

 

The Galaxy Nexus latched onto my 802.11n APs on both 2.4 and 5 GHz and used 20 MHz long guard interval rates at 65 Mbps the same as other BCM4330 based devices. Throughput is unsurprisingly very good on the Galaxy Nexus in our WiFi test, which consists of downloading a 100 MB PDF hosted locally over WiFi. Of course, since we can now control and choose which band the device uses, I tested on both 2.4 GHz and 5 GHz, both with a negotiated link rate of 65 Mbps.

WiFi Performance

WiFi range on the Galaxy Nexus is good as well, I can make it to the same place before hopping off my network as other devices. I have gotten a few emails and read reports about power-save mode incompatibility with some APs that causes it to drop off when on standby mode. Since we've seen BCM4330 work just fine on other devices, I have no doubt this is a software issue which will be fixed soon. 

Speakerphone

As usual I also measured speakerphone volume on both variants of the Galaxy Nexus using a sound datalogger. There is apparently a difference between the two models, possibly from different acoustical chambers in the vibration unit and antenna. Also there’s possibly still a difference as a result of the different voice coders in use, and the different dynamic range.

Speakerphone Volume - 3 Away

Either way, the two test differently, and subjectively my experience backs those measurements up. I found the GSM/UMTS Galaxy Nexus a bit too quiet while using Google Navigation, and the CDMA/LTE Galaxy Nexus on the quieter side but totally useable for Navigation.

GPS

Just like the SGS2, the Galaxy Nexus uses a SiRFStarIV GSD4t for GPS. Subjectively the Galaxy Nexus GPS doesn’t lock quite as fast as some of the other GNSS solutions that are integrated into the cellular basebands in phones, but it does get the job done pretty fast. I see a time to first fix of between 4-7 seconds depending on visible sky swath presented to the handset.

I did receive a few emails from readers with reports of some Galaxy Nexuses shipping with GPS issues or taking too long to lock. One of my friends with a CDMA/LTE Galaxy Nexus also reported that he couldn’t get a GPS lock at all for Google Navigation. I’m not entirely sure what the deal is here since I never was able to encounter this behavior, although manually downloading the A-GPS data (ephemeris) using a tool like GPS Status seems to in general helps mitigate those problems when they do happen. This just manually re-downloads the xtra.bin file from http://xtra1.gpsonextra.net/xtra.bin as configured in gps.conf. I have to admit that I didn’t encounter any GPS issues in my time with the Google Nexus (CDMA/LTE or GSM/UMTS version) so far.

Audio

We’re going to do a more in-depth audio analysis with the Galaxy Nexus when we have our testing suite more fleshed out, and possibly bring you Francois Simond’s thoughts once more. For now however, we have some RMAA runs I talked about a while ago in another review, and my own impressions with Galaxy Nexus sound after using the device for a while now as my primary music player with some Shure SE535s.

 

First off, the Galaxy Nexus out of the box is pretty decent subjectively. The Galaxy Nexus uses TI’s TWL6040 low power audio codec for its DAC and other audio responsibilities, alongside the vibrator actuator. We’ve seen some other TI audio codecs (like AIC3254 in the HTC Sensation) but this our first time seeing TWL6040. Almost immediately I noticed that there isn’t any constant high frequency whine present like I’ve heard on so many phones lately (Bionic, SGS2, others), and it’s hard to hear any noise when the DAC turns on and off after music stops playing. Even plugged into USB power, the device also doesn’t pick up any more noise or change at all. There’s also almost no CPU noise, though if you listen very carefully you can indeed hear some state changes, but it’s very minimal and very difficult to pick out.

Though the frequency response isn’t entirely flat as shown, the Galaxy Nexus doesn’t sound bad subjectively. Our testing here is just a RMAA run from line out on the devices to line in on an ASUS Xonar Xense sound card. In addition, testing is done at 44100/16 bit on the devices - Android will downsample anything more than this.

https://images.anandtech.com/reviews/gadgets/Motorola/RAZR/Three/fr.png
From 20 Hz to 20 kHz: +0.10, -0.62 (dB)

Noise on the Galaxy Nexus also isn’t bad, definitely better than the RAZR we tested earlier.

Noise Level
Noise Level: -96.2 (dB, A weight)

Dynamic range shows the difference in level between the maximum output and minimum output on the smartphone. This is limited by voltage swing and system noise. Galaxy Nexus again here looks pretty good, minus a few spikes.

Dynamic Range
Dynamic range: 96.0 (dB, A weight)

The two total harmonic distortion charts are next, which are the summation of integer multiples of the test frequency and expressed as a ratio of the input signal (in this case at 1 kHz). THD+Noise gives all frequencies except the input signal. The Galaxy Nexus is pretty good here, but still has some spikes at a few noteworthy integer multiples, plus some odd spikes at high frequencies.

THD + Noise
THD %: 0.0088

Intermodulation distortion is similar to total harmonic distortion, however it applies two input signals and then measures the signal at all frequencies except the two inputs. In this case, the two signals are on opposite sides of the spectrum. Galaxy Nexus ends up not looking too bad here although there are disconcerting spikes above 1 kHz that I can’t explain.

IMD
IMD + Noise %: 0.013

Finally stereo crosstalk is pretty flat on the Galaxy Nexus.

Stereo Crosstalk
Stereo Crosstalk: -87.4 dB

Again, this isn’t meant to be a totally comprehensive analysis of the Galaxy Nexus’ sound characteristics, just some educated impressions. Subjectively the Galaxy Nexus sounds nice and clean, and is absent of the annoyingly audible background noise and whine that’s present on some of the other noteworthy phones we’ve tried as of late. Francois (supercurio) has expressed a few times that the Galaxy Nexus has good audio potential, and that alone should tell you something.

Cellular Performance and Call Quality on Galaxy Nexus Battery Life Analysis
Comments Locked

185 Comments

View All Comments

  • Brian Klug - Thursday, January 19, 2012 - link

    Interesting. I originally picked S5K4E5 family as being the likely choice - as it's the BSI equivalent, and though that was what was inside until I decompiled/dug around inside the ducati-m3.bin file as noted in the review.

    You'll see numerous references to "S5K4E1G" and none for "S5K4E5" which is the BSI version. EG:

    "CSI.COMPLEIO¿F¿MSP.NEW_SENSOR¿S5K4E1GA¿F¿S5K6A1GX03¿MSP.NEW_LENS¿F¿VM149C¿MSP.NEW_CSICSI2A¿FCSI2B"

    It could very well be BSI since they've x-rayed it.

    -Brian
  • tom5 - Thursday, January 19, 2012 - link

    Official Samsung site says SGS II has quad band 3G and Galaxy Nexus has penta-band 3G, so there's a difference in GSM connectivity:
    http://goo.gl/gvIWV
  • Stas - Thursday, January 19, 2012 - link

    I appreciate the thoroughness in this review, Anand.
    Interesting, however, how I find so many things about the software completely irrelevant to someone who just can't leave things vanilla. Browser performance and features, launcher scrolling, screenshots, on-screen keyboard, etc. None of those things are in their original Android form on my phone (SGS2). Some issues have been addressed by Samsung, some by XDA developers, some by myself. As a result, I believe I have the perfect phone on the market (for me). Reading every section of this article, I kept finding myself thinking, "Heh, my phone doesn't have that problem," or, "Mine does that even better," or, "would suck to have that phone instead of my Galaxy."
    I always thought advancement in tech = replacing devices sooner. However, after reading this review, I have no desire whatsoever to replace my current phone with the new flagship. I always get that feeling when I read a video card review, CPU review, SSD review, etc. But I feel like my phone lacks nothing, and I will stick with it for a long while. Customizing and tweaking software to your own taste, making it feel just right is the most important aspect of an electronic device that provides so much interaction. I guess that's why I almost feel handicapped on a stock Android phone or, especially, iPhone. The devices just feel so clunky and unrefined.
    Thank you, if nothing else, for helping me see a different perspective on things :)
  • Lucian Armasu - Thursday, January 19, 2012 - link

    1. Can you re-check and confirm if swiping tabs off in the task menu, actually KILLS the apps, or it just takes them off the list? Because I've heard before that it doesn't kill them.

    2. The battery tests, especially the Wi-Fi ones, were they done with 3G and LTE on?
  • silow675 - Thursday, January 19, 2012 - link

    "At 720p, which happens to be the GN's native resolution, the OMAP 4460 is a bit faster than Tegra 2 but not significantly so. The more important thing to keep in mind is just how much faster Tegra 3's GPU is by comparison"

    I don't understand this remark. The chart that's posted for the 720p offscreen renders don't have a Tegra 2 device. In the RightWare charts the Galaxy Nexus scores much more than "a bit faster" than the Tegra 2 devices. And to my knowledge no Tegra 2 smartphones are offered at native 720p resolution.

    I also checked the AT Bench database and couldn't find any Tegra 2 benchmarks to compare. Do you guys have some unposted numbers?
  • RobElk - Thursday, January 19, 2012 - link

    You guys do a great job. Love the attention to detail in your review. Thanks.
  • DrKlahn - Thursday, January 19, 2012 - link

    I found this comment interesting. I have had the phone since launch day (VZW) and have yet to notice any lag hitting the virtual buttons. Perhaps I am just not as sensitive to it or some other process on your test phone is affecting it. I have got the phone to lag doing some very intensive tasks on occasion, but it's very infrequent. My chief complaint has been the volume which I remedied with a free app (Volume+ with the +2 setting). Otherwise I give the phone very high marks. I have no real desire to root or tinker with it yet, the stock experience is excellent.
  • peokuk - Thursday, January 19, 2012 - link

    for the font comparison, why not 'the quick brown fox jumps over the lazy dog'? using cat and jumped leaves out the letters 'g' and 's'...
    http://en.wikipedia.org/wiki/The_quick_brown_fox_j...
  • DanSmith - Thursday, January 19, 2012 - link

    No one has actually said it yet so I will. Good review guys, in depth and informative as always.
    Thanks for your hard work.

    Dan
  • DanSmith - Thursday, January 19, 2012 - link

    Actually, someone already has! Seems the internet is not completely populated by haters. :)

Log in

Don't have an account? Sign up now