WiFi on Android phones dropping

janspambox · Wed Aug 01, 2018 3:30 pm

Hi,
I have two Android phones, and when I'm actively using them in some of the worse-covered areas of my apartment, they keep getting disconnected for a few seconds every couple minutes, which is extremely annoying (page loads fail, VoIP calls drop). I'm running a WiFi on both 2.4 and 5 GHz, same name. In the logs I see this:

  529 Aug/01/2018 13:59:37  memory  wireless, info  <Pixel2>@wlan4: connected, signal strength -63 
  530 Aug/01/2018 13:59:37  memory  wireless, info  <Pixel2>@wlan3: disconnected, registered to other interface  
  531 Aug/01/2018 13:59:40  memory  wireless, info  <Pixel2>@wlan4: disconnected, received deauth: sending station leaving (3) 
  532 Aug/01/2018 13:59:43  memory  wireless, info  <Pixel2>@wlan4: connected, signal strength -66 
  533 Aug/01/2018 13:59:43  memory  dhcp, info  dhcp-guest deassigned <localip1> from <Pixel2> 
  534 Aug/01/2018 13:59:43  memory  dhcp, info  dhcp-guest assigned <localip1> to <Pixel2> 

  535 Aug/01/2018 14:01:01  memory  wireless, info  <Pixel2>@wlan3: connected, signal strength -64 
  536 Aug/01/2018 14:01:01  memory  wireless, info  <Pixel2>@wlan4: disconnected, registered to other interface  
  537 Aug/01/2018 14:02:11  memory  wireless, info  <Pixel2>@wlan4: connected, signal strength -62 
  538 Aug/01/2018 14:02:11  memory  wireless, info  <Pixel2>@wlan3: disconnected, registered to other interface  
  539 Aug/01/2018 14:02:14  memory  wireless, info  <Pixel2>@wlan4: disconnected, received deauth: sending station leaving (3) 
  540 Aug/01/2018 14:02:16  memory  wireless, info  <Pixel2>@wlan4: connected, signal strength -62 
  541 Aug/01/2018 14:02:16  memory  dhcp, info  dhcp-guest deassigned <localip1> from <Pixel2> 
  542 Aug/01/2018 14:02:16  memory  dhcp, info  dhcp-guest assigned <localip1> to <Pixel2>

What I suspect is happening is that the phone is trying to switch from one WiFi to the other, establishes the second connection, gets kicked out of the first one before the second one is ready, panics, and drops the new connection too.

I've also seen a second, periodic failure mode (something like "every 15 minutes on the minute but sometimes skipping one") but the above issue is preventing me from easily determining whether that one is still there.

Niffchen · Thu Aug 02, 2018 11:56 am

For me it seems that you have more than one AP at this area with the same signal strength and your Phone changes if another AP has a better signal.
Do you tried to power off all APs instead of one and then connect again? If this is as you suggested I would expect that everything works fine with only one AP.

AlainCasault · Thu Aug 02, 2018 1:04 pm

Maybe you could describe your setup but it sure looks that way. If you do have two APs, try the previous suggesting. Then try to lower one so that both are not "heard" at close to equal strength.
While in any spot, there should always be a fair difference in signal strength between both APs otherwise you'll get roaming issues and possible ACI issues.

Regards

Sent from Tapatalk

Niffchen · Thu Aug 02, 2018 1:51 pm

Maybe you could describe your setup but it sure looks that way. If you do have two APs, try the previous suggesting. Then try to lower one so that both are not "heard" at close to equal strength.
While in any spot, there should always be a fair difference in signal strength between both APs otherwise you'll get roaming issues and possible ACI issues.

Regards

Sent from Tapatalk

Or he could change Android phone for iPhone and will get this strange behaviour never again ... because iPhone will not change to better AP without a good reason and would use the one with weak signal until signal is gone

Only a joke ... ignore it

AlainCasault · Thu Aug 02, 2018 2:41 pm

Maybe you could describe your setup but it sure looks that way. If you do have two APs, try the previous suggesting. Then try to lower one so that both are not "heard" at close to equal strength.
While in any spot, there should always be a fair difference in signal strength between both APs otherwise you'll get roaming issues and possible ACI issues.

Regards

