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

  • HooDooMagic - Friday, January 20, 2012 - link

    I think it's already been mentioned that 4.03 fixed the task switcher lag. I have alpha ICS 4.03 roms running on a Nexus One, Nook Color and Samsung Galaxy Tab 10.1 and everything runs very smoothly on all 3 devices. Even the very underpowered Nook has surprisingly little lag and stutter when using the task switcher and transitioning between screens/app drawer etc.
  • Chloiber - Wednesday, January 18, 2012 - link

    The Galaxy Nexus is a very nice phone indeed, but there are just some things that I don't like about it. As mentioned in the review, the GPU is not the best, which is actually the main reason I won't buy the phone. I buy smartphones which should last about 2 years. Buying one with a GPU from the beginning of last year is just not good enough. As Anand mentions: better wait for Q2, maybe Q3. At the moment, the GN is certainly the best phone (in my opinion) money can buy, but it's not the right moment to buy an android phone.
    The review is very late indeed...but very thorough - thank you!

    One question remains: are microSD slots a thing of the past? Google mentioned that there is a good reason why they didn't include one (slow speeds for apps). But I still think that's a very bad reason not to include a slot. While it is true, that the mSD cards are pretty slow compared to internal storage, there is just no way in hell I'm gonna pay 100$+ for 16GB of additional internal NAND. Additionally, you don't need high speeds for music, pictures and movies (the main reason to get an SD card).

    I hope for a phone in Q2/Q3 with a) better SoC, b) an SD card slot and c) a 720p IPS or SAMOLED+ screen.
  • humancyborg - Wednesday, January 18, 2012 - link

    I agree. The GPU is a terrible oversight on this phone, particularly considering the inclusion (finally) of OpenGL rendering throughout Android.

    With the 4S GPU being 3-4x faster it's tough to see how this phone is going to stand the test of time. Presumably the iPad3 and next iPhone will be packing an even more powerful SoC and GPU.

    This is one of the main reasons that I think Apple is in a great position going forward with regards to hardware. With the exception of Samsung, everyone else is relying on TI, Qualcomm, Intel, etc to make the right decisions with regards to CPU/GPU etc combination and clearly those chip makers do not always have the best insight with regards to product pipeline or requirements.

    A retina display-ish version of the iPad is going to take a GPU far beyond anything the current SoC guys are manufacturing.
  • tipoo - Wednesday, January 18, 2012 - link

    The next generation of PowerVR SGX graphics chips are supposedly 20x as powerful as the current ones. I'm guessing Apple will still be using the dual core variant of the 6** series. That's good, if the 4x screen resolution rumours are true.

    Yeesh, Android devices still haven't caught up to the old GPU now a new one is around the corner. Nvidia is stuck with their own GPU's of course, but TI or Samsung should switch to PowerVR if this performance domination continues.
  • trob6969 - Wednesday, January 18, 2012 - link

    What performance domination?! Android phones are easily the most powerful on the market!
  • Greg512 - Wednesday, January 18, 2012 - link

    Not when it comes to GPU power. The iPhone 4S has a GPU 3-4 times as powerful as the one in the Nexus. Android phones do tend to have higher clocked processors, however, so they do have a healthy advantage on that front. Android phones also have more RAM, though many would debate that iOS is memory efficient, negating the hardware advantage.
  • KoolAidMan1 - Wednesday, January 18, 2012 - link

    You're kidding, right? The Tegra 3 is slower than the eight month old A5. Everything in Android world is playing catch-up with old parts, which is odd given that they have a more frequent upgrade cycle. Problem is that they've been behind since the beginning.
  • doobydoo - Thursday, January 19, 2012 - link

    trob6969 - the leading Android phones have CPU's which are largely comparable to the CPU in the iPhone 4S - in some cases they even boast up to ~10% extra performance (as a result of, in some cases, 50% higher clock speed), but only in CPU limited tasks, and that <10% is barely noticeable.

    Graphically, the GPU in the Nexus Prime is far slower than even the Samsung Galaxy S2 - using an older GPU which is up to 3x slower than the GPU in the iPhone 4S. The GPU in the SG2 (the fastest Android GPU) is also far slower than the iPhone 4S (as the benchmarks in this review show)

    Because iOS is hardware accelerated (and tightly intertwined with the iPhone), the performance of the iPhone 4S and iOS is far superior to any Android phone out at this moment in time.
  • zorxd - Thursday, January 19, 2012 - link

    uh?
    50% faster clock speed gives you 50% more performance in CPU limited tasks. Don't forget that it's the same architecture (Cortex A9).

    I hope you are not making that 10% claim based on javascript bencmarks. They are browser benchmarks more than CPU benchmarks.
  • Zoomer - Thursday, January 19, 2012 - link

    Not really, the A9 ISA have many different architecture implantations. TI does their own, Apple probably did their own, and I believe nVidia has their own too.

Log in

Don't have an account? Sign up now