Closed harshit-sharma-gits closed 2 years ago
This would work if there were an autostart setting in a setting file of the daemon. But AFAIK, the daemon has no settings. I don't know if we should add a setting to deactivate all notifications in the Calendar main app in the future. Anyway, for now a simple "launch" with the path to the daemon should work.
Understood. The configuration file should look like this:
service x-vnd.CalendarDaemon {
launch path/to/daemon/
no_safemode
legacy
}
But I wonder what path/to/daemon/
should be?
That depends on where the daemon ends up when creating the package. Currently, the main app sits directly in /system/apps/. We wouldn't want to have the daemon there, I think. Maybe we should have it in /system/servers/ ?
Currently, the main app sits directly in /system/apps/. We wouldn't want to have the daemon there, I think. Maybe we should have it in /system/servers/ ?
I agree with putting the daemon in /system/servers/
That should work.
For issue: #130
Scope of the PR: To write the configuration file for the daemon, so that it can be started automatically by the launch_daemon when the system boots up, or when the daemon has closed/crashed.