New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash and reboot loop #316
Comments
Same here, unofficial cyanogenmod 12.1 for GT-i9001 (ariesve, Samsung Galaxy S+) by Christopher83 from XDA-Developers. The boot intent handler causes memory corruption in system_server. Actually, the linked report in DAVdroid refers to a thread in the Google issue tracker. It's a bug in CyanogenMod / LineageOS, triggered by using aapt2 to build apk files. See here: https://issuetracker.google.com/issues/64434571#comment22 |
Just bootlooped my 4.4.4 carbon. I guess no more trusting updates to yalp store from yalp store without reading changelog. |
The issue mentioned by @karcherm is fixed in new build tools, so here is an apk built with 27.0.1. @forkoz Sorry about your situation. But I am one dev with three and a half phones. This happened on none of them. I cannot check for everything, especially the things I don't write. Also, nothing in the changelog could tell you this would happen. |
This new APK works on my phone. I have recovery so I was able to recover but lost a few settings... ie frozen apps unfroze, receivers became enabled, etc. |
Since the latest version fixes the issue, I assume it's better to close it, update on F-Droid is another topic. |
Looks like the newest version of Yalp Store published on F-Droid is running into the exact same problem as the one below, encountered by DAVdroid on update 1.9.1, immediate system crash on installation, then reboot loop unless deactivating the app through recovery:
https://forums.bitfire.at/topic/1603/replicant-lineage-1-9-1-causing-instant-crash-and-bootloops
Yalp Store version breaking my system: 0.29
Version 0.28 working fine if reinstalling after recovery.
CyanogenMod 12.1, Android 5.1.1, F-Droid 1.0.1
The text was updated successfully, but these errors were encountered: