0

Currently it isn't exported. In a sane Android environment the boot listener would start it up automatically and it wouldn't need to be.

Unfortunately not all Android environments are sane. I have a car head unit that runs some weird version of android. It's not Android Auto, it's normalish Android. I use KDE connect so passengers can send destinations to the head unit for navigation, also maybe DJ if I like their tastes. This helps delegate tasks and keeps the driver (usually me) focused on the road.

When it starts up it ignores boot listeners on every app. It lets me select a "Navigation app" which it does open automatically, in my case this a home made app that just opens up what I want to start automatically. Unfortunately opening activities is slow and annoy because it does this every time the car is turned off and then on. Basically it's like an app slide show. I'd like to do it by background service to avoid this.

Specifically what I'm asking is there any reason not modify the AndroidManifest.xml to export the service so third party apps can start up KDE Connect via service? For example, like this?

Code: Select all

        <service
            android:name="org.kde.kdeconnect.BackgroundService"
            android:foregroundServiceType="connectedDevice"
            android:icon="@drawable/icon"
            android:exported="true"
            android:enabled="true" />

No hurt feelings if you don't think it's a good idea. Just a gentle request.