Permission denied running version command when targeting Android Q #126

darrinps · 2019-07-26T17:49:06Z

Not sure if it's because I am running Android Q beta, or I'm doing something wrong but I am getting the following:

2019-07-26 12:29:01.320 24329-24408/com.android.testffmpeg E/FFmpeg: Exception while trying to run: [/data/user/0/com.android.testffmpeg/files/ffmpeg, -version]
java.io.IOException: Cannot run program "/data/user/0/com.android.testffmpeg/files/ffmpeg": error=13, Permission denied
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1050)
at nl.bravobit.ffmpeg.ShellCommand.run(ShellCommand.java:15)

All I am doing is calling this function:

`
private fun versionFFmpeg() {
FFmpeg.getInstance(TestFFmpegApplication.instance.applicationContext)
.execute(arrayOf("-version"), object : ExecuteBinaryResponseHandler() {
override fun onSuccess(message: String?) {
Timber.d(message)
}

            override fun onProgress(message: String?) {
                Timber.d(message)
            }
        })

}

`

The only setup I have in the code is this:

implementation 'nl.bravobit:android-ffmpeg:1.1.7'

Can anyone see what it is I am missing, or perhaps there is an issue running on Android Q?

The text was updated successfully, but these errors were encountered:

darrinps · 2019-07-26T18:33:20Z

Looks like it's Q. If I build and run your sample app verbatim, it works, but when I change the compile and target SDK to be 29....crash. Same as I see in my app. So I think this looks to be a fairly high bug given Q will be released shortly.

alexcohn · 2019-08-07T08:03:59Z

~~Tried this on Q emulator, system-images\android-29\google_apis\x86, and it simply worked.~~

alexcohn · 2019-08-11T11:24:48Z

I have updated the Q emulator (now it is [google/sdk_gphone_x86/generic_x86:10/QPP6.190730.005.B1/5775370:userdebug/dev-keys]), and the it does not permit to run ffmpeg from the files directories anymore. Or maybe the trigger is that I set targetSdk=29.

Actually, this is a documented change.

The fix is to move ffmpeg from assets to jniLibs.

see bravobit#126

desaibijal · 2019-12-23T09:10:05Z

Someone has solution to run ffmpeg commands in android Q its urgent??

kartik1225 · 2019-12-27T20:14:09Z

Any updates on this?

kazemihabib · 2019-12-27T20:18:57Z

Hi,
I didn't try it myself but probably you can fix it with adding

android:requestLegacyExternalStorage="true"

to application in AndroidManifest.xml

kartik1225 · 2019-12-27T20:26:21Z

No, it still does not work

WassimErriha · 2020-01-09T19:05:08Z

Try this library
I just tested it on a physical device running Android Q (android 10)

PO15ON · 2020-02-15T14:51:35Z

@WassimErriha Thanks, it worked.

Aditya94A · 2020-02-27T04:24:18Z

Any updates on this?

Or is this the end of this library?

Le-Dinh-Nam · 2020-03-08T03:06:15Z

I found solution on this issue.
https://issuetracker.google.com/issues/128554619

exec() no longer works on files within the application home directory, it continues to be supported for files within the read-only /data/app directory. In particular, it should be possible to package the binaries into your application's native libs directory and enable android:extractNativeLibs=true, and then call exec() on the /data/app artifacts. A similar approach is done with the wrap.sh functionality, documented at https://developer.android.com/ndk/guides/wrap-script#packaging_wrapsh .

It works well on my project(tested on Pixel 3a XL android Q)

AmioLee · 2020-03-12T03:42:09Z

I have updated the Q emulator (now it is [google/sdk_gphone_x86/generic_x86:10/QPP6.190730.005.B1/5775370:userdebug/dev-keys]), and the it does not permit to run ffmpeg from the files directories anymore. Or maybe the trigger is that I set targetSdk=29.

Actually, this is a documented change.

The fix is to move ffmpeg from assets to jniLibs.

I have create jniLibs folder then move the lib from assets,but still not work,
Is there something i miss?

alexcohn · 2020-03-12T07:37:24Z

I have create jniLibs folder then move the lib from assets,but still not work,
Is there something i miss?

It's much more than simply renaming some folders, see #130

vincent-paing · 2020-04-08T11:04:19Z

Why hasn't this been merged yet, even Android 11 is about be released, has this project been abandoned?

pratikbutani · 2020-05-05T04:26:05Z

Just change targetSdkVersion 29 to 28 in build.gradle

It worked for me.

kibotu · 2020-05-05T13:06:30Z

@pratikbutani not a solution that works on higher android versions

pratikbutani · 2020-05-06T01:43:42Z

@kibotu
It's working on higher version too. I have checked on Android 10.

SnehaDZ · 2020-05-11T06:07:55Z

not working for me

aliraza96 · 2020-05-12T05:58:59Z

NOT WORKING FOR ME TOO. Have anyone found an answer to this problem?

alexcohn · 2020-05-12T07:05:46Z

@SnehaDZ @aliraza96 if you can set targetSdkVersion less than 29, your app will continue to work even on Android 11 (a.k.a. Android R). Note that this does not prevent you from using the new Android Q APIs in your code.

