-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Daijisho being killed after Going from Emulator back to Daijisho #710
Comments
Maybe the last update broke it. Did it happen before the latest update? |
I just got my Odin 2 two days ago, so I'm not sure. However, I did not have this issue with my Retroid Pocket 4 Pro a few weeks ago. (I have since sold it so I can't test currently.) Also, thanks for getting back to me so quickly! |
Lemme see if I can fix that in next update. ( |
Cool! Thanks for looking into it! |
I hope the problem is resolved. |
Hi there, Tapioca! It's not unfortunately. It will still close out on 1.4.74. It usually happens with larger file games like Switch or Wii. It doesn't seem to have gotten better or worse. But it should be pretty easy to replicate if you open a Switch game and play for a few minutes and then back out. It will reload the front end. It happens about 1/3rd of the time with larger games and randomly with others. For reference, I am using Beacon Game Launcher the past few days and the issue does not occur there. |
@outlandernwah May I ask what device/system you are using? Perhaps some specs for reference. |
Sure! Latest update on the base model of Odin 2 (8GB RAM SD8G2) |
Hmmm seems like a rather mid-higher end side. Are there any peculiar logs in the logger. It could probably killed by your OS scheduler aggressively. |
Daijisho is set as my home app on my Odin 2. However, every so often when leaving a game, Daijisho will reload. It's like it's closing out/restarting on me or leaving memory. I have it as Battery Unoptimized. Not sure what the issue is but it's definitely annoying.
Any ideas? Maybe a way to keep it in memory?
The text was updated successfully, but these errors were encountered: