Home / Mali-G52 / Compare

Mali-G52 MC2 vs Mali-G52

On Mali-G52 (CHUWI HiPad-Air, HONOR X5c, HONOR X5c, Infinix HOT 60i, Oppo A18, Oppo A38, realme RMX3710, Redmi 12, Redmi 12C, Redmi 14C, Redmi 15C, TECNO POVA 3, TECNO SPARK 20, Xiaomi 24049RN28L). The first driver named is compared against the second, which is the baseline.

StockMali-G52v1.r27p0-01eac0.560a3910a3367e0bb739a6eb4e910d0f

CustomMali-G52 MC2v1.r32p1-01eac0.52688e0652bc37eab85ce86c674ab12f

Graphics system version (Vulkan)1.1.149 to 1.1.177

Optional features (extensions)58 to 66+8 -0

Features that pass their check (validated)39 to 28Mali-G52: sent from a device this site could not confirm (unverified)2 pass only on Mali-G52 MC2 13 pass only on Mali-G52

Speed test scenes (benchmark)no shared scenes

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

Mali-G52 details Mali-G52 MC2 details

Feature checks that differ (18)

Unverified Mali-G52: The results below were sent from a device this site could not confirm. A result the site counts replaces them.

Feature	Stock	Mali-G52 MC2	Change
largePoints VkPhysicalDeviceFeatures	pass	untested	lost
compat.helper_loop_terminator core	pass	untested	lost
compat.nested_map core	pass	untested	lost
core.blend_advertised_formats core	pass	untested	lost
core.compute_big_stack core	pass	untested	lost
core.host_coherent_readback core	pass	untested	lost
core.mrt_partial_kill core	pass	untested	lost
core.ubo_update_buffer core	pass	untested	lost
core.ubo_written_after_record core	pass	untested	lost
core.varying_subset core	pass	untested	lost
mem.image_padding core	pass	untested	lost
stage.geometry_max_output core	pass	untested	lost
sync.first_submit_clear_then_compute core	pass	untested	lost
customBorderColors VK_EXT_custom_border_color	unsupported	pass	gained
stress.submit_memory core	inconclusive	pass	gained
customBorderColorWithoutFormat VK_EXT_custom_border_color	unsupported	untested	changed
timelineSemaphore VK_KHR_timeline_semaphore	crash	fail	changed
stage.geometry_point_size core	unsupported	untested	changed

Speed test scenes (benchmark)

unverified Mali-G52: 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	Mali-G52 MC2 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	63.71 typical 62.83	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
hdr_2160p	160.91 typical 157.70	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
oit_linked_lists	71.56 typical 71.03	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
pipeline_barriers	44.54 typical 3.42	n/a	only one side	3 of 3 vs ?	? vs ? clock unknown	not checked
subpasses	99.31 typical 3.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 Mali-G52 MC2 against Mali-G52. "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 Mali-G52 MC2 (8)

VK_EXT_4444_formats
VK_EXT_calibrated_timestamps
VK_EXT_custom_border_color
VK_EXT_device_memory_report
VK_EXT_provoking_vertex
VK_EXT_subgroup_size_control
VK_EXT_swapchain_maintenance1
VK_KHR_shader_non_semantic_info

Extensions only in Mali-G52 (0)

None

Core features that differ (0)

None

Limits that differ (11)

Limit	Stock	Mali-G52 MC2
maxImageDimension2D	16383	16384
maxImageDimension3D	16383	16384
maxImageDimensionCube	16383	16384
maxImageArrayLayers	1024	4096
maxTexelBufferElements	65536	268435456
maxViewportDimensions	16383, 16383	16384, 16384
viewportBoundsRange	-32766, 32765	-32768, 32767
maxFramebufferWidth	16383	16384
maxFramebufferHeight	16383	16384
timestampComputeAndGraphics	0	1
timestampPeriod	0	76.9231

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

Only in Mali-G52 MC2:

A4B4G4R4_UNORM_PACK16
A4R4G4B4_UNORM_PACK16

Only in Mali-G52:

None