Enable AC3 and DTS support on MXplayer with Custom Codecs


If you have a Android device, then you must installed the ultra popular MX player on it. Just like VLC is to windows, MXplayer is there for Android. With more than 500 million users and a 4.4 rating, it is one of the most popular apps on the Google Play Store.
I have been using the app as the default video player on my android devices and to this day it had always played all the video formats that i have thrown at it. However starting last year November, the app was no more able to play audio formats with the AC3, DTS and Dolby digital codec.
As i dug deeper for a solution, i found out that issue had surfaced due to some licensing issues and as a result MXPlayer had to ditch native support for the AC3 and DTS /Dolby audio codec. Which means if any video file had a dts/dtshd/ac3/eac3/mlp audio track then the video will play without the audio.
Fortunately the codec can be installed separately on MXplayer and for those who want to enable support for codecs such as AC3, here’s how you can do so.

How to Enable Support for AC3 and DTS codecs on MXplayer.

  • Step 1: Navigate to MXplayer’s Settings and Tap on Decoder.


  • Step 2: Scroll down to the bottom of the menu and note down the architecture of your phone displayed under the Custom codec option. ( Note: In my case my phone’s architecture was ARMv7 NEON )

Alternatively for those who are not sure what their phone’s article is, you can download the “AIO pack “.

  • Step 3: Head over to the following link and download the AC3 codec file based on your phone’s architecture.

Download: AC3 and DTS Codec for MXplayer.

  • Step 4: Tap on Custom codec and select the codec file that you’ve downloaded from the link provided above.

That’s it, once the codec has been installed, MXplayer will request for a restart and then you can play videos with AC3 and DTS audio once again.

About the author



By lovejeet


Get in touch

Quickly communicate covalent niche markets for maintainable sources. Collaboratively harness resource sucking experiences whereas cost effective meta-services.