Sent from Tapatalk
Or he could change Android phone for iPhone and will get this strange behaviour never again ... because iPhone will not change to better AP without a good reason and would use the one with weak signal until signal is gone
Only a joke ... ignore it

Sent from Tapatalk

janspambox · Fri Aug 03, 2018 4:25 am

The Mikrotik router in question is the only AP I have, and it offers one 2.4 GHz and one 5 GHz WiFi with the same SSID. This happens when the phone is switching from one to the other (possibly only in one direction). I managed to reproduce this issue and capture a bug report on the Android device (this time a Pixel 2).

These events happened as I moved the phone to an area with slightly worse (but still OK) WiFi coverage.

02:05:51 wireless,info <Pixel 2>@wlan4: connected, signal strength -58
02:05:51 wireless,info <Pixel 2>@wlan3: disconnected, registered to other interface
02:05:55 wireless,info <Pixel 2>@wlan4: disconnected, received deauth: sending station leaving (3)
02:05:57 wireless,info <Pixel 2>@wlan4: connected, signal strength -64
02:05:57 dhcp,info dhcp-guest deassigned 192.168.10.216 from <Pixel 2>
02:05:57 dhcp,info dhcp-guest assigned 192.168.10.216 to <Pixel 2>
02:06:28 wireless,info <Pixel 2>@wlan3: connected, signal strength -51
02:06:28 wireless,info <Pixel 2>@wlan4: disconnected, registered to other interface

On the Android device (add 10 seconds to the phone timestamps to match the time shown in router time stamps):

08-03 02:05:41.906  wifi  2165  2165 D wpa_supplicant:   * roam BSSID <Mikrotik 'wlan4'>
08-03 02:05:41.906  wifi  2165  2165 D wpa_supplicant: nl80211: Roam event
08-03 02:05:41.906  wifi  2165  2165 D wpa_supplicant: nl80211: Set drv->ssid based on req_ie to '<ssid>'
08-03 02:05:41.906  wifi  2165  2165 D wpa_supplicant: nl80211: Associated on 2452 MHz
08-03 02:05:41.906  wifi  2165  2165 D wpa_supplicant: nl80211: Associated with <Mikrotik 'wlan4'>
[...]
08-03 02:05:44.978  wifi  2165  2165 D wpa_supplicant: wlan0: Cancelling scan request
08-03 02:05:44.978  wifi  2165  2165 D wpa_supplicant: wlan0: Request to deauthenticate - bssid=<Mikrotik 'wlan4'> pending_bssid=00:00:00:00:00:00 reason=3 state=COMPLETED

Interestingly, the MAC address of the "wlan3" interface isn't mentioned in the Android log between these two events (last mention before that at 02:05:27 phone time pointing out that the scan shows being associated to it, next mention at 02:05:47 phone time when it apparently tries to reconnect to both).

Or he could change Android phone for iPhone and will get this strange behaviour never again

You may be joking but I seriously considered that (and slightly less seriously considered throwing all my electronics into the bin and moving to a cave in the woods). I'm so sick of having to debug technology that really should just work.

Keep in mind that it is quite possible that this is an Android bug. It'd be good to know which device (router or phone) to start with if I decide to solve the problem by replacing hardware by new one from different vendors until things start to work in a satisfactory manner.

Niffchen · Fri Aug 03, 2018 3:20 pm

You may be joking but I seriously considered that (and slightly less seriously considered throwing all my electronics into the bin and moving to a cave in the woods). I'm so sick of having to debug technology that really should just work.

Keep in mind that it is quite possible that this is an Android bug. It'd be good to know which device (router or phone) to start with if I decide to solve the problem by replacing hardware by new one from different vendors until things start to work in a satisfactory manner.

For me it looks like a normal behaviour of a client which is roaming at low signal strength.
If you only have 1 AP your phone is switching from 2GHz to 5GHz? Is it switching only from 5GHz to 2GHz or different direction or both like a flip-flop? What happens if you stay at a place 1 or 2 meter beside your AP? Is the 2GHz/5GHz network stable, means the phone is not switching?
Do you have any access rules for your wireless lan like accept at signal strength better than xx and reject at signal strength worth than yy?

