Subject: Re: bug#61385: 30.0.50; android eshell cannot executable file under ~/ directory

From: xiliuya <[email-masked]>
Date: Fri, 10 Feb 2023 20:49:58 +0800

Po Lu <[email-masked]> writes:

> xiliuya <[email-masked]> writes:
>
>> Po Lu <[email-masked]> writes:
>>
>>> xiliuya <[email-masked]> writes:
>>>
>>>> --text follows this line--
>>>>
>>>> My operation is as follows:
>>>> 1. cp /system/bin/sh .
>>>> 2. chmod 755 sh
>>>> 3. ./sh
>>>> 4. libandroid-emacs.so: /data/data/org.gnu.emacs/files/sh: Permission
>>>> denied
>>>
>>> This is described under (emacs)Android Environment.  On Android, system
>>> security policy prevents launching executables from read-write
>>> directories.
>>>
>>> Free versions of Android allow you to obtain access as the super user.
>>> In that case, run:
>>>
>>>   C-x C-f /su:/data/data/org.gnu.emacs/files RET
>>>
>>> and run the binary as the super user instead.
>>
>> I see. I found another alternative is to modify AndroidManifest.xml:
>>
>> 	-    android:targetSdkVersion="33"/>
>>         +    android:targetSdkVersion="28"/>
>
> The Android developers say they will progressively block applications
> targeting older SDK versions from being installed, so that is not a real
> long-term option.

Yes, that only solves a small part of the problem.
Super users are more convenient.

-- 
xiliuya :)