{
  "displayName": "Giovanni's S25 Ultra",
  "platform": "android",
  "version": "2026.5.25",
  "clientId": "openclaw-android",
  "clientMode": "node",
  "caps": [],
  "commands": [],
  "connected": true
}


### Steps to reproduce

## Reproduction
1. Generate setup code with `/pair`
2. Pair Android app to Gateway
3. Approve pairing
4. Open voice / Talk in Android app
5. Try speaking


### Expected behavior

## Expected behavior
After pairing, the Android node should:
- expose Talk-related capabilities/commands
- work with voice/Talk from the app
- not fall into broken Talk session lifecycle immediately after session creation

### Actual behavior

## Actual behavior
Pairing succeeds and node connects, but:
- node exposes no capabilities/commands
- Talk/voice does not work
- logs show Talk session creation followed by immediate failure

### OpenClaw version

2026.6.1

### Operating system

Ubuntu 24.04

### Install method

npm

### Model

openai-codex

### Provider / routing chain

openai-codex

### Additional provider/model setup details

Additional notes

• This is not just stale pairing state: the issue reproduced after multiple fresh pairings and a clean reinstall.
• Browser access to the Gateway via HTTPS/WSS works.
• Docs suggest Android Talk should normally use native/local speech flow unless explicit realtime relay config is set, but behavior here appears to go through a broken Talk session path.
• I did not find an obvious Gateway config issue that would explain the Android node exposing caps: [] / commands: [].

Question

Could this be:

1. a known Android client bug in 2026.5.25,
2. a mismatch between Android app build and Gateway 2026.6.1, or
3. an issue where Android node capability registration fails even though pairing/connect succeeds?

### Logs, screenshots, and evidence

```shell
Relevant logs

Pairing succeeds, node connects as v2026.5.25 and without capabilities.

Examples from Gateway logs:

[ws] ... client=Giovanni's S25 Ultra node v2026.5.25 ...

[ws] ⇄ res ✓ talk.session.create ...
[ws] ⇄ res ✗ talk.session.appendAudio ... errorMessage=Error: Unknown Talk session

[ws] ⇄ res ✓ talk.session.create ...
[ws] ⇄ res ✗ talk.session.close ... errorMessage=Error: Unknown transcription Talk session

Also, Talk sessions appear to be closed almost immediately after creation.