But if you want to switch to 29, you can try my fork. In the long run, I would recommend to switch to another library, even though this means that your code must be changed: with every upgrade, Android becomes less open to running executables in the context of an app.

Ahmed-Basalib10 · 2020-07-18T12:56:31Z

any update ?

kdsrsl · 2020-07-20T11:08:22Z

still unrepaired

iamkdblue · 2020-07-22T07:22:59Z

any update?

vincent-paing · 2020-07-22T08:21:42Z

We're using this library instead now, which is still maintained actively

https://github.com/tanersener/mobile-ffmpeg

1nikolas · 2020-07-23T17:45:01Z

You can take a look on my approach on the original repo. I basically moved ffmpeg to the libs folder and renamed it to libffmpeg.so (should start with lib and end with .so in order for this to work). Then I added android:extractNativeLibs = "true" to the manifest so the binary is moved into data/app/{package_name}/lib/{arch}/, where it can me executed on Android 10.

There is a problem with this though. You have to put the binaries 4 times in the apk (if you want an apk that supports all architectures). The only way to have the binaries 2 times is to build the apk for arm and x86 only (so it can use the x86 binary on x64 and arm binary for arm64). But then playstore wont let you upload your app because it doesn't have native x64 support.

AamirNaseer1 · 2020-08-05T12:42:32Z

I have updated the Q emulator (now it is [google/sdk_gphone_x86/generic_x86:10/QPP6.190730.005.B1/5775370:userdebug/dev-keys]), and the it does not permit to run ffmpeg from the files directories anymore. Or maybe the trigger is that I set targetSdk=29.

Actually, this is a documented change.

The fix is to move ffmpeg from assets to jniLibs.

how can I move from assets to JNI libs?

iamkdblue · 2020-08-05T12:55:40Z

use this
implementation 'com.arthenica:mobile-ffmpeg-full:4.3.1.LTS'

plazar99 · 2020-08-17T21:15:17Z

use this
implementation 'com.arthenica:mobile-ffmpeg-full:4.3.1.LTS'

I tried this, ffmpeg -version hits onFailure.
do I need to do load library with this version. The 0.3.2 from writingminds required it.

alexcohn · 2020-08-17T21:39:05Z

@plazar99 normally, the library loads its native part by itself. But your mileage may vary.

plazar99 · 2020-08-18T00:01:17Z

I just rebuild it for sdktarget 28, no difference. I'm afraid I'm missing something fundamental here.

plazar99 · 2020-08-18T03:48:48Z

I figured out my mistake. I followed the example provided,

implementation 'com.arthenica:mobile-ffmpeg-full:4.3.1.LTS' <=== do not use this
===> use this implementation 'nl.bravobit:android-ffmpeg:1.1.7'