I am asking these questions because this behaviour would normally be what a user is expecting. If you use 5GHz because it is faster than 2GHz and you are leaving the range of this network my client is also switching to 2GHz and I am going surfing on the web without a interrupt.

rushlife · Sun Sep 09, 2018 12:24 pm

I have this problem too, in log: received deauth, sending station leaving.
I have 4 APs, managed with capsman. Phone is (sometimes) flapping between APs, struggling with choose one of then to connect.

mkx · Sun Sep 09, 2018 1:13 pm

I have this problem too, in log: received deauth, sending station leaving.
I have 4 APs, managed with capsman. Phone is (sometimes) flapping between APs, struggling with choose one of then to connect.

Try to pinpoint where this happens. If the signal strength of both APs is not good (e.g. below -70dBm) and it's a place where wifi clients tend to stay (like: not in the corridor where everybody will just pass but a sitting area), then you'll have to improve signal ... possibly by installing additional AP or by moving one of original APs closer.
If the signal strength of both APs is good, then you can still try to make one of them better than another one just to avoid ping-pong effect. But I guess most of WiFi clients won't just roam to another AP with slightly better signal if the current one is good. There's an exception to this: some devices will prefer 5GHz AP over 2.4GHz one even if 5GHz signal is considerably worse than 2.4GHz signal. In this case you just have to improve 5GHz signal ... or get rid of it entirely in the trouble area.

Creating well performing multi-transmitter network is not an easy task and one must understand the mechanisms of roaming/handover to avoid many associated problems. As WiFi was not created with mobility as one of main goals, number of problems is even higher than when building network based on truely mobile technology (such as LTE).

janspambox · Tue Jul 30, 2019 11:12 am

I've just reproduced this on my third Android phone. It's happening in the same room with the router. The worst RSSI I was able to measure was -67. It's extremely annoying because it keeps dropping my calls.

If I had to guess, I'd say the problem seems to be that the router disconnects the phone on one of the two frequencies when it connects on the other one, and this disconnect causes it to drop the connection entirely.

yottabit · Tue Dec 10, 2019 3:53 am

I'm still having this problem. Updated to latest ROS. Android 10 shows flapping the Wi-Fi with a dim Wi-Fi icon. Going to Wi-Fi settings shows connected/no Internet, and then it starts again.

It seems like the switch FIB is blocking when it sees a MAC quickly switch from one AP to another. My extension RB sees my phone MAC on its station-bridge interface (connected to the other AP), and then the phone attempts to roam to the extension RB and it freaks out because it sees the same MAC show up on the AP interface.

It should just replace the FIB entry with the latest interface where it sees the frame, rather than blocking it and causing the phone to fail its attachment.

Sent from my Pixel 3 using Tapatalk

RB951G2HnD · Tue Dec 10, 2019 2:42 pm

I have had the same problem. I think it solved now – may need to retest. I have an AP with two IAPs: wlan1 – 2.4 GHz and wlan2 – 5 GHz. My mistake was that I set transmit power for both radios to be equal. That caused software logic of android phone to be jumping between radios where is the signal strength is better. Thus in the log file I saw wlan2 – wlan1 – wlan2 - wlan1 and so on.

yottabit · Tue Dec 10, 2019 11:45 pm

My problem isn't that Android hops between them. My problem is that after Android has made the decision to jump to the other radio, its Internet reachability test fails (presuming the RB is blocking the frames as it still believes the same MAC is reachable on another interface), and so Android disconnects, and then continues to attempt reconnecting to the new radio over and over again, with the same error repeating.

I have experimented by turning off route caching, in case this is locking the layer-2 FIB record.

If I see it again, I will experiment by turning on RSTP, in case that allows prevention of this by "trusting" that there is no loop. I would prefer to keep RSTP/STP disabled to prevent the extra broadcasts over the Wi-Fi, though.

yottabit · Thu Jan 02, 2020 9:15 pm

That didn't help. I also turned on RSTP to see if that would help, and it didn't.

I haven't had time to correlate the logs yet to see if the routers actually show anything obvious during this behavior.

Sent from my Pixel 3 using Tapatalk

yottabit · Wed Jan 15, 2020 4:27 am

Here's my network topology:

