![MX Player Custom Codec [AC3, DTS, EAC3, MLP, TrueHD, and more]](https://cdn.droidfeats.com/wp-content/uploads/2026/05/mx-player-custom-codec-2026-1024x576.webp "MX Player Custom Codec [AC3, DTS, EAC3, MLP, TrueHD, and more]")
MX Player, now published by Amazon, plays almost anything you throw at it, but the version on Google Play leaves out a few audio formats. Open a movie with a Dolby Digital Plus (E-AC-3) or Dolby TrueHD soundtrack and the picture plays in silence while MX Player tells you: “This audio format (EAC3) is not supported.” The MX Player Custom Codec fixes that. It’s a small ZIP file that adds the missing audio decoders to the app.
Below you’ll find the latest custom codec (3.1.0, including the MX Player AIO ZIP), the older 2.7.0, 1.87.0 and 1.49.0 codecs with the exact MX Player versions each one fits, and a step-by-step installation guide with fresh screenshots. We tested every step on MX Player 3.3.1, the current version on Google Play, on October 17, 2026.
What’s new in this update (October 21, 2026)
- We checked which codec more than 60 MX Player releases ask for, from 1.85 to the new 3.4.0. The table below lists exact versions, so you can match yours.
- MX Player 3.1.1 and later, including 3.3.1 on Google Play and 3.4.0, need custom codec 3.1.0. We installed it on MX Player 3.3.1 and played E-AC-3, TrueHD and MLP soundtracks that wouldn’t play before.
- New sections for codecs 1.87.0, 2.7.0 and 1.49.0, for the EAC3 codec and its “not supported” message, and for picking the right CPU type.
- A correction: MX Player recognizes a codec by the file inside the ZIP, so the ZIP’s own name doesn’t matter.
Which MX Player custom codec do I need?
The codec has to match the codec version your MX Player asks for, which is a different number from the app’s own version. We read it from more than 60 MX Player releases, so find yours in the left column. Your phone shows the app’s version at the bottom of Settings > Apps > MX Player.
| Your MX Player | Codec it asks for | Download |
|---|---|---|
| 3.1.1 to 3.4.0, including 3.1.2, 3.1.4, 3.2.1 and 3.3.1 (Google Play) | 3.1.0 | aio-v3.1.0_r1.zip |
| 2.7.1 to 3.0.13, including 2.13.4, 2.14.1, 3.0.12 and 3.0.13 | 2.7.0 | aio-v2.7.0_r0.zip |
| 2.6.1 to 2.6.3 | 2.5.0 | aio-v2.5.0_r0.zip |
| 1.87.0 to 2.6.0, including 1.9x, 2.1.1, 2.3.0 and MX Player Pro 1.93 | 1.87.0 | mx_aio.zip (1.87.0) |
| 1.49 to 1.86 | 1.49.0 | mx_neon64.zip (1.49.0) |
Not sure? MX Player tells you. If you load a codec that doesn’t fit, it names the exact version and CPU type it wants, for example “Please use version 3.1.0 ARMv8 NEON codec.”
What is MX Player Custom Codec?
MX Player decodes audio and video with FFmpeg, an open-source library that comes built into the app. To avoid licensing costs, the version on Google Play ships with some audio decoders turned off. A custom codec is the same FFmpeg library rebuilt with every decoder turned on. MX Player loads it instead of its own, and the missing formats start to play.
AC3, DTS and TrueHD support in MX Player
This is how MX Player 3.3.1 handles common movie soundtracks without a custom codec. We tested each format with our own sample files. With custom codec 3.1.0 installed, the three that failed played too:
| Audio format | Where you’ll see it | MX Player 3.3.1 without codec |
|---|---|---|
| E-AC-3 (Dolby Digital Plus, “DDP”) | Most WEB-DL movies and TV episodes | Not supported |
| TrueHD (Dolby TrueHD, often with Atmos) | Blu-ray remuxes | Not supported |
| MLP (Meridian Lossless Packing) | DVD-Audio and some older discs | Not supported |
| AC-3 (Dolby Digital, “DD”) | DVDs, TV recordings, older movies | Plays |
| DTS | Blu-ray and DVD movies | Plays |
So in today’s MX Player, the custom codec is about E-AC-3, TrueHD and MLP. AC-3 (Dolby Digital) and DTS play without it. Older MX Player versions also need the codec for AC-3 and DTS, which is where it got its reputation: if yours refuses an AC3 soundtrack, install the codec version it asks for from the table above.
Download MX Player Custom Codec (& MX Player AIO ZIP)
These builds are compiled from the official MX Player FFmpeg source code, which Amazon publishes on MX Player’s website, with every decoder turned on. They come from the open-source MX-FFmpeg project on GitHub, where GitHub’s own servers compile and publish each release.
If you’re not sure which file to get, download the AIO ZIP (all-in-one). It holds the codec for every CPU type and MX Player picks the right one by itself. In older builds the same file was called mx_aio.zip.
MX Player Custom Codec 3.1.0 (latest, for MX Player 3.1.1 and later)
MX Player Custom Codec 3.1.0 (AIO ZIP)
Prefer a smaller download? Get only the file for your phone’s CPU type:
| CPU type (as MX Player shows it) | File | Size |
|---|---|---|
| ARMv8 NEON (64-bit, nearly every phone) | neon64-3.1.0-build_1.zip | 5.9 MB |
| ARMv7 NEON (older 32-bit phones) | neon-3.1.0-build_1.zip | 6.0 MB |
| x86_64 (64-bit Intel) | x86_64-3.1.0-build_1.zip | 6.4 MB |
| x86 (32-bit Intel) | x86-3.1.0-build_1.zip | 6.5 MB |
MX Player 3.3.1 is built only for ARM processors, so on a phone you almost certainly want ARMv8 NEON or the AIO ZIP. Not sure? See which CPU type to download.
Check the files (SHA-256)
aio-v3.1.0_r1.zip ebb0bd5db0f855caca6167747987a229836d7cc0062a2d5c23dbf91d057c617b
neon64-3.1.0-build_1.zip 9bb53b27f1956a6397396006c6d14237b4e60ea22712a3188a7d641b1e954f40
neon-3.1.0-build_1.zip 5813e02d437230a3a055c3fb050dc195d2d0289a5d5cc59ab5b5f3c360537a2a
x86_64-3.1.0-build_1.zip a5fbec4c7448a641d710ece5f9316f4e2df861263a0bb8d377eaa01a3246c04f
x86-3.1.0-build_1.zip 0852c1510aae7b8d2f130a71d3769e5004568512181f4b974a89774b3d48d74eCustom codec for older MX Player versions
On an older MX Player, install the codec version it asks for. Each one has its own section below: 1.87.0, the MX Player AIO ZIP for 1.9x and Pro 1.93, 2.7.0, 2.5.0 and 1.49.0.
MX Player AIO ZIP 1.87.0 (for MX Player 1.87 to 2.6.0 and Pro 1.93)
MX Player 1.87.0 to 2.6.0 and MX Player Pro 1.93 ask for custom codec 1.87.0. For the 1.9x versions and Pro 1.93, get mx_aio.zip from USBhost’s last release:
MX Player AIO ZIP 1.87.0 (mx_aio.zip)
These MX Player versions name it whenever you load another codec: “Can’t find custom codec. Please use version 1.87.0 ARMv8 NEON codec.” On older 32-bit phones the message says ARMv7 NEON instead.
mx_aio.zip holds four files, one per CPU type: libffmpeg.mx.so.neon64.1.87.0 (ARMv8 NEON), libffmpeg.mx.so.neon.1.87.0 (ARMv7 NEON), libffmpeg.mx.so.x86.1.87.0 and libffmpeg.mx.so.x86_64.1.87.0. mx_neon64.zip (5.9 MB) holds only the ARMv8 NEON file, which is what nearly every phone needs. The other single files (mx_neon.zip, mx_x86.zip and mx_x86_64.zip) are on the release page.
Is there an MX Player AIO ZIP 1.87.0 APK?
No. The custom codec isn’t an app, so there’s no APK to install: it’s the ZIP file above, and MX Player loads it by itself. Anything offered as an “AIO ZIP APK” or a “codec APK” is not the codec, so don’t install it.
How to install the 1.87.0 codec
- Download mx_aio.zip, or mx_neon64.zip, on your phone. It’s saved in the Download folder.
- Open MX Player. If it finds the codec and asks whether to use it, tap OK, then OK again to restart the app.
- No question? Open MX Player’s settings, go to Decoder > Custom codec, pick the ZIP file and restart MX Player.
The full guide below walks through the same steps in MX Player 3.3.1, with screenshots.
On MX Player 2.0 to 2.6.0
These versions ask for 1.87.0 too, but USBhost’s file was built for the 1.9x apps. The MX-FFmpeg project on GitHub made newer 1.87.0 builds for them: aio-v1.87.0_r6.zip (made for MX Player 2.5) and aio-v1.87.0_r5.zip (made for MX Player 2.1). Start with the one closer to your version, and if MX Player can’t load it, try the other.
MX Player Custom Codec 2.7.0 (for MX Player 2.7 to 3.0)
MX Player 2.7.1 to 3.0.13 ask for custom codec 2.7.0. That includes versions people often look for, such as 2.13.4, 2.14.1, 3.0.12 and 3.0.13.
MX Player Custom Codec 2.7.0 (AIO ZIP)
The ARMv8 NEON file is neon64-2.7.0-build_0.zip, and it’s all most phones need. The ARMv7 NEON and x86 files (neon-2.7.0-build_0.zip, x86-2.7.0-build_0.zip and x86_64-2.7.0-build_0.zip) are on the release page.
These MX Player versions ask for it like this: “Can’t find custom codec. Please use version 2.7.0 ARMv8 NEON codec.” Like every custom codec, 2.7.0 has no APK. Searches for an “AIO ZIP 2.7.0 APK” lead to apps that aren’t the codec, so download the ZIP above and install it the usual way.
Codec 2.5.0 (for MX Player 2.6.1 to 2.6.3)
MX Player 2.6.1 to 2.6.3 ask for codec 2.5.0, a version MX Player used only for these three releases. Get aio-v2.5.0_r0.zip (24.8 MB) or, for ARMv8 NEON, neon64-2.5.0-build_0.zip (5.9 MB).
MX Player Codec 1.49.0 ARMv8 NEON (for MX Player 1.49 to 1.86)
MX Player 1.49 to 1.86 ask for codec 1.49.0. On nearly every phone, their message reads “Please use version 1.49.0 ARMv8 NEON codec,” and this is the file:
MX Player Codec 1.49.0 ARMv8 NEON
Inside is one file, libffmpeg.mx.so.neon64.1.49.0. For an older 32-bit phone, take mx_neon.zip from the same release, or mx_aio.zip, which holds every type.
On MX Player 1.86? USBhost also made a newer build from that version’s source code, and its files still carry the 1.49.0 name: release 1.86.0. Use it if the 2022 build doesn’t load.
ARMv8 NEON vs ARMv7 NEON vs x86: which codec file to download
Every codec version comes as four files, one per processor type, and MX Player only loads the one that matches your device. The AIO ZIP holds all four, so if you’re unsure, take it and let MX Player pick.
| MX Player asks for | Devices | File name has |
|---|---|---|
| ARMv8 NEON | 64-bit ARM phones and tablets: nearly every phone today | neon64 |
| ARMv7 NEON | Older 32-bit phones, and TV boxes that run a 32-bit system | neon (no 64) |
| x86_64 | 64-bit Intel and AMD devices, such as PC emulators | x86_64 |
| x86 | 32-bit Intel devices, such as a few old tablets | x86 (no _64) |
For example, the ARMv8 NEON file is neon64-3.1.0-build_1.zip for codec 3.1.0, and mx_neon64.zip in the older USBhost builds.
To check, open MX Player and go to Me > Settings > Decoder, then scroll to the bottom. The line under Custom codec names the type your device needs.
“Use ARMv8 NEON type custom codec”: what it means
It isn’t an error. MX Player shows this line under Custom codec while no custom codec is installed, to tell you which type to get. Download the ARMv8 NEON file (the one with neon64 in its name) for the codec version your MX Player needs, or the AIO ZIP, and install it. After that, the line shows the file MX Player loaded.
If it says “Use ARMv7 NEON type custom codec” instead, get the file with neon, without 64, in its name.
How to install MX Player Custom Codec
Installing the codec takes about a minute and doesn’t need root. MX Player can find the file by itself, so start with method 1.
Method 1: Let MX Player find the codec (easiest)
Step 1: Download the AIO ZIP, or the ZIP for your CPU type, on your phone. Your browser saves it in the Download folder. There’s no need to unzip or rename it: MX Player looks inside ZIP files for the codec file it needs.
Step 2: Open MX Player. If it asks for access to all files, allow it. The app needs that permission to read the codec.
Step 3: MX Player finds the file and asks whether to use it as the custom codec. Tap OK.
Step 4: Tap OK again when MX Player says it’s restarting to reload the codec. The app closes. Open it again.
Step 5: Play your video. E-AC-3, TrueHD and MLP soundtracks now play like any other.
Method 2: Choose the codec file yourself
Use this method if MX Player doesn’t offer the codec on its own, for example because the file is in a different folder.
- Open MX Player and tap Me at the bottom right.
- Tap Settings, then Decoder.
- Scroll to the bottom. Under General, tap Custom codec.
- Go to the folder with the ZIP file and tap it.
- Tap OK to restart MX Player, then open it again.
Can’t tap Custom codec? It’s the last option on the Decoder screen, and on phones with three navigation buttons it can end up behind them. Switch to gesture navigation in your phone’s settings for a moment, and the option moves into view.
How to check that the custom codec is working
Go back to Me > Settings > Decoder. Instead of the codec type, the Custom codec option now shows the file MX Player loaded. Then play a video with E-AC-3 audio: the “audio format is not supported” message should be gone.
EAC3 codec for MX Player: download and setup
There’s no separate EAC3 codec. E-AC-3, the Dolby Digital Plus sound you’ll see as DDP or DD+ in file names, is one of the formats the custom codec adds, so the EAC3 codec for MX Player is the same AIO ZIP. For MX Player 3.1.1 and later, including 3.3.1 on Google Play, that’s version 3.1.0:
EAC3 codec for MX Player (custom codec 3.1.0)
- Download the ZIP on the phone or TV that runs MX Player. It goes to the Download folder.
- Open MX Player and tap OK when it offers the codec, then OK again so it restarts.
- Play your video. The EAC3 soundtrack now plays.
Screenshots of each step are in how to install MX Player Custom Codec.
EAC3 on Android TV
MX Player on Android TV uses the same codec. Download the AIO ZIP on the TV if it has a browser, or copy it to the TV’s Download folder with a USB stick or a file manager app, then open MX Player. The AIO ZIP is the safest choice on a TV, because it covers every CPU type.
EAC3 in MX Player Pro
MX Player Pro uses the same codec files as the free app. Pro 1.93 asks for codec 1.87.0, so get the MX Player AIO ZIP 1.87.0.
How to fix “This audio format (EAC3) is not supported” in MX Player
MX Player shows this message when a video’s soundtrack is E-AC-3 (Dolby Digital Plus) and no matching custom codec is loaded. The picture plays, but there’s no sound. To fix it:
- Look up the codec version your MX Player needs in the table at the top. For the current MX Player, that’s 3.1.0.
- Download that codec’s AIO ZIP and install it. It takes about a minute.
- Open the video again. It now plays with sound.
The same message with TRUEHD or MLP in place of EAC3 means the same thing, and the same fix works.
Still not supported after installing the codec?
First check Me > Settings > Decoder > Custom codec. If it doesn’t show your ZIP file, the codec isn’t loaded: install it again, and make sure it’s the version MX Player asks for. If it does show the file, the soundtrack may use a format no MX Player codec decodes, such as Dolby AC-4. If the video has a second audio track, pick that one from MX Player’s audio track menu.
MX Player custom codec not working? How to fix it
“Can’t find custom codec. Please use version 3.1.0 codec”
MX Player shows this when the codec doesn’t match. The message names the version and CPU type it wants, so download exactly that: 3.1.0 for MX Player 3.1.1 and later, 2.7.0 for 2.7 to 3.0, and 1.87.0 for 1.87 to 2.6.0. MX Player 3.3.1 shows it, for example, when you load the old 1.87.0 codec.
“Custom codec is out of date”
MX Player updated to a new FFmpeg version and stopped using your codec. Download the codec version the app now asks for and install it the same way. We update this page when a new codec comes out.
MX Player doesn’t find the codec file
- Keep the file in the Download folder or the main folder of your phone’s storage.
- Make sure it’s the version MX Player asks for. MX Player 3.3.1, for example, doesn’t offer the 1.87.0 mx_aio.zip, because it needs 3.1.0.
- Don’t rename the file inside the ZIP. MX Player looks for an exact name such as libffmpeg.mx.so.neon64.3.1.0. The ZIP itself can have any name.
- Allow MX Player access to all files when it asks.
- Still nothing? Use method 2 and pick the file yourself.
The codec stopped working after an update
Google Play updates MX Player automatically, and a big update can need a new codec. Download the version MX Player now asks for. If you’d rather stay on a version that works, open MX Player’s page in the Play Store, tap the three-dot menu and turn off Enable auto update.
What to do when you update MX Player?
Usually nothing. MX Player’s app version and its codec version are separate numbers: MX Player 3.3.1 and the newer 3.4.0 still use codec 3.1.0, so most updates keep working with the codec you have.
When an update moves MX Player to a new FFmpeg version, the app ignores your old codec and asks for the new one. Download the version it names and repeat the steps above. Until then, nothing else changes. MX Player simply plays without the extra formats.
Does the custom codec fix 4K, HEVC or HDR video?
No. The custom codec is MX Player’s own FFmpeg library (version 4.2), rebuilt from Amazon’s source code with one change: the limits on which formats it may decode are switched off. It doesn’t make video play faster or look better, and it adds no HDR or Dolby Vision support.
4K, HEVC and HDR video play best with the HW+ or HW decoder, which uses your phone’s own video hardware. If such a file stutters, tap the decoder label (HW+, HW or SW) at the top right while it plays and try another one. If none of them plays smoothly, your phone can’t handle that file, with or without a custom codec.
Dolby Vision video only shows correct colours on phones that support Dolby Vision. On other phones, some Dolby Vision files play with green and purple tints, and no codec can fix that.
Where the codec comes from: GitHub and XDA builds
Amazon publishes MX Player’s FFmpeg source code on MX Player’s website. Two open-source projects on GitHub turn it into custom codecs:
- iDNA420/MX-FFmpeg builds the current codecs: 3.1.0, 2.7.0 and 2.5.0, plus the 1.87.0 builds for MX Player 2.x. GitHub’s own servers compile each release from Amazon’s source and list a SHA-256 checksum for every file.
- USBhost/MX_FFmpeg is the older project, with releases going back to 2020, and its mx_aio.zip files have been downloaded more than 3.6 million times. It made the 1.87.0 and 1.49.0 codecs on this page. Its last release came out in June 2025, before MX Player 2.
Both projects come up in the long-running MX Player Custom Codec thread on XDA Forums, where users report which codec each new MX Player version asks for. Every download link on this page points straight to the GitHub releases, so you get the same files without digging through the forum.
Is the MX Player custom codec safe?
The codecs on this page are built from MX Player’s official open-source FFmpeg code, the source Amazon publishes for the app, and the only change is that all decoders are turned on. The current builds are compiled and published by GitHub’s servers, so anyone can check what went into them.
Before writing this guide, we downloaded the 3.1.0 files, compared them with the checksums GitHub lists and installed the codec on MX Player 3.3.1. Steer clear of “codec APKs” and modified MX Player apps from download sites. A real custom codec is always a ZIP file or a file whose name starts with libffmpeg.mx.so, never an app.
Frequently asked questions
Does MX Player still need a custom codec for AC3 and DTS?
Not the current version. In our tests, MX Player 3.3.1 played AC-3 and DTS soundtracks with its built-in decoder. You still need the custom codec for E-AC-3 (Dolby Digital Plus), TrueHD and MLP, and older MX Player versions need it for AC-3 and DTS too.
How do I install the EAC3 codec in MX Player?
Download the custom codec’s AIO ZIP (3.1.0 for the current MX Player) on your phone, open MX Player and tap OK when it offers the codec. MX Player restarts, and EAC3 soundtracks play. If it doesn’t offer the file, go to Me > Settings > Decoder > Custom codec and pick the ZIP yourself.
Which custom codec works with the latest MX Player?
Custom codec 3.1.0, the file aio-v3.1.0_r1.zip. We tested it with MX Player 3.3.1, the current version on Google Play in October 2026, and the newer MX Player 3.4.0 asks for the same codec.
What is the MX Player AIO ZIP?
It’s the all-in-one codec file. It holds the codec for ARMv8 NEON, ARMv7 NEON, x86 and x86_64, and MX Player loads the one that matches your phone. Older builds called it mx_aio.zip; the current file is aio-v3.1.0_r1.zip.
Does the custom codec work with MX Player Pro?
Yes, the same codec files work with both editions. MX Player Pro is no longer on Google Play, though. MX Player Pro 1.93 uses codec 1.87.0, the MX Player AIO ZIP 1.87.0; if yours asks for a different version, use that one.
Do I need root to install the custom codec?
No. MX Player loads the codec itself, so it works on any phone.
Will the custom codec play Dolby Atmos?
It plays the soundtrack of Atmos movies, because Atmos is carried on top of an E-AC-3 or TrueHD track. You hear the regular 5.1 or 7.1 mix, but MX Player doesn’t decode the Atmos height channels.
Can I use the custom codec on Android TV?
Yes, if your TV runs MX Player. Copy the ZIP file to the TV’s Download folder with a file manager, then follow the steps above.
How do I remove the custom codec?
Open Me > Settings > Decoder > Custom codec and tap Use default codec. MX Player restarts with its built-in codec.
Is there a video player that plays E-AC-3 without a codec?
Yes. VLC for Android plays E-AC-3, TrueHD and DTS out of the box. Many people still prefer MX Player for its gestures, subtitle options and hardware decoding, and with the custom codec it plays these formats too.
Final thoughts
MX Player is still one of the best video players on Android, and the custom codec is what makes it play everything. Grab the 3.1.0 AIO ZIP, let MX Player find it, and your E-AC-3 and TrueHD movies will play with sound. On an older MX Player, use the codec version it names. If something doesn’t work, tell us your MX Player version and the exact message in the comments, and we’ll help.
More on MX Player: How to make MX Player the default video player · Why MX Player Pro 1.26.7 remains unbeatable
![Download Vivo X300 Ultra GCam Port [Most Compatible Version]](https://cdn.droidfeats.com/wp-content/uploads/2026/04/Vivo-X300-Ultra-768x523.avif "Download Vivo X300 Ultra GCam Port [Most Compatible Version]")
Codec for neon armv8
Post updated. Please try the newer version of AIO ZIP.
ARMv8 neon codec i need
1.44.0 ARMv8 NEON I want
Anyone have zip file armv8 neon for 1.25.0 mx player veriosn . If anyone have this Pls reply
Please try the All in One version.
TnQ for your msg ????
You are most welcome 🙂
Hello sir i need 1.44.0 ARMv7 neon no other codec working for me my device is Samsung j7 prime plz sir solve my problem
Thank you very much..
You are welcome 🙂
Hello,
I downloaded an mx player from Google Play in version 1.26.7,
and when I want to run the decoder – (I tried NEON and AIO),
it writes to me “Can’t find a custom decoder. Please use the ARMv7 NEON 1.25.0 decoder version”.
What am I supposed to do?
Some audio files are not working (EAC3) And it sucks me a lot.
Thank you very much
Hi Avi,
It’s strange that the AIO ZIP isn’t working for you. However, can you please tell me your device name so that I can provide you the specific files?
I got along, thanks for the goodwill ????
Glad, you got it.
Hello Ashif, I was facing trouble in using any of the provided codec even the AIO was not working for me.
can you please provide me any specific codec ? please advice.
Attaching you the error that I was facing.
Sorry ! I forgot to mention my device.
Samsung j7 pro.
Mx player version
Version 1.26.7 (ARMv7 NEON)
Please try version 1.25 here: https://github.com/USBhost/MX_FFmpeg/releases/download/1.25.0/mx_aio.zip
Replied in the another comment, please check.
I want 1.49.0 ARMv8 NEON codec
Vivo y 35 device name
Sir I have redmi and I also want arm v7 neon 1.25.0 codec
Check this out: https://forum.droidfeats.com/t/latest-release-mx-player-custom-codec-github/38/2
Ine is vivo Z1 pro
All in one is still not working
Ki phone use kori asa? Device specific files di asu, judi device architecture tu kobo para?
Tried MX aio pack but didn’t work. It says “Can’t find custom codec. Please try version 1.25 ARMv8 NEON codec.”
Hi Anandhu,
Thank you for your report. Can you please mention your device architect so that we can update the perfect link for you?
Please try AIO version 1.25, and do let me know!
no codec was working for me… popping an error saying to use 1.25.0 ARMv7 Neon codec…
please help me with this
Here’s the NEON 1.25 ZIP for you!
Enjoy!
Thank U…. working for me ????
You are most welcome 🙂
Thanks a lot. I was frustrated with all the zips popping the same error. Finally your link worked (neon 1.25).
You are most welcome 🙂
Hii bro. Well im having same trouble as this guy. And i used this 1.25 version u have given still its not working for me.
BTW my phone is poco F1 and Mx player version is : version 1.28.7(ARMv8 NEON)
Since you are in ARM v8, you can try out the latest version AIO version here: https://github.com/USBhost/MX_FFmpeg/releases/download/1.25.0/mx_aio.zip
If this doesn’t work, you need to downgrade the MX Player, or else, just wait for the developer to release a newer version of Codec.
Hey brother, Your link custom codec for 1.25.0 ARMv7 Neon is still working. Thank you & Take love ❤️
You are most welcome ????
Glad it helped you!
Hie bro. See this error msgs im getting from trying to use those codecs zip files even the ones u posted for SAI SARAT,. ANYWAYS this is the error im getting and my phone is MI POCO F1 having SG845 chipset , plus MX player version is 1.28.7 (ARMv8 NEON). ..
And im error its asking for version 1.25.0 armv8 neon codec which shown in my scren shot.. plzz see if u can help me with this bro. Thks..
Sorry for the late reply, please download from this link for v1.25: NEON 1.25 ZIP
my phone is Samsung m30s still showing this please help me
Link updated for the latest AIO version. Try this: https://forum.droidfeats.com/t/latest-release-mx-player-custom-codec-github/38
Not supporting eac3
Mi 10 5g
Sir Aio Zip isn’t working ????…… my device name is “Moto g5splus” plz plz provide me any specific codec ….
if anyone have “version 1.25.0 ARMv7 Neon codec” plz provide me
Browse the required version here: https://drive.google.com/drive/folders/1Jh6id4rYW4Vujyhm5tIcddTb5ilmG-D9
Please?
Bro aio zip isn’t working it needs armv8 1.25.0
Nd my mobile is one plus 5
Pls help man
Find it here: https://drive.google.com/drive/folders/1Jh6id4rYW4Vujyhm5tIcddTb5ilmG-D9
Hi,
If you are looking for ARMV8 NEON 1.25.0, Please click on this link or copy-paste to your browser https://drive.google.com/file/d/19Ts63n_oBpSwKF8933tnfNNr1QXeoU-Z/view?usp=sharing and download the file on google drive. After download moves it to any other folder then unzips the file. Now go the MX Player and locate/select the unzipped file (ie lipffmpeg.mx.so.neon64.1.25.0).
You are done !!!
Sarwar Alam
Hello sir can send v1. 25.0 neon armv8 AIO zip please
Already provided. Please visit the forum!
It’s showing this error for me. “Can’t find custom codec. Please use version 1.42.2 ARM v8 Neon codec.” I tried using aio.zip and neon.zip
Same here
Any of those codecs are not working its showing use ARMv8 1.41.2 version
Check now. All updated.
Hlw sir audio EAC3 is not supported telling to use 1.41.2 version ARMv8 NEON my device is redmi 10 prime
Hlw sir audio EAC3 is not supported telling to use 1.41.2 version ARMv8 NEON my device is redmi 9 prime
Showing Use version 1.44.0 ARMv8 NEON codec ..what to do now?
look up for this version brother
Hi
How may I help you?
I have Xiaomi Redmi Note 9 Pro (global/joyeuse) and it says wants V1. 44 version. Is there a reason why it won’t use any later versions?
Compatibility.
Hi sir please find version 1.51.7 ARMv7 custom codec and version 1.49.0 ARMv7 please find out sir
We are working on it!
Stay tuned!
Audio note support
Which codec? And the device?
Hello sir 1.49.0 armv7 version upload please sir
Thank you for your feedback. We have updated the links for armv7. Please check them now and let us know if you have any further questions.
Additionally, please feel free to share this post on social media as a way to express your gratitude.
Hello sir 1.49.0 ARMv8 NEON codec please upload sir
Hello Shivam,
Thank you for your message. I wanted to let you know that we are working on uploading the files you requested. We understand your eagerness and assure you that they will be available shortly. We appreciate your patience and encourage you to stay tuned for updates.
Good