- Aug 1, 2017
- 83
- 0
- 0
Ugh!!!After the update, I still cannot get a remote connection.
Ugh!!!After the update, I still cannot get a remote connection.
Whoa, so I just tried and it looks like it is connected remotely now!!!!!After the update, I still cannot get a remote connection.
Whoa, so I just tried and it looks like it is connected remotely now!!!!!
Likewise. Looks like they fixed it in the last hour or so.
Good news guys it looks like they might have fixed the problem![]()
This was a Samsung glitch that was on there end. No update on the watch was neededYeah, mine is fixed, 46mm LTE TMobile, but I didn't do any update though... but it's working so yayyyyyyyy!
This was a Samsung glitch that was on there end. No update on the watch was needed
Yea it was weird it just sort of happened without any update..... actually just had an update last night but so far everything is fineI didn't see the information about no watch updated needed when I posted. Thanks!
So was the update just an update to the Gear app or the watch itself?
After coming back out here I saw you all posting about an update. I did have a Gear app update but no watch update. That said, I disconnected from Bluetooth to see if it said standalone or remotely connected and it said remotely connected.
Thanks for the easy tip arunma![]()
Yup agreedAny time!
I don't believe any update on our end was responsible for fixing the issue. A lot of people reported this happening around the time the Wearable app was updated. But for whatever reason (carrier-related?), my app only updated a couple days after the remote connection capability died. I believe this was a server-side issue on Samsung's end, which is why one day we couldn't get a remote connection, and a few days later it just started working again.
Sounds like that was probably what happened.