Device Connection

Hook an emulator or phone into the online editor — USB cable · same Wi-Fi wireless connection

Quick Nav

Emulator Connection (ADB Port Forwarding)

For Android emulators such as LDPlayer, MEmu and MuMu — use the ADB tool on your PC to hook the emulator into the online editor.

Prerequisites

Step 1: Confirm the device is connected

Run this command in a terminal or command prompt:

adb devices

Seeing the emulator in the device list means your PC has recognized it:

List of devices attached
emulator-5554 device

Step 2: Port forwarding

Run these commands to bridge your PC and the emulator so the editor can reach it:

adb forward tcp:8080 tcp:8080
adb forward tcp:8081 tcp:8081
Some emulators use a different default ADB port — check that emulator's docs. Once connected, running adb forward tcp:8080 tcp:8080 and adb forward tcp:8081 tcp:8081 is all you need.

Step 3: Connect in the editor

  1. Open the online editor
  2. Enter 127.0.0.1 in the address field
  3. Click connect to start remote editing and debugging
If the connection fails, check that the Remote Development switch is on in AutoLua's settings.

Emulator Wireless Connection (Bridge Mode)

Give the emulator its own network address like a real phone, so you can connect by IP directly — no commands needed.

When to use

Step 1: Turn on bridge mode in the emulator

  1. Open the emulator's Settings or Network Settings
  2. Switch the network mode to Bridge Mode
  3. Select your PC's wireless adapter (e.g. Intel Wireless-AC)
  4. Save and restart the emulator
After bridging, the emulator joins the same Wi-Fi as your PC and gets its own IP address.

Step 2: Find the emulator's IP

After the emulator restarts, go to Settings → WLAN or Network Info inside it to see the IP:

192.168.x.x

Make sure this IP shares the same first three groups as your PC (e.g. both 192.168.x.x), meaning they're on the same network.

Step 3: Connect in the editor

  1. Open the online editor
  2. Enter the emulator's bridge IP, e.g. 192.168.1.10
  3. Click connect

Can't connect?

Run ping in your PC terminal to check whether the PC and emulator can reach each other:

ping 192.168.x.x

Phone Wireless Connection (LAN)

With the phone and PC on the same Wi-Fi, connect straight by the phone's IP — no USB cable needed.

Step 1: Find the phone's IP

On the phone, go to Settings → WLAN → current Wi-Fi details to see the IP, usually like:

192.168.x.x

Step 2: Turn on Remote Development

Open AutoLua on the phone, go to Settings, and turn on the Remote Development switch. The phone will then wait for the PC to connect.

Step 3: Connect in the editor

  1. Open the online editor in your PC browser
  2. Enter the phone's IP address in the form 192.168.x.x
  3. Click connect
Make sure the phone and PC are on the same Wi-Fi. Some office or campus networks block devices from talking to each other — in that case, turn on the phone's hotspot and connect the PC to it, then try again.

WSS Connection

When the editor reports WSS connection failed (e.g. "WSS connection failed, please open … click Advanced → Proceed → go back to the editor and refresh"), follow the steps below.

Why it fails

The online editor is a secure (HTTPS) page. For safety, the browser blocks the device connection by default. Just allow it once in the browser using the steps below, and it will connect normally afterward.

Step 1: Open the device's address

Open the device's address in a new browser tab (same IP you use in the editor, port 8081):

https://192.168.x.x:8081

The page will warn "Your connection is not private / not secure" — this is normal, don't worry.

Step 2: Click Proceed

Click AdvancedProceed to <IP> (unsafe) on the page.

Wording varies slightly by browser; in Edge / Chrome it's "Advanced → Proceed".

Step 3: Confirm it's allowed

If the page shows this line of text:

404 WebSocket Upgrade Failure
Seeing 404 WebSocket Upgrade Failure means it's allowed. This is not an error — it means the device can now connect normally.

Step 4: Go back and reconnect

  1. Return to the online editor
  2. Refresh the page
  3. Re-enter the device IP and click connect

Alternative: download the local editor

If you'd rather skip the allow step, download the editor and run it locally — no blocking prompt, just open and connect:

Download local editor

Troubleshooting

Connection failed

adb devices shows no device

← Back to editor guide