[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog-post-en-connect-phoma-android-wifi-wireless-adb-debugging":3},{"slug":4,"lang":5,"title":6,"summary":7,"date":8,"tags":9,"tag_slugs":14,"thumbnail_url":15,"translations":16,"body":17,"asset_base":18},"connect-phoma-android-wifi-wireless-adb-debugging","en","Connect Phoma to Android Over Wi-Fi Using Wireless ADB Debugging","Pair and connect Android phones to Phoma over Wi-Fi with wireless ADB debugging, plus fix common connection issues on Windows.","2026-11-07",[10,11,12,13],"android","adb","wi-fi","troubleshooting",[10,11,12,13],"https://blog-api.phomaapp.com/api/blog/posts/connect-phoma-android-wifi-wireless-adb-debugging/thumbnail.svg?lang=en",[5],"Running the same checks on Android phones every day means plugging and unplugging USB cables all the time. If your test phones sit on a charging rack or move around a warehouse, a Wi-Fi connection to Phoma keeps them ready without touching a cable. This guide shows how to pair an Android phone with Phoma over Wi-Fi using wireless ADB debugging, what to do when a phone will not connect, and how to keep the link stable day to day.\n\nPhoma runs flows on your own Windows PC and phones. It does not have a public API, SDK, or CLI, so device setup happens in the Phoma app. The adb commands below are only for preparing the phone with Android platform tools; you still add and run the phone from Phoma.\n\n## What You Need Before You Start\n\n- A Windows PC with Phoma installed\n- An Android phone on the same Wi-Fi network as the PC\n- A USB cable for the first pairing, recommended for all Android versions\n- Developer options enabled on the phone\n- The phone screen unlocked during setup\n\n## Step 1: Enable Developer Options and Wireless Debugging\n\nOn the phone, open Settings and tap About phone. Tap Build number seven times until you see a message that developer mode is on. Back out to System, then tap Developer options.\n\nTurn on these settings:\n\n- USB debugging\n- Wireless debugging, available on Android 11 and later\n\nIf your phone runs Android 10 or earlier, you can still use Wi-Fi debugging, but you must start with a USB cable and the adb tcpip command described in Step 2.\n\nWhen USB debugging is on and you plug the phone into Windows, tap Allow on the phone when the RSA authorization prompt appears. Check Always allow for this computer if you trust the PC.\n\n## Step 2: Put the Phone in Wireless Debug Mode\n\nFor Android 11 and newer, open Developer options and tap Wireless debugging. Tap Pair device with pairing code. The phone shows an IP address, a port, and a six-digit pairing code. Keep this screen open.\n\nFor older Android versions, connect the phone by USB once. Open a command prompt on the PC where Android platform tools are installed and run:\n\n```text\nadb tcpip 5555\n```\n\nThen unplug the USB cable. Find the phone's Wi-Fi IP address in Settings under Network and internet or About phone, and run:\n\n```text\nadb connect 192.168.1.42:5555\n```\n\nReplace 192.168.1.42 with your phone's actual IP address. If the command says connected, the phone is listening for wireless adb on port 5555.\n\nThese are Android platform tools, not Phoma commands.\n\n## Step 3: Add the Phone to Phoma Over Wi-Fi\n\nOpen Phoma on your Windows PC. Go to the Devices page and click Add device. Choose Wi-Fi or wireless debugging, depending on the option shown in your Phoma version.\n\nEnter the phone's IP address and port from Step 2. For Android 11 and later, Phoma may also ask for the pairing code shown on the phone. Enter it and click Pair or Connect.\n\nOn the phone, accept any debugging authorization prompt. In Phoma, the device should change to Online. You can now select it when building or running a flow.\n\nIf you paired over USB first, the phone may stay discoverable on Wi-Fi until you restart it or toggle wireless debugging off.\n\n## Real-World Example\n\nA QA tester supports three Android builds for a delivery app. Each morning she places five test phones on a shelf, connects them to power, and pairs each one to Phoma over Wi-Fi. Instead of crawling under desks to swap USB cables, she opens Phoma, selects all five devices, and starts the same smoke-test flow on all of them at once. When a phone drops offline, she checks the Wi-Fi icon and re-pairs it in under a minute.\n\n## Troubleshooting: Phone Will Not Connect to Phoma\n\n### Device does not appear in Phoma\n\nFirst, confirm the PC and phone are on the same Wi-Fi network. Some routers split 2.4 GHz and 5 GHz into separate networks or isolate wireless clients, which blocks adb traffic.\n\nCheck these phone settings:\n\n- Developer options is on\n- USB debugging is authorized\n- Wireless debugging is on, for Android 11 and later\n- Screen is unlocked and not in a strict battery-saver mode\n\nOn the PC, confirm Phoma is not blocked by Windows Firewall. If you use adb manually, restart the server:\n\n```text\nadb kill-server\nadb start-server\n```\n\nThen refresh the Phoma device list.\n\n### Pairing code fails or expires\n\nWireless pairing codes expire quickly. Regenerate a new code on the phone and enter it right away. Pairing over Wi-Fi without USB requires Android 11 or later. On older phones, use the USB plus adb tcpip method instead.\n\nIf the phone's IP address changes after a router restart, the saved Phoma connection breaks. Set a static IP for the phone or create a DHCP reservation in your router settings.\n\n### Connected but flows do not run\n\nRevoke USB debugging authorizations on the phone, then reconnect and allow the PC again. Avoid tapping Always allow on shared or public computers.\n\nIf Phoma shows the device as offline, remove it from the Devices page and add it again. Do not root the phone or install a custom ROM to fix connection issues; Phoma works with standard Android debugging.\n\n## Keep Wi-Fi Connections Stable\n\nEnable Stay awake in Developer options so the screen does not lock while the phone is charging and idle. A locked screen does not always stop adb, but it can make mirroring and interaction less reliable.\n\nGive test phones static IP addresses so Phoma always reaches them at the same address. If your office Wi-Fi has client isolation turned off, wireless adb should work across the same subnet.\n\nWhen a phone receives a major Android update, debugging authorizations reset. Plan to re-pair the device after updates.\n\n## USB vs Wi-Fi: When to Use Each\n\nUse USB for first-time setup, for phones that refuse to pair wirelessly, and for very large file transfers. Use Wi-Fi for daily flow runs, device farms on a bench, and situations where you need to start tests without walking to the phone.\n\n## Quick Checklist\n\n- Developer options and USB debugging enabled\n- Wireless debugging enabled on Android 11+\n- Phone and PC on same Wi-Fi network\n- IP address and port copied from the phone\n- Device added and marked Online in Phoma\n- RSA authorization accepted on the phone\n- Static IP or DHCP reservation for long-term test phones\n\nOnce a phone is online in Phoma, you can build visual flows, run them on one device or many, and schedule checks while the app stays open. No code is required to run the flow itself; the adb setup is only the connection step.\n","https://blog-api.phomaapp.com/api/blog/posts/connect-phoma-android-wifi-wireless-adb-debugging/assets",1794038289214]