vulkan-805-adpkg vs Qualcomm Technologies Inc. Adreno Vulkan Driver
On Adreno (TM) 22 (HONOR 200 Pro, Moorechip Retroid Pocket G2, POCO F6, realme GT 6, realme 真我GT Neo6, Xiaomi Pad 7 Pro). The first driver named is compared against the second, which is the baseline.
StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: ae801e1e7c, I15873b352d, 1735922436
vsCustomvulkan-805-adpkgDriver Build: d4f1d5539c, Iad64dfeba7, 1731002436
Graphics system version (Vulkan)1.3.128 to ?
Optional features (extensions)126 to ?not checked on both
Features that pass their check (validated)not tested on bothvulkan-805-adpkg: no driver check yet
Speed test scenes (benchmark)none comparable
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 vulkan-805-adpkg details
Feature checks that differ
vulkan-805-adpkg: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
Speed test scenes (benchmark)
| Scene | Stock ms | Custom ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
| compute_nbody | n/a | 8.33 typical 8.33 | only one side | ? vs 3 of 3 | ? vs 950 clock unknown | not checked |
| hdr_2160p | n/a | 30.25 typical 30.20 | only one side | ? vs 3 of 3 | ? vs 950 clock unknown | not checked |
| oit_linked_lists | n/a | 19.31 typical 19.33 | only one side | ? vs 3 of 3 | ? vs 875 clock unknown | not checked |
| pipeline_barriers | n/a | paced at 5.55 | not compared | ? vs 3 of 3 | ? vs 611 clock unknown | not checked |
| pipeline_barriers_2160p | n/a | 10.70 typical 10.73 | only one side | ? vs 3 of 3 | ? vs 950 clock unknown | not checked |
| subpasses | n/a | paced at 5.56 | not compared | ? vs 3 of 3 | ? vs 950 clock unknown | not checked |
| subpasses_2160p | n/a | 17.92 typical 17.90 | only one side | ? vs 3 of 3 | ? vs 950 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 vulkan-805-adpkg 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.