Hi all (or whoever hasn't given up on this thread due to the rash of less than constructive posts lately).....
Like many, I was asked to install a wifi log diagnostic tool (for the music player app airplay related issues). Anyway, I thought I'd have another look at analyzing the log files for this issue (which, I don't seem have, maybe because I don't have a lot on my phone. or maybe my neighbour has a cellphone frequency jammer at just the right power level to confuse my phone.. or maybe I live under a multidimensional vortex or something).
After a good glance up and down my log files, I saw this (items of interest in bold):
03/11/15 19:07:05.831 <NOTICE>: Client itunesstored set type to normal application
03/11/15 19:07:05.831 <NOTICE>: __WiFiManagerSetEnableState: state TRUE, manager->enable.setting TRUE, manager->unlockedSinceBoot TRUE
03/11/15 19:07:05.832 <NOTICE>: BG Application: Not Present, BG Daemon: Present. Daemons: assistantd networkd
03/11/15 19:07:06.423 <NOTICE>: Client apsd set type to background application
03/11/15 19:07:06.423 <NOTICE>: __WiFiManagerSetEnableState: state TRUE, manager->enable.setting TRUE, manager->unlockedSinceBoot TRUE
03/11/15 19:07:06.423 <NOTICE>: BG Application: Not Present, BG Daemon: Present. Daemons: assistantd networkd apsd
03/11/15 19:07:06.424 <NOTICE>: Already connected to XXXXXXXXX.
03/11/15 19:07:06.424 <ERROR>: Enable WoW requested by "apsd"
03/11/15 19:07:06.425 <NOTICE>: WoW Capable = YES, Attempting to enable WoW and disable LPAS
03/11/15 19:07:06.425 <NOTICE>: Setting WoW params to <dictionary> {
IO80211InterfaceEnableLowPwrAssocMode : FALSE
IO80211InterfaceEnableWoW : TRUE
}
03/11/15 19:07:06.426 <NOTICE>: WiFiDeviceRequestAssociatedSleep: ActiveDuringSleepRequested is already set (<dictionary> {
}).
03/11/15 19:07:06.426 <ERROR>: Unable to dispatch WowStateChanged message to client MobileMail (268435460)
03/11/15 19:07:06.427 <ERROR>: Unable to dispatch WowStateChanged message to client dataaccessd (268435460)
03/11/15 19:07:06.427 <ERROR>: Unable to dispatch WowStateChanged message to client softwareupdatese (268435460)
03/11/15 19:07:06.428 <ERROR>: Unable to dispatch WowStateChanged message to client itunesstored (268435460)
03/11/15 19:07:06.428 <ERROR>: Unable to dispatch WowStateChanged message to client assistantd (268435460)
03/11/15 19:07:06.429 <ERROR>: Unable to dispatch WowStateChanged message to client dataaccessd (268435460)
03/11/15 19:07:06.429 <NOTICE>: WoW Enabled by 1 Clients, lpas is Disabled
03/11/15 19:07:06.429 <NOTICE>: apsd[83] is a wow client
03/11/15 19:07:06.429 <NOTICE>: WoW is Enabled, 1 WoW Clients
03/11/15 19:07:07.085 <NOTICE>: _wifi_manager_start_browsing_for_service: client discoveryd, key size 56
Something else too I found was periodic entries saying "Already connected to XXXXXXXXX" (XXXXXXX is my SSID) so it seems that something on the phone is checking something on the internet to find out it's still connected to wifi. If it's connecting every few minutes, it could be keeping the phone connected to the wifi network.
From what I could find, apsd is the part of ios that manages push notifications. I'm thinking it may be possible that I have one or more apps (twitter for example) that is telling iOS it wants to receive and which is allowed to receive push notifications, but being twitter in this case, may be checking often enough that it is keeping the connection going. I also allow a number of apps to run in the background as well. A scan through logs I had from several weeks ago seem to show that apsd and wow only show up at times when I am home and connected to wifi (I only connect to my home wifi).
I have airdrop and bluetooth enabled along with 3 airplay devices and apple tv.
One thing I did notice which is pretty annoying and doesn't address the topic of this thread, the list of airplay devices gets constantly reset (when I lock the screen for some time for example) and it takes many long seconds (sometimes 30 seconds and the impression I need a bit of hoodoo-voodoo ritual magic at times to get it to see the very airplay device i want to use).
In my case, it may not be dropping the wifi connection, but it does seem to be quick to forget what is on the network.
Not sure if anybody else who has this problem and has the wifi diagnostic tool installed can compare results with mine (like the bold items from my log file for example)... The "ActiveDuringSleepRequested" seems a bit too close to the problem for me.