Actually, I will go into this one as an old servicedesk employee from a university/Network Administrator I might ignore some of the issues considering I don't/can't experience them. But believe me when I say it that apple devices tend to have a lot of issues by itself (Will leave the list behind for now). We tend to get used to some of the issues after experiencing a product/software experience for quite long considering we tend to work around them. From a technical perspective an SSID is to "Define" a network, basically every access point with the same SSID should be configured to have WiFi Roaming, if your network does not support this feature its effectively asking for issues. Basically, whenever a device connects to the network the first thing it does is to set up a "session" with the specific SSID, once the session has been established it will try to request an IP Address from the DHCP server. Depending on the implementation of the vendor of the AP (Access point) the following oddities might occur if your network is not enabled for WiFi Roaming. 1: If each device has its own DHCP, it will have to get a new IP address. 2: The session is not "transferred" (Because simply stated, it can't be transferred). Your phone might just be thinking that its still connected to the same network because the SSID is the same, even though it isn't. The Considering the SSID is intended to be the unique identifier for the WiFi-Network I would say that its reasonable to assume that the phone uses that to identify the network itself. I guess that apple itself tends to kill the session off in the background whenever a ping to their servers tends to fail which works too but has its own issues (Something with killing sessions is never a clear solution if you just want to transfer it) and a constant ping/check in the background does cost some battery. Instead there is simply the decision to check for the SSID, if it changes or if the signal gets too weak it will simply switch to the nearest one that it remembers. At my work we have roaming and we get zero complaints about Galaxy 10 users that can't transfer their session properly I also know another school in the area that intentionally uses a different SSID for every classroom to save costs for this feature and to prevent issues. Anyhow, both approaches have its up and downsides, but I can't really see it as a flaw at Samsungs side. Its clearly something that its wrong on the networking side (Roaming is simply not supported in the networking infrastructure). Can't blame a device for keeping itself properly to the standards. Basically it looks like this is an ages old decision with android, not really a Samsung specefic thing: https://www.reddit.com/r/Android/comments/3z9pi5/wifi_roaming_between_aps_with_the_same_ssid/
... View more
