While we can dance around the issue, it’s impossible to have any real discussion about Snapdragon 810 without addressing the flurry of rumors that have surrounded this SoC. There have been rumors of overheating, delays, and all sorts of defects. In light of this, the Snapdragon 810 and its performance has been the subject of intense interest. In order to learn more, we recently met with Qualcomm to do a deep dive on the Snapdragon 810 and properly benchmark it for comparison against other SoCs.

While those that have followed the SoC market closely are likely to be quite familiar with the Snapdragon 810, it’s still worth going over the basics of the SoC before diving into aspects such as performance. In general, the area of greatest focus and one of the most important aspects of any SoC is the application processor. In the case of the Snapdragon 810, Qualcomm has licensed ARM’s Cortex A57 and A53 architectures for the CPU, which we’ve previously discussed in depth in our review of the Galaxy Note 4 Exynos. The Snapdragon 810 comes with the A57 cluster clocked at 1958 MHz and the A53 cluster at 1555 MHz.

Qualcomm Snapdragon S810 Specifications
SoC Snapdragon 810 Snapdragon 805 Samsung
Exynos 5433
CPU 4x Cortex A53@1.555GHz

4x Cortex A57 r1p1 @1.958GHz
2MB L2 cache
4x Krait 450@2.65GHz
4x512KB L2 cache
4x Cortex A53 r0p1@1.3GHz
512KB L2 cache

4x Cortex A57 r1p0 @1.9GHz
2MB L2 cache
2x 32-bit @ 1555MHz

24.8GB/s b/w
4x 32-bit @ 800MHz

25.6GB/s b/w
2x 32-bit @ 825MHz

13.2GB/s b/w
GPU Adreno 430
@ 600MHz
Adreno 420
@ 600MHz
Mali T760MP6
@ 700MHz
20nm SoC
28nm HPm
20nm HKMG

For the most part, Qualcomm seems to have adopted a relatively similar approach by using a 4+4 big.LITTLE design, which means that four Cortex A57s serve as the “high power” cores, and four Cortex A53s work as the “low power” cores, with a CCI-400 to allow for cache coherency between the two clusters. However, while the architecture is licensed from ARM the actual implementation of the logic has been optimized by Qualcomm to improve performance and/or power consumption. Like most recent big.LITTLE SoCs, Qualcomm’s Snapdragon 810 has all eight cores exposed to applications, and relies upon task scheduling mechanisms to decide how to place threads on each core. However Qualcomm, as opposed to all other licensees of big.LITTLE, has decided to stray away from ARM's and Linaro's software implementation, and we'll be scratching the surface of what this means in terms of power and performance on the Snapdragon 810.

Outside of the SoC, Qualcomm has integrated an Adreno 430 GPU, which is said to deliver a performance improvement of 30%, possibly more for a shader-heavy workload. Outside of this the Adreno GPUs continue to be a black box in terms of technical detail. Qualcomm states that this GPU wasn’t a straight extension of the Adreno 420 which suggests that there have been architectural changes to the GPU, although we weren’t told what they were. We should be seeing final clocks running at 600MHz, meaning the GPU is running at the same frequency as the Adreno 420 in Snapdragon 805 devices.

To feed these components and the rest of the SoC, Qualcomm has fitted the SoC with a dual-channel 32-bit (total 64-bit) wide LPDDR4-1555 memory interface, which means a peak of 24.9 GB/s in memory bandwidth and basically maintains parity with the Snapdragon 805 despite the reduced bus width. The move to LPDDR4 should also bring a reduction in power consumption of the memory interface of up to 20% when compared to LPDDR3.

Outside of the GPU and CPU, Qualcomm has focused on iterating all other aspects of this SoC. The Snapdragon 810 represents Qualcomm’s first high-end SoC with an HEVC encoder, which is said to support up to 4K30 although we were not told the exact bit rate limits or any other encoder settings. Along the same lines, Qualcomm has upgraded the ISP in the Snapdragon 810 to a “14-bit” dual ISP, which allows for features such as multiple cameras for depth mapping or other computational photography features. This new ISP in the Snapdragon 810 can process 1.2 GP/s, in contrast with the 1 GP/s of the Snapdragon 805’s ISP. As mentioned in previous articles, this ISP is clocked at 600 MHz. The audio codec is the WCD9330 which is carried over from the Snapdragon 805.

