fix : Service does not starts
Description
The “directBootAware” parameter prevents the alarm startup service from starting, which causes the behavior described in the bug, when the mobile has a user lock (see logfile).
Setting the value to false causes the service to start correctly once unlocked.
Screenshots
Technical details
Tests
Issues
https://gitlab.e.foundation/e/os/backlog/-/issues/3366