Android app is paired, but operator is offline

[drifting mural]

I recently installed the OpenClaw android app from the play store on my pixel 8a and after successful QR code scan and permission setup, the app fail to connect.

Running openclaw nodes status shows pixed8 is paired and connected. And i can successfully fetch my GPS position from discord, but the app is not able to completed the connection flow

[mighty plank]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[midnight tree]

Let me check the current docs layout and the Android pairing flow notes, then I’ll give you the shortest path to isolate it.

That pattern usually means the node paired, but the app’s operator session did not.

That fits your symptoms really well:

• openclaw nodes status shows the phone connected
• GPS works from Discord, so the node side is alive
• but the app still can’t finish because the operator side is offline

First check these on the gateway host:

openclaw --version
openclaw devices list

If you see a pending request for the phone, approve it:

openclaw devices approve <requestId>

Then keep the Android Connect screen open for a moment, it should auto-retry.

If it still doesn’t complete, please paste:

openclaw --version
openclaw qr --json
openclaw devices list
openclaw nodes status

and also the exact status text shown in the app, especially if it says something like Connected (operator offline).

Relevant docs:

• https://docs.openclaw.ai/platforms/android
• https://docs.openclaw.ai/gateway/pairing
• https://docs.openclaw.ai/help/faq

I’m fairly confident this is a second pairing/auth step for the operator side, not a node connectivity problem.

[drifting mural]

OpenClaw 2026.4.15 (041266a)
{
"setupCode": "eyJ......dQcyJ9",
"gatewayUrl": "ws://192.168.100.100:18789",
"auth": "token",
"urlSource": "gateway.bind=lan"
}

🦞 OpenClaw 2026.4.15 (041266a) — I don't have opinions about tabs vs spaces. I have opinions about everything else.

│
◇
Paired (3)

│ Device │ Roles │ Scopes │ Tokens │ IP │

│ Pixel 8a │ node, │ operator.approvals, operator.read, operator.talk.secrets, operator.write │ node, │ 192.168.100.173 │
│ │ operator │ │ operator │ │
│ e545ffe....82104cf2 │ operator │ operator.admin, operator.approvals, operator.pairing, operator.read, operator.write │ operator │ │
│ bc0273ca9138184a821 │ │ │ │ │
│ 6d80d118.....05c9 │ operator │ operator.admin, operator.approvals, operator.pairing, operator.read, operator.write, │ operator │ │
│ 5afed60ff4f3dd1f915 │ │ operator.talk.secrets │ │ │

🦞 OpenClaw 2026.4.15 (041266a) — It's not "failing," it's "discovering new ways to configure the same thing wrong."

│
◇
Known: 1 · Paired: 1 · Connected: 0
┐
│ Node │ ID │ IP │ Detail
│ Pixel 8a │ d8...26960e033f696419 │ 192.168.100.173 │ client: openclaw-android/node │ paired · disconnected │ │

[midnight tree]

I’ve got enough signal now, let me check one more thing in the Android docs/code: what makes a paired phone show up as paired · disconnected even after onboarding.

Nice, this rules out my first guess.

Your phone is already paired correctly:

• devices list shows Pixel 8a with node + operator
• nodes status shows paired, but currently disconnected

So this is not an approval problem anymore. It’s now a runtime connection problem on the Android side.

Also, your route looks valid:

• ws://192.168.100.100:18789
• urlSource: gateway.bind=lan

That is fine for same-LAN Android, so I don’t think this is a Tailscale/TLS issue.

What I’d check next:

1. Do you see the persistent OpenClaw Node notification on the phone after tapping Connect?

If not, the foreground service probably is not staying alive, which would explain paired · disconnected.

2. On the gateway host, run:

   openclaw logs --follow
   

   Then, on the phone, tap Connect Gateway again and paste the lines that appear around the connect attempt.

3. Please also paste the exact status text shown in the app.
   Especially if it says something like:

   • Connected (operator offline)
   • Gateway error: ...
   • pairing required
   • missing scope: ...

One extra easy try: generate a fresh QR/setup code and rescan once. If the app kept a stale auth token, a fresh scan can clear that up.

Docs:

• https://docs.openclaw.ai/platforms/android
• https://docs.openclaw.ai/help/faq

At this point, the host log during a fresh connect attempt is the fastest way to catch it.

[shell trellis]

@drifting mural Any luck with this? Having the same exact issue. My bot has not been able to figure it out

[midnight tree]

Not fully solved yet, but the current theory is: pairing succeeds, then the Android app fails to keep the live gateway connection up.

For the other report, the useful signals were:

• device shows up in devices list
• sometimes even has both node + operator
• but nodes status ends up paired · disconnected
• app onboarding never finishes

If you want, post these too:

openclaw --version
openclaw qr --json
openclaw devices list
openclaw nodes status

And two app-side details:

1. the exact status text shown in the Android app
2. whether you see the persistent “OpenClaw Node” notification after tapping Connect

Best extra check on the host:

openclaw logs --follow

Then tap Connect Gateway in the app and paste the connect/auth lines that appear.

If both of you are hitting the same thing on the same version, I’m starting to suspect a real Android app bug rather than bad setup.

[drifting mural]

No luck. I'm still stuck. Any help is welcome

[midnight tree]

Let me dig a bit deeper in the Android app code. If there’s a real bug here, I’d rather give you something concrete than keep you in log purgatory.

I dug into the Android source a bit, and I’m pretty suspicious this is a real Android app bug, not just bad setup.

Why I’m saying that:

• the app only finishes onboarding when both are true:
  • operator session connected
  • node session connected
• your earlier output already showed the phone paired
• so if onboarding still won’t finish, it’s likely the app is getting stuck in the operator/live-connection path

A few concrete things to try/check:

1. Update first if Play Store offers anything newer than 2026.4.15.

2. On the gateway host, run:

   openclaw logs --follow
   

Then tap Connect Gateway in the app and paste the lines from that attempt.

3. Also paste:

   openclaw --version
   openclaw devices list
   openclaw nodes status
   

4. From the phone, tell us:

   • the exact status text in the app
   • whether the persistent “OpenClaw Node” notification appears

Quick hint for interpreting logs:

• AUTH_TOKEN_MISMATCH → generate a fresh QR/setup code and rescan
• PAIRING_REQUIRED → run openclaw devices list and approve the pending request
• missing scope: ... → paste it, that’s actionable