Notebookcheck Logo

Qualcomm Adreno 642 vs Qualcomm Adreno 680

Qualcomm Adreno 642

► remove from comparison Qualcomm Adreno 642

The Qualcomm Adreno 642 is a smartphone and tablet GPU that is integrated within the Qualcomm Snapdragon 780G SoC. The chip will be available from mid 2021 and will be used mainly in upper mid-range Android devices.

According to Qualcomm, the Adreno 642 GPU offers a 50% improved performance over the Adreno 620, its predecessor, which is integrated in the Snapdragon 768G SoC. This is also thanks to the fast LPDDR4X-4200 memory support of the SoC.

The Adreno 642 supports OpenCL 2.0 FP, OpenGL ES 3.2 and Vulkan 1.1.

The Snapdragon 780G is manufactured in the modern 5nm LPPE process with EUV at Samsung that should provide a good power efficiency.

Qualcomm Adreno 680

► remove from comparison

The Qualcomm Adreno 680 is an integrated graphics card in the Qualcomm Snapdragon 8cx SoC for Windows laptops. According to Qualcomm it is 2x faster than the previous Adreno 630 in the Snapdragon 850 for Windows PCs with a 60% improved efficiency (thanks to the 7nm process). The performance should be similar to a Intel UHD Graphics 620 (e.g. in a 8th gen Core i5) when running native ARM64 compiled Windows apps and games. Running emulated 32 bit games (64 bit games compiled for AMD/Intel are not supported), the performance is notably slower.

show full text
Qualcomm Adreno 642Qualcomm Adreno 680
Adreno 600 Series
Adreno 660 compare
Adreno 650 compare @ 0.25 - 0.67 GHz
Adreno 685 compare
Adreno 680
Adreno 642
Adreno 642L compare
Adreno 640 compare
Adreno 630 compare
Adreno 620 compare
Adreno 619 compare
Adreno 619L compare
Adreno 618 compare
Adreno 616 compare
Adreno 612 compare
Adreno 610 compare
Adreno 660 compare
Adreno 650 compare @ 0.25 - 0.67 GHz
Adreno 685 compare
Adreno 680
Adreno 642
Adreno 642L compare
Adreno 640 compare
Adreno 630 compare
Adreno 620 compare
Adreno 619 compare
Adreno 619L compare
Adreno 618 compare
Adreno 616 compare
Adreno 612 compare
Adreno 610 compare
Shared Memoryyesyes
APIOpenGL ES 3.2DirectX 12
technology5 nm7 nm
FeaturesOpenGL ES 3.2, OpenCL 2.0, DirectX 12, Vulkan 1.1
Date of Announcement07.05.2021 06.12.2018
Power Consumption7 Watt
CPU in Adreno 642GPU Base SpeedGPU Boost / Turbo
Qualcomm Snapdragon 780G 5G8 x 1900 MHz? MHz? MHz
CPU in Adreno 680GPU Base SpeedGPU Boost / Turbo
Qualcomm Snapdragon 8cx Gen 2 5G8 x 3150 MHz, 7 W? MHz? MHz
Qualcomm Snapdragon 8cx8 x 2840 MHz, 7 W? MHz? MHz
min. - max.? MHz? MHz

Benchmarks

