Moto X Reviewby Brian Klug on August 26, 2013 1:30 PM EST
- Posted in
- Android 4.2
- Moto X
It has been a long time since I’ve seen a smartphone so fervently rumored, discussed, hyped, and finally announced like the Moto X has been. The level of buzz surrounding the Moto X slowly built to nearly messianic levels just before the official announcement, after which point we were given the device for a hands on and initial impressions. Hype aside, Motorola built considerable attention for the Moto X, now the question is how the device really stacks up to the competition.
For Motorola, the Moto X is a hugely aspirational phone. If the name doesn’t already make it somewhat obvious, this is literally the device that Motorola is relaunching itself under. Greater still, the Moto X is the first device built and released under its new Google ownership. While it’s obvious that Google didn’t buy Motorola solely for its product portfolio, it’s still an important data point for its mobile strategy, to say nothing of how closely the rest of the Android hardware vendors are probably watching this launch. Motorola did an awesome job timing its announcement and release window, giving us just short of a month of time with the Moto X before release date crept up, something I wish more handset makers would do instead of the usual 1 week rush.
For me, reviewing Motorola phones seemed to be a constant affair up until the acquisition and Motorola quieting down. The breadth of its handset portfolio seemed to dwindle down to essentially only Droid branded handsets for Verizon, to the point that many considered Motorola a de-facto Verizon handset ODM. That’s not to say Motorola didn’t make interesting phones, like the RAZR i or M for example, but it certainly quieted down.
All of that changes with the Moto X, which will launch on the five major wireless network operators in the USA (Verizon, AT&T, Sprint, T-Mobile, US Cellular), in addition to a version sold on Google Play, and two Developer Editions (one for Verizon Wireless, another general North American WCDMA/LTE version) with unlockable bootloaders direct from Motorola. Motorola now effectively joins Samsung and HTC in the Android space by getting its branding and device portfolio consistent and uniform across the operator landscape. There are still a lot of variants of the Moto X, but the upside is that almost all the possible combinations are covered for the US, Latin America, and Canada.
There’s been a narrative lately about smartphones and their ever increasing size. It’s shocking to me that this far into the mobile device surge, the industry hasn’t quite settled down on one clear optimal display size, with flagships getting bigger each successive generation. I’d posit that the optimal size is somewhere just shy of 5-inches diagonal, say between 4.7 and 5, but this is a subject of heated debate.
HTC One, Moto X, RAZR MAXX HD (Left to right)
While there are definitely smaller phones out there, the problem is that handset makers divide up their portfolio along display size lines. Smallest ends up being low end, medium ends up being midrange, and the largest devices end up being the flagships. If you want that midrange sized phone, that ends up putting you squarely in midrange territory, and therein lies the problem - smaller shouldn’t automatically connote midrange.
HTC One mini, Moto X, RAZR i (Left to right)
The Moto X is positioned as an Android handset that fills exactly that niche - a flagship phone with a still quite big display (4.7-inch diagonal) but not quite as big as the 5-inch flagships, and overall smaller 2D dimensions, all while being flagship. Or at least, that’s one part of the unstated goal of the Moto X. Size is kind of a tired discussion at this point, so much so that I feel like a broken record talking about it each device, but the Moto X is clearly on the smaller side of the spectrum right now.
The easiest thing to talk about is the in-hand feel of the Moto X. The short version is that the rounded backside of the Moto X is more ergonomic than most, but the plastic it gives way to halfway along the lip makes it feel like relatively standard fare. After you get over that plastic on the front, however, the shape is great and there aren’t any sharp edges to get hung up on or cause discomfort when held to the face during a call.
The long story is that the Moto X design allegedly reflects Google’s data-driven approach to just about everything. Google’s guidance to Motorola on the Moto X was something along the lines of - go get a statistical sampling for device size and shape, do a user study and gather feedback, and then build the phone that optimizes for positive feedback.
I’m not sure what the size of Motorola’s sample was, but it clearly was enough to convince Google. I’ve always wanted to design a phone something like that - get 3D data on a huge number of human hands, then empirically derive the optimal size and shape for a device, and engineer a phone around those constraints. The reverse of that is most often what happens during device design - the display I want to fit inside has this aspect ratio, I have to fit this much board area for the platform inside, and then fill the resulting empty space inside the cube with battery. The mechanical engineering, industrial design, and RF design of a smartphone are really three competing things all pulling different ways.
The result of that data is the Moto X’s unique backside curve, which isn’t a spherical or cylindrical shape but rather a more complicated quadratic one. Holding the phone, you can see how this plays out - the Moto X is thicker at the top than it is at bottom, with the thickest point peaking at the Motorola dimple. Similarly, the rolloff in thickness from side to side changes depending on height. It’s a really hard to describe curve that seems much more organic than the extruded rectangle shape of traditional devices. I can’t deny that the Moto X shape seems almost natural when held in the hand during normal use or when held to the head during calls. The Motorola-logo dimple also does double duty by serving as a great way to tell if you’ve pulled it out of your pocket in the right orientation.
Like other vendors with a curved back shape, Motorola fills as much of this volume as possible with components required for a phone. HTC chose to fill its rounded devices with a stack of battery, then PCB, Motorola goes for a monolithic single-sided PCB (a regular design staple for Motorola instead of the double-sided L shaped PCB), then tops it off with a stepped battery made by LG. So much of in-hand feel is a byproduct of the internal construction, and putting that the volume formed by the rounded section to use with a stepped, stacked battery is critical.
Materials are the other axis of in-hand feel and quality. Here Motorola continues to use composites with the default woven white and woven black. If you’ve held the Kevlar Droid RAZR or the composite-backed RAZR HD, you’ll know exactly what I’m talking about, as that seems to be the same material as what’s employed here. One of the other material choices is a more traditional polymer with soft touch, which is the case of the different colors available if you go the customization route through Moto Maker which we’ll talk about later. Last are wood options which won’t be available at launch but rather sometime later in Q4 - teak, bamboo, rosewood, and ebony will be choices. The wood is sealed with a clear layer, to both prevent damage but also stop water from being absorbed and causing unintended attenuation of RF signals.
I’ll say that I’m spoiled and colored by my time spent using metal phones as of late, but the composite-backed Moto X still seems of higher quality than the plastic used by some of the Korean handset makers.
Motorola’s unique materials story continues on the front with a fused glass-plastic layer. The front glass and touch panel are fused into the plastic lip which rings the top side of the Moto X. They’re not separate parts, but literally fused together into one. Motorola is very proud of this feature since it results in one unbroken surface instead of the usual pressure-fit plastic ring affair with a raised section or gap. I can still detect a bit of a seam where the glass-plastic interface is, but it’s so much less than what I normally encounter on other devices.
The top and bottom of the Moto X also have a small raised plastic lip, which lets you lay the phone front-down on a surface without the display glass resting coplanar and picking up scratches from any dirt or dust in-between. This is a subtle but important feature given the Active Display feature and the display-down emphasis that’s part of it. The Moto X also feels great held to the head with this rounded unbroken curve - a lot of other handsets with sharp edges really start to hurt after a while on long conference calls, and the Moto X feels notably better than the competition in this regard. The front facing camera is off to the extreme right, the earpiece is a small centered slit, and to the left is the ambient light and proximity sensor.
There are three microphones on the Moto X for ambient noise reduction on calls and for ASR (Automatic Speech Recognition). One on the front at bottom just off-center, one on the back facing out, and one at top next to the headphone jack. Motorola was the first to put three microphones on its devices, and this continues with the Moto X, even if I suspect this is still a beamforming system that uses the microphones in pairs.
At the bottom is a microUSB port, at top in the thick region at center is the headphone jack.
The left side is home to the Moto X’s nanoSIM tray, which makes it one of the few new devices embracing nanoSIM besides the iPhone 5. At right is the single piece volume rocker and power button above it. The buttons feel positively clicky and are easy to locate, but can be pushed around up and down and rattle slightly.
The backside is again home to a secondary microphone, rear facing camera and LED flash, speakerphone grille, and Motorola logo. The speakerphone is a series of small holes to the right of the camera aperture and rather traditional mono. The backside also carries AT&T branding at the bottom, which is rather unfortunate. The upside however is that there isn’t any on the front of the Moto X.
The Moto X ends up being a uniquely shaped device that lends it great in-hand presence, and makes it incredibly pocketable. I also have to applaud Motorola for its above average material quality. The Moto X is not small by 2012 standards, but smaller than most of the 2013 competition, something that it plays off as a positive rather than a negative. It truly is crazy to think that a device the size of the Moto X is now considered on the smaller side of the spectrum.
Qualcomm Snapdragon S4 Pro (MSM8960Pro) 1.7 GHz
Motorola X8 System (SoC+NLP Processor+Contextual Processor)
|Display||4.7-inch AMOLED (RGB) 1280x720|
|WiFi||802.11a/b/g/n/ac, BT 4.0|
|Storage||16 GB standard, 32 GB online, 2 years 50 GB Google Drive|
|I/O||microUSB 2.0, 3.5mm headphone, NFC, Miracast|
|Battery||2200 mAh, 3.8V, 8.36 Whr|
|Size / Mass||65.3 x 129.3 x 5.6-10.4 mm, 130 grams|
10 MP Clear Pixel (RGBC) with 1.4µm pixels Rear Facing
2 MP 1080p Front Facing
|Price||$199 (16 GB), $249 (32 GB) on 2 year contract|
Post Your CommentPlease log in or sign up to comment.
View All Comments
PC Perv - Monday, August 26, 2013 - linkSame for the screen. It's not as if everyone is in publishing industry. Human eyes are not limited to sRGB. Colors can be accurate or inaccurate, but there is no right or wrong ones. The author talks as if having larger gamut than sRGB in and of itself is always a negative. Ever looked into the ocean and be marveled at the nature's wonder?
Friendly0Fire - Monday, August 26, 2013 - linkIt is a negative if the software is not aware that the gamut is larger (hint: it isn't), causing incorrect colors.
I doubt anyone at AnandTech would spit on an AdobeRGB screen if the OS and all software handled it properly, but that's just not happened and probably won't for the foreseeable future. In the meantime, accurate colors are better than higher gamut.
MartinT - Tuesday, August 27, 2013 - linkI'd argue that a large portion of what remains as a debate on optimal screen size is down to one particular supplier with considerable market share in the US not providing a model anywhere even close to what Brian (and the market) have zeroed in on as optimal.
This is where Samsung's policy of trying absolutely everything comes real handy to anyone interested in cellphone trends.
quickbunnie - Monday, August 26, 2013 - linkBrian Klug didn't think he'd like the Moto X. After using it, Brian Klug liked the Moto X.
Translation: This phone is frickin awesome!
Brian Klug - Monday, August 26, 2013 - linkI like it a whole lot more than I thought I would, still using it! :)
Fiebre - Monday, August 26, 2013 - linkI wish you guys could do a battery test on the Droid maxx. I would really appreciate it.
icrf - Tuesday, August 27, 2013 - linkI second this point. I'm thus far assuming that, industrial design aside, all Moto X points apply to Droid Maxx, except battery life. The Verge posted their review and said the new Droid Maxx falls short of last year's Droid Razr Maxx despite having an inflated battery life number in the marketing. That said, everyone else's battery tests seem to do silly things like not calibrating the display to a standard, which means the tests are neigh useless. We need Anandtech's superior consistency.
Honest Accounting - Sunday, September 15, 2013 - linkThe battery test here isn't as "objective" as the reviewer claims. It uses a fixed "200 nits" screen brightness, which will favour current LCD technology (and Apple in particular) over OLED . To be credible the screen brightness on the battery test should be a percentage of maximum screen brightness.
geniekid - Wednesday, August 28, 2013 - linkBut would you prefer using the Moto X or the HTC One?
Solandri - Monday, August 26, 2013 - linkI was a bit confused by the flash read/write performance charts. The standard in reviews seems to be to order them sequential r/w, then random r/w. I did a double take, then realized you'd ordered them write random/sequential, then read random/sequential. Different, but no big deal.
Then I did a triple take and realized you'd ordered them write random/sequential, then read sequential/random. Coincidentally, this ordering is best-to-worst for the Moto X.
I trust your site's reviews enough to believe this was purely a coincidence, and that you switched the ordering because you led off by talking about the F2FS filesystem's write speed improvement (with the read speeds maintaining the traditional sequential/random order). But if you're going to switch around the order for the write speeds, you should switch the order of the read speeds to be consistent. The current ordering is not logical, and it gives the appearance of bias in favor of the Moto X.