On the RF side of things, Qualcomm is introducing a new category 9 modem that is built into the Snapdragon 810. In our experience, an integrated modem does improve battery life, although in practice these benefits will likely be difficult to distinguish from a multitude of other factors on total battery life. While one might guess that this is similar to the MDM9x45 external modem, it seems that there may not be enough bandwidth to support both upload and 3x download carrier aggregation. We also see a new suite of RF360 parts to accompany the Snapdragon 810, which include an antenna tuner, CMOS PA/antenna switch, and envelope tracker. Outside of the WTR3925 transceiver that was introduced with the Snapdragon 805, we see a new WTR3905 companion chip for 3x download CA and upload CA. In addition, we see a new variant of the QCA6174 WiFi chip, the QCA6174A, which enables MU-MIMO and a separate chip to enable 802.11ad.


The basics can be all that's necessary to cover the RF changes in the Snapdragon 810 platform, but now is as good a time as any to really get down to the details of how this all works. For a while now, RF has been a black box. We’ve done some work on demystifying some aspects of RF, but there’s still quite a bit left to cover. While we have covered parts of RF systems like the envelope tracker, that’s only one piece of the puzzle. As a front-end solution, we’re still missing a great deal of nuance on the CMOS PA and integrated switch, along with the dynamic antenna tuner. In addition, there’s quite a bit in the pipeline that has come out since our last article on the state of Qualcomm’s RF components. WTR3925 and MDM9x35 have been shipping in mobile devices for a while, and we’re on the cusp of seeing new modems like Qualcomm’s MDM9x45 so there’s no better time to talk about all of this.

For those that are unfamiliar with how radio works at a high level it’s well worth going over in order to understand how everything comes together. At the basic level, on the receive path we can start at the antenna. The antenna is rather simple, and its goal is to convert radio waves into electrical energy. There’s definitely a lot more to this area, but for now that’s really all the knowledge that’s necessary. From there, the next step in the path is an antenna switch, which is used to select the right path for receive and transmit depending on the band used. A duplexer is the next step in the chain and is used to allow transmit and receive to be split into two separate parts. Before we get to the transceiver itself, filters (ideally) strip out any received signal that is out of the desired frequency band.

Once we get to the transceiver, a low noise amplifier takes the relatively weak signal from the filter and boosts it. After this, a down-converter converts the frequency of the signal to a baseband frequency by using a local oscillator that generates a signal that is mixed with the incoming signal. This is necessary because the signal is coming in at anywhere from 700 MHz to 5 GHz, which is almost impossible to process in real time with a relatively low-clocked DSP. In addition, this makes it easier to reject noise and due to the conversion in frequency it’s much easier to design an amplifier for this signal. That’s exactly what happens after this down-conversion. The signal is then split into the in-phase and quadrature components to make signal processing simpler. Another amplifier boosts the signal and then it reaches the baseband. At the baseband, an analog to digital converter processes the signal, and then the signal is demodulated. Once this is accomplished, the rest of the system simply sees the information as if it were packets of data in a format like TCP/IP.

The path for transmission is similar, although there are a few modifications on that end. Starting from the baseband, the information is modulated into a specific format, then converted from a digital signal to an analog one as it leaves the baseband. From here, the signal travels through another set of amplifiers before it is combined and raised to the frequency needed for transmission in the up-converter. At this point, another driver amplifier is used to amplify the signal before it leaves the transceiver. There’s currently not much need to understand what the driver amplifier does other than to know that it exists, so don’t worry about that for now. What’s definitely important is the power amplifier. This is the point where the signal is driven from the relatively low levels in the transceiver and baseband to high enough power to contact a cell tower. After this is done, the signal goes through the duplexer, through an antenna switch, out to the antenna.

