If you’re thinking that the Snapdragon 801 isn’t a huge step over the Snapdragon 800, you’d be correct. The 801 expands on the foundation laid with the 800 by packing the same quad-core Krait 400 CPU, the same Adreno 330 GPU, and the same 32-bit dual-channel LPDDR3 memory controller. Clock speeds for all these items have increased, but the effects of this shouldn’t be massive.
However, we are talking about an upgrade to the HTC One M7, which was announced in February 2013 and powered by the Snapdragon 600. When we started to see the first wave of Snapdragon 800 devices later in the year there was a sizable performance gap between the two SoCs, so I’m expecting to see something similar going from the M7 to the M8. Interestingly, there are two variants of the HTC One (M8) in the wild: the international version, which packs the Snapdragon 801 MSM8974ABv3 clocked at 2.26 GHz, and the Asian model with a Snapdragon 801 MSM8974ACv3 clocked at 2.45 GHz. HTC kindly provided me with the latter model, which should be even faster than the Snapdragon 800 and give more meat to this performance section. You’ll also find the GPU clock speed has been raised to 578 MHz, and the LPDDR3 memory controller now clocked at 933 MHz for 14.9 GB/s of bandwidth. As far as I’m aware, eMMC 5.0 is not utilized on the all new HTC One. You can compare the device to the HTC One M7 and the Snapdragon 800-powered Nexus 5 in the table below.
Nearly everything has received an upgrade going from the One M7 to the One M8, although internal storage in the base model has dropped from 32 GB to 16 GB. This is made up for by the microSDXC card slot, which supports up to 128 GB cards and provides a far cheaper way of getting a lot of storage in the handset. One downside to the replacement of large internal storage with a microSD card slot is you’ll now have two storage locations in the device, which is a clunky experience on Android. Internal NAND also tends to be faster than microSD card storage, which makes it a better choice for app storage. With that said, companies overcharge extra storage options to ridiculous extents, so the microSD slot is more than welcome. Before I had hands-on time with the HTC One M8 I was curious to learn whether the Snapdragon 801 was noticeably faster than the Snapdragon 800 or Snapdragon 600. On paper, the SoC is definitely faster, as you’ll discover in the benchmarks below, but it’s becoming increasingly hard to tell just how capable it is during regular usage. The HTC One M8 is undeniably a fast smartphone. Everything from loading apps and browsing the web, to navigating the operating system and multitasking, is ridiculously speedy and very fluid. It definitely appears to have a performance edge over the original HTC One, especially in app loading, but it’s a subtle difference rather than a wide speed chasm. Comparing the real-world speed of the HTC One M8 to a Snapdragon 800-powered device like the Sony Xperia Z1 Compact is even trickier, and to be honest, I can’t really discern which is faster.
Gaming is a slightly different story, as the 578 MHz Adreno 330 GPU is significantly faster than the Snapdragon 600’s Adreno 320. The HTC One M7 was no slouch in most handheld games, but occasionally the 1080p display would stretch the rendering capabilities of the graphics core. This is no longer the case in the M8: I simply can’t find a game on the Play Store that stretches the Adreno 330 in either the Snapdragon 800 or 801 to its absolute limits. As other publications have noted, the HTC One (M8) is a benchmark cheater, which is disappointing but not overly surprising to discover. Out of the benchmarks we perform, 3DMark, GFXBench and Vellamo appear to be affected, with the device artificially boosting the GPU’s core clock up to the maximum 2.45 GHz when it detects benchmark applications have launched. This appears to be slightly different behaviour than for the MSM8974AB model, which simply uses a more aggressive governor when benchmarks are detected, rather than forcing the CPU to run at maximum frequencies. Either method is unacceptable, but as most devices contain some form of benchmark cheating code, it evens the playing field somewhat. Interestingly, HTC will actually make the benchmark cheating behaviour available in all apps through a setting in the hidden developer options. On the Asian review model I received, the ‘feature’ was unfortunately missing.
In Peacekeeper, the HTC One (M8) is the new fastest Android device we’ve tested at TechSpot, falling 30% behind the iPhone 5s, but 28% ahead of the next-fastest device: the Snapdragon 800-powered Galaxy Note 3. The Snapdragon 801 MSM8974AC’s clock speed is only 10% higher than the 800, and there’s 16% more memory bandwidth, so gains are a little higher than expected. The One M8 is 49% faster than the One M7 in this test.
Kraken tells a different story, with the HTC One (M8) performing on-par with the Sony Xperia Z1 in this largely CPU-bound benchmark. We’re also seeing significant performance gains compared to the original HTC One.
Vellamo’s HTML5 test is a curious one, because it appears the benchmark optimizations have completely failed, and performance has actually regressed compared to the HTC One M7. In the Metal test, though, performance is as expected: 3% faster than the Galaxy Note 3, and 69% faster than the One M7.
In 3DMark we’re seeing the One M8’s upclocked GPU flex its muscles, topping the charts with a score 12% higher than the Galaxy Note 3. The GPU is actually clocked 28% higher, but I doubt it’s running at its maximum frequency throughout the entirety of the benchmark’s run, especially through the CPU-heavy physics section.
Taking a look at results for GFXBench and with the Adreno 330 inside, the HTC One M8 is the first device with a 1080p display to hit 30 frames per second in the onscreen T-Rex HD test. It performs 8% faster than the Galaxy Note 3 offscreen, and 15% faster onscreen thanks to the onscreen buttons reducing the overall rendering resolution. I’ve also included GFXBench’s new OpenGL ES 3.0 benchmark ‘Manhattan’, which is new in GFXBench 3.0. I’ve been testing this benchmark with a few devices behind the scenes now, and it’s certainly a stressful one (it refused to load on the Moto G). Like in T-Rex HD, the One M8 shows that it’s the fastest GPU overall in fixed-resolution scenarios, but falls behind in onscreen tests having to render to a near-1080p display.
Another set of benchmarks I’ve been preparing behind the scenes is a sequential and random read/write test for a smartphone’s internal NAND. Here you can really see the differences between the HTC One M8 (which tops the charts) and the HTC One M7, the latter of which is much slower across the board.
Topping it all off is the USB file transfer test. The HTC One M8 is limited to USB 2.0 transfer speeds, so it fails to match the Galaxy Note 3. Throughout my usage I had no trouble with Wi-Fi 802.11n on either the 2.4 GHz or 5 GHz bands, Bluetooth 4.0, GPS (which locks quickly) or NFC. There’s also the IR LED hidden inside the power button, which can be used to control TVs through the aptly named ‘TV’ app on the handset
