Bonjour,
J'ai vu le meme probleme il ya plusieurs mois sur un Galaxy Note 3 et l'Internet-box. (meme SSID sur le Wlan 2.4 et 5G)
J'observais des coupures / lenteurs de la connectivité Internet depuis ce smartphone mais pas depuis mon PC.
Apres quelques investigations j'ai indentifié que le Wlan 5GHz posait probleme.
J'ai utilisé l'outils "Réseau Signal Info de KAIBITS Software" pour identifier sur quel réseau Wlan j'etais connecté et verifier que je n'avais pas de probleme de Signal.
Lorsque le problème apparaissait le Smartphone était toujours connecté/associé au Wlan 5GHz mais les paquets semblaient bloqués durant 20, 30, voir 60 secs et libérés après.
J'ai identifié ce phénomeme en lancant un ping 192.168.1.1 depuis un Terminal (termmux, juicessh....).
~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
(Durant le probleme)
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=12074 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=11067 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=10060 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=9060 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=8060 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=7049 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=6040 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=5040 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=4040 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=3039 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2029 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1020 ms
(Ca refonctionne pour qq minutes)
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=21.4 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=15.7 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=9.58 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=33.0 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=6.74 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=85.6 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=8.12 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=14.3 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=14.4 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=14.5 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=13.6 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=11.3 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=8.67 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=15.0 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=11.6 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=5.25 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=14.0 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=17.7 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=11.4 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=2.60 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=6.15 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=94.1 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=32.5 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=12.7 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=8.63 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=15.0 ms
64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=8.25 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=11.6 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=14.3 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=2.99 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=14.3 ms
64 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=2.83 ms
64 bytes from 192.168.1.1: icmp_seq=45 ttl=64 time=14.2 ms
64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=155 ms
(De nouveau un probleme)
64 bytes from 192.168.1.1: icmp_seq=47 ttl=64 time=18048 ms
64 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=17041 ms
64 bytes from 192.168.1.1: icmp_seq=49 ttl=64 time=16041 ms
64 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=15041 ms
64 bytes from 192.168.1.1: icmp_seq=51 ttl=64 time=14041 ms
64 bytes from 192.168.1.1: icmp_seq=52 ttl=64 time=13041 ms
64 bytes from 192.168.1.1: icmp_seq=53 ttl=64 time=12041 ms
64 bytes from 192.168.1.1: icmp_seq=54 ttl=64 time=11031 ms
64 bytes from 192.168.1.1: icmp_seq=55 ttl=64 time=10032 ms
64 bytes from 192.168.1.1: icmp_seq=56 ttl=64 time=9032 ms
64 bytes from 192.168.1.1: icmp_seq=57 ttl=64 time=8032 ms
64 bytes from 192.168.1.1: icmp_seq=58 ttl=64 time=7032 ms
64 bytes from 192.168.1.1: icmp_seq=59 ttl=64 time=6032 ms
64 bytes from 192.168.1.1: icmp_seq=60 ttl=64 time=5032 ms
64 bytes from 192.168.1.1: icmp_seq=61 ttl=64 time=4032 ms
64 bytes from 192.168.1.1: icmp_seq=62 ttl=64 time=3031 ms
64 bytes from 192.168.1.1: icmp_seq=63 ttl=64 time=2032 ms
64 bytes from 192.168.1.1: icmp_seq=64 ttl=64 time=1032 ms
64 bytes from 192.168.1.1: icmp_seq=65 ttl=64 time=32.3 ms
J'ai trouvé plusieurs solutions à mon problème:
- En séparerant les réseaux Wlan 2.4Ghz & 5GHz sur l'internet box et en preferant le 2.4GHz
- En désactivant le Wlan Power Saving sur le Galaxy Note3 via les menu de service Samsung
- En migrant vers le Galaxy S6 😉
Vous pouvez confirmer si vous observez le meme phénomene sur le réseau 5GHz et si la latence des pings augmente durant les "coupures"?