3DMark - 3DMark Sling Shot (ES 3.0) Unlimited
5587 Points (33%)
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited Graphics
8380 Points (20%)
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited
4478 Points (39%)
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited Graphics
6148 Points (24%)
3DMark 11 - 3DM11 Performance Score
min: 1650     avg: 1847     median: 1847 (4%)     max: 2044 Points
3DMark 11 - 3DM11 Performance GPU
min: 1593     avg: 1936     median: 1935.5 (3%)     max: 2278 Points
Cinebench R10 Cinebench R10 Shading (32bit) + Qualcomm Adreno 680
Cinebench R10 - Cinebench R10 Shading (32bit)
353 Points (1%)
GFXBench (DX / GLBenchmark) 2.7
GFXBench 2.7 T-Rex HD Onscreen C24Z16 + Qualcomm Adreno 642
GFXBench (DX / GLBenchmark) 2.7 - GFXBench 2.7 T-Rex HD Onscreen C24Z16
90 fps (3%)
GFXBench 2.7 T-Rex HD Onscreen C24Z16 + Qualcomm Adreno 680
58.9 fps (2%)
GFXBench T-Rex HD Offscreen C24Z16 + Qualcomm Adreno 642
GFXBench (DX / GLBenchmark) 2.7 - GFXBench T-Rex HD Offscreen C24Z16
153 fps (1%)
GFXBench T-Rex HD Offscreen C24Z16 + Qualcomm Adreno 680
140.2 fps (1%)
GFXBench 3.0 - GFXBench 3.0 Manhattan
79 fps (22%)
GFXBench 3.0 - GFXBench 3.0 Manhattan Offscreen
90 fps (7%)
GFXBench - GFXBench 5.0 Aztec Ruins High Tier Onscreen
26 fps (17%)
GFXBench - GFXBench 5.0 Aztec Ruins High Tier Offscreen
18 fps (6%)
GFXBench - GFXBench 5.0 Aztec Ruins Normal Tier Onscreen
42 fps (20%)
GFXBench - GFXBench 5.0 Aztec Ruins Normal Tier Offscreen
50 fps (7%)
GFXBench - GFXBench Car Chase Onscreen
35 fps (1%)
GFXBench - GFXBench Car Chase Offscreen
40 fps (0%)
Basemark GPU 1.2 - Basemark GPU 1.2 Vulkan Official Medium Offscreen 1080
48 fps (4%)
ComputeMark v2.1 - ComputeMark v2.1 Result
1890 Points (4%)
Power Consumption - Furmark Stress Test Power Consumption - external Monitor *
12.6 Watt (2%)
012345678910111213Tooltip

Average Benchmarks Qualcomm Adreno 642 → 100% n=2

Average Benchmarks Qualcomm Adreno 680 → 79% n=2

- 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

Game Benchmarks

The following benchmarks stem from our benchmarks of review laptops. The performance depends on the used graphics memory, clock rate, processor, system settings, drivers, and operating systems. So the results don't have to be representative for all laptops with this GPU. For detailed information on the benchmark results, click on the fps number.

Armajet

Armajet

2020
high
100%
Adreno 642:
30 fps  fps
PUBG Mobile

PUBG Mobile

2018
low
100%
Adreno 642:
60 fps  fps
med.
100%
Adreno 642:
59 fps  fps
high
100%
Adreno 642:
60 fps  fps
ultra
100%
Adreno 642:
40 fps  fps
Asphalt 9: Legends

Asphalt 9: Legends

2013
low
100%
Adreno 642:
60 fps  fps
high
100%
Adreno 642:
60 fps  fps

Average Gaming Qualcomm Adreno 642 → 100%

Average Gaming 30-70 fps → 100%

For more games that might be playable and a list of all games and graphics cards visit our Gaming List

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 27. 20:01:23

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

#1 checking url part for id 9846 +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 Fri, 24 Jun 2022 17:25:51 +0200 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.044s ... 0.044s

#5 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.046s

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

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

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

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

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

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

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

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

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

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

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

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

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

#19 composed specs +0s ... 0.046s

#20 did output specs +0s ... 0.046s

#21 start showIntegratedCPUs +0s ... 0.046s

#22 getting avg benchmarks for device 10693 +0.028s ... 0.075s

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

#24 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#25 got single benchmarks 10693 +0.005s ... 0.08s

#26 getting avg benchmarks for device 9846 +0s ... 0.081s

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

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

#29 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.083s

#30 got single benchmarks 9846 +0.005s ... 0.088s

#31 got avg benchmarks for devices +0s ... 0.088s

#32 linkCache_getLink using $NBC_LINKCACHE +0.006s ... 0.094s

#33 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.097s

#34 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.1s

#35 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.101s

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

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

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

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

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

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.103s

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

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.103s

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

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.104s

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

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

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

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

#50 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.106s

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

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

#53 min, max, avg, median took s +0.008s ... 0.115s

#54 before gaming benchmark output +0s ... 0.115s

#55 Got 7 rows for game benchmarks. +0.003s ... 0.118s

#56 composed SQL query for gamebenchmarks +0s ... 0.118s

#57 got data and put it in $dataArray +0.001s ... 0.119s

#58 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.12s

#59 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.121s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.121s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.122s

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

#63 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.123s

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

#65 benchmarks composed for output. +0s ... 0.123s

#66 calculated avg scores. +0s ... 0.123s

#67 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.124s

#68 return log +0.002s ... 0.126s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Graphics Card Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)