I'm running the Gforth 0.7.9_20251001 app on Android 16 smartphone.
A few months ago, Bernd helped me here to get around Android's golden
caging by creating a directory under /storage/emulated/0/Download for
copying files in and out of the Gforth app, and adding that directory
to fpath.
That worked well at that time, but yesterday I copied a new file into
that shared directory (/storage/emulated/0/Download/gforth on my
phone) and Gforth cannot find the file with either include or 'sh
ls', even though files I copied into the directory months ago still
show up as expected.
Permissions on all the files in the directory, old and new, is 660 (read+wrote for owner and group). I tried changing perms to 666 (add
world read+write), but it had no effect, and permissions were reset to
660 after I restarted the phone.
Any idea what's going on with the new file?
On Sat, 30 May 2026 10:57:36 +0900
David Meyer <[email protected]> wrote:
Android/Linux, I seem to remember, silently re-mounts the disk
read-only.
Any idea what's going on with the new file?
Am Sat, 30 May 2026 10:57:36 +0900 schrieb David Meyer:
Any idea what's going on with the new file?
I recently updated Android, too, and can reproduce this. I suppose
Google tightened the screws again.
Checking for possible workarounds: If Gforth creates the file, it can see and read it even when the file manager edited it. So you might want to define a "touch" command that allows you to quickly create files there,
and then overwrite/edit them with the file browser.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,123 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 37:20:56 |
| Calls: | 14,371 |
| Files: | 186,380 |
| D/L today: |
3,549 files (995M bytes) |
| Messages: | 2,540,672 |