Home / Adreno (TM) 830 / Compare

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

On Adreno (TM) 830 (HONOR AAK-AN00, HONOR Magic V5, nubia NX789J, OnePlus 13, POCO F8 Pro, realme GT 7 Pro, Samsung Galaxy S25, Samsung Galaxy S25 Ultra, Samsung Galaxy S25 Ultra, Samsung Galaxy S25 Ultra, Samsung Galaxy S25+, Xiaomi 15, ZTE NP05J). The first driver named is compared against the second, which is the baseline.

StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 0603ba43d2, Id52d3f334b, 1782110333

CustomQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 3967b80d3b, Ica4ce9bea6, 1770914544

Graphics system version (Vulkan)1.3.284 to 1.3.284

Optional features (extensions)171 to 165+0 -6

Features that pass their check (validated)44 to 44both pass the same checks

Speed test scenes (benchmark)1 faster 3 slower14% faster overall (geometric mean)

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

compute_nbody_2x5% slower
oit_linked_lists12% slower
pipeline_barriers_2160p11% slower
subpasses125% faster

Custom driver against stock, per scene. Bars to the right are faster, to the left slower.

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

Feature checks that differ (0)

Every feature check ends the same way on both drivers.

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	n/a	too light, see compute_nbody_2x	3 of 3 vs 3 of 3	611 vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
compute_nbody_2x	8.22 typical 8.22	8.65 typical 8.57	5% slower	3 of 3 vs 3 of 3	1133 vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	n/a	13.91	only one side	3 of 3 vs 3 of 3	1200 vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists	15.57 typical 15.58	17.75 typical 17.30	12% slower	3 of 3 vs 3 of 3	1200 vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	2.75 typical 2.39	1.62 typical 1.51	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	726 vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers_2160p	5.43 typical 5.42	6.11 typical 5.83	11% slower	3 of 3 vs 3 of 3	1039 vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
subpasses	5.62 typical 4.38	2.50 typical 2.41	125% faster	3 of 3 vs 3 of 3	607 vs ? clock unknown	not checked
subpasses_2160p	n/a	9.29	only one side	3 of 3 vs 3 of 3	1167 vs ? 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 (6)

VK_EXT_present_mode_fifo_latest_ready
VK_EXT_present_timing
VK_KHR_present_id
VK_KHR_present_id2
VK_KHR_present_wait2
VK_KHR_swapchain_maintenance1

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