Update Android port

* doc/emacs/android.texi (Android): Add new node to menu.
(Android Environment): Add footnote pointing to new node.
(Android Software): New node.
* doc/emacs/emacs.texi (Top): Add new node to menu.
* java/AndroidManifest.xml.in (manifest): Fix location of
sharedUserId property.
* java/INSTALL: Improve documentation of shared user ID
support.

2 files changed, 15 insertions, 5 deletions

diff --git a/java/AndroidManifest.xml.in b/java/AndroidManifest.xml.in
index 3aae2032fff..895e7f88c57 100644
--- a/java/AndroidManifest.xml.in
+++ b/java/AndroidManifest.xml.in
@@ -25,6 +25,8 @@ along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>. -->
           android:targetSandboxVersion="1"
           android:installLocation="auto"
           android:requestLegacyExternalStorage="true"
+          @ANDROID_SHARED_USER_ID@
+          @ANDROID_SHARED_USER_NAME@
           android:versionCode="@emacs_major_version@"
           android:versionName="@version@">
 
@@ -74,8 +76,7 @@ along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>. -->
                android:supportsRtl="true"
                android:theme="@style/EmacsStyle"
                android:debuggable="@ANDROID_DEBUGGABLE@"
-               @ANDROID_SHARED_USER_ID@
-               @ANDROID_SHARED_USER_NAME@
+               android:allowBackup="true"
                android:extractNativeLibs="true">
 
     <activity android:name="org.gnu.emacs.EmacsActivity"
diff --git a/java/INSTALL b/java/INSTALL
index 63b99272004..0646db426e0 100644
--- a/java/INSTALL
+++ b/java/INSTALL
@@ -161,15 +161,24 @@ to provide both debug and release versions.
 BUILDING WITH A SHARED USER ID
 
 Sometimes it may be desirable to build Emacs so that it is able to
-access executables from another program.  To achieve this, that other
-program must have a ``shared user ID'', and be signed with the same
-signing key used to sign Emacs (normally `emacs.keystore'.)
+access executables and application data from another program.  To
+achieve this, that other program must have a ``shared user ID'', and
+be signed with the same signing key used to sign Emacs (normally
+`emacs.keystore'.)
 
 Once you have both that signing key and its ``shared user ID'', you
 can give it to configure:
 
     ./configure --with-shared-user-id=MY.SHARED.USER.ID
 
+For instance,
+
+    ./configure --with-shared-user-id=com.termux
+
+will result in Termux (https://termux.dev)'s application data being
+accessible to Emacs, within its own application data directory located
+at `/data/data/com.termux/files'.
+
 Don't do this if you already have Emacs installed with a different
 shared user ID, as the system does not allow programs to change their
 user IDs after being installed.