rb1 (hap ac2, router, no wifi) <--eth--> rb2 (hap ac, wifi ap only) <--wifi--> masterbedroom (hap ac, wifi ap only)

And here is the utter junk I keep getting with my Pixel 3 Android 10 phone trying to roam from rb2 to masterbedroom (notice you don't see any log entries from rb2):

Jan 14 20:22:24 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:22:24 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:22:24 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -42
Jan 14 20:22:24 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -42
Jan 14 20:22:39 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:39 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:39 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:22:39 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:22:39 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:22:39 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:22:39 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D
Jan 14 20:22:39 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D
Jan 14 20:22:42 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:42 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:42 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:22:42 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:22:42 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -44
Jan 14 20:22:42 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -44
Jan 14 20:22:42 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D
Jan 14 20:22:42 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D
Jan 14 20:22:45 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:45 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:45 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:22:45 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:22:45 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -42
Jan 14 20:22:45 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -42
Jan 14 20:22:45 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D
Jan 14 20:22:45 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D
Jan 14 20:22:56 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:56 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:57 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:22:57 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:22:57 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:22:57 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:22:57 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D
Jan 14 20:22:57 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D
Jan 14 20:22:59 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:22:59 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:23:00 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:23:00 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:23:00 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:23:00 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:23:02 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D
Jan 14 20:23:02 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D
Jan 14 20:23:04 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:23:04 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:23:05 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:23:05 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:23:05 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:23:05 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -43
Jan 14 20:23:10 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D                         
Jan 14 20:23:10 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D                                           
Jan 14 20:23:13 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:23:13 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: disconnected, received deauth: sending station leaving (3)
Jan 14 20:26:27 <daemon.err> rb2 rb2 login failure for user admin from 172.16.42.102 via web                                                    
Jan 14 20:26:28 <daemon.info> rb2 rb2 user yottabit logged in from 172.16.42.102 via web                                                               
Jan 14 20:26:46 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D attempts to associate
Jan 14 20:26:46 <daemon.debug> masterbedroom masterbedroom debug: wlan2-ap: 3C:28:6D:0A:B2:1D not in local ACL, by default accept
Jan 14 20:26:46 <daemon.info> masterbedroom masterbedroom 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -42
Jan 14 20:26:46 <daemon.info> masterbedroom masterbedroom debug: 3C:28:6D:0A:B2:1D@wlan2-ap: connected, signal strength -42
Jan 14 20:26:46 <daemon.info> rb1 rb1 dhcp1 deassigned 172.16.42.68 from 3C:28:6D:0A:B2:1D
Jan 14 20:26:46 <daemon.info> rb2 rb2 3C:28:6D:0A:B2:1D@wlan2-5G: disconnected, received deauth: class 3 frame received (7)
Jan 14 20:26:46 <daemon.info> rb2 rb2 debug: 3C:28:6D:0A:B2:1D@wlan2-5G: disconnected, received deauth: class 3 frame received (7)              
Jan 14 20:26:46 <daemon.info> rb1 rb1 dhcp1 assigned 172.16.42.68 to 3C:28:6D:0A:B2:1D

This goes on for ~5 minutes until the phone finally joins the masterbedroom AP. Absolute nightmare.

It looks like the phone isn't properly leaving the rb2 AP first, and eventually it times out, and only at that point can it successfully connect to masterbedroom. I assume this is something in Router OS trying to be "too" smart, but I still don't know how it would work. The DHCP server won't know because it will always see the same MAC, and that MAC is not connected to the local device, but through an ethernet cable (it doesn't know if it's on the first hop, rb2, or the second hop, masterbedroom). Now rb2 may be the problem. It may think the MAC is still connected on its local AP interface directly, and throw a fit when it sees the MAC try to come from a station-bridge MAC. I assume rb2 is blocking the MAC and causing the problem.

yottabit · Wed Feb 19, 2020 1:35 am

I converted AP masterbedroom from repeater-like configuration to WDS. Problem solved.

Doesn't make any sense, but at least I don't have the problem anymore. I have not heard anything back from MikroTik support.

Luckily, on this AP I don't need the higher throughput that repeater mode tends to provide, so I'm happy enough to use WDS mode.

WiFi on Android phones dropping

WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Re: WiFi on Android phones dropping

Who is online