[Bug]: Termux startup scripts and crond behavior issues on Android 13

[wingfieldmitchell84-eng]

Problem description

I’m encountering multiple issues when using Termux on an Android 13 device:

1. Startup scripts (~/.termux/boot.sh) sometimes do not execute as expected.
2. crond requires manual starting with crond -P each session; the -b option is not recognized.
3. Temporary crontab edits often truncate lines or fail to save, especially when editing multiple commands.
4. fetch-and-clean scripts work manually but sometimes fail when scheduled via crontab, producing errors like:
   • "ls: cannot access '/data/data/home/termux_work/downloads/example_*.html': No such file or directory"
   • "mv: missing destination file operand"
5. Termux behavior differs between sessions, even with identical scripts and crontab entries.

This seems related to Android 13 permissions, startup behavior, or PATH/environment inconsistencies.

Logs:

• [Please attach any available logs or error messages from logcat or your scripts.]

Steps to reproduce the behavior.

• Verified crontab entries and ran scripts manually — they work.
• Created ~/.termux/boot.sh and made it executable.
• Started crond manually with crond -P.
• Ensured directories exist (~/termux_work/{downloads,logs,scripts}) and scripts have execute permissions.
• Observed errors when scripts are invoked automatically on boot or via crontab.

What is the expected behavior?

Scripts and crond should start automatically on Termux launch, scheduled commands should run without truncation, and logs should record all activity.

System information

• Termux application version: [current version]
• Android OS version: 13
• Device model: [your device model]

[sylirre]

Show your crontab and scripts that fail.

High chance of user error here.

Termux behavior differs between sessions, even with identical scripts and crontab entries.

Never experienced this.

Termux application version: [current version]

Provide information about what Termux version you use.