[Bug]: Gateway fails to start on Android/proot when libuv cannot enumerate network interfaces

[hastagaming]

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

• Device: Android
• Running inside proot
• os.networkInterfaces() patched successfully
• NODE_OPTIONS=--require /root/.openclaw-patch.js is loaded
• node -e "console.log(require('os').networkInterfaces())" works correctly
• But openclaw gateway run still exits immediately.
• This suggests the failure is happening below Node's os.networkInterfaces(), possibly in libuv (uv_interface_addresses()) or another native network interface check.
• It would be helpful if gateway could gracefully fall back to loopback instead of exiting.

Steps to reproduce

1. Install AnyClaw on Android.
2. Complete the runtime setup.
3. Start the Gateway from AnyClaw.
4. Observe that the gateway exits immediately instead of staying running.

Expected behavior

The gateway should start successfully and remain running after launching from AnyClaw.

Actual behavior

The gateway exits immediately after launch.

Investigation shows that:

• NODE_OPTIONS is applied.
• /root/.openclaw-patch.js is loaded.
• os.networkInterfaces() is successfully patched.

Despite this, the gateway still terminates.

OpenClaw version

2026.2.10 (bundled with AnyClaw)

Operating system

Android 15 (proot environment)

Install method

AnyClaw (Android)

Model

openai/gpt-4.1

Provider / routing chain

OpenAI

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

I inspected the APK and found that AnyClaw bundles OpenClaw 2026.2.10.

The application injects:

export NODE_OPTIONS='--require /root/.openclaw-patch.js'

before executing:

openclaw gateway run --port ...

I also confirmed that the runtime patch is loaded successfully and that os.networkInterfaces() returns valid data.

This suggests the remaining failure may occur below the JavaScript layer (for example libuv or another native network interface check), or it may already be fixed in newer OpenClaw releases.