What should I do if the OpenClaw mobile node tool fails?

If the OpenClaw mobile phone node has been paired but the camera, Canvas, screen, and exec tools fail, first check whether the node is online, whether the capability exists, and whether the system permission is granted. Successful pairing only means that nodes can connect, not every tool has permissions.

Troubleshooting order

1. openclaw status and openclaw gateway status confirm that the gateway is OK.
2. openclaw nodes status See if the node is online.
3. openclaw nodes describe --node <idOrNameOrIp> See the list of competencies.
4. openclaw logs --follow Investigate the specific reasons for refusal.

Common mistakes

• NODE_BACKGROUND_UNAVAILABLE: Switch the Node App to the foreground.
• *_PERMISSION_REQUIRED: The system camera, microphone, screen, etc. are not given.
• SYSTEM_RUN_DENIED: approval required: The exec operation of the node host is waiting for approval.
• allowlist miss: The command is not on the allow list.

Mobile nodes are suitable for taking photos, voice, Canvas, and device-side operations, but don't treat your phone as an unlimited remote terminal. Commands that can be completed in the Gateway are prioritized in the Gateway. If you have to do it on your phone, you can open the node permission separately.

Official open source address: https://github.com/openclaw/openclaw.

If the permission is still failed, restart the node App and Gateway to test again. Mobile systems often require apps to re-enter the foreground before they can actually refresh their permission state, especially camera, microphone, and screen-related capabilities.