SystemUI magically enters flight mode, maybe via one of its powerkeymenu callback return values, and then MCE tells SystemUI to open a modechange ASUI calls req_device_mode_change and MCE sends out the signal confirming the change. All the wifi and bluetooth dbus activity after the flight signal is the same for SystemUI and ASUI. I don't see how the different MCE calling mechanisms would make any difference since the services all respond the same. @ maacruz, could you try logging `dbus-monitor --system --profile` after entering flight mode with SystemUI and see if ICD still scans for networks?