FauxVkDB
English
Home / Adreno (TM) 840 / Compare

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

On Adreno (TM) 840 (iQOO 15, LENOVO TB324ZC, nubia NX809J, OnePlus 15, POCO F8 Ultra, Samsung Galaxy S26, Samsung Galaxy S26 Ultra, Samsung Galaxy S26 Ultra, Samsung Galaxy S26 Ultra, Samsung Galaxy Z Fold8, Samsung Galaxy Z Fold8 Ultra, Xiaomi 2512BPNDAG). The first driver named is compared against the second, which is the baseline.

StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 98e17e88c5, I5de6f8773d, 1761333136
vs
CustomQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 308c636798, I3b35b00dbb, 1789475015
Graphics system version (Vulkan)1.4.295 to 1.4.295
Optional features (extensions)180 to 183+3 -0
Features that pass their check (validated)44 to 44Qualcomm Technologies Inc. Adreno Vulkan Driver: sent from a device this site could not confirm (unverified)both pass the same checks
Speed test scenes (benchmark)none comparable
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

Not compared: 2 scenes with a paced frame rate (pipeline_barriers, subpasses). At least one of the two drivers was held at a fixed frame rate there, so the two times do not measure the same thing.

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

Feature checks that differ (0)

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.

Every feature check ends the same way on both drivers.

Speed test scenes (benchmark)

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

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.

SceneStock msQualcomm Technologies Inc. Adreno Vulkan Driver msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodyn/a6.00 typical 5.91only one side? vs 3 of 3? vs ? clock unknownnot checked
compute_nbody_2xn/an/aonly one side? vs 3 of 3? vs ? clock unknownnot checked
hdr_2160pn/a16.73 typical 16.48only one side? vs 3 of 3? vs ? clock unknownnot checked
oit_linked_listsn/a16.03 typical 15.97only one side? vs 3 of 3? vs ? clock unknownnot checked
pipeline_barriersn/apaced at 4.02not compared? vs 3 of 3? vs ? clock unknownnot checked
pipeline_barriers_2160pn/a5.82 typical 5.81only one side? vs 3 of 3? vs ? clock unknownnot checked
subpassesn/apaced at 4.02not compared? vs 3 of 3? vs ? clock unknownnot checked
subpasses_2160pn/a11.95 typical 11.95only one side? vs 3 of 3? vs ? clock unknownnot 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 (3)
  • VK_ARM_data_graph
  • VK_ARM_tensors
  • VK_QCOM_data_graph_model
Extensions only in Qualcomm Technologies Inc. Adreno Vulkan Driver (0)
  • None
Core features that differ (0)
None
Limits that differ (0)
LimitStockQualcomm 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