2.use this => ffmpeg.execute(ffcommand, new FFcommandExecuteResponseHandler() {
dont use the one in the example provided.

This fixed everything.

nivas412 · 2020-08-21T07:52:10Z

You can take a look on my approach on the original repo. I basically moved ffmpeg to the libs folder and renamed it to libffmpeg.so (should start with lib and end with .so in order for this to work). Then I added android:extractNativeLibs = "true" to the manifest so the binary is moved into data/app/{package_name}/lib/{arch}/, where it can me executed on Android 10.

There is a problem with this though. You have to put the binaries 4 times in the apk (if you want an apk that supports all architectures). The only way to have the binaries 2 times is to build the apk for arm and x86 only (so it can use the x86 binary on x64 and arm binary for arm64). But then playstore wont let you upload your app because it doesn't have native x64 support.

How you moved ??

aliraza96 · 2020-08-21T07:55:43Z

I didn't. I just used EpMedia Library. That is totally better than this. It uses FFMPEG at it's backend. But it automatically handles all these cases

…

On Fri, Aug 21, 2020, 12:52 PM Srinivas ***@***.***> wrote: You can take a look on my approach <cropsly/ffmpeg-android-java#361> on the original repo. I basically moved ffmpeg to the libs folder and renamed it to libffmpeg.so (should start with lib and end with .so in order for this to work). Then I added android:extractNativeLibs = "true" to the manifest so the binary is moved into data/app/{package_name}/lib/{arch}/, where it can me executed on Android 10. There is a problem with this though. You have to put the binaries 4 times in the apk (if you want an apk that supports all architectures). The only way to have the binaries 2 times is to build the apk for arm and x86 only <cropsly/ffmpeg-android-java#361 (comment)> (so it can use the x86 binary on x64 and arm binary for arm64). But then playstore wont let you upload your app <https://9to5google.com/wp-content/uploads/sites/4/2019/01/android-app-64-bit-requirement.png> because it doesn't have native x64 support. How you moved ?? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOFC6OFEZPWIQNU5RVH2CA3SBYRTVANCNFSM4IHF5NJQ> .

see bravobit#126

kadnan0900 · 2020-12-02T12:38:24Z

i didn't see any clear fixed please guide me to solve this issue.

alexcohn · 2020-12-02T15:05:37Z

i didn't see any clear fixed please guide me to solve this issue.

See #126 (comment)

plazar99 · 2020-12-02T17:14:50Z

I gave up on this version of ffmpeg, I was able to get it working, but noticed that when running large number of ffmpeg (120) the number of failures were too much. I went back to the older version from writing minds, this gave me zero failures.
I spent too much time on it and my project was due. The build runs with android11 well, I set my target sdk to 28.

kadnan0900 · 2020-12-02T18:18:06Z

@plazar99 but when you upload app on playstore you have to upgrade your tarketsdkversion to 29 thats the major issue.

mans17312 · 2021-12-17T12:48:32Z

Facing this issue, have any one fixed it so far ?

mans17312 · 2021-12-17T12:49:10Z

Here is the issue, only for android 10+ devices
Permission denied
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1050)
at java.lang.Runtime.exec(Runtime.java:699)

SyedSaadUrRehman-MAD · 2022-07-02T08:58:45Z

bravobits-ffmpeg works for on android 12 with target set to 28, no more permission denied froom ffmpeg after i added "-y" in the start of my every ffmpeg-command

darrinps changed the title ~~Permission denied running version command~~ Permission denied running version command when targeting Android Q Jul 26, 2019

alexcohn added a commit to alexcohn/FFmpeg-Android that referenced this issue Aug 11, 2019

let it run on Android Q

777c9b4

see bravobit#126

alexcohn added a commit to alexcohn/FFmpeg-Android that referenced this issue Aug 11, 2019

let it run on Android Q

881e007

see bravobit#126

alexcohn mentioned this issue Aug 11, 2019

use jniLibs to work with targetSdkVersion=29 #130

Open

joshuamking-driveclutch mentioned this issue Nov 21, 2019

android Q run error error=13, Permission denied #140

Open

alexcohn mentioned this issue Feb 4, 2020

No such file or directory on android ffmpeg in api level 28 #141

Open

dzboot02 mentioned this issue Feb 21, 2020

Not working in android Q 10.0 gayanvoice/android-vpn-client-ics-openvpn#7

Closed

alexcohn mentioned this issue Jun 17, 2020

Not working on Android 10 #158

Open

nivas412 mentioned this issue Aug 22, 2020

permission is denied using Android Q ffmpeg": error=13, Permission denied tanersener/react-native-ffmpeg#190

Closed

iradcn pushed a commit to getnexar/FFmpeg-Android that referenced this issue Sep 10, 2020

let it run on Android Q

75befd4

see bravobit#126

Permission denied running version command when targeting Android Q #126

Permission denied running version command when targeting Android Q #126

Comments

darrinps commented Jul 26, 2019 • edited Loading

darrinps commented Jul 26, 2019 • edited Loading

alexcohn commented Aug 7, 2019 • edited Loading

alexcohn commented Aug 11, 2019 • edited Loading

desaibijal commented Dec 23, 2019

kartik1225 commented Dec 27, 2019

kazemihabib commented Dec 27, 2019

kartik1225 commented Dec 27, 2019 • edited Loading

WassimErriha commented Jan 9, 2020

PO15ON commented Feb 15, 2020

Aditya94A commented Feb 27, 2020

Le-Dinh-Nam commented Mar 8, 2020 • edited Loading

AmioLee commented Mar 12, 2020

alexcohn commented Mar 12, 2020

vincent-paing commented Apr 8, 2020

pratikbutani commented May 5, 2020

kibotu commented May 5, 2020

pratikbutani commented May 6, 2020

SnehaDZ commented May 11, 2020

aliraza96 commented May 12, 2020

alexcohn commented May 12, 2020

Ahmed-Basalib10 commented Jul 18, 2020

kdsrsl commented Jul 20, 2020

iamkdblue commented Jul 22, 2020

vincent-paing commented Jul 22, 2020

1nikolas commented Jul 23, 2020 • edited Loading

AamirNaseer1 commented Aug 5, 2020

iamkdblue commented Aug 5, 2020

plazar99 commented Aug 17, 2020

alexcohn commented Aug 17, 2020

plazar99 commented Aug 18, 2020

plazar99 commented Aug 18, 2020

nivas412 commented Aug 21, 2020

aliraza96 commented Aug 21, 2020 via email

kadnan0900 commented Dec 2, 2020 • edited Loading

alexcohn commented Dec 2, 2020

plazar99 commented Dec 2, 2020

kadnan0900 commented Dec 2, 2020

mans17312 commented Dec 17, 2021

mans17312 commented Dec 17, 2021

SyedSaadUrRehman-MAD commented Jul 2, 2022

darrinps commented Jul 26, 2019 •

edited

Loading

darrinps commented Jul 26, 2019 •

edited

Loading

alexcohn commented Aug 7, 2019 •

edited

Loading

alexcohn commented Aug 11, 2019 •

edited

Loading

kartik1225 commented Dec 27, 2019 •

edited

Loading

Le-Dinh-Nam commented Mar 8, 2020 •

edited

Loading

1nikolas commented Jul 23, 2020 •

edited

Loading

kadnan0900 commented Dec 2, 2020 •

edited

Loading