FauxVkDB
English
Home / Adreno (TM) 650 / Compare

Turnip_v26.2.0-R6 vs Qualcomm Technologies Inc. Adreno Vulkan Driver

On Adreno (TM) 650 (blackshark SHARK PAR-A0, MANGMI Pocket Max, Moorechip Retroid Pocket 5, POCO F4, Samsung Galaxy S20 FE, Samsung Galaxy S20 FE 5G, Sony Xperia 5 II). The first driver named is compared against the second, which is the baseline.

StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: a9e8e6fb86, I7abed35a9a, 1716361183
vs
CustomTurnip_v26.2.0-R6
Graphics system version (Vulkan)1.1.276 to ?
Optional features (extensions)98 to ?not checked on both
Features that pass their check (validated)not tested on bothTurnip_v26.2.0-R6: no driver check yet
Speed test scenes (benchmark)no shared scenes

Qualcomm Technologies Inc. Adreno Vulkan Driver details Turnip_v26.2.0-R6 details

Feature checks that differ

Turnip_v26.2.0-R6: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

unverified Turnip_v26.2.0-R6: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

SceneStock msCustom msDifferenceStartsGPU clock, MHzPicture vs stock
hdr_2160pn/a80.67 typical 80.99only one side? vs 3 of 3? vs 800 clock unknownnot checked
oit_linked_listsn/a29.55 typical 29.50only one side? vs 3 of 3? vs 818 clock unknownnot checked
pipeline_barriersn/a4.20 typical 4.01only one side? vs 3 of 3? vs 800 clock unknownnot checked
pipeline_barriers_2160pn/a14.83 typical 14.37only one side? vs 3 of 3? vs 800 clock unknownnot checked
subpassesn/a6.68 typical 6.54only one side? vs 3 of 3? vs 800 clock unknownnot checked
subpasses_2160pn/a25.28 typical 25.00only one side? vs 3 of 3? vs 789 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 Turnip_v26.2.0-R6 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)

Both drivers need a driver check (validation report) before their technical details (Vulkan) can be compared.