This is our the first smartphone we’ve seen with a 28nm SoC, and thus battery life is the big question. Further, the handset includes all the onboard MSM8960 radio goodness as we’ll mention in a bit. The problem with some HTC phones for the longest time was that they shipped with smaller than average batteries - while the competition continued up past 6 Whr, HTC would ship phones with 5 or so. That changes with the HTC One X, which includes a 6.66 Whr (1800 mAh, 3.7V) internal battery. I’m presenting the same battery capacity chart that we did in the Xolo X900 review for a frame of reference.

Like we did with the X900 review, we’re going to present the normalized battery performance - battery life divided by battery capacity - to give a better idea for how this compares with the competition.

Battery Capacity

As a reminder, the browsing tests happen at 200 nits and consist of a few dozen pages loaded endlessly over WCDMA or WiFi (depending on the test) until the phone powers off. The WiFi hotspot tethering test consists of a single attached client streaming 128 kbps MP3 audio and loading four tabs of the page loading test through the handset over WCDMA with the display off.

Web Browsing (Cellular 3G - EVDO or WCDMA)

HTC is off to an incredible start with our 3G web browsing tests. Even if you assume that Android and iOS are on even footing from a power efficiency standpoint, the HTC One X is easily able to equal Apple's best in terms of battery life. In reality my guess is that the 4S is at a bit of an unfair advantage in this test due to how aggressive iOS/mobile Safari can be about reducing power consumption, but either way the AT&T One X does amazing here. The advantage isn't just because of the larger battery either, if we look at normalized results we see that the One X is simply a more efficient platform than any other Android smartphone we've tested:

Normalized Battery Life - Web Browsing (Cellular 3G)

The Tegra 3 based international One X doesn't do as well. NVIDIA tells us that this is because of differences in software. We'll be testing a newer build of the One X's software to see how much of an improvement there is in the coming days.

Moving onto WiFi battery life the AT&T One X continues to do quite well, although the Droid 4 and RAZR MAXX are both able to deliver longer battery life in this case:

Web Browsing (WiFi)

There are too many variables at play here (panel efficiency, WiFi stack, browser/software stack) to pinpoint why the One X loses its first place position, but it's still an extremely strong performer. Once again we see a noticeable difference between it and the international One X.

Normalized Battery Life - Web Browsing (WiFi)

The big question is how well does the AT&T One X do when we're using the MSM8960's LTE baseband? Pretty darn well, when you consider that it's bested only by the RAZR MAXX with its gargantuan battery. Probably the most notable comparison point here is the HTC Vivid or Galaxy Note on AT&T which both are based on the APQ8060 + MDM9200 combination. 

As a reminder, the Verizon / CDMA2000 LTE devices here are at a bit of a disadvantage due to virtually all of those handsets camping CDMA2000 1x for voice and SMS. The AT&T LTE enabled devices use circuit switched fallback (CSFB) and essentially only camp one air interface at a time, falling back from LTE to WCDMA to exchange a call.

Web Browsing (Cellular 4G WiMAX or LTE)

This particular graph doesn't tell the full story however. In practice the AT&T One X seems to last a lot longer using LTE than any LTE Android phone we've tested in the past. Nipping at the heels of the RAZR MAXX, we need to look at normalized battery life to get an idea of just how efficient the new 28nm LTE enabled SoC is:

Normalized Battery Life - Web Browsing (Cellular 4G)

Now that we have 28nm baseband we've immediately realized some power gains. As time progresses, the rest of the RF chain will also get better. Already most of the LTE power amplifiers vendors have newer generation parts with higher PAE (Power-Added Efficiency), and such improvements will hopefully continue to improve things and gradually bring LTE battery life closer to that of 3G WCDMA or EVDO.

Using the AT&T One X as a WiFi hotspot is also going deliver a pretty great experience:

WiFi Hotspot Battery Life (3G)

WiFi Hotspot Battery Life (4G)

