Completely normal for watches. Keep in mind 5ghz wifi is a lot shorter coverage area than other wifi. It is faster but in some homes will have spotty coverage. I thing watches do not support it (a few do I think) because a watch doesn't need super fast connection so the go with cost versus practicality.Since getting my Galaxy Watch just over a week ago, I have noticed that is doesn't find 5ghz Wifi - is this normal?
Not understanding this, as you would have the same wifi connection requirements for the 5ghz band as the 2.4 ghz band on your router. Now if your talking cellular LTE, there is a version of the GW that supports LTE.It's more than just lame. It means the remote connection will not work unless your phone is on the same 2.4 ghz wifi.
Not understanding this, as you would have the same wifi connection requirements for the 5ghz band as the 2.4 ghz band on your router. Now if your talking cellular LTE, there is a version of the GW that supports LTE.
It means, that if you have differing names for each of your bands (2.4 vs 5 ghz), and the watch cannot connect to your 5ghz network, then you have to use the 2.4 ghz network in order to be on the same wifi network. I have reasons for separating the networks and having to use two different names. Using the same name for both networks causes connection problems for many devices that can only use 2.4 (ecobee thermostat for one).
It's a but ridiculous that in 2020, a "top end" device such as a Galaxy Watch doesn't have 5 ghz capability.
And yes, I am aware that it's supposed to be a backup for bluetooth. That is EXACTLY what I was hoping it would be. That way, I can leave my phone on the charger upstairs and still be connected and get notifications downstairs on my watch when I am out of bluetooth range. It just doesn't work unless I switch my phone over to the 2.4 ghz band.
It's a but ridiculous that in 2020, a "top end" device such as a Galaxy Watch doesn't have 5 ghz capability.
It just doesn't work unless I switch my phone over to the 2.4 ghz band.
Don't know if I'm misunderstanding your issue. I have the same 2.4ghz and 5ghz setup as you. Different names for each band (which is highly recommended btw). I often have my phone on 5ghz band and have no issues with watch connecting on 2.4ghz. The watch wifi is not dependent on your phone wifi connection.
Hey Kikbxr1969, See my reply to this thread (below i'd imagine) If your still having the issue you can try to nip it with my wonderous knowledge.It will connect to wifi. It just will not remotely connect to my phone unless I have it on the same named network.
Hey Kikbxr1969, See my reply to this thread (below i'd imagine) If your still having the issue you can try to nip it with my wonderous knowledge.
Well, for someone with "in depth knowledge," you made one of the worst troubleshooting mistakes known.... that is assuming. I don't and never have run guest networks and have turned them off on all routers I have ever had. Not sure what the problem was. But, I solved it by leaving the Samsung eco system for watches. It wasn't really an issue most of the time. The issue was not just "a" router. It was three different ones - Asus, Liksys, and Firewalla. I have always only had one subnet, so that wasn't the issue.Kikbxr1969's router is the issue (nothing else) and is setup with at least 2 separate networks (in a sense, the kind of thing a coffee shop owner does with their guest WiFi so that a guest can't talk to his till-machine) OR it's 5Ghz, or 2.4Ghz, bands are set in "guest mode" (again, within the router's settings; and in coffee shop e.g. it is so that one guest's cannot "talk" to another Guest)