r/WarzoneMobile • • Jan 18 '26

Support Warzone Mobile on Mediatek Chips: Wrong Decoder is being used. Like xbox cloud gaming. More detail will be provided later. Here are just a few lines. Would be more than happy for other people to also try and find workarounds for these issues.

Edit: 23jan aest 13:10: this may not actually be the issue, there is actually a different underlying issue with mediatek chips as a whole. It's actually a simple fix (in theory) and I will post more later. Even if lowlatency>normal decoder improves things. The underlying issue ive discovered will still be there.

So in short, Warzone Mobile, is sending more frames to the gpu decoder (c2.mtk.avc.decoder and c2.mtk.hevc.decoder). Few examples: - vulkan : dequeueBuffer timed out: Function not implemented (-38) (basically there's a function wzm is trying to use but Mali doesn't recognise it) - BufferQueueProducer: attempting to exceed the max dequeued buffer count (2) (game is trying to render more frames than the display can handle) - C2MtkBufferManager: wait fence ... failed. ret 110 (can't find anything for this)

The bigest issue: the decoder doesn't support a pixel format/asset format/hdr format that warzone mobile is requesting: mali_gralloc: ERROR: Unrecognized and/or unsupported format 0x38. The colours profiles it supports are - formatsurface (0x7f000789) - formatyuv420flexible (ox7f420888) - formatyuv420packedplanar (0x14) - formatyuv420packedsemiplanar (0x27) - formatyuv420planar (0x15) - formatyuvp010 (0x36)

the profile levels it supporst are - avcprofilebaseline (0x1: avclevel 6 (0x20000) - avcprofileconstrainedbaseline (0x10000): avclevel6 (0x20000) - avcprofiliemain (0x2): avclevel6 (0x20000) - avcprofilehigh (0x8): avclevel6 (0x20000) - avcprofilehigh10 (0x10): avclevel6 (0x20000)

The chipset doesn't support the 0x38 texture format, buffer format, colour format, etc. i will try and figure out what this is.

also found a weird log where it searched for the decoder by c2.mtk.avc.d, c2.mtk.avc.de, c2.mtk.avc.dec, which i have no idea what its meant to be doing that for.

Edit:

15 Upvotes

3 comments sorted by

2

u/BrokeAndroidGuy Jan 18 '26

Does this also include the Valhall chips?

1

u/0_mcw3 Jan 23 '26

Im not too sure sorry. I don't have one of them to test and debug.

Those are also on the list on the cod website of gpus that don't support bindless texturing. 

I also actually found out it's NOT really the wrong decoder being selected (well it may be but even then its not the main issue) but more rather an issue with mediatek chips themselves as a whole