The Galaxy Nexus - Hardware and Aesthetics

The evolution of Google’s Nexus line is an interesting one. Each year, Google choses both a silicon partner and an OEM to make a unique hardware archetype which it caters a specific build of Android to. We’ve now seen three Nexus handset designs from two OEMs and three silicon vendors - the Nexus One (HTC and Qualcomm’s QSD8x50), Nexus S (Samsung and Samsung’s S5PC110 ‘Hummingbird’), and today the Galaxy Nexus (Samsung and TI’s OMAP4460).

Looking at the hardware of those three handsets gives a great survey of the course the Android ecosystem has taken over the last couple of years. The Nexus One started things out with a 3.7” LCD, capacitive buttons, and hardware trackball. Nexus S then removed the trackball, added a curved 4.0” display, and ditched the microSD card slot. The Galaxy Nexus continues in that direction, increasing display size to 4.65” and resolution to 1280x720, and finally removing the capacitive buttons all together. Instead, the Galaxy Nexus uses a 96 x 720 region at the bottom of the display to visualize the navigational buttons, a move that has the consequence of also keeping the display interaction area aspect ratio close to that of WVGA.

It’s interesting to see how many of the design motifs set by the original Nexus One still have been thoughtfully preserved on the Galaxy Nexus. The notched chrome ring around the camera aperture has continued as a thread for three generations, as has the overall lightly rounded shape. The Galaxy Nexus also retains the chin from Nexus S backside where the speakerphone port and primary cellular antennas are located. In addition, the volume rocker, power/lock button, headphone jack, and primary microphone position from the Nexus S is unchanged.

The Galaxy Nexus’ backside is no longer the extremely slippery and scratch prone plastic that the Nexus S (and original Galaxy S) adorned, instead it’s a textured, lightly soft touch material. I’m always surprised by how much of a difference changing the backside texture makes on the overall in-hand feel impressions I come away with, and in this case it’s a major positive change. It’s clear that this is an evolution of Nexus more than a huge departure from what’s come before - if anything the Galaxy Nexus is like a larger, thinner, more refined Nexus S.

We’ve taken a look at both the CDMA/LTE (codename mysid/toro) and the GSM/UMTS (codename yakju/maguro) Galaxy Nexus variants.

The two differ beyond just the air interfaces they support slightly in the physical department as well, though the two share all the same other features (SoC, display, camera, etc.). The CDMA/LTE Galaxy Nexus is ever so slightly thicker than the GSM/UMTS Galaxy Nexus, though the difference is enough to be perceptible.

In addition, the two have the same exterior “titanium silver” color, no doubt the differences we saw earlier can be attributed to the difference between renders and the real deal. The other small detail is that the two use very different, non-interchangeable batteries - the GSM/UMTS variant uses a 6.48 Whr battery, the CDMA/LTE version gets a slightly larger 6.85 Whr battery. Both of these include the NFC antenna patterned the outside surface of the battery, just under the sticker. 

Other than those subtle differences, Samsung has done a good job masking the challenges which underlie having two superficially similar phones with different cellular architectures. The two variants do feel different in the hand, but the difference isn't dramatic. 

Physical Comparison
  Apple iPhone 4S Samsung Galaxy S 2 Samsung Galaxy Nexus (CDMA/LTE) Samsung Galaxy Nexus (GSM/UMTS)
