FauxVkDB
English

RADV-Xclipse-Android--2- vs Samsung Proprietary driver

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.

StockSamsung Proprietary driverDriver version: 24.0.534, git hash: 1900168dcb
vs
CustomRADV-Xclipse-Android--2-Mesa 27.0.0-devel (git-0340c63330)
Graphics system version (Vulkan)1.3.279 to ?
Optional features (extensions)146 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)no shared scenes

Samsung Proprietary driver 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.

SceneStock msCustom msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodyn/an/aonly one side? vs 3 of 3? vs ? clock unknownnot checked
compute_nbody_2xn/an/aonly one side? vs 3 of 3? vs ? clock unknownnot checked
hdr_2160pn/a18.66 typical 18.69only one side? vs 3 of 3? vs ? clock unknownnot checked
oit_linked_listsn/a8.02 typical 7.85only one side? vs 3 of 3? vs ? clock unknownnot checked
pipeline_barriersn/a4.07 typical 4.13only one side? vs 3 of 3? vs ? clock unknownnot checked
pipeline_barriers_2160pn/a16.79 typical 16.69only one side? vs 3 of 3? vs ? clock unknownnot checked
subpassesn/an/aonly one side? vs 3 of 3? vs ? clock unknownnot checked
subpasses_2160pn/a27.57 typical 27.77only one side? vs 3 of 3? vs ? clock unknownnot 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 Samsung Proprietary 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.