At a high level, that’s how things work. To break things down into the simplest form, there are two distinct sections. The RF front end and baseband. The front end is designed to accurately capture as much information from the antennas as possible and filter it down to a form that the baseband can handle. The baseband is where all information is processed after the front end and receiver, and acts as the control center for rest of the RF system. It’s definitely a lot to take in, but it will help a lot with understanding the relevance of RF360, WTR3925, and MDM9x35.

RF: Antenna Tuner, CMOS PA/Switch


View All Comments

  • PC Perv - Saturday, February 14, 2015 - link

    Not an accurate description of the state of affairs. It is because Apple has the power over the carriers that other OEMs lack. I wish Congress can intervene in the situation and rein in on the carriers. That will not only benefit the U.S. consumers but also potentially influence the world market.

    Absolutely not "because Apple spend more money and Android OEMs do not want to spend money"
  • name99 - Friday, February 13, 2015 - link

    "While there are multiple solutions to solving the power problem that comes with OoOE, ARM currently sees big.LITTLE as the best solution. "

    I can't help but think (based on all the evidence we've seen so far) that big.LITTLE is the VLIW of low energy CPUs. Just like VLIW would be totally awesome if we could only solve those pesky compiler issues (which are just out of reach, but maybe next year...), so big.LITTLE would be awesome if we could only solve those pesky scheduler issues (which will, likewise, maybe be solved next year...)

    It's nice that QC claim they have a better scheduler; it would be even nicer if they were confident enough about it to provide actual power/energy NUMBERS...
  • TT Masterzz - Sunday, February 15, 2015 - link

    Amazing article. Although to be frank I hardly understood the antenna part. It would be amazing if the authors at Anand Tech make an article explaining the RF system/modems/naming scheme and baseband processors in depth. Also an article explaining some terms like CPU pipeline length/branch mispredict would be amazing. Reply
  • Laststop311 - Friday, February 20, 2015 - link

    All this is telling me is that it can barely beat last generation exynos. The exynos 7 most likely stomps this in performance which is why samsung had to go qwith it for all countries. People would be too mad if only S Korea got the super fast exynos 7 and every 1 else got the slower 810. Before snapdragon had the slioght performance edge but looks like exynos may finally be the better chip.

    That is untile qualcomm busts out their custom made 64 bit krait that just wasnt ready in time so they had to use standard arm cores to get 64 bit to market faster. Custom Kraint 64 whatever they call it it krait 500 or something will most likely beat exynos again.
  • Zingam - Wednesday, February 25, 2015 - link

    Will these be DX12, OpenGL Next compatible, or will we have to wait for another 5 years for sufficient market penetration. Reply
  • Keermalec - Saturday, March 21, 2015 - link

    So The 1-year old Nvidia K1 trounces the yet to arrive snapdragon 810...
    And yes, LTE is not integrated into the K1 in order for OEMS to have a choice between wifi or wifi+LTE tablet versions. Nvidia CAN integrate LTE in the SoC as they have done with the Tegra 4i. It was just sound business practice not to do so with the more powerful chip.
  • radeonex - Saturday, April 11, 2015 - link

    I want to point out that for linear amplifier circuits, most of the transistors operation in the saturated region (they do not act as switches but rather voltage controlled current sources). The high electron mobility helps with trans-conductance and other characteristics especially in the context of combating short-channel effects (helps smaller devices). It also helps to reduce the minimum voltage drop required to keep the saturated transistors in the correct region of operation. Reply
  • Ning3n - Monday, July 27, 2015 - link

    To give a "joe sixpack" review of the 810. I recently replaced my HTC M7 with an M9....

    As far as I've seen/noticed, the 810 (combined with the 430 GPU), is *ROUGHLY* 15-20% faster than the 600 series I've upgraded from.

    Gaming performance (for a cellular device) is great! But, it took over an hour to encrypt just under 5Gb of mp3s, and 1.5Gb of pictures.

    Hardly a "phenomenal" improvement.
  • b.akhil96 - Tuesday, June 21, 2016 - link

    How do you categorize the loads ? max(avg,recent) policy when loads are categorized as peak or non peak . what would be an ideal policy to be applied on Moderate loads. (similar to max(avg,recent) ) Reply

Log in

Don't have an account? Sign up now