Problem: WiFi setting automatically changed itself from "Auto" to "Always On". I just tried to replicate it again and this time it changed itself to "Always Off"
How to replicate:
Anything else of note: When originally setting up WiFi on the watch I did set the watch temporarily to "Always On" so I could make it connect to my WiFi network just to try it out. After that, I set it back to Auto and didn't touch it again.
After the latest update this is still an issue. Could someone look into it please as it's really annoying. I occasionally have to restart this watch due to other bugs (such as the heart rate monitor no longer working) and every time the WiFi setting changes itself. My guess is that it sets itself to whatever the connection state was when it was powered off, rather than keeping itself on auto if that's what it was set to.
Our developer was unable to reproduce this one at their end. Is this issue still happening for you? If so, are you able to use the Members app to send an error report and log files their way?
(For anyone else out there experiencing the same issue, please do the same.)
Say "Hello!" to the Community in The Introduce Yourself Thread.
I don't have this problem.
I have another one. Sometime I loose my wifi. The watch try to connect the WiFi but It can't. To use again the WiFi I have to forget the WiFi and connect it again with the password and it's work again.
Does somedody have the problem?
The same issue on my side - the watch doesn't connect to WiFi automaticaly when out of bluetooth range
(you need to 'forget' the saved network then re-enter the password and connect manually.
the WiFi issue is reported on various Samsung forums (in US and EU) and I found no support/response from Samsung to help people there.
For me this is a basic feature for the watch to stay connected and receive notifications from phone in WiFi range.
Very annoying - reason for complaint and return of the watch.
I have this same issue , cant connect to my wifi , the watch trys but can not establish a connection , only way around it , is to forget network , anyone else aware of this issue?