Home / Mali-G925-Immortalis MC11 / Compare

PanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83eff vs Mali-G925-Immortalis MC12

On Mali-G925-Immortalis MC11 (POCO X8 Pro Max, POCO X8 Pro Max, REDMI Turbo 5 Max, Samsung Galaxy Tab S11 Ultra, vivo X200s, Xiaomi 15T Pro). The first driver named is compared against the second, which is the baseline.

StockMali-G925-Immortalis MC12v1.r49p1-03bet0.f8a98b506b89b21c80a508d70abfcb3f

CustomPanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83effPanVK-kbase beta.13 (Mesa 27.0.0-devel (git-e2d83eff1c))

Graphics system version (Vulkan)1.3.278 to ?

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

Features that pass their check (validated)not tested on bothPanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83eff: no driver check yet

Speed test scenes (benchmark)0 faster 3 slower 1 even35% slower overall (geometric mean)

compute_nbody1% slower
hdr_2160p37% slower
oit_linked_lists40% slower
pipeline_barriers52% slower

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 1 scene (pipeline_barriers: 1490 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

Mali-G925-Immortalis MC12 details PanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83eff details

Feature checks that differ

PanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83eff: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

unverified PanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83eff: 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	Stock ms	Custom ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	10.80 typical 10.60	10.92 typical 10.79	1% slower	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.3 64x36
hdr_2160p	8.39 typical 8.27	13.27 typical 13.37	37% slower	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	13.17 typical 13.39	21.79 typical 21.56	40% slower	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	5.66 typical 5.61	11.82 typical 12.21	52% slower	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 9.3 differs in 1490 small areas worst 60.0 64x36
pipeline_barriers_2160p	6.09 typical 6.22	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
subpasses	7.39	n/a	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	not checked
subpasses_2160p	9.86 typical 9.84	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 PanVK-Kbase-Android-g925-v13-csf-v0.0.1-bc-mip-priority-20261029-e2d83eff against Mali-G925-Immortalis MC12. "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.