Meet the Droid X

The X is big, eXtreme, even. In many ways, the X is Motorola’s EVO, sans 4G. Both pack 4.3 inch screens, but no keyboard. In fact, the X is slightly taller than the HTC EVO by  5.6 mm on paper (127.5 for the X, 121.9 for the EVO), which itself is impressive. That’s not to say it’s unusably large, or that the size is a problem, but it’s a big phone that commands big pockets.

Everything about the X seems like it can be followed up with a “that’s what she said.” The thing’s size, performance, how long it lasts - on battery of course. Seriously, you can mentally add that onto so many sentences, it seems as if the EVO and X are both answers to the proverbial question “why not?”

In reality, the 4.x” size screen phones seem a class of their own now, of which the EVO and X are newest members. Until we grow larger thumbs (genetic modification perhaps?) I think this is the upper limit for smartphone screen size until we get foldable screens. Any larger, and your thumb literally can’t sweep out far enough to reach the far corners of the screen. Anand has stated before that his cutoff size for when the tablet segment starts is at 5 inches; I think that’s right on the money.
 

The X increases the screen size of the original Droid, while maintaining the somewhat unique FWVGA 854x480 resolution of the original Droid (Motorola erroneously maintains this is WVGA), compared to the more standard WVGA 800x480 resolution of other Android devices. The result is that dot pitch is a bit higher on the X than the EVO. It’s interesting that Motorola is sticking to FWVGA - this is admittedly exactly 16:9 aspect ratio and excellent for anamorphic videos, but no doubt still gives developers a bit of pause.

The other major change the X brings is TI's OMAP 3630 SoC with a 1GHz CPU core, but more on that in a bit.

The X is also thin. Really thin. The majority of the device is 9.9 mm thick, while the top of the device is 1.4 cm. Motorola has made a tradeoff here - make the rest of the device thin and wide at the expense of a bulge in another location. That bulge, unsurprisingly, is the camera. The camera’s optical system simply requires a certain throw distance. Motorola could’ve made the entire device a uniform (and beefy) thickness, or do what it did and make a phone with a bit of a step.

The step isn’t a problem at all. I couldn’t feel it in my pocket, don’t think it’s ugly, and it has the added benefit of keeping most of the device propped up off of whatever surface it’s on. The result is that you won’t scratch the camera cover, won’t scratch the back of the device, and won’t have the device rock and roll from having a curved backside. The other positive is that when rested, the device is propped up at a few degrees.

But probably the biggest and most welcome change is that Motorola has ditched the ubiquitous capacitive buttons that have been an intermittent annoyance on some Android devices.

Some phones have pulled it off perfectly - the EVO’s buttons work fine, and the Motorola Droids that I’ve played with were perfect - but on others it’s a real scourge. On my Nexus One, the entire digitizer intermittently decides that keyboard presses map to menu, home, or back at times. Apparently I’m not alone either.

On the X, the row of buttons are the real uncut deal, and they’re perfect. There are really two sets of rocker buttons - the leftmost two is one rocker, the rightmost two are the other - but you won’t notice. They don’t jut out a lot, and don’t get pressed accidentally in the pocket. Right below the row of buttons in the center is one of three microphones on the X.

Up at the top of the X is the proximity sensor, notification LED and handset speaker. The proximity sensors are on the right side under the plastic, and the LED is on the left. There’s also the ambient light sensor up there.

On the right side of the phone are the volume up/down buttons, and the two level camera button. Motorola made a sort of big deal about their gold colored camera button on the original Droid, so I’m really confused why it’s a metallic red now. The volume rocker on the original Droid used to be stiff and problematic, the X’s is perfect. The camera button still requires a lot of force to click in all the way, and remains the only way to actually trigger camera capture.

Moving around to the other side are the Micro-USB and Micro-HDMI ports. They’re a bit close together - maybe I’m special, but more than once I found myself trying to plug the USB charger into the HDMI port on accident.

Up top, there’s the power/lock button, 1/8” headphone jack, and a second microphone port. The top is slightly tilted - thankfully the power button doesn’t stick out normal to this surface, but rather perpendicular with respect to the display. Otherwise it’d get worn in really odd and probably fail fast.

The bottom is where things are interesting. There’s the slightly raised 14 mm bulge where the camera and LED flash are, which rolls off over part of the battery door to the 9.9 mm thickness area. Finally, down at the bottom is the third of the X’s microphones, and a slit for the speakerphone. You can slide a fingernail in there, but there’s thankfully a fine mesh preventing pocket lint from collecting inside. The Motorola logo has some pattern to it, so it shouldn’t rub off.

In the Motorola Droid review, I talked a lot about the beefy metal battery door. I’m pleased to report that the X has one as well, and it slides on and off snug and secure, doesn’t creak, doesn’t vibrate. It’s solid. Under that door is battery - you have to pull up on a tab to get the battery out. Once it’s out, you can get to the preinstalled 16 GB microSD card. The card doesn’t have a push-click mechanism, it simply slides in and out.

My only complaint about this pull tab battery release arrangement is that you pull and rotate the battery about the wrong axis. The battery slides in and goes down along its long axis, while the tab pulls up and kind of pries the battery against the way it slides in. I could see someone - if they’re not careful - being aggressive and breaking something, but I’ve yanked the battery numerous times to get the SD card out and haven’t broken anything yet. Just be careful.

Looking carefully, there’s a gold contact switch next to the pull tab which clearly makes contact with the metal underside of the battery door. You can see where it’s made contact with the door and left a little mark as well. More on that later.

