PanVK-FristOneRR-V.3.5 vs Mali-G57 MC2
On Mali-G1-Ultra MC12 (Infinix HOT 50 Pro, Infinix NOTE 30, Infinix NOTE 30 5G, Infinix NOTE 40 Pro, itel RS4, Oppo A6 5G, Oppo A6t 5G, Oppo Find X9s Pro, realme RMX5111, REDMI 15C 5G, Redmi Note 10 5G, Redmi Note 13 5G, Redmi Note 13 Pro, Redmi Pad 2, Samsung Galaxy A07, Samsung Galaxy A07, Samsung Galaxy A15 5G, Samsung Galaxy A16, Samsung Galaxy A16, TCL 50 XE 5G, Tecno POVA 5, Vivo Y56 5G). The first driver named is compared against the second, which is the baseline.
StockMali-G57 MC2v1.r32p1-01eac0.745b2925e235161571d02cd6e9b890a7
vsCustomPanVK-FristOneRR-V.3.5FristOneRR 3.5 (Mesa 26.3.0-devel)
Graphics system version (Vulkan)1.1.177 to ?
Optional features (extensions)68 to ?not checked on both
Features that pass their check (validated)not tested on bothPanVK-FristOneRR-V.3.5: no driver check yet
Speed test scenes (benchmark)no shared scenes
Mali-G57 MC2 details PanVK-FristOneRR-V.3.5 details
Feature checks that differ
PanVK-FristOneRR-V.3.5: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
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 | 59.48 typical 59.03 | n/a | only one side | 3 of 3 vs 0 of 3 | ? vs ? clock unknown | not checked |
| hdr_2160p | 137.38 typical 137.47 | n/a | only one side | 3 of 3 vs 0 of 3 | ? vs ? clock unknown | not checked |
| oit_linked_lists | 30.37 typical 30.33 | n/a | only one side | 3 of 3 vs 0 of 3 | ? vs ? clock unknown | not checked |
| pipeline_barriers | 30.77 typical 30.94 | n/a | only one side | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 9.3 differs in 1725 small areas worst 71.0 64x36 |
| subpasses | 89.02 typical 89.33 | n/a | only one side | 3 of 3 vs 2 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 PanVK-FristOneRR-V.3.5 against Mali-G57 MC2. "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.