4.3 Update: It looks like Android 4.3 (JWR66V) did not fix the Nexus 4 delayed notifications on wifi issue. New wifi drivers with ARP offload support are included but for some unknown reason, Google disabled ARP offload in this release (even though ARP offload was enabled in the leaked 4.3 version). Interestingly, ARP offload is now re-enabled in AOSP JSS15J.
If you are on JWR66V and still have delayed notifications on wifi, then check this post for instructions on how to enable ARP offload either manually or with a flashable ZIP: http://forum.xda-developers.com/showpost.php?p=43940926&postcount=601. Only do this if you are running 4.3 JWR66V.
An alternative option is to try disabling wifi optimization. Some people have found this fixes the delayed notification problem but also causes an increased battery drain.
----------------------------
Below is for Android 4.2 builds only
Update: Android 4.2.2 is out and despite a comment from a Google rep that this was fixed and the fix was scheduled to be included in 4.2.2, it appears that isn't the case. This same rep from Google just confirmed as much in post 34 - https://code.google.com/p/android/issues/detail?id=42272#c34.
I've confirmed the workaround described in this thread does still work on 4.2.2. Also, the ini file that this workaround changes was untouched between 4.2.1 and 4.2.2 so the same zip files posted here will work on either version.
Also, thanks to thesebastian for finding this - it looks like Qualcomm is finally getting ARP Offload fixed (http://forum.xda-developers.com/showpost.php?p=38598963&postcount=267). Hopefully they will get this pushed out sometime soon.
------------------
Since the Nexus 4 was released, there have been many reports of various problems with wifi. Everything from slow speeds to delayed notifications to not being able to connect to certain APs at all. With the release of Android 4.2.2, a lot of these problems have been fixed. Unfortunately, a number of issues still remain.
One issue that has yet to be fixed as of 4.2.2 is the ability for the phone to respond to ARP requests while the screen is off. This results in the phone being unable to receive network traffic over wifi under certain circumstances while asleep. The most noticeable effect of this issue is notifications being delayed for up to 15 minutes while the screen is off. During this time, turning the screen on will result in these delayed notifications flooding in all at once. You may also notice the wifi signal indicator turning gray immediately after turning the screen on followed a few seconds later by it turning blue. Another symptom that some have had is incoming VoIP calls not ringing the phone while the screen is off but working fine while the screen is on.
This issue has been confirmed by Google (https://code.google.com/p/android/issues/detail?id=42272) and is related to a buggy implementation of ARP Offload in the Nexus 4 wifi driver. Due to this, ARP Offload is disabled on the N4. In addition, the N4 wifi driver is set to filter all incoming broadcast and multicast traffic during sleep. Since ARP is broadcast (usually), the combination of these settings will prevent the phone from hearing and responding to ARP requests while the screen is off. If a neighboring network device (such as your router) is unable to obtain the MAC address of the phone, it will be unable to send any traffic to the phone.
Please note that this issue only affects the Nexus 4 (and possibly other devices with the Prima wifi chip). Wifi issues on other devices are not affected by this particular issue. Also note, this is one particular issue with the N4 wifi. There are lots of other issues. The workarounds described here will not help with those issues.
Also, even though all Nexus 4's are affected by this issue, not everyone will be affected in the same way. One of the main reasons for this is due to varying router configurations (in particular, the ARP cache timers). Some will even be lucky enough to have this problem completely masked due to their router configuration. If you are so lucky, you can still see the effect of this issue - turn the screen off, wait a few minutes, and ping the phone from your PC. While doing this run Wireshark and notice the unanswered ARP queries being sent to your phone.
----------------
Until Google releases a proper fix (ARP Offload), there are a couple of options to work around this issue.
Option 1 - Static ARP
The easiest fix is to add a static ARP entry for your N4 to your router. This allows the router to communicate with the phone without having to bother with the ARP process (thereby bypassing the issue completely). On some routers, there is an option to directly add a static ARP entry. On some, you have to do it via the CLI. On some, adding a static DHCP lease also adds a static ARP entry. And of course some just don't allow you to set this.
There are a couple of negatives. First, you may not have access to all routers that you connect to. Even if you do have access, you may not be able to set a static ARP depending on the firmware on the router. Also, you would have to add a static ARP to every device on the same network segment that you would want to communicate with. Say for example you used wireless ADB. In that case you would have to add a static ARP to both the router and the PC that you ran ADB on.
The positive to adding a static ARP entry is you don't have to muck with a system file on the phone and this option is the most battery efficient.
Option 2 - Disable filtering on the N4
Another solution is to disable the unicast and/or multicast filtering on your N4 by modifying an ini file on the phone. This will allow the phone to see all broadcast traffic (including ARP) during sleep. As a result the phone will be able to properly respond to ARP requests.
The positive is once you make this change, the phone will properly respond to ARP requests without having to make any other changes. It will work with any wifi network that you connect to.
The negative is making this change will cause a negative impact on battery life. How much of an impact depends entirely on how much broadcast and multicast traffic exists on your network. The more traffic, the more the phone is woken up, the more the battery hit will be. The only way to know how much of a battery impact you will have is to test it out.
To make the ini file change manually (see below for installable zip files):
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=0"
Save the file and double check file permissions (-rw-r--r-- root root)
Reboot the phone
To undo this change, simply change the "0" back to the original value of "3". If you want to prevent the the phone from hearing multicast traffic while the screen is off but still allow broadcast traffic, you could change the value to "1". This may help with battery life and will keep most things working.
Please remember, this changes a system file so 2 things. First, I'm not responsible if you break something. Second, this will likely prevent the phone from being able to get an OTA. You would need to revert the change before applying an OTA.
--------------------
One other router setting that can cause the same type of issue that some have run into is related to the TCP Established timer. If you are still having this problem after making the ini file change (or static ARP), make sure that the TCP Established timer on your router is set to at least 1200 seconds.
------------------------------------------
Edit 12/31: I attached CWM installable zip files to make changing the ini file easier and help prevent file permission problems, etc. I tested all 3 files with my Nexus 4 using CWM 6.0.2.3.
n4-wifi-sleepfix-restore-original.zip -- This restores the ini file to the original one from stock 4.2.1 JOP40D / 4.2.2 JDQ39.
n4-wifi-sleepfix-mcast_and_bcast.zip -- This sets McastBcastFilter to 0, allowing the phone to hear multicast and broadcast traffic during sleep. Only for 4.2.1 JOP40D / 4.2.2 JDQ39.
n4-wifi-sleepfix-bcast_only.zip -- This sets McastBcastFilter to 1, allowing the phone to hear broadcast traffic during sleep, but not multicast. Only for 4.2.1 JOP40D / 4.2.2 JDQ39.
Don't forget to make a CWM backup first!
bganley said:
Since getting the Nexus 4, I've had problems with wifi network connectivity while the screen is off. The phone will stay associated to the AP (as can be verified by looking at the AP itself), but after a couple minutes of screen-off time, incoming network traffic seems to be ignored by the phone. I also have a Nexus 7, a Galaxy Nexus, and an Atrix - none of which have this problem.
The symptoms are things like gmail notifications taking up to 15 minutes to arrive while the screen is off. Another symptom is seeing the wifi indicator turn gray followed a few seconds later by the indicator turning blue again immediately after turning the screen on.
An easy way to see the issue is to ping the phone from another device connected to the same network segment. Turn the screen on, ping the phone and you should get a response as expected. Turn the screen off, wait a few minutes and try to ping the phone again and you will likely get a timeout. The amount of time you have to wait depends on the OS of the device you are sending the ping from (more specifically the ARP cache timeout).
Doing a network capture, I found the issue that I've been having is the phone doesn't respond to ARP requests while the screen is off. One easy fix that I've been using for a couple of days is to add a static ARP entry. I added one to my router so that it doesn't need to perform an ARP request when sending traffic to the phone. Since doing this I've had 0 problems. Gmail notifications now come in faster on my Nexus 4 than any other android device I own. I also never see the wifi indicator turning gray any more.
I've been doing some more digging and I think I found a better solution to the issue. There is an ini file that allows you to set parameters for the wifi driver on the phone. One of these parameters controls the filtering of multicast and broadcast traffic during power save. The default on the Nexus 4 is to filter all broadcast and multicast traffic. Since ARP requests are broadcast, this is obviously an issue.
I tried changing the parameter to only filter multicast traffic and so far so good. The phone takes a couple of seconds to respond to ARP requests while the screen is off (which is expected during low power states) but it now does respond. Now I just need to run this for a couple of days and see what kind of impact it will have on the battery.
To make the ini file change:
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=1"
Save the file and reboot
To undo this change, simply change the "1" back to the original value of "3". If you want the phone to hear multicast traffic while the screen is off, you could change the value to "0".
Please remember, this changes a system file so 2 things. First, I'm not responsible if you break something. Second, this will likely prevent the phone from being able to get an OTA. You would need to revert the change before applying an OTA.
I just wanted to pass this along and see if anyone else has been experiencing this issue. If so, hopefully this info will help prevent others from wanting to smash their phone into a million bits.
Click to expand...
Click to collapse
You're my hero. I'm not rooted and don't want to mess with this yet but curious about static ARP. Assuming you do this by turning on Mac address filtering and adding the N4 Mac address to router. I don't see any way to edit the ARP table on my Cisco E4200
Sent from my Nexus 4 using Tapatalk 2
I recently got a Nexus 7 and i can definitely see a difference in wifi performance. I wish i could fix it
mobilehavoc said:
You're my hero. I'm not rooted and don't want to mess with this yet but curious about static ARP. Assuming you do this by turning on Mac address filtering and adding the N4 Mac address to router. I don't see any way to edit the ARP table on my Cisco E4200
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
MAC address filtering is different from a static ARP entry. MAC filtering just defines which MAC addresses are allowed to associate to an access point. A static ARP entry is a way to manually define the MAC address associated with a specific IP address. Normally, the ARP protocol takes care of this for you by broadcasting an ARP request. The device which has the IP address in question sees that broadcast and replies back with its MAC address. Since the phone isn't listening to broadcast traffic while the screen is off, it will never see the ARP request and thus will not respond to an ARP request while the screen is off. Setting a static ARP entry just bypasses the need for the normal ARP processing as the sending device will always know the MAC address of the device it is trying to send a packet to.
I don't have an E4200 so I'm not sure what options it has. On my router, I can telnet to a linux shell on it which allows me to add a static ARP entry with the command "arp -s ip-address mac-address". This adds a static entry to the ARP cache which will be lost on reboot. Of course, you could just add it to a startup script so that it would be added every time the router reboots.
I've heard reports that some routers will effectively add a static ARP entry if you define a static DHCP reservation. You could try that. Somewhere in your router you should be able to say that the MAC address of your phone should always get assigned a specific IP address from DHCP. Actually, I would highly recommend that anyone who wants to try the static ARP method do this regardless. If you specify IP address X equals MAC address Y, it would be a good idea that it always does
Let us know if you have any luck figuring out how to do this on an E4200.
bganley said:
Since getting the Nexus 4, I've had problems with wifi network connectivity while the screen is off. The phone will stay associated to the AP (as can be verified by looking at the AP itself), but after a couple minutes of screen-off time, incoming network traffic seems to be ignored by the phone. I also have a Nexus 7, a Galaxy Nexus, and an Atrix - none of which have this problem.
The symptoms are things like gmail notifications taking up to 15 minutes to arrive while the screen is off. Another symptom is seeing the wifi indicator turn gray followed a few seconds later by the indicator turning blue again immediately after turning the screen on.
An easy way to see the issue is to ping the phone from another device connected to the same network segment. Turn the screen on, ping the phone and you should get a response as expected. Turn the screen off, wait a few minutes and try to ping the phone again and you will likely get a timeout. The amount of time you have to wait depends on the OS of the device you are sending the ping from (more specifically the ARP cache timeout).
Doing a network capture, I found the issue that I've been having is the phone doesn't respond to ARP requests while the screen is off. One easy fix that I've been using for a couple of days is to add a static ARP entry. I added one to my router so that it doesn't need to perform an ARP request when sending traffic to the phone. Since doing this I've had 0 problems. Gmail notifications now come in faster on my Nexus 4 than any other android device I own. I also never see the wifi indicator turning gray any more.
I've been doing some more digging and I think I found a better solution to the issue. There is an ini file that allows you to set parameters for the wifi driver on the phone. One of these parameters controls the filtering of multicast and broadcast traffic during power save. The default on the Nexus 4 is to filter all broadcast and multicast traffic. Since ARP requests are broadcast, this is obviously an issue.
I tried changing the parameter to only filter multicast traffic and so far so good. The phone takes a couple of seconds to respond to ARP requests while the screen is off (which is expected during low power states) but it now does respond. Now I just need to run this for a couple of days and see what kind of impact it will have on the battery.
To make the ini file change:
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=1"
Save the file and reboot
To undo this change, simply change the "1" back to the original value of "3". If you want the phone to hear multicast traffic while the screen is off, you could change the value to "0".
Please remember, this changes a system file so 2 things. First, I'm not responsible if you break something. Second, this will likely prevent the phone from being able to get an OTA. You would need to revert the change before applying an OTA.
I just wanted to pass this along and see if anyone else has been experiencing this issue. If so, hopefully this info will help prevent others from wanting to smash their phone into a million bits.
Click to expand...
Click to collapse
Thank you, but edit "WCNSS_qcom_cfg.ini" not works for me. WiFi simbol nether apears, even when I return to option "3". I used cwm restore and it returned like before (conect but transfer data only for 15 seconds).
Enviado de meu Nexus 4 usando o Tapatalk 2
The ini change just made wifi fail to start for me, unfortunately.
Lucena04 said:
Thank you, but edit "WCNSS_qcom_cfg.ini" not works for me. WiFi simbol nether apears, even when I return to option "3". I used cwm restore and it returned like before (conect but transfer data only for 15 seconds).
Enviado de meu Nexus 4 usando o Tapatalk 2
Click to expand...
Click to collapse
adamase said:
The ini change just made wifi fail to start for me, unfortunately.
Click to expand...
Click to collapse
Sorry to hear you guys are having problems. Make sure the file editor you are using isn't changing the permissions. After modifying the file, it should look exactly like this:
[email protected]:/system/etc/wifi # ls -l WCNSS_qcom_cfg.ini
-rw-r--r-- root root 5577 2012-12-29 19:17 WCNSS_qcom_cfg.ini
Make sure the permissions (-rw-r--r--), the owner (root), and the group (root) are identical to this. If the permissions, owner, or group are different, you can reset them with:
chmod 644 WCNSS_qcom_cfg.ini
chown root.root WCNSS_qcom_cfg.ini
I've been running this change for 2 days and my wifi has been 100% stable. It has fixed all the problems I was having.
I just wanted to add that I've read about a lot of various wifi problems that people have been experiencing. This fix is specifically to address the problem with the phone not being able to properly maintain an active network connection while the screen is off. The most noticeable symptom is incoming notifications (like new gmail alerts) taking minutes (sometimes up to 15 in my case) instead of seconds to appear.
If you have other problems like slow wifi speeds or not being able to connect to wifi, this patch is still applicable to your Nexus 4 but there are additional problems you are likely encountering. I personally have not experienced any of these other issues.
Also just to clarify, how noticeable the problem is to you will depend on the settings of your router, in particular the ARP cache timeout. For example, enterprise level Cisco gear uses a 4 hour timeout by default whereas linux (which most home routers run) defaults to 60 seconds. The quicker the cache times out, the more noticeable the problem.
Updated first post with CWM installable files to make ini file changes. Please let me know if anyone has any problems installing these.
bganley said:
Updated first post with CWM installable files to make ini file changes. Please let me know if anyone has any problems installing these.
Click to expand...
Click to collapse
Please contact Google so they know about this. I'll be applying the patch tomorrow when I'm back home. Happy New Year!
Sent from my Nexus 7 using Tapatalk 2
How does this impact battery life e.g. will it cause wakeups when responding to broadcast/multicast requests?
Whilst my Nexus 4 seems to stop responding to pings when the screen is off I still seem to get notifications in a timely manner, even with mobile data turned off just to test
I flashed the n4-wifi-sleepfix-mcast_and_bcast.zip but the problem still exists. Gmail and whatsapp notification takes about 5 minutes...
How do the default settings on the N4 differ when it comes to this line in the INI when compared to other devices? Are other devices able to capture GMail messages almost instantly despite having a value of '3' in this line? I know that my One X was fantastic when it came to receiving messages quickly, whereas this N4 takes a long time to get messages.
defnz said:
How does this impact battery life e.g. will it cause wakeups when responding to broadcast/multicast requests?
Whilst my Nexus 4 seems to stop responding to pings when the screen is off I still seem to get notifications in a timely manner, even with mobile data turned off just to test
Click to expand...
Click to collapse
I've been testing the battery life impact the last few days and so far it appears the ini file patch has an impact. This is expected as the phone now has to process incoming broadcast/multicast packets. With the patch applied, it appears to really aggravate the msm_hsic_host wakelock nonsense and in turn cause the phone to spend less time in deep sleep according to BBS. In my case, this hasn't resulted in that much of a difference in battery life but I'm continuing to monitor.
I did try out Franco's latest kernel as he has some patches for the wakelock issue and with his kernel there was a huge improvement in deep sleep time both with and without this patch applied. Battery usage per hour also improved from about 1.2% with the stock kernel to about 0.5% with Franco's kernel.
Interesting that you still receive notifications in a timely manner. What amount of time do you consider timely? For me, it was taking anywhere from instant notification (rare) to 15 minutes at the worst without this patch. What router do you use? Are you running any custom firmware on your router? Is your phone assigned a static or DHCP address? Are you using a static DHCP reservation for your phone?
antih3ro said:
I flashed the n4-wifi-sleepfix-mcast_and_bcast.zip but the problem still exists. Gmail and whatsapp notification takes about 5 minutes...
Click to expand...
Click to collapse
Your sig says your are running CM? I'm not sure how this patch would work with that ROM. I've only tested with stock JOP40D.
floepie said:
How do the default settings on the N4 differ when it comes to this line in the INI when compared to other devices? Are other devices able to capture GMail messages almost instantly despite having a value of '3' in this line? I know that my One X was fantastic when it came to receiving messages quickly, whereas this N4 takes a long time to get messages.
Click to expand...
Click to collapse
The other devices I've looked at don't have the same wifi chip and therefore don't have this INI file. I did a bunch of testing with my Galaxy Nexus and Nexus 7 to try and determine how they were behaving in regards to multicast/broadcast traffic during sleep. I was able to show that both devices process and respond to both broadcast and multicast traffic during sleep.
This makes sense as certain network functions (such as ARP) rely on broadcast traffic. If a device isn't processing broadcast traffic, then those things break as we've seen with this phone.
I have a GNex, a N7, and an Atrix all running alongside the Nexus 4. All of those phones respond to incoming gmail notifications within seconds and now with this patch, so does my N4.
I've had the exact same issues with my nexus 4....thanks
Sent from my Nexus 7 using Tapatalk HD
bganley said:
Interesting that you still receive notifications in a timely manner. What amount of time do you consider timely? For me, it was taking anywhere from instant notification (rare) to 15 minutes at the worst without this patch. What router do you use? Are you running any custom firmware on your router? Is your phone assigned a static or DHCP address? Are you using a static DHCP reservation for your phone?
Click to expand...
Click to collapse
I've been doing comparisons with a SGS2 and sometimes the N4 receives it before the SGS2, sometimes after, it's anywhere from instant ~5 seconds for gmail, sometimes it can take longer but the delay is seen on both the N4 and the SGS2. However with gTalk its pretty much instant on both.
I'm running an Asus RT-N66U w/ Asuswrt-Merlin 3.0.0.4.264.22 firmware
DHCP, no DHCP reservations, no static arp entry either
In saying that, I don't disagree with your findings though. The phone should have multicast/broadcast enabled so that it doesn't break things like ARP.
I'd like to get this to work, but unfortunately, things haven't changed a bit. Permissions are correct, rebooted, etc. I'm running DD-WRT and have reserved a static IP at the router by MAC association, which I do for everything on the network by the way. I've even changed DHCP to static on the device. Gmails show instantly at the PC, but appear up to 15 minutes later on the device. The device is ping-able when the screen is off.
floepie said:
I'd like to get this to work, but unfortunately, things haven't changed a bit. Permissions are correct, rebooted, etc. I'm running DD-WRT and have reserved a static IP at the router by MAC association, which I do for everything on the network by the way. I've even changed DHCP to static on the device. Gmails show instantly at the PC, but appear up to 15 minutes later on the device. The device is ping-able when the screen is off.
Click to expand...
Click to collapse
Try changing to 0 so it is not filtering anything
Sent from my Nexus 4 using Tapatalk 2
Related
Hello everyone!
Just moved from a P3600 to the P4550 and noticed something strange twice in the last 4 days. When I looked at the display in the morning (phone and WLAN were off overnight.....hardly ever turn on WLAN, as I only use it when travelling) I found that WLAN had switched itself on sometime during the night. What gives?
Any ideas would be greatly appreciated!
Thanks!
This happens to me also if:
(1) ActiveSync is set to "as items arrive" (i.e. push)
(2) There is no phone signal.
Apparently AS looks for the Exchange server, and not being able to find a phone signal, turns on Wifi to see if it can connect like that.
I suppose this will also happen if you have AS set to poll mail at intervals. When the interval time arrives, I guess AS will want to go online and - not being able to use the phone signal - will turn on Wifi.
Very annoying as it drains the battery. It does NOT turn Wifi off after a while.
Oh well.
This happens to me also if:
(1) ActiveSync is set to "as items arrive" (i.e. push)
(2) There is no phone signal.
Apparently AS looks for the Exchange server, and not being able to find a phone signal, turns on Wifi to see if it can connect like that.
I suppose this will also happen if you have AS set to poll mail at intervals. When the interval time arrives, I guess AS will want to go online and - not being able to use the phone signal - will turn on Wifi.
Very annoying as it drains the battery. It does NOT turn Wifi off after a while.
Oh - an afterthought: in CONNECTIONS I have set both programs accessing the net and programs accessing a private network configured to use MY WORK NETWORK. Don't know if fiddling around with that may stop AS turning on WifI.
Should you find a solution, please post coz I would like to fix this bug/feature too.
Hmmm.....if this theory is correct then going to flight-mode instead of just turning the phone off - should effectively not allow any kind of connections.....will check tomorrow....
I seem to be having pretty severe wifi issues on networks that are composed of a large number of routers (i.e. campus/business networks) where going between routers will result in the phone believing it is connected, but not being able to send/receive data. This is evidenced both by the lack of notifications/apps working, as well as the wifi icon in the quick toggle panel being orange (which indicates no data being sent/recieved, I believe) despite having full signal. This means that without any external indication that anything is wrong, my phone essentially does not work anymore until I turn the wifi off and back on. Previous phones (galaxy nexus, droid) as well as computers did not have this issue on the same network.
Has anyone else noticed this problem, and if so, found any way to get around it other than remembering to reset the wifi power every time you move between areas?
It sounds like there are multiple WAPs all using the same SSID, and Android is not requesting a new IP address when it disconnects from one WAP and connects to another. You could probably work around the issue using Tasker, and have it toggle Wifi off and on again any time Wifi is disconnected. I you go that route I would recommend using the trial version available from the developer's site, or one of the many similar apps that are available in the Play Store for free.
There may be something more to this though. Hopefully someone else has another idea.
WiFi issues
ice20978 said:
I seem to be having pretty severe wifi issues on networks that are composed of a large number of routers (i.e. campus/business networks) where going between routers will result in the phone believing it is connected, but not being able to send/receive data. This is evidenced both by the lack of notifications/apps working, as well as the wifi icon in the quick toggle panel being orange (which indicates no data being sent/recieved, I believe) despite having full signal. This means that without any external indication that anything is wrong, my phone essentially does not work anymore until I turn the wifi off and back on. Previous phones (galaxy nexus, droid) as well as computers did not have this issue on the same network.
Has anyone else noticed this problem, and if so, found any way to get around it other than remembering to reset the wifi power every time you move between areas?
Click to expand...
Click to collapse
I'm having the same issues both out in public and at my home. This issue didn't seem to exist prior to 4.4 update. Now I'm constantly having to toggle my WiFi on and off or toggle airplane mode and also hitting the symbol down at the bottom left on my phone and on my router at the same time. If someone has any information to correct this would be great. Like I said I never had this problem prior to 4.4.
UncleMike said:
It sounds like there are multiple WAPs all using the same SSID, and Android is not requesting a new IP address when it disconnects from one WAP and connects to another. You could probably work around the issue using Tasker, and have it toggle Wifi off and on again any time Wifi is disconnected. I you go that route I would recommend using the trial version available from the developer's site, or one of the many similar apps that are available in the Play Store for free.
There may be something more to this though. Hopefully someone else has another idea.
Click to expand...
Click to collapse
Thanks for the suggestion! One question though: does the wifi actually "disconnect" when there is a handover between two routers of the same network? Is a handover while constantly connected something tasker could detect?
ice20978 said:
Thanks for the suggestion! One question though: does the wifi actually "disconnect" when there is a handover between two routers of the same network? Is a handover while constantly connected something tasker could detect?
Click to expand...
Click to collapse
As far as I know, Android doesn't "roam" seamlessly from one AP to another even when the SSIDs are the same. I'm pretty sure Tasker would see this as Wifi being disconnected (albeit briefly). You could then tell Tasker to turn off Wifi for 5 seconds and then turn it back on again.
UncleMike said:
As far as I know, Android doesn't "roam" seamlessly from one AP to another even when the SSIDs are the same. I'm pretty sure Tasker would see this as Wifi being disconnected (albeit briefly). You could then tell Tasker to turn off Wifi for 5 seconds and then turn it back on again.
Click to expand...
Click to collapse
I finally got around to making a tasker script to do this, and tried it out for a few days, but unfortunately it does not seem to detect the changing between the different routers on my institute network as having the wifi disconnected, and thus doesn't solve the issue. It was a good idea to try though!
I've cross-posted the issue at the link below in hope motorola will see this, but if anyone knows a better way to report this, please let me know.
https://forums.motorola.com/posts/68884aa31b
I just received my gen 2 moto x last night and am having trouble connecting to Wifi at work. It connects to my home network and one of my work networks just fine, but when I try to connect to the work network I need it to connect to the signal strength drops to "poor" as soon as I press connect. My home network and work network both are password protected. I've verified the password and have the same connection settings as my friend's gen 1 moto x, which connects properly. The work network has excellent signal at all times when I am not trying to connect to it. It just keeps cycling from "connecting" to "saved."
Has anyone else experienced this or know a workaround? I found this but this is for a gen 1 (I'm not sure if that would help) but I'm not rooted so I don't have access to phase 2 authentication. http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-signal-drops-trying-to-connect-t2872241
Thanks,
Mike
mikekory87 said:
I just received my gen 2 moto x last night and am having trouble connecting to Wifi at work. It connects to my home network and one of my work networks just fine, but when I try to connect to the work network I need it to connect to the signal strength drops to "poor" as soon as I press connect. My home network and work network both are password protected. I've verified the password and have the same connection settings as my friend's gen 1 moto x, which connects properly. The work network has excellent signal at all times when I am not trying to connect to it. It just keeps cycling from "connecting" to "saved."
Has anyone else experienced this or know a workaround? I found this but this is for a gen 1 (I'm not sure if that would help) but I'm not rooted so I don't have access to phase 2 authentication. http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-signal-drops-trying-to-connect-t2872241
Thanks,
Mike
Click to expand...
Click to collapse
Exact same problem. Fine at home and everywhere else. Spent a couple hours this week on the phone with Moto. They keep saying it's the network, yet everyone else is on it. They say update firmware and open MAC. Both of which are done.
This is the message in the Access point every 3 seconds when my phone is trying to connect...
"Client Deauthenticated: MACAddress:9c:d9:17:a1:c8:51 Base Radio MAC:b8:62:1f:ad:5e:90 Slot: 0 User Name: unknown Ip Address: unknown Reason:Unspecified ReasonCode: 1"
My wife's phone drops WiFi in favor of 4G LTE at home. I have to turn off data to connect to WiFi but it eventually drops the WiFi. I'm still waiting on my pure edition so I'm not sure if its just her phone or if its a common problem.
bradley26 said:
My wife's phone drops WiFi in favor of 4G LTE at home. I have to turn off data to connect to WiFi but it eventually drops the WiFi. I'm still waiting on my pure edition so I'm not sure if its just her phone or if its a common problem.
Click to expand...
Click to collapse
This!
I have this problem all the time ON multiple networks, its very frustrating
Mines will disconnect from my 5ghz when the screen goes off and reconnects when turned on, works fine on 2.4ghz. I have a Nighthawk ac1900 so the phone is definitely the problem.
Sent from my Hammerhead
This is related to 802.1X, We have it implemented Radius and 802.1X at work and it doesnt connect. But the same AP has a guest SSID which has no protection and a separate vlan which has access only to internet and it works fine.
giovannirc said:
This is related to 802.1X, We have it implemented Radius and 802.1X at work and it doesnt connect. But the same AP has a guest SSID which has no protection and a separate vlan which has access only to internet and it works fine.
Click to expand...
Click to collapse
Sounds like this could be my problem. We have 4 networks we can login to, but they are all broadcast from the same access point. One says "secured with 802.1x" and is for laptops, two say "secured with WPA/WPA2" and are for cell phones/other, and the final is unsecured. I can only connect to the unsecured network.
So does it sound like it's the phone that's refusing the network, the network is refusing the phone for something the phone is sending back to it, or the network is refusing the phone for another reason?
I'm having this same issue. 1st Gen Moto X sitting right next to 2nd Gen, and the 1st Gen is connected while the 2nd Gen can't.
I'm having the exact same issue. It appears the problem is that older Cisco firmware doesnt support 802.11w, which is what the moto x 2014 uses by default. Here is a thread where a moto rep explains it to Cisco - https://supportforums.cisco.com/discussion/12331486/connectivity-issues-cisco-controllers-and-pmf-enabled-moto-x-gen-2
My girlfriend and I have this phone and we had a similar problem. It would connect/reconnect like a billion times before staying connected on our home network but connect fine on other networks. I tried several solutions but the one that worked was changing the channel on the router. I live in an apartment building and there are a lot of WiFi networks around me so I figured that might be causing some interference. I changed my channel from 6 to auto (it automatically jumped to 11) and now it connects instantly and is solid. What's weird is I tried channels recommended by WiFi analyzer and my other devices would connect just fine but the Moto X's couldn't even see the network in the list when it was on a lot of channels like 12, 13, and 14.
Seems like a weird WiFi radio firmware bug to me.
Is there a client side fix for this?
I just ran into the problem at my work. It is a major hospital. They are not going upgrade their cisco firmware so a couple of people's personal phones are able to connect to the network.
WiFi in general is bad on the X2014 and I am reading the same in the Droid Turbo forums.
Sent from my XT1095 using XDA Free mobile app
What!? Really?
I've not had a single issue with WiFi connectivity. I'm an IT professional so heavily reliant on WiFi.
will54880 said:
WiFi in general is bad on the X2014 and I am reading the same in the Droid Turbo forums.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Wutang200 said:
I've not had a single issue with WiFi connectivity. I'm an IT professional so heavily reliant on WiFi.
Click to expand...
Click to collapse
I never had a WiFi problem with the Moto X 2014 until today at work. It wouldn't connect to a few different clients Wireless APs. At the first client site I power cycled the phone and WiFi still wouldn't connect. I then went to another client site and once again it would no longer connect. I power cycled again and this time it connected just fine albeit Bluetooth was acting funny and not connecting to the Moto 360. After cycling Bluetooth off and on again the 360 finally connected. Not sure if this is an actual issue or just dumb luck. I wonder if anyone that was having WiFi issues with this phone also has a Moto 360 connected via Bluetooth?
I don't own a 360 and my bluetooth is normally switched off unless I'm streaming music at home.
I know none of what I am about to write will solve anyone's issue but sharing my experiences mught help understand you're not alone. I wander between as many as a dozen different wifi networks daily. I manager a 63 room hotel on 7.5 acres where we are currently running EnGenius EAP350 AP's broadcasting in 2.4mhz band ONLY using .11bgn. I set the entire network to use one SSID so roaming is, in theory, problem free. My XT1095 has not had any issues at all here on property.
I also have my personal network in the lobby and main building under 2.4/5/.11AC side by side with out guest network. No issues bouncing around. I honestly expected issues but have found none.
There is one issue I have found in Android in general which can happen randomly, or I have not been able to induce the behavior only recognize it. Occasionally when I move from one building to another Android (ICS forward for sure) will forget which actual AP it's after and just hang. My solution is to tell the device to forget that node then once forgotten the network, of course, shows up in the list. I then select it and boom we're back in business.
I do have issues when I visit a network at say, the grocery store which requires accepting an EULA...the device simply will hang Wifi wize, even when I delete and reconnect I won't get the note to open the authorization page. I end up just killing wifi and going with LTE.
I get the same behaviors from all my phones ICS though Kitkat, don't have Lollipop yet darn it!!
I have long been frustrated with this weirdism from Android but have reached a point of M.A.D. with my devices but never found a solution.
I have noted I have the most issues by far with Cisco/Linksys devices. It has been almost assured that if I have an issue it's one of those routers running an older firmware version (amazing how many AP/routers use default password settings...I mean, really???)
Not 100% sure it's a firmware only issue but I do think it's some common bit of hardware in an AP/Router which can go spastic for some reason preventing Android from figuring out how to remain or get connected. I even had one of the EnGenius AP's go nuts, a fast swap with a freshly configured AP resolves but, again, still does not identify or solve the problem
I also sense there is some oddness deep in the bowels of Android's wifi/networking subsystem which just was never written correctly and may never be fixed.
Last I run and app called Wifi Analyzer by Kevin Yuan, it helps me a GREAT deal because I can target a specific AP/node to connect with. Android versions often defeat this by not remaining connected to that desired target AP and switching to something else. Here is where I think some of the issues with wifi connectivity live...Google MUST spend some time refining their wifi subsystem.
No matter this is a Very frustrating issue when it happens. My best solution has always been to forget the current connection then reconnect with it again once it reappears. Better yet use Wifi Analyzer or similar app to target a specific AP/node and connect/forget from inside the app, that really does seem to help, mostly...sigh, I know, sorry...
This WiFi issue is really aggravating. I have tried so many things:
1. Rebooting Router
2. Powering Off/On Phone
3. Turning WiFi Radio Off/On
4. Resetting Phone Cache Partition
5. Using WiFi analyzer and setting my router to various channels manually
6. Changing Router SSID
7. Forgetting SSID on phone and re-adding it
8. Verifying MAC Filtering is not enabled
9. Enabling MAC filtering and specifically allowing phone MAC address
10. Disabling "Avoid Poor Connections" in WiFi settings
11. Manually setting WiFi frequency band to 2.4ghz in phone settings
12. Disabling "WiFi Optimization" in phone settings
23. Changing WiFi direct and BT phone names (yeah, a big stretch, but I read somewhere that this worked)
24. Installed updated firmware on my ASUS RT-N12D1 (3.0.0.d.376_3602)
25. Disabled WPS on router
26. Switched router between Auto, Legacy and N-Only
27. Disabled Authentication and Encryption on router, just an "Open" connection.
After all of this, the phone still has WiFi connectivity issues. Sometimes after a phone power cycle it will connect to WiFi, but never for very long. Every other device I have connects to the WiFi without issues. I just got the Moto X a few days ago (AT&T version) and this is the first time I have ever had a device with WiFi connectivity issues like this. Very aggravating. There is clearly something wrong with either the hardware, or software on the phone.
There are some other oddities. When it won't connect to WiFi, there is something strange with the phone. Its not like it just can't connect or stay connected to WiFi, but somehow it seems like the WiFi is in a stalled state. Sometimes it won't show any WiFi networks and just says "Searching for WiFi networks..." until I turn off wifi and turn back on again. Then as soon as it turns back on, it will show the nearby SSID's, and try to auto-connect to my router, but after a few seconds it shows "Disabled" under the SSID. Then after a few seconds the disabled goes away, and it just shows the SSID name. It also won't let me change the WiFi Direct phone name while the WiFi is in this state, it gives me an error saying "Failed to rename device", followed by "Group Creation Failed". However, when I am actually connected to WiFi, I can rename the WiFi direct name just fine. So its not just simply an issue with bad radio signal or something, but something more serious, like the WiFi state is hung or something. If I can't resolve this in another day or two, I am going to have to return the phone, and hopefully a replacement will work. If not, I might have to get something other than a MotoX because I can't not have WiFi while at home and work.
---------- Post added at 12:29 PM ---------- Previous post was at 12:10 PM ----------
I found a way that seems to work to connect to WiFi. To clear, this isn't a fix for the data-sync issue that some people are having, or poor signal, but the issue where you can't connect to an SSID, and there is no error or anything.
1. Hold Down Power Button
2. Turn Airplane Mode On
3. Turn Wi-Fi On
4. Connect to SSID
5. Press Power Button down again
6. Turn airplane mode "Off"
I have now tried this several times, and it works everytime. If I turn off Wi-Fi and back on again, it won't connect, until I do the airplane mode trick. I don't know who to give credit for this, I have spent days and hours searching, and I remembered reading that from somebody else, but not sure where, so this is not my fix, I am just posting it here as it seems to work.
This issue is strange, and must be some combination of Android, and Motorola software/hardware/firmware configuration. I hope they get this fixed, but it at least now, this temporary fix will work whenever WiFi is not connecting.
For those of you getting WiFi connectivity problems, it could be related to your router setup. Download an app called InSSIDer and run a scan, then choose a channel that's not being used but make sure it's 5 channels higher or lower. For example, if it detects 3 networks on channels 3, 5 & 6, then you want to choose channel 10 or 11. If it detects one network on channel 6, then you should choose channel 1 or channel 10 or 11.
I noticed issues like this when I bought my Nexus 4 after my iPhone 4. Android devices seem to ship with rubbish WiFi radios.
Like I've mentioned before, I've not experienced a single disconnection with my phone either at home, work, in laws, coffee shops or anywhere else ever. Same with my first gen Moto X.
Mine is slightly different. Now and then, after power cycling or rebooting, it forgets all the WiFi passwords. Not every time. Just now and then.
Also sometimes it's quite fast, some slow. My wife's firs gen is pretty constant.
How the F do I fix the wi-fi in 5.1? The thing drops every 10-15 minutes and sits there saying “Obtaining IP Address”. It has nothing to do with the router because it does this at work and home and only started after updating to lollipop. I’ve factory reseted my phone and everything.
jeffgt14 said:
How the F do I fix the wi-fi in 5.1? The thing drops every 10-15 minutes and sits there saying “Obtaining IP Address”. It has nothing to do with the router because it does this at work and home and only started after updating to lollipop. I’ve factory reseted my phone and everything.
Click to expand...
Click to collapse
Do you have a bluetooth switched on? Try to turn off it. I have this issue too, and don't fix it at now..
I also have this issue. It will work fine and then suddenly it doesnt. I have to turn the wifi off and then back on again and it works fine.
I know of 2 other people with this phone that have the same issue.
No solution but just wanted to let you know I'm having the same issue. Definitely not related to the server/router.
Same problem here, will try out the bluetooth toggle later today.
Tried the bluetooth off and it doesn't help any.
It's the main reason i switched to CM12 and since I have no more wifi issue.
Not router related for sure. I've been looking at logcat too but found nothing (but I'm not an expert)
Model XT 1052 retail rooted and initial rom was something ....o2.de
Yea if I wasn’t so close to just pulling the trigger on the Nexus 5x I’d probably switch too. I’m worried about trying to sell the dang phone though and someone complaining because the wifi doesn’t work worth a crap.
same problem cm12.1
I'm also with the same problem in CM12.1 , wifi drops or speed decreases dramatically whenever I connect Bluetooth headset
My wife's phone does the same thing. I found that by going into advanced settings and setting a static ip for our home network
@Danielson01 I have a pebble connected in BT all day long. Which CM do you use ? I'm on 20151007 snapshot.
Power profile is set to "Balanced" (not sure of the translation).
At home my IP address have always been static (router setting)
Router Wifi channel is 11.
Please share some of this information (IP setting, power management and so on). Maybe we can find the guilty one ?
sha.public said:
@Danielson01 I have a pebble connected in BT all day long. Which CM do you use ? I'm on 20151007 snapshot.
Power profile is set to "Balanced" (not sure of the translation).
At home my IP address have always been static (router setting)
Router Wifi channel is 11.
Please share some of this information (IP setting, power management and so on). Maybe we can find the guilty one ?
Click to expand...
Click to collapse
Hello!!! User'm new and I can not post images yet, so I will try to describe the problem.
I use cyanogem mod version 12.1 is specifically:
cm-12.1-20151007-SNAPSHOT-YOG4PAO332-ghost.zip
battery is in balanced mode.
Bluetooth device I use and a philips shp9100 headset
when I hear a song on the poweramp the download rate drops dramatically when the play store down something or when I see the youtube videos is too slow catching all the time that the WiFi 2.4 GHz, since the network 5ghz is normal.
Note: I do not speak English and am using google translator excuse for the mistakes committed.
sha.public said:
@Danielson01 I have a pebble connected in BT all day long. Which CM do you use ? I'm on 20151007 snapshot.
Power profile is set to "Balanced" (not sure of the translation).
At home my IP address have always been static (router setting)
Router Wifi channel is 11.
Please share some of this information (IP setting, power management and so on). Maybe we can find the guilty one ?
Click to expand...
Click to collapse
Just an FYI. I set the ip on the phone itself versus a static dchp lease on the router. This rules out dhcp which I believe is the issue on my wife's moto x.
Also having the same issue where it drops and comes back or speed slows really bad. Overall quite disappointed in Moto for taking so long and releasing 5.1 with so many significant bugs. 5x may be in my near future!
Sent from my XT1060 using Tapatalk
A quick update. The wife's phone had the issue again last night. Toggling airplane mode fixes it every time but then I have to listen to her complain.
Hey Guys and Gals.
Same issue here... On KITKAT wifi worked perfectly fine. After updating to 5.1 (clean install) wifi keeps dropping quite frequently.
Tried various "solutions" like setting up static IP, changing wifi channel, choosing only 2,4GHz frequency. None of them worked.
Searching through the Internet brings a lot of different forums (phones) with similar issue, so it may not be Motorola specific.
Nevertheless Motorola should have taken care of this but before they rolled out 5.1 update...
Sent from my XT1052
My wife and I both have the Turbo on VZW (joint plan, etc). I generally perform any mods on my phone first, before doing the same to hers, so that I know what issues will happen and I can make sure the phone doesn't work any differently for her daily usage. So, aside from apps, we have the same phone in theory. Both phones are stock SU4TL-44, rooted, BL-unlocked (via Sunshine) states.
My wife's has been having rather poor battery life for the past many months. I can get a good 3.5+ hours of screen-on-time on my phone (as reported by GSam) but hers only gets like 1.5 hours on a good day. Her phone radio is what's reported as the largest load, so I started trying things there. We were both on the .49 radio (using the TWRP download by firstEncounter), so I thought maybe her phone doesn't like that radio, and put her back to the .44 radio. (Note, I have checked the hashes on these files, and they match. I also have used the same-exact files on both phones (via dropbox)... so it shouldn't be a radio/corruption issue.) Both
I'm not sure if the battery life has improved or not (only been a few days, but checking just now it looks like her max is now 2.5 hours in GSam, so that's a start I guess) but now another problem has come up - her phone keeps dropping the internet connection. Wifi appears to remain connected, but it shows an "!" which means it has lost internet connectivity. Checking the browser confirms that it is really lost for internet sites. (Next time, I plan to try going to the router IP and seeing if I can get to that, at least...) This drop happens sporadically, and doesn't self-repair... it is only fixed by disabling and then re-enabling Wifi. I "forgot" the wifi (2.4GHz, by the way), re-connected, and re-entered the password... this doesn't seem to fix the dropout either.
The wifi, itself, is working well. My Turbo has none of these issues, my work phone (Turbo2) doesn't appear to have issues, nor do our 2 laptops or wifi-Tivo... every other device works fine, just her phone has been giving issues.
Needless to say, the priority is to fix the dropping internet connectivity... if anyone can help me troubleshoot this further, I would appreciate it.
Longer term, I'd like to figure out the battery issues (health is reported as "good" by various battery apps... is there a way to see what the "real" capacity is, and not just "good/bad"?)... but the wifi is the primary issue. Part of me thinks of doing a factory reset (or maybe flashing SU4TL-49 and then re-rooting)... but I fear this may not fix anything.
Any help/ideas are appreciated. Thank you!
EDIT: One more difference - she has a Tile Gen2 along with the associated app. The app requires Bluetooth to be on, as it does some polling, I expect. I have turned this off for now (further testing) to see if it helps. She's had the Tile for a while, so it's not a new change... but I'm running out of ideas. Battery usage isn't significant, based on what's reported... but I thought maybe it has some effect on the wifi... I simply don't know, so I'm trying anything!
A little more info. I have left her bluetooth off for the past day, thinking that maybe Tile was the problem... it certainly seems to have helped the battery life (weird, since all the battery tools I've used don't seem to identify the app or BT as a large battery sink?)
Things were great for about 24 hours, but now the dreaded exclamation point is back. I tried getting to the router, but I get "ERR_ADDRESS_UNREACHABLE" from Chrome. Weird since I'm giving it an actual IP address (so no DNS should be involved). Phone has a valid IP address (same one it's had for a while now) and claims to have the interface "up" as well.
Any ideas, anyone?
EDIT: I see some UPNP activity in my router... I wonder if that has something to do with it. As a test, I have disabled UPNP to see if that helps (and what it breaks... which shouldn't be much, as I try to keep things explicitly configured)....
A further update in case others run into problems like this.... the issue may be caused by an interaction between my router and the bluetooth Tile app (which isn't on my phone but uses BT relatively often) - note that BT runs on the same 2.4GHz frequency as her wifi. I chose 2.4Ghz wifi (instead of 5Ghz) on her phone because it helps extend the range. Turning off BT on her phone seems to keep the connection stable and without issue... I have a little more testing to do to ensure it's the root cause before I consider it found.
There are a few potential solutions. One is to update the firmware on the router to a newer one which has an option to enable BT coexistence mode (disables some features in 2.4GHz wifi to improve compatibility). Another is to move her to 5GHz. I plan to test the coexistence mode, just to prove it's the problem... but my final solution will likely be to move her to 5GHz as the coexistence mode may reduce performance on 2.4GHz.
schwinn8 said:
A further update in case others run into problems like this.... the issue may be caused by an interaction between my router and the bluetooth Tile app (which isn't on my phone but uses BT relatively often) - note that BT runs on the same 2.4GHz frequency as her wifi. I chose 2.4Ghz wifi (instead of 5Ghz) on her phone because it helps extend the range. Turning off BT on her phone seems to keep the connection stable and without issue... I have a little more testing to do to ensure it's the root cause before I consider it found.
Click to expand...
Click to collapse
What about changing Wi-Fi channels on the router?
I also disable 5GHz on both our Quarks because the 5GHz range is shorter. I set our phones to ONLY connect to 2.4GHz and that's what I use for Wi-Fi router too (even routers with dual bands, I disable the 5GHz band).
But you can change 2.4GHz Wi-Fi router channels to mitigate interference, right?
http://www.goldtouch.com/stop-bluetooth-interference-messing-devices/
How to Stop Bluetooth Interference From Messing With Your Other Devices
Change Router Channel: If you have an Apple router and you’re constantly getting interference with your WiFi, try rebooting it. Upon restart, the station will search for a new channel — specifically, a different channel than the one your Bluetooth devices are using to communicate. If you don’t have an Apple router, you may need to instead go into your router settings and try changing the channel manually. Experiment with different channels to see which one works best.
Click to expand...
Click to collapse
I don't use anything Apple -- I just quoted from that article because it suggested what I was suggesting, changing Wi-Fi channels...
Yeah, I kept testing and found that the BT wasn't the only issue (may have been part of it, but it still dropped internet after a day or two even when BT was off).
Like you said, it's probably a 2.4GHz interference issue... and since I'm in an apartment building the spectrum is rather crowded. Plus, if anyone else bought a new phone/monitor/microwave/router that could be causing the issue, too. Bottom line, there's too much out of my control, so I switched her back onto 5GHz and the problem seems to have gone away (at least for the past few days)... so I'll leave it at that. I can't solve the entire area's problem, after all!
I am on the "cleanest" channel I can find, but that's only based on seeing other routers (via Wifi Analyzer)... interference won't be "seen" there, so we can only guess on those issues.
Bottom line, switching her phone to 5GHz is good enough for now, and solves the issue. I'll flip her phone back to the 49 radio as well.
In fact, this might have also helped her battery issue - when the phone lost internet, it would sit there and suck down power for "phone radio" doing who-knows-what. I don't see why it should do that, but it really killed the battery on one of the days. Putting her on 5Ghz prevents the loss of internet, and the battery drain from that, too... so that's better. Still, she gets much less SOT than I do on my phone, and she uses it less than I do... maybe the battery just needs to be replaced after all.
I wish there was a way to see what the "real capacity" is of the battery, instead of just assuming that 100% = original capacity (which we know it won't be). Do you know of a way to get that info?