JosJuice 003696fd78 Android: Fix race condition when exiting emulation ... The main activity loads settings essentially as soon as it starts, in order to determine which tab to show. If the process of stopping emulation has not finished at this point, a race condition may be triggered where two IOS kernels are created at once due to the emulation thread loading or saving the SYSCONF while the GUI thread is loading the SYSCONF. To fix this, we can wait for emulation to fully end before returning. Because this race condition is hard to reproduce, I have not been able to test that this actually fixes the race condition, or even that the cause of the race condition is exactly what I believe it is. But I am relatively confident.		2020-09-15 19:10:56 +02:00
..
app	Android: Allow editing settings during emulation	2020-09-15 19:10:56 +02:00
gradle/wrapper	Bumps compile API to 29 (Q) removes unecessary casts and deprecated	2019-11-22 13:17:37 -03:00
jni	Android: Fix race condition when exiting emulation	2020-09-15 19:10:56 +02:00
.gitignore
build.gradle	Android: update to Gradle 3.5.3	2019-12-06 12:13:53 -05:00
code-style-java.xml	Android: Update code-style-java for androidx files	2020-09-08 05:59:08 -04:00
gradle.properties	Bumps compile API to 29 (Q) removes unecessary casts and deprecated	2019-11-22 13:17:37 -03:00
gradlew
gradlew.bat
settings.gradle