Languages

Menu
Sites
Language
Gear S2 Not Connecting Remotely

Hello,

I've been developing on the new Gear S2 for a while now. Unfortunately, my S2 out of nowhere stopped being able to be connected to any computer anymore. Nothing changed with any settings, it just stopped connecting to anything remotely... (which sucks because there is no way to connect the watch to your computer with the NFC charger....).

 

Here are the steps:

 

 

  1. 1. Debugging is on
  2. 2. Wifi is on and on the same network as any machine I try
  3. 3. Bluetooth is off (keep in mind - this was working fine ever since I bought it from the store)
  4. 4. Double check the IP on the watch
  5. 5. Run  sdb connect <IP address>:26101
    1. * Error: failed to connect to remote target '<IP address>'

 

 

I've tried this on 3 different machines (Ubuntu 15.04, Mac Yosemite, Mac El Capitan) and 3 different networks. I have the latest software with both the Gear Manager and S2. Also, the watch has no problem connecting remotely to the phone. Needless to say, super frustrating having the watch connect fine for weeks and all the sudden stop. About to just return the watch.

Thanks in advance for anyone with the fix.

Edited by: Casey Baggz on 28 Oct, 2015
List

Responses

6 Replies
daniel kim

Hi,

I would suggest you to check IP address of your pc as I experienced same problem in office. In my case, connection issue was gone after I changed IP address of my PC to use same gateway of WiFi hub .

Regards

Joel Ivory Johnson

I know this thread is old, but that I would make an addition since I ran into the same thing. 

After turning debug mode to "on" it helps if the watch is reset. This is listed in Samsung's instructions but it's something I had overlooked. After that when I attempted to connect my attention was on the success/error response from my PC. I didn't notice that SDB had successfully initiated communication with the watch and the watch was asking me whether or not to accept a certificate from the computer. Once I accepted the certificate I had no further problems. 

Bob Frankston

My Gear S3 is indeed at 192.55.226.111 and I can ping (though not all pings get through). In the past I've gotten SDB to work but then application download fails for "unknown reasons". How do I debug this?

Armaan-Ul- Islam

In my case it worked... the process I had gone through:

1. Reset the Gear. Settings > Gear Info > Reset Gear > Light Reset/Factory Reset (Do not recover settings)

2. Enable Debbuging.

3. Enter Static IP for Gear if needed.

4. Check the time settings on each device and correct it if necessary.

5. Run  'sdb connect <IP address>' command repeatedly. (four-five times may do the trick).

Rich Mabb

Sharing my solution.......

I had the exact same issue and troublshooted over 2 days, I tried everything mentioned in these posts.

Not only I reset my watch, reinstalled Tizen Studio (1.1 and 1.2), I even tried connecting from different different PCs. 

After enabling debug mode, I rebooted my watch (not reset), only then I was propmpted to accept the certificate (as Joel montioned) and that solved it.

So, when all fails make sure you have been prompted and accepted the certificate.

 

Armaan-Ul- Islam

Thanks Rich Mabb, For sharing your experience. Updating the List :)

6. Accept the promt asking for certificate acceptance on your Gear.