Hans-Christoph Steiner
Hans-Christoph Steiner
And I can reproduce this crash on my machine in an account that has KVM access, with Nexus_5X_API_29 created via Android Studio's GUI: ```console $ /opt/android-sdk/emulator/emulator-headless @Nexus_5X_API_29 -no-accel -no-window -verbose...
Since there seems to be related progress, I did a quick test of `-no-accel`. Unfortunately, it seems it is still just an early core dump: ```console root@6317bb8513ba:/builds/eighthave/fdroidclient# avd_name=Pixel2 root@6317bb8513ba:/builds/eighthave/fdroidclient# emulator...
Actually, adding `-no-window` seems to have fixed the core dump, but I'm still waiting for the emulator to actually boot: ```console root@6317bb8513ba:/builds/eightahve/fdroidclient# emulator -avd $avd_name -no-accel -no-window emulator: Android emulator...
Made some progress. I can get the x86* system image booting without KVM, e.g. with `-no-accel`, then our test suite passes like 25% of the time, otherwise there is a...
One key thing is sticking with a specific, proven version of the emulator. It has been broken and fixed and broken and fixed over the years.
If a new release is tagged, then its easy for F-Droid to update
I've used it on Android 14 and it works still. Not as well as before, but still useful
@googlebot I signed it!
I see you just refactored the _Dockerfile_ template handling. I think it probably makes sense to just include these changes in the _Dockerfile_ templates. I can't figure out which Docker...
Seems to be just a random warning from Android itself: https://stackoverflow.com/a/24229604