When the watch is not connected to Bluetooth and remote connection is enabled my Galaxy watch 46 will only show "standalone" operation when on WiFi, or Mobile network, It will not remotely connect to the phone as designed. I have tried resetting the watch, resetting the mobile connection, removing and reinstalling "Galaxy wearable", removing and reinstalling my Samsung account. Nothing is working. The watch shows the correct account, I have good signal. I'm loosing my noodles here.
Solved! Go to Solution.
And I am Swisscom (Switzerland), also on LTE
My guess its the Wearable app or something at Samsung broke
Yeah but there seems to be some kind of policy at samsung against accepting the blame for their mistakes...
We have escalated this to our team of specialist for further research. We will reach back out when we have further information.
Be sure to click " ✓ Accept as Solution" when you find an answer that works for you.
Please note, notification emails are a DO NOT REPLY address, you must log-in on the community page in order to respond.
I got my first galaxy watch last weekend and it would only remotely connect to my phone from the phones end, if I tried from the watch's end I would just get the msg saying somthing like remotely connecting if this takes to long please try again then two or three days ago it became impossible to remotley connect all together.. I just spent the last 3 hours at telus exchanging my old watch and trying to get my new one to remotely connect. It's for sure Samsung's fault. Brand new watch straight out of the box would not remotely connect it's like they did somthing to the wearable app over the weekend. Luckily I have 15 days for Samsung to fix the problem or I will be returning my watch for a refund as watch is useless without remote connection.
Has anyone ever been able to remotely connect from the watches end? Before this update ruined the app.
I'm having this exact problem on both my Gear S2 Classic and Galaxy Watch 42mm connected to my Galaxy s10.
Both have T-Mobile service
Neither of my watches will remotely connect to my phone when on wifi or cellular. I've been trying to get them to work all night. Reset both watches multiple times. Nothing's working.
I can confirm this has nothing to do with the cell carrier. On cellular data the internet service works fine. Youtube videos and browsing work fine over TMobiles network. It just won't remote connect to my phone and operates in standalone mode.
This is the same in WiFi mode. Internet works fine but remote connect to phone does not.
Watches that are having this problem:
Gear S2 Classic T-Mobile (Model # SM-R735T)
Galaxy Watch 42mm T-Mobile (Model #SM-R815U)
Galaxy S10 Android 9.0
Galaxy Wearable 18.104.22.16821251
Gear S Plugin 2.2.03.19022851
I think this rules out watch software. No way both watches got the same problem because of the software... This should help samsung narrow down to app or server problem
Agreed. My S2 Classic hasn't gotten a software update in probably a year. Nothing has changed on my end. So it's definitely not a software issue. Something's wrong with the Samsung account backend for forwarding phone notifications to the watches.
I just spent half an hour with a support agent who was adamant the remote connection issues is somehow a hardware issue even though multiple people are reporting it withing the same couple of days and i linked the multiple threads on it. Is support on the forum any better? or should i start pursuing a refund through warranty?
Me too! My watch cannot be working fine then suddenly when I update the wearable app my watch is all of the sudden defective. Support agent blamed my carrier and that I have a defective watch. It is starting to get annoying as I have to carry my phone during my workouts. One of the main reasons for getting the LTE version was to leave my phone at home and just take my watch.