#I have an issue with adb connect 127.0.0.1:5555

1 messages · Page 1 of 1 (latest)

finite runeBOT
#

There are two separate things here:

1) ADB → BlueStacks is only for installing/debugging the Android app.
In BlueStacks: Settings → Advanced → enable “Android Debug Bridge” → Save changes. Then on your PC:

adb kill-server
adb start-server
adb connect 127.0.0.1:5555
adb devices

BlueStacks documents the ADB toggle under Settings → Advanced, and Android’s adb docs use 5555 as the first emulator adb port. (support.bluestacks.com)

2) OpenClaw Android node → OpenClaw Gateway does not use adb connect.
Once the Android app is running, connect it from the app’s Connect tab using a setup code:

# 
openclaw qr --setup-code-only
openclaw devices list
openclaw devices approve <requestId>
openclaw nodes status

Docs: https://docs.openclaw.ai/platforms/android and https://docs.openclaw.ai/cli/qr

Also: please paste your openclaw --version and the exact error from adb connect 127.0.0.1:5555. If it says connection refused, BlueStacks either doesn’t have ADB enabled, isn’t running, or that instance is using a different port.

empty radish
#

I am using vs code not open claw

finite runeBOT
#

Ah got it — then ignore the OpenClaw parts.

For VS Code + BlueStacks, connect through ADB from the VS Code terminal:

  1. In BlueStacks: Settings → Advanced → enable Android Debug Bridge (ADB). (support.bluestacks.com)
  2. In VS Code terminal:
adb kill-server
adb start-server
adb connect 127.0.0.1:5555
adb devices

If 5555 fails, check the ADB port shown in BlueStacks Advanced settings and use that instead: