Home / Samsung Xclipse 920 / Compare

RADV-Xclipse-Android--2- 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-Android--2-Mesa 27.0.0-devel (git-0340c63330)

Graphics system version (Vulkan)1.4.358 to ?

Optional features (extensions)228 to ?not checked on both

Features that pass their check (validated)not tested on bothRADV-Xclipse-Android--2-: no driver check yet

Speed test scenes (benchmark)3 faster 0 slower42% faster overall (geometric mean)

hdr_2160p112% faster
pipeline_barriers_2160p14% faster
subpasses_2160p18% faster

Custom driver against stock, per scene. Bars to the right are faster, to the left slower.

Small areas of the picture differ from the stock driver in 2 scenes (pipeline_barriers: 274 of 2304 cells, pipeline_barriers_2160p: 10 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

RADV-Xclipse-Android--1- details RADV-Xclipse-Android--2- details

Feature checks that differ

RADV-Xclipse-Android--2-: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

unverified RADV-Xclipse-Android--2-: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

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-Android--2- ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	6.50	n/a	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
compute_nbody_2x	19.38	n/a	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	39.63 typical 39.41	18.66 typical 18.69	112% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.3 64x36
oit_linked_lists	n/a	7.85	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	n/a	4.13	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 1.2 differs in 274 small areas worst 24.7 64x36
pipeline_barriers_2160p	19.06 typical 19.54	16.79 typical 16.69	14% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.1 differs in 10 small areas worst 12.3 64x36
subpasses	n/a	n/a	too light, see subpasses_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	not checked
subpasses_2160p	32.44 typical 32.72	27.57 typical 27.77	18% faster	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 RADV-Xclipse-Android--2- 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)

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