Battery Life

Battery life is a huge concern in the smartphone space these days, especially as phones get bigger and more powerful. The Moto X includes a unique 2200 mAh, 3.8 V (8.36 Whr) stacked battery made by LG chem, which maximizes battery volume given the Moto X’s rounded form factor. Motorola was very vocal about the battery life of the Moto X, and made the claim of up to 24 hour of mixed use with the device in addition to up to 13 hours of call time. Given the smaller (albeit AMOLED) display and dual core SoC, the Moto X was an easy target for the narrative that higher end specs and quad core SoCs are killing smartphone battery life, which many immediately latched onto and parroted claims of amazing battery life.

The Moto X's stacked battery

Of course, the real question is how the Moto X stacks up to the competition in our objective tests. I have to admit that my initial subjective impressions of the Moto X battery life were not all that great. My first time daily driving the Moto X was after getting it in NYC and flying home – I left the hotel with it fully charged, spent 4 hours in a plane with it in airplane mode, and Moto X still died in the baggage claim before I could make it home. The second time I daily drove the Moto X, I also managed to kill it doing nothing out of the ordinary before I got back home. I honestly can’t remember the last time I drained a phone completely actually using it. Since those couple of times I haven’t had problems making it through a full day when I’ve daily driven the Moto X, but that’s with my usual opportunistic charging from every available wall socket and USB port, and my mixed use definitely isn’t 24 hours, rather closer to 8.

Our objective battery life tests are unchanged so I’m not going to go through all of it in excruciating detail again – you can read any previous review and get the details. At a high level we calibrate the display to exactly 200 nits, then run through a bunch of webpages with content every dozen or so seconds until the device dies, on both cellular, and WiFi. The call test is self explanatory – there’s voice at both the originating terminal and terminating terminal, and we time how long the call goes for until the device dies.

AT Smartphone Bench 2013: Web Browsing Battery Life (4G LTE)

AT Smartphone Bench 2013: Web Browsing Battery Life (WiFi)

Cellular Talk Time

Battery life on the Moto X doesn't turn out to be all that much different from the other flagships based on APQ8064 on LTE. In fact, it's about par. That's not too surprising for me considering compared to the HTC One and SGS4 it's the same CPU (Krait 300) and process (28nm LP). For better battery life we'll need better efficiency, which will come either through newer process (28nm HK-MG variants at TSMC) or even more efficient CPU architecture.

In reality, having fewer cores here means in something multithreaded like our battery test (Chrome is very multithreaded) it needs to send the Moto X's two cores to a higher frequency and voltage state than the four on the other devices. I'm not surprised at all to see invalidation of the "fewer cores translates to better battery life" narrative others have crafted. The only validation is that having two fewer cores does translate to less dynamic range in power use. It all becomes a matter of how you're using the device at that point, however. On WiFi the Moto X does do pretty well, and Motorola has always had very good talk time. 

One thing I will note is that the Moto X does have a power saver mode, but it appears to just disable background sync and put the data connection to sleep aggressively. It doesn't change the governor so that the max CPU frequency is lower (say the 1.1 GHz state) like a lot of other OEMs power savers do, which seems like a missed opportunity. 

The Moto X comes with a dual-USB port 850 mA charger, like the previous revision of Motorola devices. In practice I've seen the Moto X reliably pull closer to 1 A from the Moto X bundled charger.

What's interesting however is that the Moto X can charge up to the maximum BC1.2 rate of 1.5A. If you use that kind of charger, it charges impressively fast, around 2.3 hours. 

Device Charge Time - 0 to 100 Percent

Display & Sound CPU Performance


View All Comments

  • Tralio - Wednesday, September 11, 2013 - link

    Havn't needed to clean my X yet. The touchless control works in standby mode and responds so far to every application i've thrown at it including the downloaded ones (and of course the web search). As for the car being the only place needed, not at all. I'm a chef and use my phone for radio at work, so obviously having to touch the screen after i plug it into the radio is a major hassle. Not everyone is going to use this feature for the same reasons, and some of us are going to use it alot more than others. For me this was part of the selling point, and so far i'm not disappointed. Reply
  • Honest Accounting - Monday, September 16, 2013 - link

    With the Android 4.3 update (and Bluetooth LE) expect an API ("MotoActv API") that will allow it to act as a pseudo-fitness tracker like the iPhone 5S with Nike+ ... They'll probably integrate with MyTracks out of the box Reply
  • Honest Accounting - Monday, September 16, 2013 - link

    No other phone has a distinct voice control MCU. Apple have just add a contextual core (M7) to create what you could call a "X7 Computing System" (assuming dual swift A7 CPU, quad 543MP4 GPU, and M7 processor - there's no M8 "core" for voice processing). The Moto X is unique in this regard - AFAIK Reply
  • Krysto - Monday, August 26, 2013 - link

    Exciting to see F2FS already on an Android phone. Now I'm sure it will come to KLP, since it's rumored to support kernel 3.10, and many improvements to the F2FS file system. With KLP, F2FS might replace ext4 as the default file system for Android, which would be quite excellent. Reply
  • Impulses - Tuesday, August 27, 2013 - link

    I wonder if any of Motorola's work in implementing F2FS makes it back to stock Android at some point or if the teams are segregated enough that they'll just do their own thing regardless... Reply
  • Honest Accounting - Monday, September 16, 2013 - link

    OEMs contribute back to the central Android effort all the time Reply
  • Krysto - Monday, August 26, 2013 - link

    I wish Motorola would've at least used Aptina's Clarity+ camera, which seems significantly better in both low-light (2 clear pixels instead of 1) and in clarity. It's also a crime that they didn't use OIS on it - come on!

    Btw is it me or is the color on BOTH Lumias completely off?
  • rcpinheiro - Monday, August 26, 2013 - link

    Great review. Just a small nitpick :4K and UHD are not synonymous, they are two different standards. Reply
  • jeffkibuule - Monday, August 26, 2013 - link

    UHD is a standard, 4K is a marketing term, much like Full HD and 1080p before it. Reply
  • Mondozai - Monday, August 26, 2013 - link

    UHD and 4K is not the same thing and neither is a marketing term. You need to read up on the facts.

    UHD = 3840x2160
    4K = 4096x2160

    In addition, 4K should have an aspect ratio of 1.9:1 while UHD is usually at 1.78:1.

    Jeff, if you don't know what you're blabbering about, then don't babble.

Log in

Don't have an account? Sign up now