Every feature check ends the same way on both drivers.
Speed test scenes (benchmark)
Scene
8Elite2-842.6 ms
Qualcomm_849_adpkg ms
Difference
Starts
GPU clock, MHz
Picture vs stock
compute_nbody
10.07 typical 9.99
10.13 typical 10.05
1% slower
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
hdr_2160p
10.92 typical 10.85
11.23 typical 11.04
3% slower
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
oit_linked_lists
17.14 typical 17.00
17.12 typical 16.76
0% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
pipeline_barriers
3.07 typical 2.39
3.07 typical 2.46
too light, see pipeline_barriers_2160p
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
pipeline_barriers_2160p
7.75 typical 7.76
9.15 typical 9.17
15% slower
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
subpasses
3.90 typical 3.58
3.97 typical 3.55
too light, see subpasses_2160p
3 of 3 vs 3 of 3
? vs ? clock unknown
not checked
subpasses_2160p
14.45 typical 14.28
14.89 typical 14.83
3% slower
3 of 3 vs 3 of 3
? 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_849_adpkg against 8Elite2-842.6. "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_849_adpkg (1)
VK_EXT_non_seamless_cube_map
Extensions only in 8Elite2-842.6 (1)
VK_KHR_maintenance7
Core features that differ (0)
None
Limits that differ (0)
Limit
8Elite2-842.6
Qualcomm_849_adpkg
Formats supported by only one driver (0 gained, 0 lost)