Document daemonizing-command gotcha and exited-state UI in README
This commit is contained in:
@@ -48,6 +48,16 @@ file manager (allow "install from unknown sources" if asked).
|
||||
```
|
||||
The default, `sleep 180`, is just a harmless placeholder for testing
|
||||
that the app itself works before wiring up your real command.
|
||||
|
||||
**If your command daemonizes/detaches** (`tmux new-session -d`,
|
||||
`screen -d`, `nohup ... &`, etc.), the app sees the *launching*
|
||||
command exit successfully the moment the detached thing is created —
|
||||
not when the real workload actually ends — and will show the
|
||||
"process exited" screen (see below) even though your daemon is still
|
||||
running fine. Make the command wait on the real thing instead, e.g.:
|
||||
```
|
||||
su -c '... -- sh -c "tmux new-session -d ...; while tmux has-session 2>/dev/null; do sleep 5; done"'
|
||||
```
|
||||
3. Tap **Save**.
|
||||
4. (Recommended) In Android's own Settings → Apps → Slocker Launcher →
|
||||
Battery, turn off any "put app to sleep" / battery optimization for
|
||||
@@ -66,6 +76,11 @@ file manager (allow "install from unknown sources" if asked).
|
||||
running in the background. There's no way back to the menu from here
|
||||
by design — this mode is meant to run unattended. To change settings
|
||||
again, close/reopen the app (or reboot).
|
||||
- If your command exits (crashes, finishes, or never started), the screen
|
||||
stays black and on, but a small message + Exit button appear at a
|
||||
random position, moving to a new random spot every minute — so a device
|
||||
left unattended in this state for a long time doesn't develop burn-in
|
||||
from a static message. Tap Exit to close the app.
|
||||
- Output (and any startup errors) from your command is logged to a file
|
||||
inside the app's own storage, useful if something didn't start the way
|
||||
you expected. Pull it with:
|
||||
|
||||
Reference in New Issue
Block a user