Height 115.2 mm (4.5") 125.3 mm (4.93") 135.5 mm (5.33") 135.5 mm (5.33")
Width 58.6 mm (2.31") 66.1 mm (2.60") 67.94 mm (2.67) 67.94 mm (2.67)
Depth 9.3 mm ( 0.37") 8.49 mm (0.33") 9.47 mm (0.37") 8.94 mm (0.35")
Weight 140 g (4.9 oz) 115 g (4.06 oz) 150 g (5.3 oz) 135 g (4.8 oz)
CPU Apple A5 @ ~800MHz Dual Core Cortex A9 1.2 GHz Exynos 4210 Dual Core Cortex A9 1.2 GHz Dual Core Cortex-A9 OMAP 4460 1.2 GHz Dual Core Cortex-A9 OMAP 4460
GPU PowerVR SGX 543MP2 ARM Mali-400 PowerVR SGX 540 PowerVR SGX 540
RAM 512MB LPDDR2-800 1 GB LPDDR2 1 GB LPDDR2 1 GB LPDDR2
NAND 16GB, 32GB or 64GB integrated 16 GB NAND with up to 32 GB microSD 32 GB NAND 16/32 GB NAND
Camera 8 MP with LED Flash + Front Facing Camera 8 MP AF/LED flash, 2 MP front facing 5 MP with AF/LED Flash, 1080p30 video recording, 1.3 MP front facing 5 MP with AF/LED Flash, 1080p30 video recording, 1.3 MP front facing
Screen 3.5" 640 x 960 LED backlit LCD 4.27" 800 x 480 SAMOLED+ 4.65" 1280x720 SAMOLED HD 4.65" 1280x720 SAMOLED HD
Battery Internal 5.3 Whr Removable 6.11 Whr Removable 6.85 Whr Removable 6.48 Whr

 

Settings & File Transfers The SoC - TI's OMAP 4460
Comments Locked

185 Comments

View All Comments

  • zorxd - Wednesday, January 18, 2012 - link

    The Skyrocket is also 1.5 GHz so the CPU helps.
  • sprockkets - Wednesday, January 18, 2012 - link

    There's a very small bit of lag on the bottom buttons. Quite frankly I think the delay is just the OS making sure you are holding down the home button for the task manager instead of just going home.

    Using ICS on a HTC Sensation. The status of it is beta - HTC still has work to do on it to make it as good as the 2.3.4 ROM.
  • webmastir - Wednesday, January 18, 2012 - link

    Love my Galaxy Nexus. Best phone I've ever had & have no DOUBT in my mind that I'll be happy until my next Phone.
    Thanks Google!
  • OCedHrt - Wednesday, January 18, 2012 - link

    Since I can't get the HTC keyboard working on AOSP ICS...I have to make this comment: I prefer the HTC keyboard much much more than even the ICS keyboard. It is ridiculously easy to mistype on the ICS keyboard.
  • vithee05 - Wednesday, January 18, 2012 - link

    Can you guys tell me how the accessibility is in ICS? It's supposed to be better for those of us who are visually impaired. I am debating between the galaxy nexus, the razr, or waiting on the droid 4 to get the keyboard. Do you think the accessibility is good enough to not need the keyboard?
  • secretmanofagent - Friday, January 20, 2012 - link

    I have a Droid RAZR (2.3.5) in my hands, and looking at the accessibility settings, it's pretty paltry. If you're considering a RAZR or Droid 4, I would wait until ICS shows for it.
  • tipoo - Wednesday, January 18, 2012 - link

    I agree that its worlds better than the Gingerbread browser, but scrolling on image heavy pages still lags a bit compared to Opera Mobile (not to be confused with Mini). AFAIK Opera Mobile uses GPU acceleration as well and seems to do it better than Google at their own game. Just an idea, but a comparison of all the Android browsers would be nice :)
  • tipoo - Wednesday, January 18, 2012 - link

    *on my Nexus S. Maybe on newer/faster phones it would be a toss up.
  • bjacobson - Wednesday, January 18, 2012 - link

    Really? interesting. Opera seems to get everything right. Their browser is blazing fast for Netbooks too. Everything in the UI and foreground tab gets processing priority, everything else (like background tabs rendering) gets delayed. It's a flawless design, much more responsive than Chrome when loading multiple tabs.
  • tipoo - Thursday, January 19, 2012 - link

    Yeah, and as far as I know its the only browser that dynamically adjusts its memory use depending on how much your using for other tasks, so it scales up or down to more powerful or less powerful systems, another reason its good on netbooks. It has addons now too which are rapidly gaining traction. If it wasn't for some compatibility niggles I would say its hands down the best browser, but I keep Chrome around for the 1 in 1000 site it might break. Oddly enough the Mobile version seems to be the opposite, its the only mobile browser that I've never seen break a site.

Log in

Don't have an account? Sign up now