You see those with GW4 and GW5 too with the new tool. It happens when you don’t wait long enough to OK the file transfer from computer to watch.
I don’t know why but this is a recent thing and It takes a long time (like almost a minute) for that OK to pop up. It didn’t take that long before. I had forgot about it because I had selected don’t show again.
I got my GW6 test device today and I’m having the same issue. Just can’t find a way to connect the new GW6 with WFS 1.3.13.
Also, no matter how long I wait for the “OK” to pop up (I tried waiting 2-3 minutes with various settings each time), it doesn’t show up on the GW6.
ADB debugging is allowed, watch has been rebooted, I even tried with “Wireless debugging” turned on (which wasn’t required on GW4), and the GW6 just won’t connect to WFS 1.3.13.
I’m trying the same “Run on device” process that works instantly and without issues with GW4.
Worth noting - There’s an option “Debug over Wi-Fi” under Developer options in GW4, but this option doesn’t exist on the new GW6 for some reason. This might be the issue.
Can it be that it’s only possible to connect the new GW6 with WFS 1.4.20, and not at all with 1.3.13?
Now you should see connection successful, you can check this with
After computer is paired, it is only needed to connect to the main IP:Port (Not the one from the pairing screen), it will also work on any Wi-fi network but you need to confirm this on the watch.
What’s unfortunate for me, maybe not for others is that Wi-fi debugging is turned off every time there is a drop in Wi-fi connection (maybe because of battery saving purposes). This means that for example every morning you need to go to dev options, enable wireless debugging, check port because port is always different random number, and connect to it.
When I finished work in the evening, I set airplane mode. In the morning, I turned off the airplane mode, the watch connected to Wifi, then I just pressed the predefined command and I could test the faces on the watch. In the morning I always found almost the same battery level. During the day, I keep the watch near the charger all the time and recharge it from time to time. When I use the watch mainly for watch face testing purpose, the battery does not bother me at all
With GW6, process is a bit more complicated. But nothing terrible.
After you have connected the Watch to the WIFI network and activated the developer options, go to debug wireless … Then pair new device, from there you will get Pairing code and Pairing port (after the colon). While the main port is IP address are in the previous menu.
Here go to developer options
In this case IP address: 192.168.1.68 and port 44289
Here instead Pairing Code 494306 and Pairing Port 33453 (you have to tap on “Associate new device”):
You need these 4 data to connect the Watch to WFS.
BTW, you can NOT connect the GW6 to WFS 1.3.13. Only 1.4.x or higher*
Reading other users’ answers, it seems that it is possible to link GW6 to WFS 1.3.x via shell.
i believe as soon as Samsung Watch 5 Pro and Watch 4 Classic are updated to Wear OS 4.0 This procedure will also be valid for them. It is bit of unconveyneance pairing every day andother option not switch off watch and keep it on airplane mode at night when sleeping seems better off. Then re-pairing every time.
Thanks to all for above information. This means per force when wear OS 4.0 comes we have no option but to upgrade from 1.3.13 WFS to latest WFS 1.14.20
and does this also mean we have to update all our watchfaces with 1.14.20 to be compatible with watch 6 series??
This method uses the adb command and requires some DOS knowledge.
The command to use is:
1.adb pair 192.168.1.xxx:xxxxx (The last 5 digits are the pairing port number.)
2.adb connect 192.168.1.xxx:xxxxx (The port number is 5 digits, and it is a wireless debugging number.)
To execute this command, you need a program called platform-tools distributed by Google.
You can search for it, download it in advance, and unzip it.
After that, run the above two commands in the command prompt.
If you pair first, it continues until you cancel the pairing, so you only need to use the port access command for the second WFS connection.
Activate developer mode on your watch.
Enable adb debugging in watch developer mode.
Activate wireless debugging in watch developer mode and connect to wifi. (You can see the ip and port number.)
Press the + sign to register the device. (If you press it, the pairing number, IP, and 5 digits of the port number appear. Do not close the screen, but you must perform the pairing command on the computer while it is open.)
4-1. Right-click on the platform-tools folder that you downloaded and unzipped in advance and click Open in Terminal to open a command prompt.
Enter the pairing command adb pair 192.168.1.xxx:xxxxx (This port number is the port number indicated in pairing.) and then insert the 6 digit pairing number.
Connect to the computer using the connection command adb connect 192.168.1.xxx:xxxxx (This port number is the port number displayed in Wireless Debugging).
If successful, connected blah blah comes out.
You should now see that the watch name is already displayed before WFS does as usual.
If not, restart WFS and try again.
If you try it and leave a comment if it doesn’t work, we will help you.
Good old Tizen, I had just to turn on debugging on watch (never turned it off, it did not affect battery drain at all) turn on wi-fi, confirm the RSA prompt and try the connecting multiple times until it worked, but did not need additional tools nor searching for ports and what not. I guess there is all the tightened security in background, but to me on the outside this new OS keeps looking inferior
Hello, I was unable to connect my Galaxy Watch 6 to Wfs despite following all the instructions mentioned above.
Platform Tools is installed, I am running powershell in the platform tools folder, adb is installed, adb debugging is on, wifi debugging is on, and I am adding a device, but I am getting the following error. I would be glad if you help.