[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 Albert Vacachanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 --- Comment #7 from Nicola--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 --- Comment #6 from Albert Vaca--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 --- Comment #5 from Albert Vaca--- KDE Connect is already built with buildToolsVersion '27.0.3'. I have no idea what to do to get this fixed :/ -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 villene...@arcor.de changed: What|Removed |Added CC||villene...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 --- Comment #4 from Nicola--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 --- Comment #3 from Ian Kelling--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 Ian Kellingchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 Ian Kellingchanged: What|Removed |Added CC||i...@iankelling.org --- Comment #2 from Ian Kelling --- Created attachment 59 --> https://bugs.kde.org/attachment.cgi?id=59=edit logcat from installing kdeconnect-android, showing the system crash -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)
https://bugs.kde.org/show_bug.cgi?id=389904 Nicolachanged: What|Removed |Added CC||d...@dominiofelice.com --- Comment #1 from Nicola --- Same problem here with CM11 on a Sony Xperia P. More info about this problem here: https://gitlab.com/fdroid/fdroiddata/issues/979 -- You are receiving this mail because: You are watching all bug changes.