Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Reduce APK Size / Split project into three different libraries for x86, armv7 and armv7-neon #66
This project leads to apk of size > 40mb, this is huge waste of space and download time as most of the time, device has only one cpu architecture. Most android phones are armv7, so no need to ship x86 libraries along with the app. And as very few phones support armv7-neon, so no need to ship armv7-neon as well, you can always create three different apps for three different platforms.
Manually, I was able to delete x86 and armv7-neon, and brought down size of app to 10mb. So if there are three different libraries,
It will be of great help to developers.
It turns out that you can use cdn.jsdelivr to directly download ffmpeg binaries when user tries to use ffmpeg first time. There is no need to package this inside apk. See
changed the title from
Split project into three different libraries for x86, armv7 and armv7-neon
Reduce APK Size / Split project into three different libraries for x86, armv7 and armv7-neon
Feb 23, 2016
Release Apk with different cpu architecture
referenced this issue
May 13, 2016
I agree with the above statements.
I personally find it frustrating having spent weeks optimizing all assets in my APK only for it to become 5x larger after including this library...
i am using nexus device for testing. and still confused about app size.…
On 27-Dec-2016, at 3:03 PM, sashatinkoff ***@***.***> wrote: You shouldn't use both aar files, only one. As for me, I use gradle to make flavor for different architectures, one for x86 and another one for arm. AFAIK, x86 is not popular architecture so I decided to not publish build for it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#66 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXo7cD6Bvqzs6oATVutw47gXd3DvJFmEks5rMNtQgaJpZM4HX4as>.
@zoedevelopers i've just created a repo on github https://github.com/sashatinkoff/ffmpeg-for-Android-compiled
@zoedevelopers I guess ffmpeg has couple of flags that can affect on speed conversion. Unfortunately I faced that native ffmpeg library seems a little outdated and doesn't support them (such as -preset ultrafast). If you'll find any way to do it please share your solution here =)
As for me, conversion seems too slow. To make it a little faster I reduce a size of input video / images. In fact, you'll get a video with low quality but it's a best way that I found how to handle it. Honestly speaking, I didn't spend a much time to find a solution that really works.