I don’t think there’s any way to sugarcoat this, but 2015 has not been a particularly great year for Qualcomm in the high-end SoC business. The company remains a leading SoC developer, but Snapdragon 810, the company’s first ARMv8 AArch64-capable SoC, did not live up to expectations. Seemingly held back by design matters and a rough 20nm planar manufacturing process – a problem shared by many vendors in the last year – Snapdragon 810 couldn’t make good use of its highly clocked ARM Cortex-A57 cores, and ultimately struggled in the face of SoCs built on better processes such as Samsung’s surprisingly early Exynos 7420.

But the purpose of today’s article isn’t to reminisce about the past, rather it’s to look towards the future. Qualcomm knows all too well what has happened in the past year and the cost to the company that has come from it, so now they need to dust themselves off and try again. With Samsung’s more advanced 14nm FinFET process in hand, a new CPU core, a new GPU, and a number of other advancements, Qualcomm is ready to try again; to try to recapture the good old days of 28nm and their Krait CPU architecture.

If there is any unfortunate aspect to any of this, it’s that while Qualcomm is showing off Snapdragon 820 today, it won’t be ready for the holidays (lining up with what we expect will be the typical spring smartphone refreshes). But some of this is clearly driven by Qualcomm’s business needs and the aforementioned effort at Qualcomm to quickly pick themselves up and try again.

Meanwhile after last month’s demonstrations, this month Qualcomm is ready to move on to the next phase in what has become their traditional roll-out process for a new SoC: giving the press access to the company’s Mobile Development Platform (MDP) devices. Designed for software developers to begin building apps and (for lack of a better word) experiences around the new SoC, the MDP is something of the home-stretch in SoC development, as it means Qualcomm is ready to let the press and developers see the hardware and near-final software stack. We’ve previously previewed the Snapdragon 800, 805, and 810 via their MDPs, and for Snapdragon 820 Qualcomm has once again opted to do the same. So without further ado, let’s take our first look at Snapdragon 820.

Qualcomm Snapdragon S810 Specifications

SoC

Snapdragon 820

Snapdragon 810

Snapdragon 800

CPU

2x Kryo@1.593GHz
512KB(?) L2 cache

2x Kryo@2.150GHz
1MB(?) L2 cache

4x A53@1.555GHz
512KB L2 cache

4x A57@1.958GHz
2MB L2 cache

4x Krait 400@2.45GHz
4x512KB L2 cache

Memory
Controller

2x 32-bit
LPDDR4 @ 1803MHz

28.8GB/s b/w

2x 32-bit
LPDDR4 @ 1555MHz

24.8GB/s b/w

2x 32-bit
LPDDR3 @ 933MHz

14.9GB/s b/w

GPU

Adreno 530
@ 624MHz

Adreno 430
@ 600MHz

Adreno 330
@ 600MHz

Mfc.
Process

Samsung
14nm LPP

TSMC
20nm SoC

TSMC
28nm HPm

Taking a trek down to sunny San Diego, Qualcomm handed to us the Snapdragon 820 MDP/S. A 6.2” phablet, the MDP/S is a development kit designed for function over form, containing a full system implementation (sans cellular) in an otherwise utilitarian design. Along with the Snapdragon 820 SoC, the 820 MDP/S also includes a 6.2” 2560x1600 display, 3GB of LPDDR4 memory runnning at a slightly higher 1804MHz instead of 1555MHz we've seen on the Snapdragon 810 and Exynos 7420, a 64GB Universal Flash Storage package, a 21MP rear camera, 802.11ac WiFi, and a Sense ID ultrasonic fingerprint scanner. Overall the aesthetics of the MDP/S differs significantly from what retail phones will go for, but internally the MDP/S won’t be far removed from the kinds of configurations we’ll see in 2016 smartphones.

Overall there’s little to report on the MDP/S experience itself. Qualcomm is still sorting out some driver bugs – only one device in our group was ready to run PCMark – and to be sure like past Qualcomm MDP previews this is very much a preview. However the experience was otherwise unremarkable (in a good way) with our unit completing all of our tests bar part of SPEC CPU 2000, which will require further analysis.

