Project

General

Profile

Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27?

Added by Xan VFR 14 days ago

If I understood correctly, Google made some changes in its SDK v27 that causes crash/reboot loop when installing/upgrading apps developed with SDK v27 in some Android derivatives, such as Replicant (and LineageOS, for instance).

If that's the case, is there any provisional patch/solution?

Or did I just misunderstand the issue?


Replies (10)

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by green blue 14 days ago

I would also be highly interested in this. I have successfully set up the build environment for Replicant 6.0 in the last couple of days, but my own images show the exact same behaviour as the official builds.

What kind of changes could be made during the build process to mitigate this problem? I have read about the deactivation of aapt2, but due to lack of experience with the Android world (and, as a consequence, the build environment) it is unclear to me how exactly this is done, and if there's a need to do this on the OS side, on the app side, or both.

Are there any simple commands/scripts that could be used so we can build our own, working images until there's a new official release? Or does this approach make no sense?

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by green blue 12 days ago

Short update: I have now managed to build Signal with disabled Aapt2, and this seems to work normally with the official Replicant image. I will try building more apps (e.g. Firefox Focus/Klar) that way in the next couple of days, but this is ofc not a viable solution for most users. Would still be interested in learning which changes are necessary to the OS so that it works normally with apps that have Aapt2 enabled.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by Dustin Oury 12 days ago

Apparently my Note 2 was hit by this as well. Opening Keepassxdroid causes a reboot loop, and attempting to uninstall the program causes a "program uninstaller stopped unexpectedly" message.

edit: Tried again while writing this message and it looks like it uninstalled successfully. Trying to install KeepassDX as an alternative caused a reboot. Oh well.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by Finn Ryan 7 days ago

I installed the Signal apk from the website and replicant 6.0 crashed for me when I launched it, and proceeded to boot loop. I saw other people mention using safe mode to uininstall it, but that still caused a boot loop for me. I'm using an S2. I had to replace the default replicant recovery with TWRP https://dl.twrp.me/i9100/ (using heimdall, same method as installing default recovery here https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100Installation ) as the the default didn't allow me to browse files, mount the FS with MTP to connected PC or use adb (I guess I didn't have it enabled in developer options? I've always found it silly that the setting in the android OS prevents you from using adb from recovery before OS launches, so if you get bootloop and it wasn't enabled you can't use adb to fix.)

With TWRP booted (power+home+volume up when turning on) I went into the Advanced>File Manager (you need to make sure the data partition is mounted, can't remember where option is) and delete the offending applications directories under both /data/data and /data/app. Eg I deleted /data/data/org.thoughtcrime.securesms and /data/app/org.thoughtcrime.securesms . Then clear your cache - I think just the davik cache, but may as well clear the "cache" and "davik cache" or something like that. Make sure not to clear your data or any other partitions, this will lose you actual user data and installed apps. Then reboot and hopefully you're back in business. This worked for me, but I'm no expert so proceed at your own peril.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by Wolfgang Wiedmeyer 6 days ago

These reboot loops shouldn't happen anymore with the latest release (0003) which includes a fix.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by green blue 6 days ago

Dear Wolfgang, thank you (Dankeee!) for the update. I will try it out on my i9300 as soon as possible. I'm still pretty much a beginner in the Android world (was even living without a phone for a while, before i gave Replicant another try), and I def. need to learn more before i could solve problems like this myself.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by Xan VFR 5 days ago

Wolfgang Wiedmeyer wrote:

These reboot loops shouldn't happen anymore with the latest release (0003) which includes a fix.

Thanks a lot, Wolfgang! You rock, man! ;-)

Hope I'll be able,at least, to install latest 0003 image for the S3 tomorrow and test no crashes/reboot loops happen anymore.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by Dustin Oury 4 days ago

I can confirm that with an update to the Replicant 6 0003 version that a loop doesn't happen anymore. Although there was an issue with Keepassdroid freezing and making a soft reboot, it did not loop, and I was able to uninstall after. Not sure what the problem there is.

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by Xan VFR 4 days ago

Me too.

Upgraded Replicant in my test S3, and could upgrade, (un)install apps and reboot without any problem all day long.

Did the same thing in my S3 for daily use after those tests were successful and Replicant 6.0 0003 works like a charm!

Great job! Thx a lot, once more!

RE: Are Replicant developers aware of the reboot loop caused by apps developed with Google's SDK v27? - Added by green blue 2 days ago

Hey, i wanted to add that my S3 (i9300) is back to normal behavior as well, regarding most apps. E.g. no random crashes, no reboot loops for the usual suspects from the F-Droid store mentioned elsewhere. Strangely though, Orfox and Icecat both crash reliably a few seconds after opening them, at the latest when i'm trying to open any website. Since both are Firefox derivatives, it might in this case rather be a problem with those apps or their upstream source, right? Did anyone else run into this issue (although this might be the wrong place to ask)?

    (1-10/10)