Home / Adreno (TM) 830 / Compare

turnip_faux123_v1.2.0 vs turnip_faux123_v1.1.9

On Adreno (TM) 830 (AYANEO Pocket FIT Elite, HONOR AAK-AN00, HONOR Magic V5, nubia NX789J, OnePlus 13, OnePlus 13, OnePlus 13s, 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, Xiaomi 15, Xiaomi 15 Ultra, ZTE NP05J). The first driver named is compared against the second, which is the baseline.

Stockturnip_faux123_v1.1.9Mesa 26.3.0-devel (git-dd45fd0baa)

Customturnip_faux123_v1.2.0Mesa 26.3.0-devel (git-dd45fd0baa)

Graphics system version (Vulkan)1.4.359 to 1.4.359

Optional features (extensions)173 to 173+0 -0

Features that pass their check (validated)51 to 69turnip_faux123_v1.2.0: sent from a device this site could not confirm (unverified)18 pass only on turnip_faux123_v1.2.0 0 pass only on turnip_faux123_v1.1.9

Speed test scenes (benchmark)no shared scenes

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

turnip_faux123_v1.1.9 details turnip_faux123_v1.2.0 details

Feature checks that differ (18)

Unverified turnip_faux123_v1.2.0: The results below were sent from a device this site could not confirm. A result the site counts replaces them.

Feature	turnip_faux123_v1.1.9	turnip_faux123_v1.2.0	Change
depthClamp VkPhysicalDeviceFeatures	untested	pass	gained
largePoints VkPhysicalDeviceFeatures	untested	pass	gained
compat.helper_loop_terminator core	untested	pass	gained
compat.nested_map core	untested	pass	gained
core.blend_advertised_formats core	untested	pass	gained
core.compute_big_stack core	untested	pass	gained
core.host_coherent_readback core	untested	pass	gained
core.mrt_partial_kill core	untested	pass	gained
core.ubo_update_buffer core	untested	pass	gained
core.ubo_written_after_record core	untested	pass	gained
core.varying_subset core	untested	pass	gained
mem.image_padding core	untested	pass	gained
perf.fb_local_barrier_large_draws core	untested	pass	gained
perf.fb_local_barrier_overdraw core	untested	pass	gained
stage.geometry_max_output core	untested	pass	gained
stage.geometry_point_size core	untested	pass	gained
stress.scratch_per_batch core	untested	pass	gained
sync.first_submit_clear_then_compute core	untested	pass	gained

Speed test scenes (benchmark)

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

Scene	turnip_faux123_v1.1.9 ms	turnip_faux123_v1.2.0 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	n/a	only one side	0 of 3 vs 3 of 3	? vs 525 clock unknown	not checked
compute_nbody_2x	n/a	18.83 typical 17.79	only one side	? vs 3 of 3	? vs 525 clock unknown	not checked
hdr_2160p	n/a	16.11 typical 16.15	only one side	0 of 3 vs 3 of 3	? vs 525 clock unknown	not checked
oit_linked_lists	n/a	37.78 typical 37.67	only one side	0 of 3 vs 3 of 3	? vs 511 clock unknown	not checked
pipeline_barriers	n/a	n/a	only one side	0 of 3 vs 3 of 3	? vs 494 clock unknown	not checked
pipeline_barriers_2160p	n/a	11.52 typical 10.66	only one side	? vs 3 of 3	? vs 511 clock unknown	not checked
subpasses	n/a	n/a	only one side	0 of 3 vs 3 of 3	? vs 525 clock unknown	not checked
subpasses_2160p	n/a	19.84 typical 20.27	only one side	? vs 3 of 3	? vs 525 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 turnip_faux123_v1.2.0 against turnip_faux123_v1.1.9. "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 turnip_faux123_v1.2.0 (0)

None

Extensions only in turnip_faux123_v1.1.9 (0)

None

Core features that differ (0)

None

Limits that differ (0)

Limit	turnip_faux123_v1.1.9	turnip_faux123_v1.2.0

Formats supported by only one driver (0 gained, 0 lost)

Only in turnip_faux123_v1.2.0:

None

Only in turnip_faux123_v1.1.9:

None