Hello @smolnar18,
Hope you’re fine.
It is always recommend to turn off Bluetooth while doing WiFi/USB debugging due to interference.
Did you face the same issue when Bluetooth is off?
Try=>
BT off> make connection with device> do some changes again in WF> run on device. Do not turn on BT during this whole period.
Share the result with us after following above steps.
Sometimes it is also part of prerequisites that you have to disconnect all other connections (mobile as well) except debug PC.
Looking forward to your response.
Thanks
Shamima
1 Like
@smolnar18 Do you not prepare your watch Connection to WiFi before you Click Run on Device as I mentioned Above ? Have you been able to set the IP Address of the watch correctly . You get it from the watch in the Connection settings .
.
Another Maker friend made this some time ago .
.
3 Likes
Bravo Russell!
Suggestion: create a topic “How to connect watch to WFS” or something like that, this question is often asked and your picture is really the best guide. it will be lost in this topic.
1 Like
Thing is the trick has changed over a few years . Ron used to post a good set of instructions but he does not monitor posts any more ( Being as he retired ) and some of his notes became irrelevant .
Yeah perhaps it is time for a new Topic with a relevant Title .
.
This is a strong topic and we see where that Graphic came from .
.
[Guide] connecting watch to wfs
1 Like
Yes, I do ALL of that, exactly as you outlined in your screenshot.
1 Like
@Shamima, Hello and thanks for responding!
I always turn off bluetooth when I first set up the WFS and my watch for Run on Device.
But, you MUST turn bluetooth back on after the face is sent to the watch, or you will not get the Customize button on either the watch or Wearable app on the phone, and won’t be able to configure and test changes to complications, etc.
But my main point about all this is that I have been using Run on Device daily for a couple of months, EXACTLY how I am using it now. I never had this problem until 1.8.10. I always turn bluetooth off to set up the first Run on Device and send the face to my watch/phone. After the first Run on Device, I can turn bluetooth back on so I can test the changes on my watch/Wearable app, and leave bluetooth on for multiple Run on Devices after that (during a single session).
Let me know what you think. 
1 Like
Blimey . So we are saying it is an issue with the GW7 . Is your IP address stable . Is the WiFi stable . You may have to raise a ticket with Samsung Help Desk . Sorry if I missed them did you take some screen grabs from Laptop and Watch .
I never switch off the BT . Have you concidered cutting your losses and going back to 1.7.13 . Putting the files you worked on on hold till things are sorted better .
When I first started using WFS, I found the connection process very confusing, so I wrote it all down for myself and to share later if anybody needed it. Here’s my complete process I’ve been using all along. I have not changed a single thing between the previous version and 1.8.10. All that’s changed is that now I can only get one run before I have to go through the whole process again.
Sorry it’s so verbose - as a non-technical person, when I’m trying to learn technical things, I try not to leave anything out!
Prepare your watch. This assumes you have already put your watch in Developer Mode.
a. On your watch, go to Settings > Connections. Click on Bluetooth, then click to turn Bluetooth OFF.
b. Wait at least 30 seconds for Bluetooth to finish turning off.
c. Return to Settings and scroll all the way to the bottom of the settings screen to Developer Options.
d. Click Developer Options.
e. Scroll down to ADB Debugging and turn it ON.
f. Scroll farther down to Wireless Debugging and click on it.
g. Turn Wireless Debugging ON and wait a couple of seconds.
h. Scroll down past Device Name to IP Address.
i. WRITE DOWN THE LAST 5 DIGITS OF THE IP ADDRESS.
j. Click on the + next to Pair new device.
k. WRITE DOWN THE 6 DIGIT NUMBER DISPLAYED MID-SCREEN.
l. Scroll down slightly to another string of numbers separated by dots and WRITE DOWN THE LAST 5 DIGITS OF THIS NUMBER.
Run on Device.
a. In WFS, click Run on Device again (watch icon in upper right).
b. When the Connected Device pop-up appears, click the + button, top-right.
c. In the IP Port field, enter the first of the three numbers you wrote down (see i above).
d. In the Pairing Code field, enter the second of the three numbers (see k above).
e. In the Pairing Port field, enter the third of the three numbers (see l above).
f. Click OK and wait.
g. The Connected Device window should display something similar to “Galaxy Watch7 (AD3T)” (your watch will have its own, similar name).
h. Click on that watch name.
i. You will be returned to the WFS app screen. Wait for a few moments.
j. A pop-up Notice will tell you “Launch is Complete.” It can be very quick or take up to 2-3 minutes.
k. Click OK.
Test on Your Watch
a. On your watch, go to Settings > Connections. Click on Bluetooth, then click to turn Bluetooth ON, so you can test any complications or other set-up changes on your watch face.
b. Customize your watch on the Wearable App on your phone (easier than doing it on your watch), then test any changes you made in WFS.
c. Keep WFS open for now, in case you want to make changes after testing it on your watch. All the IP and Port number set-ups you did above may stay in effect and not have to be re-done as long as WFS is kept open and you do not re-start your watch or phone.
1 Like
Forgot to answer your questions:
My WiFi is as stable as most U.S. residential areas. I have not noticed any issues.
My IP address is “stable” if what you mean by stable is that it is always the same (except the last 5 digits).
1 Like
@smolnar18
hey, you should be able to customize the watch face from your watch even when the bluetooth is turned off.
1 Like
So there is a lot to read there .
I do not have time to write down any numbers . I copy them off my watch .
For me your list stareted well but I got a bit lost jalf wat through . I am hopless with writren instructions . They just swom in front of my eyes . So let us be clear. The 5 digit number at the end of the IP number is the port number . You do not use that at all untill a new connection has been made . So you have to type three numbers on your Laptop . Two port numbers and tge 6 digit paring number . These come from your watch after the new connection is made .
Do your very best to use the process in the Graphic that I posted above . I have an old step by step PDF but it is a bit out of date now . I will try make another . Like your list it takes a bit of time .
Thank you! I tried it only once, and that one time, I clicked Customize (on my watch) and it just did nothing (no customization options shown). So I just assumed bluetooth had to be on and never tried it with it off again. But you are (of course!!) right.
However, when testing what I’ve created in WFS, I want to see how it looks and acts in BOTH my watch AND in the Wearable app on my phone. Unless I’m again mistaken (which is always very possible), I don’t believe I can test Customize from my phone with Bluetooth off, correct?
Given that, I would guess developers often want to turn bluetooth back on during their test for that very reason, so I would assume doing that shouldn’t disconnect your watch from WFS??
Appreciate your responses!!
2 Likes
The communication of this process is difficult because I don’t always call things by the names developers/technical folks do. But since I’ve been connecting to my watch from WFS and sending my designs to my watch successfully for some time now, without any problems until 1.8.10, I think I’m doing the process correctly (and as you outline).
But just to confirm, here’s my screenshots from my watch and WFS as I’m setting it up.
1 Like
Yes this is extremely Difficult . So it seems the only thing we do differently is turning the Bluetooth on and Off . As I said I do not turn the Bluetooth off and generally set the customisation on the Watch . As you said prior to 1.8.10 the connection to the watch lasted for a bit but these days it drops very soon . So I find I have to type the numbers in each time . As I said toggle ADB and Wifi Debugging . I cam not help beyond that . All the Best .
This is a long shot, but I wonder whether the issue with unreliable connection to the watch could be due to adb getting confused about which device it should be using. When the problem arises, the command adb devices -l could be used to list the devices that adb knows about. If more than one device is listed (eg, due to more than one watch/phone/emulator/AVD), this is a possibility.
There is a way to specify a default device for adb to use, but there’s no point trying this unless there are indeed multiple devices listed.
2 Likes
I have GW6 and GW5pro . I have no issues if the IP address number is correct for the specific watch . I tend to avoid Console solutions for those starting out . But if that is what some have to do then that is how it is . I for myself would not be using WFS if I had to do Console work to get it working properly . For me it is a little bit more about timing . I personally don’t think samsung gives enough time to do type the numbers .
I agree. But if using adb via command line helps to identify the source of the problem, that would help Samsung to fix it.
Plus, it might be possible to automate the workaround I had in mind so that it happens automatically when starting WFS. It simply involves setting an environment variable.
2 Likes
You will have to show this step by step . I for one Have no Idea what you are talking about .
The release notes mentions about
" Update manifest file for WFF package according to the [WFF guide]"
So does this version allow us to modify the manifest file for the watch faces ?
If so I am not able to locate from where it is allowed, and I feel this option should be given as manifest updating option should be given.
Please help me regarding this issue
