Android services/actions launched by droid-hal-init, queued oneshot
scripts and sensorfwd are executing in parallel during bootup. During
especially the 1st boot the scheduling of tasks can lead to sensorfwd
getting hold of nonfunctional sensor hal.

Delaying sensorfwd startup until oneshot scripts have been executed
makes it less likely for the problem to surface.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Using systemd specific startup notification is preferable over cusrom
daemon forks.

Add support for systemd-notify and use it instead of forking.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Since sensorfwd is using Type=forking, specifying a BusName leads to
systemd complaining: "sensorfwd.service: Service has a D-Bus service
name specified, but is not of type dbus. Ignoring."

Remove BusName specification from the sensorfwd.service file.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

The config files should be installed per device

Signed-off-by: Matti Kosola <matti.kosola@jolla.com>

stop the mag sensor from starting and calibrating at startup.
add more debug output.

We never want to not be running. If someone wants to stop sensord, they can stop
the service through systemctl, the same as other system daemons.

Signed-off-by: Pekka Lundstrom <pekka.lundstrom@jollamobile.com>

[systemd] Make sure we dbus socket is there when sensord is starting. Also fix some minor service file typos.
Signed-off-by: Marko Saukko <marko.saukko@jollamobile.com>