Home / Adreno (TM) 660 / Compare

Qualcomm Technologies Inc. Adreno Vulkan Driver vs Qualcomm Technologies Inc. Adreno Vulkan Driver

On Adreno (TM) 660 (Asus ROG Phone 5 series, motorola edge 30 fusion, Razer Edge, Samsung Galaxy S21 Ultra 5G, Samsung Galaxy S21+ 5G, Sony Xperia PRO-I). The first driver named is compared against the second, which is the baseline.

StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: ee3f1da111, Ie1e5aac4cc, 1704965855

CustomQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 9ad1b67875, Ib48d2dada6, 1746950435

Graphics system version (Vulkan)1.1.128 to 1.1.128

Optional features (extensions)75 to 75+0 -0

Features that pass their check (validated)48 to 31Qualcomm Technologies Inc. Adreno Vulkan Driver: sent from a device this site could not confirm (unverified)0 pass only on Qualcomm Technologies Inc. Adreno Vulkan Driver 17 pass only on Qualcomm Technologies Inc. Adreno Vulkan Driver

Speed test scenes (benchmark)no shared scenes

Games each driver could run (an estimate from its feature list): green likely, yellow maybe, orange limited, red no

StockDX92002+DX102006+DX112009+DX122015+Switch

CustomDX92002+DX102006+DX112009+DX122015+Switch

Qualcomm Technologies Inc. Adreno Vulkan Driver details Qualcomm Technologies Inc. Adreno Vulkan Driver details

Feature checks that differ (18)

Unverified Qualcomm Technologies Inc. Adreno Vulkan Driver: The results below were sent from a device this site could not confirm. A result the site counts replaces them.

Feature	Stock	Qualcomm Technologies Inc. Adreno Vulkan Driver	Change
depthClamp VkPhysicalDeviceFeatures	pass	untested	lost
largePoints VkPhysicalDeviceFeatures	pass	untested	lost
compat.helper_loop_terminator core	pass	untested	lost
compat.nested_map core	pass	untested	lost
core.blend_advertised_formats core	pass	untested	lost
core.compute_big_stack core	pass	untested	lost
core.host_coherent_readback core	pass	untested	lost
core.mrt_partial_kill core	pass	untested	lost
core.ubo_update_buffer core	pass	untested	lost
core.ubo_written_after_record core	pass	untested	lost
core.varying_subset core	pass	untested	lost
mem.image_padding core	pass	untested	lost
perf.fb_local_barrier_large_draws core	pass	untested	lost
perf.fb_local_barrier_overdraw core	pass	untested	lost
stage.geometry_max_output core	pass	untested	lost
stress.scratch_per_batch core	pass	untested	lost
sync.first_submit_clear_then_compute core	pass	untested	lost
stage.geometry_point_size core	unsupported	untested	changed

Speed test scenes (benchmark)

The two drivers were not measured on the same set of device models. Frame times from different devices do not compare drivers, so read these numbers with that in mind.

Scene	Stock ms	Qualcomm Technologies Inc. Adreno Vulkan Driver ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	11.62 typical 11.83	only one side	? vs 3 of 3	? vs 840 clock unknown	not checked
hdr_2160p	n/a	58.90 typical 58.91	only one side	? vs 3 of 3	? vs 840 clock unknown	not checked
oit_linked_lists	n/a	29.63 typical 29.72	only one side	? vs 3 of 3	? vs 840 clock unknown	not checked
pipeline_barriers	n/a	8.21 typical 8.24	only one side	? vs 3 of 3	? vs 774 clock unknown	not checked
pipeline_barriers_2160p	n/a	27.06 typical 27.20	only one side	? vs ?	? vs ? clock unknown	not checked
subpasses	n/a	14.23 typical 14.23	only one side	? vs 3 of 3	? vs 840 clock unknown	not checked

Time to draw one frame, per scene: the average (mean) frame time of the scene's best round, which is how many frames the driver delivered; lower is faster. "Typical" beside it is the median frame, which can sit well under the average when a driver's frames come in two speeds. A pair of reports made before per-round averages were recorded is compared on the median. A scene whose rounds disagree by more than 15% is left out. A scene marked "paced" was held at that mean frame time by the driver or the display queue, together with at least one other scene of the same run; its time says how the frames were spaced, not how fast the driver rendered, so it is not compared. A scene marked "too light" took under 8 ms at the standard size (1920 by 1080) on both drivers, where the screen's frame queue spaces the frames more than the chip does; its heavier run is the one compared: the row ending in _2160p is the scene drawn at 3840 by 2160, and compute_nbody_2x is that scene with twice the particles. "Faster" and "slower" describe Qualcomm Technologies Inc. Adreno Vulkan Driver against Qualcomm Technologies Inc. Adreno Vulkan Driver. "Picture vs stock" compares one fixed frame per scene as a coarse colour grid (0 is identical, above 40 is a different picture); it finds a scene that was not drawn. Where both reports carry the finer 64x36 grid, the second figure is how many of its 2,304 cells differ by more than 4 of 255, and "worst" is the largest single cell; this is what finds a small rendering error in a picture that otherwise matches. A row marked 16x9 comes from a report made before the finer grid existed. "Starts" is how many of a scene's process starts reached a measured round. A GPU clock marked "not comparable" differed by more than 5% of the device's maximum between the two timings.

Technical differences (Vulkan)

Extensions only in Qualcomm Technologies Inc. Adreno Vulkan Driver (0)

None

Extensions only in Qualcomm Technologies Inc. Adreno Vulkan Driver (0)

None

Core features that differ (0)

None

Limits that differ (0)

Limit	Stock	Qualcomm Technologies Inc. Adreno Vulkan Driver

Formats supported by only one driver (0 gained, 0 lost)

Only in Qualcomm Technologies Inc. Adreno Vulkan Driver:

None

Only in Qualcomm Technologies Inc. Adreno Vulkan Driver:

None