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
- ADB installed on your PC (a small tool that lets your computer talk to Android devices). Download platform-tools from the Android website
- AutoLua installed and open on the device, with the Remote Development switch turned on in Settings
Step 1: Confirm the device is connected
Run this command in a terminal or command prompt:
Seeing the emulator in the device list means your PC has recognized it:
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:8081 tcp:8081
adb forward tcp:8080 tcp:8080 and adb forward tcp:8081 tcp:8081 is all you need.Step 3: Connect in the editor
- Open the online editor
- Enter
127.0.0.1in the address field - Click connect to start remote editing and debugging
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
- Emulators that support network bridging, such as LDPlayer, MEmu and MuMu
- When you want the emulator to connect over the LAN by IP, just like a real device
Step 1: Turn on bridge mode in the emulator
- Open the emulator's Settings or Network Settings
- Switch the network mode to Bridge Mode
- Select your PC's wireless adapter (e.g. Intel Wireless-AC)
- Save and restart the emulator
Step 2: Find the emulator's IP
After the emulator restarts, go to Settings → WLAN or Network Info inside it to see the IP:
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
- Open the online editor
- Enter the emulator's bridge IP, e.g.
192.168.1.10 - Click connect
Can't connect?
Run ping in your PC terminal to check whether the PC and emulator can reach each other:
- Pings but won't connect → check that AutoLua's Remote Development switch is on
- No ping reply → they're not on the same network; check that bridge mode picked the right wireless adapter, or use the ADB method above
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:
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
- Open the online editor in your PC browser
- Enter the phone's IP address in the form
192.168.x.x - Click connect
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
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):
The page will warn "Your connection is not private / not secure" — this is normal, don't worry.
Step 2: Click Proceed
Click Advanced → Proceed to <IP> (unsafe) on the page.
Step 3: Confirm it's allowed
If the page shows this line of text:
Step 4: Go back and reconnect
- Return to the online editor
- Refresh the page
- 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 editorTroubleshooting
Connection failed
- Check the IP is correct (use
127.0.0.1for the ADB method; the real IP for bridge mode / phone) - Timeout, refused or failed → run
ping the-IPin your PC terminal to test whether the two devices can reach each other - No ping reply → they're not on the same network; check the bridge adapter selection and that your PC is on Wi-Fi
- Pings but won't connect → check AutoLua's Remote Development switch is on
- Page reports WSS connection failed → allow the device connection in the browser first, see WSS Connection
adb devices shows no device
- Some emulators require enabling ADB debugging manually (LDPlayer: Settings → Other → ADB Debugging → enable local connection)
- Some emulators need a manual ADB connect — check their docs for the port number