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

  • TedG - Wednesday, January 18, 2012 - link

    I am looking forward to ICS on my RAZR. It seems similar in power and size to the Nexus.
  • Jonathan Dum - Wednesday, January 18, 2012 - link

    Any comments on the quality of the touch sensors? My biggest gripe with my Nexus One is the absolutely inane touch accuracy in comparison to an iPhone. If these new ICS phones have significantly improved touch sensors, I may be coaxed into sticking with Android.
  • jalexoid - Wednesday, January 18, 2012 - link

    Synaptics touchscreen controller on N1 was to blame. Even the HTC's "copy" Desire had a much better touchscreen experience due to a better touchscreen controller.

    All devices after that should have a really good controller.
  • tipoo - Thursday, January 19, 2012 - link

    Same with my Nexus S. The locational accuracy is good, but it actually senses a tap with my finger a few millimeters above the screen, which can cause problems with the keyboard and other precise apps.
  • Brian Klug - Thursday, January 19, 2012 - link

    That was always my bug with the Nexus One as well, and it remains an unsolved problem to this day on that phone.

    I've seen no touch recognitions at all on the Galaxy Nexus. For the most part honestly these issues have gone away as the OEMs stopped being cheap with their capacitive layers and controllers. The Nexus One was especially bad.

    I've seen some people complaining about issues with recognition in the bottom right corner - hardware swaps fix those problems.

    -Brian
  • Skiddywinks - Wednesday, January 18, 2012 - link

    ... is the GN still going to be the best Android on the market? I upgrade in March, and it basically comes down to the S2 or the GN. Each has their advantages, but personally it largely comes down to the display and the GPU.

    I like to play emulated games on my phone, but I don't know how they work in terms of whether they are software only, or can GPU accelerate. The better GPU in the S2 doesn't really do much if the GN can play everything else on the market at no apparent deficit. Better display all the way in that case. GN wins.

    I'm not liking the lack of mSD in the GN either, though.

    BAH. Decisions, decisions.
  • tipoo - Thursday, January 19, 2012 - link

    Yeah, the Mali 400 in the GS2 might benchmark way higher than the Galaxy Nexus, but there are no games that exclusively run on it, or even that have more features on it like Tegra phones. I'd guess that even with its relatively weak GPU the Galaxy Nexus will never leave you wanting in games for the next year or two, and its screen is better. My Nexus S can still play top end games like Shadowgun, and that was built for more powerful tablets. With Android developers aim for middling hardware.
  • medi01 - Wednesday, January 18, 2012 - link

    @Android is an OS that, although more closed than many would like, still allows more flexibility than iOS@

    And that comparing Open Source OS to something as closed as it gets. It is merely "still allows more than iOS", hilarious.
  • doobydoo - Thursday, January 19, 2012 - link

    The openness of Android wasn't being compared to iOS, the flexibility was.

    Two separate points.
  • Gwynbleidd - Wednesday, January 18, 2012 - link

    Two things, though:

    1. You wrote "Business is as usual for Windows users as ICS based devices just appear as a drive letter thanks to native MTP support." - that's not true, because of MTP Nexus appears in My Computer in Windows as a multimedia device and does not have a letter assigned, so sadly it's not possible to use traditional file managers like Total Commander to deal with files on it without additional plugins.

    2. Did you notice any screen quality issues in your devices? Mine shows ugly pinkish smudges visibly especially on gray backgrounds, here's photo (it's out of focus on purpose, otherwise there would be a rainbow goo on screen):

    http://img812.imageshack.us/img812/7794/nexussmudg...

    So when scrolling webpages you can see that text is pinkish at the top, then white stripe, then pinkish again... Apparently I'm not the only one having this issue with Nexus, and there is a long thread on xda forum about the same problem with Galaxy Note Screens

    http://forum.xda-developers.com/showthread.php?t=1...

    A little investigation, maybe? ;)

Log in

Don't have an account? Sign up now