The Android flow shown in the video is not the mainline OpenClaw deployment path. If you are testing it anyway, the safest written version is to treat the phone as a constrained Linux shell, keep the install simple, and avoid assuming desktop-grade stability.
Quick answer
Use the Android shell only for lightweight testing. Install Node, install the OpenClaw CLI, run onboarding, and stop as soon as the gateway or model path becomes unreliable.
Command line steps
1. Prepare the shell environment
If you are using Termux or a similar Linux environment on Android, start by making the shell usable before you touch OpenClaw.
2. Install the OpenClaw CLI and run onboarding
Keep the install path as close as possible to the Linux flow so troubleshooting stays predictable.
3. Verify the gateway and keep the model plan small
Phones are resource-constrained. Confirm the basics before you try heavy channel or automation setups.
What to check if it still fails
- If Node packages or native dependencies fail, move the test to a laptop or VPS. Android is not the main supported target.
- If the phone kills the process in the background, do not treat that as an OpenClaw config bug first.
- If you need a reliable always-on setup, use a VM or server and keep Telegram or the dashboard as the remote client.