Reputation: 3453
What are the magic words one has to utter to get Tizen Studio to connect to S3 watch?
I have S3 watch that is connected to my wifi network. I can ping that device just fine. I have made sure debug option is turned on the watch.
I have been able to connect to this S3 watch multiple time. But anytime I change my wifi network (between work and office) I literally have to pray that Tizen studio would connect to S3 watch.
Is there a reliable way to connect with S3 watch from Tizen Studio?
If there way to connect to Samsung S3 watch over USB?
Unfortunately my employer has decided to develop app for Samsung Gear S3, but connecting to watch from Tizen Studio has been frustrating experience so say the least....
Upvotes: 9
Views: 13056
Reputation: 53906
Same as Liam Harrison solution with extra step:
"
Tested Solution
Hi everyone, after some tedious testing I've found a way to consistently get your Watch to connect to your PC, I've tested these steps on two devices and they are as follows:
sdb connect x.x.x.x
I've tested this method with success two times on two PC's with both Intel & AMD CPUs, the main takeaway is that the Watch seems to hate prompting the user for permissions on the Watch Face screen, and simply navigating off it will get things working correctly.
"
Extra step: ensure Tizen Studio is not running if connecting from sdb
cli as Tizen Studio appears to lock the connection and cli returns message:
connecting to ...:26101
failed to connect to ...:26101
Once I quick Tizen Studio the watch connected. Upon start of Tizen Studio the watch is available from dropdown.
Upvotes: 1
Reputation: 1
I spent two hours trying to connect the watch to the studio, in my case it helped me to turn off the debug in the watch and turn it back on, the studio immediately found the watch.
Upvotes: 0
Reputation: 149
Tested Solution
Hi everyone, after some tedious testing I've found a way to consistently get your Watch to connect to your PC, I've tested these steps on two devices and they are as follows:
sdb connect x.x.x.x
I've tested this method with success two times on two PC's with both Intel & AMD CPUs, the main takeaway is that the Watch seems to hate prompting the user for permissions on the Watch Face screen, and simply navigating off it will get things working correctly.
Upvotes: 15
Reputation: 309
Do the following:
sdb kill-server
sdb start-server
sdb connect "YOURIPADDRESS"
Upvotes: 0
Reputation: 2361
I've run into that problem a few times. A few things to check and do.
Is debug mode enabled? Remember that if you pair the watch with a different phone that debug mode will be turned off.
If WiFi on? You will want to go into settings and set the WiFi to "Always On." Keep the watch on a charging cradle between debug sessions. The battery will drain much faster.
Before starting Tizen Studio try connecting from the command line. Note, pay attention to the watches screen when you do this! If the watch is pin locked or pattern locked you need to unlock it before continuing. You will get prompted to accept an RSA key the first time you try and if you are not watching the key won't be accepted and the connection will fail! As mentioned above use
sdb connect {ip address}
When I do this the command usually reports failure the first time around but success the second time. After it's connected start Tizen Studio. While this wasn't part of your question remember that if this is your first time deploying to the watch or if the watch has since been reset that you will need to take care of getting a development certificate installed on the watch.
Upvotes: 2
Reputation: 1313
Even I faced the same issue. If anybody unable to connect remote device even in same network try below steps:
Hopefully this time you will get a prompt in watch to accept connection.
Cheers!
Upvotes: 8
Reputation: 1881
I know the S3 does have an option to keep the wi-fi on. I also noticed that sometimes just because it's on the wi-fi and pingable it doesn't always connect.
I did try to restart my watch and that didn't seem to affect it. what did work for me, was I noticed in the ADB there was commands to kill server and start server. I used those then then tried again to connect from the command line, it gave me an error about being unauthorized. which was a different error then i was getting before. So I toggled the debug settings off then back on in my watch and tried connecting again from the command line. And that worked.
Upvotes: 2
Reputation: 576
I tried all steps above and was quite desperate already, then I tried to reboot my device and it did it. Facepalm. After the reboot and another attempt to connect I was prompted to accept a certificate on the gear watch and that was it.
So my advice, just reboot your (gear) device if you cant connect it might save you a lot of time.
Upvotes: 11
Reputation: 3186
I had to change my router, It would be nice to use station to plug in a reliable usb link
Upvotes: 0
Reputation: 1
If what has been suggested hasn't worked for you, just make sure your watch is using the same IP address each time it connects to a new network. If not, update the IP address in the Remote Device Manager to reflect the current address of the device each time you connect. Also, bluetooth should be off to make sure it isn't already connected to a phone.
Upvotes: 0
Reputation: 71
as far as I know S2 and S3 can only connect through WiFi.
WiFi connection can be unstable sometimes.
Instead of connecting using Tizen studio I use this script each time it disconnects, it's faster
sdb connect "device_ip":26101
Replace "device_ip" with the IP of your device, without quotes.
After running that command, the device will appear in the Connection Explorer of Tizen Studio
Upvotes: 4