networking eventually brought down due to inactivity

[Jamie Strandboge]

For various reasons, I like to be able to ssh in to my nexus 4. I have noticed with current saucy (and raring before it), after some time of inactivity the screen goes blank (fine), but then occasionally after some more time after that, networking is brought down (wifi) if there is no network activity. If I continuously ping the device, networking stays up. If I keep the screen from blanking, networking stays up. The current behavior is different than the behavior on android, where I can get various notifications for facebook, email, etc when the screen is blank.

HARDWARE=mako
JENKINS_BUILD=saucy-11
UBUNTU=ubuntu-touch-saucy-armhf
ubuntu/platform-api=:68
hybris=0.1.0+git20130606+c5d897a-0ubuntu2

[Toby Kurien (tobykurien)]

Android has a "Wifi sleep policy" under advanced which allows you to set whether Wifi stays on or not. By default (at least on older devices), the default policy is to sleep when screen is off. This is important for battery savings, so I would expect the behaviour you describe as a bug to be the default, with perhaps a setting to allow wifi to stay on as non-default.

[Tony Espy (awe)]

I changed Importance to "Wishlist", as this is really a feature request as keeping Wi-Fi active like this isn't something that Network Manager ( at least our version ) currently supports ( @Mathieu, please feel to correct me here ).

Supporting this would also require UI work to implement the associated Settings control.

[Tom Reynolds (tomreyn)]

Is this something which could be supported by now?

gnome-control-center -> power seems to offer a setting to manage wi-fi power saving but in the end this is just a wi-fi on/off switch which immediately brings the device down/up (bug 1751954).

Looking through the details of an existing NM wireless configuration profile there are no related (power saving) features exposed on the GUI. "nmcli connection show $UUID" lists a
   802-11-wireless.powersave (default: 0)
setting.

https://developer.gnome.org/NetworkManager/stable/settings-802-11-wireless.html

Is this what brings the interface down after some ~ 10 minutes of user input inactivity / ~ 5 minutes of blank screen? If so, could this be exposed on the GUI?