The Qualcomm Snapdragon 435 (SD435) is a lower mainstream SoC for (Android based) smartphones and tablets. Contrary to the Snapdragon 630, it is still manufactured in a 28-nm process and also consists of an octa-core CPU part with ARM Cortex-A53 cores. However, they are only clocked at up to 1.4 GHz. The integrated X9 LTE modem supports Cat. 4 with maximum transfer rates of 300 Mbps (downstream) and 100 Mbps (upstream). The SoC also includes an Adreno 505 GPU with support for Vulkan and OpenGL ES 3.1. WiFi 802.11ac and Bluetooth 4.1 are supported as well. The memory controller supports LPDDR3 clocked at 800 MHz (so probably dual-channel DDRL-1600). The main difference to the Snapdragon 430 is the faster LTE modem.
The HiSilicon Kirin 9000W is an SoC that can be used in smartphones and tablets based on Android and was first installed in the Huawei MatePad Pro 13.2.
Huawei does not reveal any information about the SoC. The little information that is available comes from benchmarks and system analysis tools. The CPU consists of three clusters with a total of 12 cores. The power-saving cluster has four ARM Cortex-A510 cores, each operating at up to 1,530 MHz, while six other cores use unspecified cores from HiSilicon (0x0D42) and clock at up to 2,150 MHz. The third cluster contains two HiSilicon cores (0x0D02), each with a maximum clock speed of 2,487 MHz. The performance cores could possibly be based on the TaiShan V120 architecture (as in the Kirin 9000S).
The single-core performance is correspondingly mixed, but the multi-core performance is at the level of a high-end SoC from 2022 due to the numerous cores.
A Maleoon 910 by HiSilicon is integrated as the graphics unit, similar to the 9000S (where it was clocked with up to 750MHz).
Nothing concrete is known about the manufacturing process or the architecture. The SoC will probably be manufactured in 7 nm at SMIC.
- Range of benchmark values for this graphics card - Average benchmark values for this graphics card * Smaller numbers mean a higher performance 1 This benchmark is not used for the average calculation
v1.28
log 01. 19:07:15
#0 checking url part for id 8506 +0s ... 0s
#1 checking url part for id 480 +0s ... 0s
#2 checking url part for id 17388 +0s ... 0s
#3 redirected to Ajax server, took 1719853635 +0s ... 0s
#4 did not recreate cache, as it is less than 5 days old! Created at Mon, 01 Jul 2024 05:15:43 +0200 +0s ... 0s
#5 composed specs +0.004s ... 0.005s
#6 did output specs +0s ... 0.005s
#7 getting avg benchmarks for device 8506 +0.001s ... 0.005s
#8 got single benchmarks 8506 +0.013s ... 0.019s
#9 getting avg benchmarks for device 480 +0.001s ... 0.019s
#10 got single benchmarks 480 +0.003s ... 0.022s
#11 getting avg benchmarks for device 17388 +0.001s ... 0.023s
#12 got single benchmarks 17388 +0.003s ... 0.026s
#13 got avg benchmarks for devices +0s ... 0.026s
#14 min, max, avg, median took s +0.02s ... 0.047s