Notebookcheck Logo

Qualcomm Snapdragon 400 APQ8028 vs Qualcomm Snapdragon 400 MSM8928

Qualcomm Snapdragon 400 APQ8028

► remove from comparison Qualcomm 400 APQ8028

Der Qualcomm Snapdragon 400 APQ8028 ist ein preiswerter ARM-SoC für Android-Tablets. Er integriert vier Cortex-A7-Kerne mit bis zu 1,6 GHz Taktfrequenz und eine Adreno 305 Grafikkarte. Ein Funkmodem ist dagegen nicht enthalten.

Sowohl die Leistung des Prozessors auch die der Grafikeinheit ist nur im Einstiegssegment angesiedelt. Gemäß der Taktrate und der ähnlichen Pro-MHz-Leistung entspricht die Performance in etwa den schnelleren Varianten von Nvidias Tegra 3 oder dem Samsung Exynos 4412. Die Adreno 305 des APQ8028 besitzt für Multimedia-Zwecke und einfache Android-Spiele ausreichende Leistungsreserven, ist jedoch nicht für anspruchsvolle 3D-Grafiken und extrem hohe Auflösungen geeignet.

Durch den Verzicht auf ein Funkmodem ist der Chip in erster Linie für den Tablet-Einsatz geeignet. Dort unterstützt der SoC die Wiedergabe von 1080p-Videos und den Anschluss von USB-2.0-Geräten. Desweiteren können Kameras mit einer Auflösung von bis zu 13 Megapixeln angebunden werden.

Der SoC wird in einem 28nm LP Prozess gefertigt und sollte eine niedrige Leistungsaufnahme besitzen, sodass auch ein Einsatz in kleineren und dünnen Tablets möglich ist.

Qualcomm Snapdragon 400 MSM8928

► remove from comparison Qualcomm 400 MSM8928

Der Qualcomm Snapdragon 400 MSM8928 ist ein preiswerter ARM-SoC für Tablets und Smartphones (hauptsächlich Android). Er integriert vier Cortex-A7-Kerne mit bis zu 1,6 GHz Taktfrequenz, eine Adreno 305 Grafikkarte sowie ein Mobilfunkmodem (GSM/UMTS/WCDMA/LTE). Speziell für Tablets wird auch ein ansonsten weitestgehend identisches Modell ohne Modem angeboten, der Snapdragon 400 APQ8028.

Sowohl die Leistung des Prozessors auch die der Grafikeinheit ist nur im Einstiegssegment angesiedelt. Gemäß der Taktrate und der ähnlichen Pro-MHz-Leistung entspricht die Performance in etwa den schnelleren Varianten von Nvidias Tegra 3 oder dem Samsung Exynos 4412. Die Adreno 305 des MSM8928 besitzt für Multimedia-Zwecke und einfache Android-Spiele ausreichende Leistungsreserven, ist jedoch nicht für anspruchsvolle 3D-Grafiken und extrem hohe Auflösungen geeignet.

Durch sein integriertes Funkmodem kann der Chip sowohl in Smartphones als auch Tablets mit mobilem Internetzugang verbaut werden. Dabei unterstützt der SoC die Wiedergabe von 1080p-Videos und den Anschluss von USB-2.0-Geräten. Desweiteren können Kameras mit einer Auflösung von bis zu 13 Megapixeln angebunden werden.

Der SoC wird in einem 28nm LP Prozess gefertigt und sollte eine niedrige Leistungsaufnahme besitzen, sodass auch ein Einsatz in kleineren Smartphones und Tablets möglich ist.

ModelQualcomm Snapdragon 400 APQ8028Qualcomm Snapdragon 400 MSM8928
SeriesQualcomm SnapdragonQualcomm Snapdragon
CodenameARMv7ARMv7
Serie: Snapdragon ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A compare1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
» Qualcomm Snapdragon 400 APQ80281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8960 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM8926 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8226 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8026 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM8930 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8230 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8227 compare1 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8660 compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8260 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD8250 compare1 GHz1 / 1 ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A compare1.5 GHz4 / 4 ARMv7
» Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8960 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM8926 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8226 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8026 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM8930 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8230 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8227 compare1 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8660 compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8260 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD8250 compare1 GHz1 / 1 ARMv7
Clock1600 MHz1600 MHz
Cores / Threads4 / 44 / 4
Technology28 nm28 nm
FeaturesAdreno 305 GPU, LPDDR2/3 Memory ControllerAdreno 305 GPU, LPDDR2/3 Memory Controller, GSM/UMTS/WCDMA/LTE
iGPUQualcomm Adreno 305Qualcomm Adreno 305
ArchitectureARMARM
Announced
ManufacturerQualcomm Snapdragon 400 APQ8028Qualcomm Snapdragon 400 MSM8928

Benchmarks

