mirror of
https://github.com/dolphin-emu/dolphin.git
synced 2025-07-24 01:41:50 +00:00
136e835fb4
1) Most of the times the native heap is kept around even after the activity
is killed, we can ask the native code if it is still running and resume
the emulation if that is the case.
2) In case the native heap is freed and the emulation can't resume we used
a temporary state to load on the game boot.
I couldn't find a way to test this, if you want to test this schnario,
add this block to EmulationFragment.
public void onDestroy()
{
stopEmulation();
super.onDestroy();
}
onDestroy is only called if the acivity killed by the OS and not be rotation
change whihch in this case will make sure to kill the emulation and start
again when the activiy is re-created.
|
||
|---|---|---|
| .. | ||
| app | ||
| gradle/wrapper | ||
| jni | ||
| .gitignore | ||
| build.gradle | ||
| code-style-java.jar | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| settings.gradle | ||