As an LTE hotspot the RAZR MAXX's larger battery is able to deliver a longer run time, however the One X does very well given its battery capacity and size.

Finally, our cellular talk time charts put the AT&T One X in the upper half of our results. Overall the AT&T One X appears to do very well across the board, but it's very strong in the 3G/LTE tests.

Cellular Talk Time

Normalized Battery Life - Cellular Talk Time

 

Software - ICS with Sense 4 Performance
Comments Locked

137 Comments

View All Comments

  • frostyfiredude - Tuesday, May 1, 2012 - link

    If there is one difference that really stood out between the International and ATT versions of the One X, it's the battery life. For all the talking nVidia did about Tegra3 allowing world beating battery life, it really got served by the S4 in that regard.

    In the fall I really hope HTC makes a One X like phone with WP8 on it, if I'm not feeling cheap I think I'll buy one.
  • ImSpartacus - Tuesday, May 1, 2012 - link

    Yeah, that's really the most important thing for me. I'm glad Anandtech puts it earlier in the reviews.
  • Chloiber - Wednesday, May 2, 2012 - link

    It's true. I'm currently owning a One X (international). I'm okay with the battery life (it's better than my previously HTC Desire). But as Brian has mentioned, software updates are on the way. The second update has been released yesterday. The updates are coming out nearly weekly! The improvements are huge in many aspects. The last update (released yesterday in Europe for unbranded devices) finally enabled 2D GPU Acceleration. That's right: 2D GPU Acceleration wasn't working properly before. It couldn't even be forced in the dev settings.

    I really hope they can improve the device even more, and I'm pretty confident they will. To be perfectly honest, I would have preferred the S4 version of the One X. Nvidia still seems to have some problems with the T3 - again, I'm confident that the device's performance and battery life will improve massively over the next couple of months, but S4 seems to be the safer bet.
  • pikahatonjon - Tuesday, May 1, 2012 - link

    i know its offtopic, however, how come it seems like the Droid Razr performs like 40% better than the galaxy nexus 58.7 fps vs 33.1 when they both have the same SoC? was there some error in the test
  • frostyfiredude - Tuesday, May 1, 2012 - link

    Higher resolution display on the Nexus would be the cause of most if not all of the difference. 960x540 for the RAZR v 1280x720 for the Nexus
  • PyroHoltz - Wednesday, May 2, 2012 - link

    I really wish Anandtech would normalize the graphics benchmarks to FPS/megapixel of screen resolution.

    Or, implement something that will take the fluctuations in native resolution, out of the equation a bit.
  • Goty - Wednesday, May 2, 2012 - link

    Just look at the "offscreen" numbers, those are all rendered at the same resolution regardless of handset.
  • ChronoReverse - Wednesday, May 2, 2012 - link

    The Offscreen Test is a seriously flawed one. It's clear that the act of rendering to the screen has a different penalty for different GPU's.

    Since you have to render in actual 3D applications, this means that the Offscreen test is worse than useless since it's _misleading_.

    You can't even say it's a VSync issue because in this very article, you have the GLBenchmark test at 720P where the results for both the Global and ATT OneX phones are both significantly below 59-60FPS.
  • Goty - Wednesday, May 2, 2012 - link

    Writing of the framebuffer to the screen is the least part of what each GPU has to do and certainly has less of an impact that differing resolutions between screens; I highly doubt that writing out the framebuffer is even that different between different architectures.
  • metafor - Thursday, May 3, 2012 - link

    It's very much in line with the V-Sync results we've seen with the MDP and other devices that allow you to turn V-Sync off.

    The tests with the Qualcomm MDP show exactly this kind of difference with V-Sync turned on and off, even if the resulting average doesn't come close to 60fps.

    Why? Because framerate can vary by a lot within the running of the benchmark. Simple sequences can burst up to the 100's of frames per second. That will throw off the average by a lot.

Log in

Don't have an account? Sign up now