Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11To enable ADB debugging on a Galaxy Watch 4, 4 Classic, 5, 5 Pro, 6, or 6 Classic, reveal Developer options, turn on ADB debugging and Wireless debugging, then pair and connect the watch to your computer over Wi-Fi. The current Wear OS workflow uses two different ports: one for pairing and another for the ADB connection.
These instructions apply to Wear OS-powered Galaxy Watch 4, 5, and 6 models. They do not apply to older Tizen watches such as the Galaxy Watch 3 or Watch Active 2, which use Samsung’s separate tooling and sdb.
As an Amazon Associate I earn from qualifying purchases.
What ADB debugging does
ADB, or Android Debug Bridge, is the communication interface that lets a computer issue commands to an Android or Wear OS device. On a Galaxy Watch, ADB can be used to install compatible APKs, open a shell, inspect logs, test Wear OS apps, and connect the watch to Android Studio.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsEnabling the setting does not automatically install an app or change the watch. It permits ADB communication after the computer has been paired and the watch has authorized it. Developer options is only the hidden settings menu; you must separately enable ADB debugging and the wireless-debugging feature.
#1 Best Overall
- Rotating Bezel Design: Classic rotating bezel enables precise control and smooth navigation.
- Developer options: A menu containing development controls.
- ADB debugging: Allows Android Debug Bridge communication.
- Wireless debugging: The modern Wi-Fi pairing and connection method.
- Debug over Wi-Fi: An older or alternate label that may appear on some One UI Watch versions.
Android SDK Platform-Tools includes adb. Android Studio is optional unless you are developing or debugging an app.
What you need
- A Galaxy Watch 4, Watch 5, or Watch 6 running Wear OS.
- A Windows, macOS, or Linux computer.
- Current Android SDK Platform-Tools, or Android Studio.
- Wi-Fi enabled on the watch.
- The watch and computer connected to the same local Wi-Fi network.
Google’s Wear OS guide specifies ADB 30.0.0 or newer for the wireless-pairing workflow. The simplest approach is to download the latest Platform-Tools release shown on Google’s official page rather than install a third-party ADB package.
The watch should be powered on and unlocked when an authorization prompt appears. Guest networks, some enterprise networks, VPN configurations, and routers with client or access-point isolation may stop devices from communicating even when they use the same network name.
1. Reveal Developer options on the watch
- Open Settings on the watch.
- Tap About watch.
- Tap Software or Software information. The wording varies by software version.
- Tap Software version five times.
- Return to the main Settings screen and open Developer options.
Samsung documents both Software and Software Information as surrounding menu labels, so do not tap only the general Software row and expect Developer options to appear. If there is no confirmation toast, repeat the five taps deliberately, unlock the watch if prompted, and check near the bottom of Settings.
2. Enable ADB and wireless debugging
- Open Settings → Developer options.
- Turn on ADB debugging.
- Turn on Wireless debugging. On some older One UI Watch builds this may be called Debug over Wi-Fi.
- Accept the authorization prompt by choosing Allow, or choose Always allow on this network only if the network is trusted.
Samsung also recommends enabling Turn off automatic Wi-Fi in Developer options. This can help prevent the watch from disabling Wi-Fi when its screen is off or it is not actively using the connection.
3. Install and check ADB
For command-line use, download Platform-Tools for your operating system, extract the archive, and open Command Prompt, PowerShell, Terminal, or a Linux shell in the extracted platform-tools folder. If you have added that folder to your system PATH, you can run the commands from anywhere.
adb version
The command should print the installed ADB version. Android Studio can install and manage Platform-Tools, but it is not required for basic ADB commands.
Recommended Free Tools
4. Pair the watch with the computer
- On the watch, open the Wireless debugging screen.
- Tap Pair new device.
- Note the displayed IP address, pairing port, and Wi-Fi pairing code.
- In the computer’s terminal, run:
adb pair WATCH_IP_ADDRESS:PAIRING_PORT
For example:
adb pair 192.168.1.42:37123
The address and port in that example are illustrative. Use the values currently shown on your watch. When ADB asks for it, enter the pairing code displayed by the watch.
Rank #2
- Larger Super AMOLED Display: Expanded screen area with slimmer bezels for improved visibility and usability.
5. Connect to the watch
Pairing is not the same as connecting. Return to the main Wireless debugging screen and note the watch’s current connection IP address and connection port. Then run:
adb connect WATCH_IP_ADDRESS:CONNECTION_PORT
Example format:
adb connect 192.168.1.42:41237
A successful response should indicate that ADB is connected to the IP address. The pairing port and connection port may be different. Do not reuse the pairing port unless the watch specifically displays it as the connection port.
6. Confirm the connection
adb devices
A successful result lists the watch and shows device, similar to:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsList of devices attached
192.168.1.42:41237 device
| Status | Meaning |
|---|---|
device |
The watch is connected and authorized. |
unauthorized |
The watch has not accepted the debugging authorization prompt. |
offline |
ADB sees the entry but cannot complete communication. |
Useful ADB commands
| Command | Purpose |
|---|---|
adb shell |
Opens a command shell on the watch. |
adb shell getprop |
Displays Android system properties. |
adb install app.apk |
Installs an APK from the current computer folder. |
adb uninstall PACKAGE_NAME |
Uninstalls an app by package name. |
adb logcat |
Displays device logs. |
adb disconnect WATCH_IP_ADDRESS:CONNECTION_PORT |
Disconnects the wireless ADB session. |
These commands do not bypass every restriction. APK architecture, Wear OS compatibility, package identity, permissions, signature checks, and software-version protections still matter. Removing system packages can also make the watch unstable or remove essential functions.
Fix common connection problems
Developer options does not appear
- Confirm that you tapped Software version, not just Software or Software information.
- Tap it five times in succession.
- Unlock the watch if it requests confirmation.
- Return to the main Settings screen and look near the bottom for Developer options.
- Restart the watch and repeat the process if no confirmation appeared.
The pairing code is rejected
Pairing codes and ports are temporary. Keep the pairing screen open, use the current values shown on the watch, and run the command again. Make sure the terminal uses adb pair, not adb connect, for this stage.
The device is unauthorized
Look at the watch for an authorization prompt and choose Allow or Always allow from this computer. If the prompt does not return, turn ADB debugging off and on, disconnect, and pair again. You can also restart ADB:
adb kill-server
adb start-server
adb devices
Some watch software versions provide a way to reset existing debugging authorizations; its location is not universal.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The device is offline
Try the following sequence:
adb disconnect
adb kill-server
adb start-server
adb connect WATCH_IP_ADDRESS:CONNECTION_PORT
adb devices
Then check that wireless debugging is still enabled, the watch is awake and unlocked, and the IP address and connection port are current. Wireless ADB may need to be reconnected after the watch restarts wireless debugging, reboots, or changes Wi-Fi networks.
Rank #3
- Rotating Bezel Design: Classic rotating bezel enables precise control and smooth navigation.
Connection refused or timed out
- Confirm that both devices use the same SSID.
- Use the connection port, not the pairing port.
- Check computer firewall rules.
- Disconnect a VPN that blocks local-network traffic.
- Try a private network without client isolation.
- As a diagnostic test, connect both devices to a mobile hotspot; Google notes this can help when a router isolates clients.
Do not expose the watch’s ADB port through router port forwarding. Wireless ADB is intended for local-network debugging, not public internet access.
Wi-Fi turns off and the connection drops
In Settings → Developer options, enable Turn off automatic Wi-Fi. This is particularly useful if the watch disconnects when its screen turns off.
Several devices appear
Target the watch explicitly using its serial identifier from adb devices:
adb -s DEVICE_SERIAL shell
Use the same -s DEVICE_SERIAL pattern with other commands that need a specific target.
Wireless ADB, USB, and Android Studio
Wireless ADB is the documented default for Galaxy Watch 4 and later. It avoids needing a special physical data connection, but it depends on local Wi-Fi and may require reconnection after network changes or restarts.
A normal charging puck should not be assumed to provide USB ADB access. Samsung documentation mentions a cradle or 5-pin cable for particular development setups, but that is not a universal USB method for Watch 4, 5, or 6.
Android Studio is optional. Install it if you are building, deploying, or debugging Wear OS applications. For APK installation, shell access, and log inspection, Platform-Tools alone is sufficient. The computer running ADB does not need to be the phone paired with the watch, and the phone’s USB debugging setting is not required for this computer-to-watch wireless session.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTurn debugging off when finished
When you are done, return to Settings → Developer options and disable ADB debugging and Wireless debugging. You can also disable Developer options if you no longer need the development menu. Turning the controls off reduces battery use and limits computer access, especially on shared or untrusted networks.




