Comment 5 for bug 1421249

I'm pretty sure this has to do with the ordering of the bluetooth-touch, bluetooth (bluez) and urfkill jobs. IIRC bluetooth-touch jobs do some firmware tweaks that can't work if the device isn't available or rfkill blocked, but we also need to be very sure that the radios are off all the while flight mode is enabled and bluetooth isn't, since this is part of regulatory requirements.

Since it's probably changes in the upstart jobs and only that, I'm adding a task for lxc-android-config. Let's keep the urfkill task in case there is any work needed there, but it seems to me like the logic in urfkill is already correct.