Home / Samsung Xclipse 940 / Compare

MdiEx_2400_v3.6 vs Samsung Proprietary driver

On Samsung Xclipse 940 (Samsung Galaxy S24, Samsung Galaxy S24 FE, Samsung Galaxy S24 FE, Samsung Galaxy S25 FE). The first driver named is compared against the second, which is the baseline.

StockSamsung Proprietary driverDriver version: 24.0.534, git hash: 1900168dcb

CustomMdiEx_2400_v3.6Driver version: 24.0.534, git hash: 1900168dcb

Graphics system version (Vulkan)1.3.279 to 1.3.279

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

Features that pass their check (validated)49 to 49both pass the same checks

Speed test scenes (benchmark)none comparable

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

Not compared: 6 scenes with a paced frame rate (compute_nbody, compute_nbody_2x, oit_linked_lists, pipeline_barriers, subpasses, subpasses_2160p). At least one of the two drivers was held at a fixed frame rate there, so the two times do not measure the same thing.

Samsung Proprietary driver details MdiEx_2400_v3.6 details

Feature checks that differ (0)

Every feature check ends the same way on both drivers.

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	Stock ms	Custom ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	paced at 8.32	n/a	not compared	3 of 3 vs ?	? vs ? clock unknown	not checked
compute_nbody_2x	paced at 11.03	n/a	not compared	? vs ?	? vs ? clock unknown	not checked
hdr_2160p	36.65 typical 36.50	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
oit_linked_lists	paced at 8.33	n/a	not compared	3 of 3 vs ?	? vs ? clock unknown	not checked
pipeline_barriers	paced at 5.53	n/a	not compared	3 of 3 vs ?	? vs ? clock unknown	not checked
pipeline_barriers_2160p	7.14 typical 7.10	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
subpasses	paced at 5.54	n/a	not compared	3 of 3 vs ?	? vs ? clock unknown	not checked
subpasses_2160p	paced at 11.01	n/a	not compared	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 MdiEx_2400_v3.6 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)

Extensions only in MdiEx_2400_v3.6 (0)

None

Extensions only in Samsung Proprietary driver (0)

None

Core features that differ (0)

None

Limits that differ (0)

Limit	Stock	Custom

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

Only in MdiEx_2400_v3.6:

None

Only in Samsung Proprietary driver:

None