Yesterday evening I updated kdeconnect to try the long-awaited remote input, in the morning I find phone's battery exhausted and after connecting to a charger and powering up, it's the pesky boot loop I've had before. Trebuchet crashes and that triggers a zygote restart, not ending well. Deleting the apk from /data/app, then restoring previous version via TitaniumBackup brings phone back to life. It's a known bug seemingly on all CM/LOS versions up to 7.1, just search for "libandroidfw.so android::AssetManager::getBasePackageName"..
Same problem here with CM11 on a Sony Xperia P. More info about this problem here: https://gitlab.com/fdroid/fdroiddata/issues/979
Created attachment 111159 [details] logcat from installing kdeconnect-android, showing the system crash
I got the same thing. On a fresh replicant 6.0.0003 install on galaxy s3: update f-droid, install kdeconnect-android Version 1.7.2 (1720) from f-droid, system crashes, goes into boot loop, eventuall comes out, trebuchet crashes a bunch, error on uninstall of kdeconnect-android, reboot causes more boot loop.
I read upgrading the buildToolsVersion to 27 solves the problem in other apps with the same problem. I tried to compile and test the change locally and it worked even with kdeconnect. Compiling with: buildToolsVersion '26.0.2': bootloop just after install buildToolsVersion '27.0.3': works fine I don't know if this change have some collateral effect, I'm not and Android developer.
KDE Connect is already built with buildToolsVersion '27.0.3'. I have no idea what to do to get this fixed :/
I've released a new version that should fix a crash in Android 4.X (even though it seems unrelated to the crash linked before). Let me know if it works for you once you get the update.
Tested version 1.8.4.1 and for me (xperia P and nexus7 2012, both with CM11) the problem is fixed. The upgrade of the buildToolsVersion worked. Thank you.