What this change does is ensure that when "strict flight-mode" is enabled ( which is the default ), that the state of the modem will always follow the global state of flight-mode itself.
The only way to test this is to stop urfkill, and modify its saved-state file so that it contains "[WWAN] soft=true", reboot the phone, and ensure that the modem is active.
I discussed with Alfonso, and he'll add this as a new case to the exiting urfkill test plan.
I'd also like to note that this is a safeguard that will allow the user to recover their device if the original problem is hit again. It's not a total solution, so we should make sure not include the bug in the debian/changelog, as there's more work to do on this one...
@Leo
What this change does is ensure that when "strict flight-mode" is enabled ( which is the default ), that the state of the modem will always follow the global state of flight-mode itself.
The only way to test this is to stop urfkill, and modify its saved-state file so that it contains "[WWAN] soft=true", reboot the phone, and ensure that the modem is active.
I discussed with Alfonso, and he'll add this as a new case to the exiting urfkill test plan.
I'd also like to note that this is a safeguard that will allow the user to recover their device if the original problem is hit again. It's not a total solution, so we should make sure not include the bug in the debian/changelog, as there's more work to do on this one...