Overhaul flight / airplane mode - align to end user expectations (rfkill behaviour)
Submitted by lof
Link to original bug (#761051)
Description
The flight of gnome shell works totally different compared to what users are used from other (mobile) systems like android.
On android flight mode is a mode that you manually enable (or via a trigger), but it is not automatically enable if the phone is a state similar to flight mode.
DISABLING WIRELESS: Android: When you disable all wireless functions (wifi, bluetooth) but do not enable flight mode then flight mode stays disabled.
Gnome shell: When you disable wifi and bluetooth the system enabled flight mode for you, without asking.
ENABLING FLIGHT MODE:
Android: If you wifi is on and you bluetooth is on, and you enable and then disable flight mode android will restore the wireless devices to the same state as before. So wifi is enabled, and bluetooth stays disabled (in this example).
Gnome Shell: If your wifi is on and bluetooth is off and you enable and then disable flight mode, then the system will enable both of these devices (if you only have these). The user then needs to do at least 3 steps to restore the old state.
I like that gnome has a flight mode. But it behaves totally different than i (and some other users i asked) expected. I think it would be more intuitive if the flight mode would behave the same as on other systems.
Version: 3.18.x