The performance section is probably a good place to talk about one of the elephants in the room, and that’s the SoC inside the One max. The One max includes a Snapdragon 600 APQ8064T SoC, which consists of 4 Krait 300 cores running at up to 1.7 GHz, and Adreno 320 GPU, all built on TSMC’s 28nm LP process. This is the same SoC that shipped in the original HTC One, and the same 1.7 GHz bin as well. There have been three major variants or families of APQ8064(T) to date. There first was the option for the earliest 1.5 GHz Snapdragon S4 Pro version (AA suffix), the 1.7 GHz “8064T/Pro” variant in the HTC One and One max (AB suffix) which began the Snapdragon 600 branding, and finally the 1.9 GHz CPU and 450 MHz GPU variant we first saw in the SGS4 (AC suffix). Qualcomm usually has a number of revisions of its silicon, and with APQ8064 we saw quite a few. As an aside, expect similar with 8974 or Snapdragon 800.

 

There’s nothing wrong with the 1.7 GHz Snapdragon 600 variant, it was and still is a great performer, but the reality is that HTC falls behind on its hardware platform with the One max by not going to Snapdragon 800 (MSM8974) like the rest of the competition (Note 3, ASUS Padfone Infinity 2014, LG G2, Nexus 5, and so on). So much of the SoC performance and power story right now is gated by process, and 8974 moves to TSMC’s high-k metal gate 28nm HPM process which affords some clock headroom (up to 2.3 GHz) and lower power consumption at lower performance states for Krait 400 (which is essentially 300 implemented on that new process). 8974 also brings a beefier Adreno 330 GPU with more ALUs and higher clocks, in addition to the new modem IP block, but I won’t go over all of that.

It’s pretty obvious to me that the One max stays with the same SoC used in the original One for a few reasons which ultimately boil down to cost and margin. It obviously means HTC can share the same SoC between the One and One max, and since it’s later in APQ8064’s lifespan I would suspect HTC was able to secure good pricing for it. Having closer shared hardware platform means about the same software stack on top of it, and the same source tree from Qualcomm (BSP) for building and testing ROMs. This makes the software maintenance and update costs lower for the One max. I won’t speculate too much beyond that, but I wouldn’t be surprised if the One max started out an 8974 device but later became an 8064 device, given its timing.

I Can't Believe I Have to Regularly Update This Table
Device SoC Cheats In
    3DM AnTuTu AndEBench Basemark X Geekbench 3 GFXB 2.7 Vellamo
ASUS Padfone Infinity Qualcomm Snapdragon 800 N Y N N N N Y
HTC One Qualcomm Snapdragon 600 Y Y N N N Y Y
HTC One mini Qualcomm Snapdragon 400 Y Y N N N Y Y
HTC One max Qualcomm Snapdragon 600 Y Y N N N Y Y
LG G2 Qualcomm Snapdragon 800 N Y N N N N Y
Moto RAZR i Intel Atom Z2460 N N N N N N N
Moto X Qualcomm Snapdragon S4 Pro N N N N N N N
Nexus 4 Qualcomm APQ8064 N N N N N N N
Nexus 7 Qualcomm Snapdragon 600 N N N N N N N
Samsung Galaxy S 4 Qualcomm Snapdragon 600 N Y Y N N N Y
Samsung Galaxy Note 3 Qualcomm Snapdragon 800 Y Y Y Y Y N Y
Samsung Galaxy Tab 3 10.1 Intel Atom Z2560 N Y Y N N N N
Samsung Galaxy Note 10.1 (2014 Edition) Samsung Exynos 5420 Y(1.4) Y(1.4) Y(1.4) Y(1.4) Y(1.4) N Y(1.9)
NVIDIA Shield Tegra 4 N N N N N N N

The HTC One max, like a ton of other devices, continues to employ a CPU optimization “boost” feature which plugs in all the CPU cores and increases clocks to their maximum upon detection of certain benchmarks. It’s sad that this needs to be a regular disclosure for each handset release, since the narrative will likely be the same for the near future, but yes the One max does this. 

Given product development cycles and how long it takes software in the Android landscape to make it through the chain from internal OEM testing to operator test approval and finally hitting devices, I expect we’ll see a pipeline of devices with this “feature” enabled for a while before it changes, even if we could change every OEM’s mind about it right now. I’m starting to understand more about the origin of these optimizations, the list of APKs they detect and boost for, and what party is ultimately responsible, but that’s a story for another day.

CPU

AndEBench - Java

AndEBench - Native

Google Octane Benchmark v1

Mozilla Kraken Benchmark - 1.1

SunSpider Javascript Benchmark 1.0 - Stock Browser

Browsermark 2.0

Vellamo Benchmark - 2.0

Vellamo Benchmark - 2.0

3DMark Unlimited - Physics

3DMark Unlimited - Physics Test

3DMark - Physics Extreme

3DMark - Physics Test (Extreme)

GPU

 

3DMark Unlimited - Graphics

3DMark Unlimited - Graphics Test 1

