Why won't my Gear S2 connect remotely?

Re: Gear s2 won't connect remotely.

What does signing in to a Samsung account do? I don't think I am and I can go into a remote connection. (Side note) when I tried playing samsung milk just on watch no Bluetooth connection to phone, it did say standalone mode for some reason.

The phone and watch use the Samsung account to sync. I assume it works like a central connection server, the way you might open an SSH tunnel from one machine to a central machine, then connect to a port on the central machine to access the first machine. The Samsung account probably acts as a middleman to authenticate both pieces of hardware to one another and provide a known network location where they can be found. Otherwise the phone and watch would have no idea what each others' dynamic IP addresses are, and since Verizon double-NATs 4g LTE devices there's no way for the watch to communicate directly with the phone without some sort of intermediary anyway.

Either the phone or the watch explained at one point that they would be linked via the Samsung account if I turned that feature on (I don't recall where I read it), but I did not have to enter my Samsung credentials on the watch. I assume an access token was copied over automatically as part of the BT pairing process and initial gear setup, just the way it offers to transfer Wifi credentials automatically from Gear Manager.
 
Re: Gear s2 won't connect remotely.

I am with T-mobile and i did have the same problem.. could not connect remotely - until the 19th of November when it got rectified.. there seem to be an outage for all gears in their network.. so it worked flawlessly - it would automatically connect to t-mobile network when disconnected from wifi.. sometimes 10 seconds others just less of 30 seconds.. soooooo good to see this working.. then today, November 27 it STOP... call Samsung and they say if it is connectivity it is a t-mobile issue.. so got transferred to T-mobile.. but the first line of support does not know much about these watches.. so asked for a ticket creation and I asked for an escalation of my problem... hopefully they will fix it..
 
I am assuming you have figured out how to fix this issue. But for others that are having the same issue here's something to try. I noticed that with the app update and when your phone loses either wifi or mobile data the watch can lose remote connection. In the Gear App, be sure the remote connection is turned on under the settings and that you are connected using Bluetooth. Then go into call forwarding, and forward your calls to your device. This can also be done through the watch settings. Once that is complete you need to receive a call to your phone. Reject the call and let it roll to your watch. Don't forget All of this has to be completed using Bluetooth connection. Once you turn your Bluetooth off on either device, you can go into your Gear App settings and your connection status should now read remotely connected. Hope this makes sense and works for anyone else having the same issue. I spent hours trying to figure out why it wouldn't connect. I stumbled upon this and I've tried it numerous times and it works.
 
*Update* Just got back from T-Mobile. The issue was that the Sim card they had as active for my watch was not the Sim card that was in my watch lol. Everything is working now. Thx for all your troubleshooting.

Posted via the Android Central App

Hi, I am a new gear s2 user, and my mobile is oppo r9. I face the same problem you had earlier, just don't know how to figure it out. I have done factory reset on the watch. However, I have been trying many times to turn off the BT, the gear still show standalone. It just cant connect to wifi remote control.