Qualcomm announced some mid-range processors back in February, those included two from the Snapdragon 400 series and two from the Snapdragon 600 series. The Snapdragon 620 processor includes some specs that would be typically found in high-end devices like the 4K playback and recording capabilities. It is a 64-bit octa-core processor with four Cortex-A53 cores and four Cortex-A72 cores. A 300 Mbps X8 LTE modem is also integrated into that processor and it uses the new generation Adreno 510 GPU, which should bring great visual performance while saving some battery life. The camera sensors supported by this processor are 13-megapixel ones on both the front and the back of the device. Despite being announced almost 7 months ago, there are still no devices that use it, but it now has been spotted in the GFXBench site.
The device used in the test is unknown, but we can learn a little more about the performance of the processor. As for the specs of the device, it runs on Android 5.1.1 and uses a Full HD display, presumably 2 GB of RAM and 16 GB of internal storage. There’s probably a 13-megapixel camera sensor on the back and an 8-megapixel one on the front as these sensors are fairly common, although the results show pictures of 12 megapixels and 7 megapixels, respectively. The Snapdragon 620 reaches a maximum speed of 1.8 GHz, but on this particular device it is clocked at 1.7 GHz.
The Adreno 510 GPU shows a vast improvement over devices using the last generation Adreno 405 GPU. On the Manhattan Offscreen test, it reached 13 fps, which is more than double of what the leading device with the older GPU could achieve. In the T-Rex test, the new GPU managed to produce images at 31.2 fps, once again, doubling the amount of visuals of the leading device with the older one. These results are certainly good for a mid-range device, proving that this processor is an improvement over the Snapdragon 615, but the GPU performance is still not as good as in devices using the Adreno 430. A Snapdragon 600 processor produced outstanding results in a benchmark test, so it might as well have been this one.