3DMark Unlimited - Graphics Test 2

3DMark Unlimited - Ice Storm

3DMark - Ice Storm Extreme

3DMark - Graphics Extreme

3DMark - Graphics Test 1 (Extreme)

3DMark - Graphics Test 2 (Extreme)

Basemark X - Off Screen

Basemark X - On Screen

Epic Citadel - Ultra High Quality, 100% Resolution

GLBenchmark 2.7 - Egypt HD

GLBenchmark 2.7 - Egypt HD (Offscreen 1080p)

GLBenchmark 2.7 - Fill Test

GLBenchmark 2.7 - Fill Test (Offscreen 1080p)

GLBenchmark 2.7 - T-Rex HD

GLBenchmark 2.7 - T-Rex HD (Offscreen 1080p)

GLBenchmark 2.7 - Triangle Throughput

GLBenchmark 2.7 - Triangle Throughput (Offscreen 1080p)

GLBenchmark 2.7 - Triangle Throughput, Fragment Lit

GLBenchmark 2.7 - Triangle Throughput, Fragment Lit (Offscreen 1080p)

GLBenchmark 2.7 - Triangle Throughput, Vertex LitGLBenchmark 2.7 - Triangle Throughput, Vertex Lit (Offscreen 1080p)

Storage

 

Random Read (4KB) PerformanceRandom Write (4KB) PerformanceSequential Read (256KB) PerformanceSequential Write (256KB) Performance

I’m not going to go through all the benchmark results on the One max since again it’s the 1.7 GHz Snapdragon 600 SoC we’re very familiar with at this point. The only oddity is storage performance, where the One max trails in random writes and reads, I'd attribute this to a different eMMC being used. The rest of the results are essentially within the margin of error. I initially suspected that the One max might have a bit more thermal headroom than the One, but this doesn't really seem to play itself out in the results, possibly due to the removable back door. 

Sense 5.5 and Android 4.3 Charging and Battery Life
Comments Locked

197 Comments