More interesting from a testing perspective is that Qualcomm opted to demonstrate Snapdragon 820 using the MDP/S smartphone development kit, instead of a larger MDP/T tablet development kit. Qualcomm has used MDP/T for the press demonstrations on both Snapdragon 800 and Snapdragon 810, so the fact that they are once again using the MDP/S is very notable. From a pure performance perspective the MDP/T allowed Qualcomm to show off previous Snapdragon designs at their best – these are just performance previews, after all – but after Snapdragon 810 I don’t doubt that had this been another MDP/T that the 820’s thermals and power consumption would be called into question. So instead we are looking at 820 in a phablet, and while this may not put 820 in the best possible light, the end result is that we get to see what performance in a large phone looks like, and for Qualcomm there isn’t any doubt about 820’s suitability for a smartphone.

As for Snapdragon 820 itself, we’ve already covered the SoC in some depth in past articles – and this week’s preview doesn’t come with much in the way of new architectural information – but here’s a quick recap of what we know so far. 820 uses a new Qualcomm developed CPU core called Kryo. The quad core CPU is best described as an HMP solution with two high-performance cores clocked at 2150 MHz and two low-power cores clocked at 1593MHz. The CPU architectures of both clusters are identical, but with differences in cache configuration and their power/frequency tuning.

Meanwhile the GPU inside 820 is the Adreno 530. This is a next-generation design from Qualcomm and includes functionality that until now has only been found in PC desktops, such as shared virtual memory with the CPU, which allows an OpenCL host program and a device's kernel to share a virtual address space so access to data structures like lists and trees can be easily shared between the host and GPU. The underlying architecture is capable of Renderscript and OpenCL 2.0 on the compute side – a significant step up from Adreno 400 – and on the graphics side supports OpenGL ES 3.1 + AEP and Vulkan. We know the 530 should be powerful, but like past Qualcomm designs the company is saying virtually nothing about the underlying architecture.

Finally, while it’s not something that can be covered in our brief testing, the 820 contains a new DSP block, the Hexagon 680. Hexagon 680 and its Hexagon Vector Extensions (HVX) are designed to handle significant compute workloads for image processing applications such as virtual reality, augmented reality, image processing, video processing, and computer vision. This means that tasks that might otherwise be running on a relatively power hungry CPU or GPU can run a comparatively efficient DSP instead. The HVX has 1024-bit vector data registers, with the ability to address up to four of these slots per instruction, which allows for up to 4096 bits per cycle.

You ignore the fact that Apple has been shipping Kyro class HW since 2014 and Kyro isn't going to ship until 2016. A two year lead is commanding by any kind of definition.

You talk as if only Qualcomm has access to 20% higher without also acknowledging that Apple already ships a very similar design, the A9X, that clocks 30% higher and has no L3 that is approximately 70% faster than the Kyro if we assume the Kyro performs similarly to the A8 at 1.4GHz.Reply

You don't male any sense at all. Apple's old gen core wasn't all that fast while the ipad Pro had higher clocks because the form factor allows it. We are talking in a phone form factor.it is true that Apple's per core power consumption is a bit of an unknown so certain things are assumed.Ryan is a fanboy and he tries to argue that fewer cores are better even he knows very well that more cores provide more computing power in the same TDP. AT worked hard to convince everybody that more core are better when Intel did it and now they are working hard to convince everybody that fewer cores are better when Apple does it because their OS is stuck in the past.Reply

jjj, your comments on this topic are off-base. For starters, there is nothing stuck in the past about iOS. It handles symmetric multiprocessing as well as any device. Realistically, there are far more work roads that are optimized for one processor. Every task will feel faster when a device with fewer but faster cores. There are very few workloads that truly benefit from multiple processors. Reply

It's not using the GPU or DSP. That doesnt just happen automagically ... the app needs to be specifically coded to do that. The reason it gets a high photo editing score is because if has really really great FP performance. Note the Geekbench FP scores -- it is able to beat the 810 in MT in all but ONE test with half as many cores and those 2 cores running much slower.Reply

> That doesnt just happen automagically ... the app needs to be specifically coded to do that.

The app doesn't have to be coded for it. The photo processing part is done in RenderScript by stock Android APIs and that can use the GPU or fall back to the CPU if it fails to do so. Almost all recent Android devices use the GPU. The only time I saw something explicitly fall back to the CPU was on the G4 and it was just a small portion of the test.Reply