WiFi issue with Samsung S4 on RB2011UAS-2HnD-IN

My WiFi network on RB2011UAS-2HnD-IN has been on for more than 9 months now, without any issue. Mac, iPhones, PC, … connect to it without any problem.

I have now purchased a Samsung Galaxy S4 but after connecting successfully to my WiFI, now and then it disconnects from the network after a few minutes, or sometimes a few hours.

Some Samsung or Android forums mention about possible issues with WiFi and Samsung S4. But I could not really figure out what exactly it was about.

When connecting to a 5 GHz Network on an Apple Airport Extreme, the Samsung keeps the connection without problems.

The problem only arises on my Mikrotik.


Any ideas ?

XX:XX:XX:XX@wlan1:disconnected: extensive data loss

or

XX:XX:XX:XX@wlan1:group key exchange timeout

My Wireless config on RouterOS 5.25 is :

interface wireless print basic :

name="wlan1" mtu=1500 mac-address=D4:CA:6D:63:00:54 arp=reply-only interface-type=Atheros AR9300 mode=ap-bridge ssid="Fred Network" 
      frequency=2437 band=2ghz-b/g/n channel-width=20mhz scan-list=default wireless-protocol=unspecified wds-mode=disabled 
      wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 
      default-client-tx-limit=0 hide-ssid=no security-profile=WPA compression=no

interface wireless security-profiles print :

name="WPA" mode=dynamic-keys authentication-types=wpa2-psk unicast-ciphers=aes-ccm group-ciphers=aes-ccm wpa-pre-shared-key="" 
     wpa2-pre-shared-key="xxxxxxxxxxx" supplicant-identity="MikroTik" eap-methods="" tls-mode=no-certificates tls-certificate=none 
     static-algo-0=none static-key-0="" static-algo-1=none static-key-1="" static-algo-2=none static-key-2="" static-algo-3=none 
     static-key-3="" static-transmit-key=key-0 static-sta-private-algo=none static-sta-private-key="" radius-mac-authentication=no 
     radius-mac-accounting=no radius-eap-accounting=no interim-update=0s radius-mac-format=XX:XX:XX:XX:XX:XX radius-mac-mode=as-username 
     radius-mac-caching=disabled group-key-update=5m management-protection=disabled management-protection-key=""

Have same issue in two different locations, both running on 5.25

Any idea?

Last night I tired a trick to switch off WiFi power saving through service mode on my S4

*#1111#

Menu->WiFi → Swich Off WIFI Power Save Mode

Today morning I got Firmware update from Samsung and it looks like the problem is gone.
After firmware update WIFI Power Save Mode is On again.

Some will say this is not related to Mikrotik, but same problems exists on S4 and HTC One that we have in the office,
and it is related to some Routers brands including MikroTik.

Power Saving is not fully supported, you must turn it off on the phone.

my colleague also says me about wi fi issue in Samsung galaxy S4.

Will power saving be fully supported or do i still need to reconfig all s4 and other problematic devices with power save?

What version of android installed in your sgs4?
I have the same problem in sgs2 and note 10.1. Androind 4.1.2 installed on these gadgets.

Switch Multicast Helper to Full in the wireless settings of your AP.

Then try enabling Power Save on the phone again. It should work fine.

Has this problem ever been resolved in RouterOS or Samsung devices still can’t connect to the RB2011UAS-2HnD-IN?

RB2011UAS-2HnD-IN, RouterOS v6.29.1, Samsung Galaxy SII with Android 4.1.2, firmware I9100XXLS8.

Connects to RB 2-3 times longer than to any other access point and then, if the phone was laying with the screen turned off on timeout, can’t communicate over network although WiFi state is “connected”. I have to turn Wi-Fi on the phone off and back on to work further. RB2011UAS-2HnD-IN is the only device it has problems with. (I do not have any other Mikrotik device, so it could be possibly an issue with any Mikrotik device).

It does not depend on WiFi on/off policy and occurs even when it is set to “always on”.

Setting Multicast Helper to Full didn’t help.

Update

The issue seems to be related to DHCP in some way. After I set IP address to static, all the problems are gone. I’ll test it with static IP for another couple of weeks to be sure and then will torture the DHCP in the router.