View All Comments

  • rabidkevin - Tuesday, October 29, 2013 - link

    What you are missing is that OEM's want internal only storage to CONTROL THE MARKET! Charging premiums on space for outrageous amounts. It has nothing to do with user demand. Why would anyone turn down 32gb of extra space for 30 bucks?

    I still have a galaxy s2 that I just FINALLY paid off after 2 years. I'm not ready to make payments for 2 more years when I have a perfectly good working phone in my hand.
  • Black Obsidian - Tuesday, October 29, 2013 - link

    You're rabid alright, Kevin.

    The vast majority of users don't want expandable storage, because the vast majority of users aren't using all of the storage in their (overwhelmingly base-model-storage) phones as it is. Why is this? Well, because the vast majority of users aren't carrying 1,000+ hours of music around with them at all times. Hell, I'd be shocked if the majority of users even HAVE 16GB of music in the first place!

    Us geeks aren't the whole smartphone market. Pre-iPhone, we absolutely were. Now? To say we even account for 5% of the overall market would be overly generous, probably by a factor of 10. We're a tiny, TINY fraction of the market, and even then, only *some* of us care about removable storage.

    The OEMs might enjoy milking people by charging them $100 for each $20 increment of flash, but relatively few people are bothering to pony up for 32 or 64GB even where it is an option. If you combined all the people who actually use expandable SD *and* all the people who upgrade from base 16GB devices with no expansion, I doubt you'd reach even 10% of the market. Or 5%, for that matter.

    (relatively speaking) Nobody cares.
  • Klug4Pres - Tuesday, October 29, 2013 - link

    Brian, some people want removeable SD cards, and what's more the ability to use them is, objectively-speaking, a useful feature with almost no down-side (if we ignore business decisions to economise by reducing internal storage on phones with this feature, and what Google sees as the inability of users to deal with more than one storage location). If the HTC One has a particular design that would be compromised by allowing SD cards, that may be so, but there are other possible designs, and I doubt you could argue that they would be systematically inferior.

    "Being deprecated by a platform" is not a good reason not to support them. Google obviously has a vested interest in tieing people to the Cloud, so we shouldn't care what Google thinks about this.

    You have argued, persuasively, that removeable batteries do involve more of a trade-off, but again some people are more than willing to accept that trade-off because of how they wish to use their device, and because they may wish to make use of the device for longer than the expected service life of the battery.

    Oh, and I'm calling flamebait on the "going the way of the dodo" comment.
  • Jedi2155 - Wednesday, October 30, 2013 - link

    I take issue with the comment on internal batteries being bigger when sealed in versus removable. In terms of energy I have yet to see this to be true. All the galaxy phones have continued to have removable batteries yet remain in an incredibly small form factor. My Note II has nearly the same energy capacity (~3100 mAh, Note 3 ~3200 mAh), in a smaller and thinner form factor than the 3300 mAh of the HTC One max. I personally believe most of the reason for an internal battery is simply laziness in design. It simply takes a lot more engineering and design work to include a removable battery versus not. I completely believe its possible to cram a removable version of the same 3300 mAh battery in the phone with the volume they had available in this phone. I bet they could have increase the battery volume even further if they put more effort into it.

    My primary point is that, while going internal does offer some volumetric benefits, majority of the manufacturers do not exploit it for the simple reason that it costs more.

    I'm not even going to touch the microSD comment (even while quite possibly true, many geeks and their gf's still demand it).
  • Steven JW FCK - Monday, October 28, 2013 - link

    So what is wrong having "dumb manually managed storage?"

    It sounds to me like a feature, and a feature I would happily want to have in its usefulness in being partitioned off from the rest of the phone.

    And build quality? Really? The way you talk about build quality sounds more like you are interested in how pretty it looks to you and other people? Your hand is supposed to be around the phone when you use it in the first place, so most of this phones plastic surround will be invisible to you and others, so why are so fussy on wanting a pretty phone, over a feature packed phone? Would better build quality translate into better drop-ability? Not at all! That would be an absurd conclusion to blindly believe.
  • Dentons - Monday, October 28, 2013 - link

    But Brian, you don't focus on build quality, not really. Your critique suggests an overwhelming devotion to the fashion of these devices. You're actually neglecting the underlying technology in many cases to focus instead on things one suspects most Anandtech readers could care less about. Honestly? How much time did you devote to the Gold iPhone in a recent podcast? Yes, it's gold, we get it.

    Carhartt jeans, Toyota Camry's, and Samsung phones all have good build quality. Louis Vuitton, Rolls Royce, and metal skinned phones are almost entirely about fashion. Not the phone's electronics of course, but the metal casing, yes, fashion. You're ignoring the actual technology in favor of focusing, and focusing, and focusing on the minutia of the exquisite metalized skins of these devices.

    Metal may often be studier, but that doesn't devolve everything else to crap. That is often the conclusion to be drawn from your criticism. In point of fact, there are plastics with far better strength to weight ratios than any metal. As a technology person, I really don't care if the case is metal or plastic, so long as it's functional. Your endless rants about the greasy Samsung casings truly baffles me. One wonders if you have some sort of unusual oil factories in the palms of your hands?=.

    Or just maybe, you go through so many phones that are all so similar, the small differences start to become big differences. In that light, I recommend the following XKCD comic strip: http://xkcd.com/915/ - "Connoisseur"
  • Brian Klug - Monday, October 28, 2013 - link

    Yes I do focus on build quality in the review, and the context is still the tradeoff not being worth it in the case of the One max.

    "neglecting the underlying technology"

    What are you even talking about?

    -Brian
  • Dentons - Monday, October 28, 2013 - link

    I'm talking about the fact that you rarely, or barely give any kudos to devices with microSD and user swappable batteries. Those features aren't listed as benefits, they're hardly mentioned at all. Anandtech tests everything else, but I cannot recall the last time Anandtech tested the speed of a microSD port.

    Your recent review of the Note 3 was a case in point. You barely mentioned either of those features. They are real, actual hardware differentiators. For many of us, not only are they important differentiators, the absence of them is a deal breaker.

    A cost conscious consumer can honestly want a device to be future proofed for a few years. We don't get new, free, phones a few times each month. Our batteries wear out. Media sizes are ever increasing. Not all of us want to rely, nor can we rely on the cloud for all our media needs. It is a waste for us to spend an extra $200 for a phone with 64GB when we're far better served with $30 in cheap SD storage. As you point out, we cannot use it for apps, it's for video and music. For those use cases, the highest quality NAND is generally wasted.

    Even though you don't use those features, the best selling smart phone models in the world still have them. You spend orders of magnitude more time discussing the casings, finishes, and lustrousness of phones than either of those. So yes, in this case, you definitely are neglecting the underlying technology in favor of fashion.

    On this topic, in both in your reviews and on the podcast, your attitude is one of "I know what you need better than you know what you need". That's what you're telling us. That you're the expert, and that you know best.

    How would you respond to a reviewer repeatedly telling you that you really didn't need the features you used every single day? That's what you're doing. It's annoying, and insulting.
  • apertotes - Tuesday, October 29, 2013 - link

    Well, if they did not neglect those features they would have to criticize Apple for not providing them, and that is a deadly sin.

    Since Apple is perfection, that is the mirror they use to analyze the rest. Things that do not exist in Apple are worthless by definition.
  • Dentons - Tuesday, October 29, 2013 - link

    You make a relevant point, and allude to another equally important point.

    As you point out, by not giving kudos to phone makers who include microSD and removable batteries, they don't have to list the absence of those features as cons to the Apple and Nexus products the staff here tend to glow over.

    Which leads into another key point. We all know what would happen were Brian's to neglect to mention a key, unique, hardware differentiator in the review of an Apple product. Apple or their marketing agency would contact him. They'd bitch, they'd moan, they'd complain, they may even threaten future review status.

    Many reviewers know not to neglect a focus on Apple's little differentiators, but they have little compunction in reviewing 'lesser' devices with a completely different set of rules.

Log in

Don't have an account? Sign up now