The plastic exterior on the X feels rubbery - it’s got a grippy tack that has lasted a few solid weeks of my greasy hands, and doesn’t slide around. On the front at the very top and very bottom, the plastic bits seem to actually be a stiff rubber. Not sure why you’d want those parts rubber, but they feel different and more rubbery.


Left: Motorola Droid. Right: Motorola Droid X.

Overall, the build quality of the X is solid. Motorola has pulled off two high end Android phones that really feel good and inspire a lot of confidence. There’s no give or play with any of the buttons, the volume buttons aren’t loose and broken out of the box like some Droids were, and the grippy plastic makes it feel even better. Again, I think having the phone tilt a few degrees and not rest completely flat on surfaces will help the back not get scratched up.
 

Introduction Comparisons and What's In the Box
POST A COMMENT

89 Comments

View All Comments

  • homebredcorgi - Tuesday, July 20, 2010 - link

    Who do we have to blame for the “Droid” moniker? Verizon or Motorola?

    I have a Nexus One and continually get asked, “Is that a Droid?” or “Does that run Droid?” to which I usually reply yes and let sleeping dogs lie…but seriously, why name it so similar to the operating system? And then why make “Droid” a series of phones if your first phone is just known simply as “Droid”?! At least call it the "Droid One" or something to differentiate from the series of phones....

    So now we have the Droid, Droid Eris, Droid X, and will soon have the Droid 2 which are all phones in the Droid series, all running on various builds of Android. Yeesh. Could they have made that any more confusing?

    All in all, the Droid X looks very nice. I personally think the original Droid had all the flair of a TI-82 calculator (ugly as sin in a blocky retro way), but the Droid X seems to have modernized its looks. Still not sure if I would want a phone that large though….
    Reply
  • metafor - Tuesday, July 20, 2010 - link

    Verizon owns the rights to the "Droid" trademark from Star Wars. So they decided to capitalize on that and name their whole line of Android phones "Droids".

    I think it's kinda cheezy but hey, it's selling and is something that people can focus on. With the army of phones coming out every week, it's difficult for the average person to keep up. It helps if they can just go to a store and ask for a Droid.
    Reply
  • strikeback03 - Tuesday, July 27, 2010 - link

    Actually they have only been using Droid on the high-end phones, the Devour and Ally were not Droids.

    There is also rumor of a special edition Droid 2 coming with R2-D2 on the battery cover...
    Reply
  • lewchenko74 - Tuesday, July 20, 2010 - link

    The best, most comprehensive review of the Droid X Ive read so far. Thank you.

    Just got to wait until it arrives in the UK unlocked now, but personally I think Im going to get the Droid 2 instead with the keyboard.

    I am amazed at the pace the smartphone market is moving at. Im 1yr into a 2yr contract with a HTC Hero. It feels like an antique! These 2yr contracts really are a ball and chain.

    It also seems like HTC is starting to lag behind Samsung and Moto now in terms of processor and features. Sense also seems a little 'old' compared to other UI layers (or maybe thats just me).

    Disappointed that it only runs Android 2.1 when 2.2 is now out though.... That would be like Apple releasing iPhone4 running OS3.2 whilst saying OS4 is out there too but not quite available yet! (I guess Apple actually did that though with the iPad ;-) )
    Reply
  • mvmorr01 - Tuesday, July 20, 2010 - link

    What app are you using for those CPU utilization graphs? I did a quick search and couldn't find it in the market. Reply
  • Brian Klug - Tuesday, July 20, 2010 - link

    It's an application called "SystemPanel" which I found a while back. If you turn logging on, it'll give you some very cool graphs of battery use over time and CPU utilization over days even. Produces some very cool results when I do battery life testing.

    -Brian
    Reply
  • 529th - Tuesday, July 20, 2010 - link

    First of all I want to say I love mine! :) Bought it the day it came out.

    Wow what a great review!!!

    I didn't know you could run benchmarks on a phone! Linpack!?? WOW awesome!

    I can't wait till Froyo! :)

    Thanks again chief!

    <3 Anandtech reviews!
    Reply
  • WaltFrench - Saturday, July 24, 2010 - link

    Linpack is a 90s-era benchmark that performs a specific matrix solution. As much as possible, all floating point adds and muls.

    I've tried in other forums to find an app, prior to 6/1/2010, that actually uses Gaussian elimination with partial pivoting. The particular method works best to find complex patterns within large data sets; that's great for my statistical investment models and for a lot of other stuff. It's strongly suggestive of performance on weather simulations, quantum chemistry, etc., stuff that no sane person would attempt (today) on a smartphone.

    Others claim Linpack scores around 40 on overclocked ARM chips with Froyo (the JITting being fabulously helpful for highly repetitive benchmark code). I got ~35 on my iPhone. These scores are ~ 13X–16X what the Linpack author quoted long ago for his 486 (/487, I presume).

    I don't know a lot about graphics but presume 3D work that calls for lots of floating point Add/Mul work would get routed to the GPU, so I think these scores are of extremely limited relevance to any smartphone app I can envision.
    Reply
  • vshin - Tuesday, July 20, 2010 - link

    Where are the antenna attenuation tests? No weak spots? Reply
  • Brian Klug - Tuesday, July 20, 2010 - link

    There's definitely attenuation tests in there, and weak spots. The bottom of the phone as expected causes a 15 dB drop. It's on page 14: http://www.anandtech.com/show/3826/motorola-droid-...

    -Brian
    Reply

Log in

Don't have an account? Sign up now