We're here.
No bots.

Open FOS Terminal → tap + to add a host → enter hostname, port (default 22), username → choose authentication (password or key) → tap Connect.

To use SSH keys: go to Settings → SSH Keys → Import, or tap "Generate new key." Then select the key in host settings → Authentication → Private key.

1. Switch to Mosh. Mosh is UDP-based and survives IP changes, WiFi↔mobile transitions, and spotty connections. Install mosh-server on your server (apt install mosh) and enable Mosh in host settings.

2. Enable keep-alive. Host settings → Advanced → Keep-alive interval. Set to 30–60 seconds to prevent server-side idle timeouts.

3. Check auto-reconnect. FOS Terminal auto-reconnects by default. If it doesn't, check Settings → Connection → Auto-reconnect.

Option A — File transfer: Connect your phone via USB, copy the key file to the phone, then open FOS Terminal → Settings → SSH Keys → Import → select the file.

Option B — Paste PEM: Settings → SSH Keys → Import → Paste PEM content → paste from clipboard.

Option C — SSH config import: If you have a ~/.ssh/config file, import it at Hosts → Import → SSH Config. The app resolves IdentityFile paths automatically.

Setup: Edit the target host → Advanced → Jump host → select the bastion host. The bastion host must be a separate saved host entry.

SSH agent forwarding: Enable SSH agent forwarding in host settings so the bastion can use your key to reach the target server.

Key access: Both the bastion and target server need to have your public key in ~/.ssh/authorized_keys.

Edit the host → Port Forwarding → add a rule (local, remote, or dynamic). The forwarding is active only while the SSH session is open in the background.

Local forwarding: binds a local port on your phone to a remote address (e.g., localhost:5432 → db.internal:5432).
Dynamic (SOCKS5): turns your phone into a SOCKS5 proxy through the SSH tunnel.

This is a server-side permission issue, not a bug. Your SSH user doesn't have access to the requested directory. Options:

1. Browse a directory your user owns (e.g., /home/youruser/)
2. Use a user with broader permissions
3. Use sudo or an SFTP chroot configuration on the server

With cloud sync (Pro): Sign in with the same Google account on the new device. Hosts, themes, and snippets sync automatically. SSH keys must be re-imported manually — they never leave the device.

Without cloud sync: On the old device — Settings → Backup → Export. This creates an encrypted JSON file. On the new device — Settings → Backup → Import. Then re-import SSH keys from your secure backup location.

All subscriptions are managed through Google Play. Go to Google Play → tap your profile picture → Payments & subscriptions → Subscriptions → FOS Terminal Pro. From there you can cancel, pause, or change your plan. You keep Pro access until the end of the current billing period.

1. Open Settings → Diagnostics → Crash reports to see recent crash logs.
2. Check you're running the latest version (FOS Terminal updates automatically via Google Play).
3. If the crash repeats, email us the crash report from Settings → Diagnostics → Share crash report. This helps us fix it immediately.

Android version, device model, and steps to reproduce are also very helpful.