3DMark - 3DMark Ice Storm Physics
8132 Points (5%)
min: 7756     avg: 8177     median: 8177 (5%)     max: 8598 Points
3DMark - 3DMark Ice Storm Extreme Physics
8177 Points (7%)
min: 7704     avg: 8386     median: 8696 (7%)     max: 8759 Points
3DMark - 3DMark Ice Storm Unlimited Physics
8880 Points (7%)
min: 7913     avg: 8927     median: 9016 (8%)     max: 9761 Points
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited Physics
785 Points (11%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
441 Points (7%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
1100 Points (3%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
1489 Points (3%)
min: 1109     avg: 1309     median: 1338 (2%)     max: 1451 Points
Geekbench 3 - Geekbench 3 32 Bit Single-Core
435 Points (8%)
min: 338     avg: 393.3     median: 398.5 (8%)     max: 438 Points
Geekbench 2 - 32 Bit - Geekbench Stream
300 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Memory
1334 Points (12%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
2344 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Integer
1369 Points (3%)
Geekbench 2 - 32 Bit - Geekbench Total Score
1596 Points (4%)
Linpack Android / IOS - Linpack Multi Thread
281 MFLOPS (10%)
min: 150.1     avg: 221.7     median: 249.9 (8%)     max: 265 MFLOPS
Linpack Android / IOS - Linpack Single Thread
113 MFLOPS (11%)
min: 67.9     avg: 87.9     median: 97.7 (10%)     max: 98 MFLOPS
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
min: 12714     avg: 14100     median: 13858 (16%)     max: 15968 ms
Sunspider - Sunspider 1.0 Total Score *
958 ms (11%)
min: 1207     avg: 1429     median: 1404.5 (15%)     max: 1701 ms
Sunspider - Sunspider 0.9.1 Total Score *
1529 ms (14%)
Octane V2 - Octane V2 Total Score
1759 Points (2%)
min: 1894     avg: 2330     median: 2335 (2%)     max: 2755 Points
Vellamo 3.x - Vellamo 3.x Metal
771 Points (21%)
Vellamo 3.x - Vellamo 3.x Multicore Beta
1248 Points (28%)
Vellamo 3.x - Vellamo 3.x Browser
1881 Points (25%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
10657 points (25%)
min: 9699     avg: 9949     median: 9948.5 (23%)     max: 10198 points
AnTuTu v4 - AnTuTu v4 Total Score
18926 Points (44%)
17354 Points (40%)
AnTuTu v5 - AnTuTu v5 Total Score
19444 Points (20%)
AnTuTu v6 - AnTuTu v6 Total Score
24799 Points (8%)
AndEBench - AndEBench Java
400 Iter./s (12%)
min: 290     avg: 341     median: 341 (10%)     max: 392 Iter./s
AndEBench - AndEBench Native
8610 Iter./s (28%)
min: 5540     avg: 6590     median: 6590 (22%)     max: 7640 Iter./s
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
9698 Points (1%)
min: 7044     avg: 7929     median: 7929 (1%)     max: 8814 Points
PCMark for Android - PCM f. Android Work Score
2383 Points (12%)

Average Benchmarks Qualcomm Snapdragon 400 APQ8028 → 100% n=14

Average Benchmarks Qualcomm Snapdragon 400 MSM8928 → 94% n=14

- Bereich der Benchmarkergebnisse für diese Grafikkarte
- Durchschnittliche Benchmarkergebnisse für diese Grafikkarte
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 12. 02:28:16

#0 checking url part for id 6031 +0s ... 0s

#1 checking url part for id 6034 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Thu, 11 Aug 2022 13:13:36 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.005s ... 0.005s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.006s

#6 linkCache_getLink no uid found +0.003s ... 0.01s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#14 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#16 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#19 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#20 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#24 composed specs +0s ... 0.01s

#25 did output specs +0s ... 0.01s

#26 getting avg benchmarks for device 6031 +0s ... 0.01s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#28 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#29 got single benchmarks 6031 +0.006s ... 0.017s

#30 getting avg benchmarks for device 6034 +0s ... 0.017s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.017s

#32 got single benchmarks 6034 +0.01s ... 0.027s

#33 got avg benchmarks for devices +0s ... 0.027s

#34 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.028s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

#41 No cached benchmark found, getting uncached values +0.001s ... 0.03s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#43 No cached benchmark found, getting uncached values +0s ... 0.03s

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#45 No cached benchmark found, getting uncached values +0s ... 0.031s

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#60 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.034s

#61 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.035s

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#65 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.036s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#74 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.037s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#79 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.039s

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#82 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#83 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#89 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#92 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.042s

#93 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.042s

#94 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.043s

#95 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#96 No cached benchmark found, getting uncached values +0s ... 0.044s

#97 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#98 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#99 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#100 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.045s

#101 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#102 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#103 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#104 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#105 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#106 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#107 No cached benchmark found, getting uncached values +0s ... 0.046s

#108 min, max, avg, median took s +0s ... 0.046s

#109 linkCache_getLink using $NBC_LINKCACHE +0.024s ... 0.07s

#110 return log +0.004s ... 0.074s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Prozessor Vergleich - Head 2 Head
Autor: Sebastian Jentsch,  8.09.2017 (Update: 19.05.2020)