Home / Samsung Xclipse 920 / Compare

radv-xclipse-27.0.0-devel-269238e vs RADV-Xclipse-Android--1-

On Samsung Xclipse 920 (Samsung Galaxy S22, Samsung Galaxy S22 Ultra, Samsung Galaxy S23 FE, Samsung Galaxy S24 FE, Samsung Galaxy S24+). The first driver named is compared against the second, which is the baseline.

StockRADV-Xclipse-Android--1-Mesa 26.3.0-devel (git-cd638916b5)

Customradv-xclipse-27.0.0-devel-269238eMesa 27.0.0-devel (git-269238e853)

Graphics system version (Vulkan)1.4.358 to 1.4.363

Optional features (extensions)228 to 228+1 -1

Features that pass their check (validated)52 to 6917 pass only on radv-xclipse-27.0.0-devel-269238e 0 pass only on RADV-Xclipse-Android--1-

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

RADV-Xclipse-Android--1- details radv-xclipse-27.0.0-devel-269238e details

Feature checks that differ (18)

Feature	RADV-Xclipse-Android--1-	radv-xclipse-27.0.0-devel-269238e	Change
depthClamp VkPhysicalDeviceFeatures	untested	pass	gained
largePoints VkPhysicalDeviceFeatures	untested	pass	gained
compat.helper_loop_terminator 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
compat.nested_map core	untested	crash	changed

Speed test scenes (benchmark)

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.

Scene	RADV-Xclipse-Android--1- ms	radv-xclipse-27.0.0-devel-269238e ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	6.66 typical 6.50	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
compute_nbody_2x	19.37 typical 19.38	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
hdr_2160p	39.63 typical 39.41	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
oit_linked_lists	n/a	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
pipeline_barriers	n/a	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
pipeline_barriers_2160p	19.06 typical 19.54	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
subpasses	n/a	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
subpasses_2160p	32.44 typical 32.72	n/a	only one side	3 of 3 vs ?	? 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 radv-xclipse-27.0.0-devel-269238e against RADV-Xclipse-Android--1-. "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 radv-xclipse-27.0.0-devel-269238e (1)

VK_AMD_anti_lag

Extensions only in RADV-Xclipse-Android--1- (1)

VK_EXT_mesh_shader

Core features that differ (0)

None

Limits that differ (0)

Limit	RADV-Xclipse-Android--1-	radv-xclipse-27.0.0-devel-269238e

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

Only in radv-xclipse-27.0.0-devel-269238e:

G10X6_B10X6R10X6_2PLANE_422_UNORM_3PACK16

Only in RADV-Xclipse-Android--1-:

None