@Julia Thanks for the testing report!
So when you say, "you gave it 10/15 minutes of time to reconnect on its own". I assume during this time you were assuming that the device would re-connect automatically when the screen was off? Then you say you woke the phone, and it was offline until you started to interact with the network menu. Can you give us a rough idea of how long it was between when you woke the phone, and it connected? My experience have show that it's usually somewhere between 30s and 2m to connect. Finally, the original bug describes a situation where after the phone is woken, it will *never* re-connect to an available access point it's previously been connected to. @ Pete Regarding passive network scanning... no, none of the sort happens, in fact we have no code at all in our network stack that integrates with our power management framework on touch devices. At some point, the screen turns off, which given the right conditions causes powerd to notify the kernel that it's allowed to sleep. When this happens ( ie. the kernel decides to suspend given no more wake locks ), there's no notification to wpa_supplicant or NetworkManager, and in some cases we've seen this "pulling of the rug" approach actually prevent some devices from suspending. Enabling passive scanning during suspend is something that could be accomplished automatically by the driver, or enabled by wpa_supplicant before suspend, however without some knowledge of the system power/suspend mechanism, neither wpa_supplicant or NM can do this today. Making such a thing work, also would require deeper technical cooperation from the ODM and/or IHV. Note, we also should seriously consider a new system settings for WiFi that allows a user to specify whether or not WiFi is to attempt to keep a connection going when the system goes to suspend. I would argue that our current situation is a bit ambiguous ( ie. WiFi remains on, but at some point when the device suspends, it does disconnect ). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
