libretro
[Android] While a game is loaded with mupen64plus on RetroArch, returning from phone sleep and switching apps Crash or Black Screen RetroArch
This is a bug I have noticed for quite some time with various devices running Android. If you switch apps / go to a recent app and then back to retroarch/ Come back from sleep mode to RetroArch, RetroArch loaded with a game with Mupen64 will either crash (noticed with various Samsung phones throughout the years) or comes back to a black screen with the audio still playing but none of the controls work (Happens on Retroid Pocket 4 Pro).
Here are some logs for @m4xw, should they help. retroarch__2024_10_13__22_06_20.log retroarch__2024_10_13__22_06_14.log retroarch__2024_10_13__22_05_49.log
Seems the audio driver stops which i guess could cause some unexpected behaviour inside of RA Can you check that 1. it doesnt occur with NULL audio driver, 2. it doesnt occur with "pause sounds in menu" (cant fully recall the name of the option) @fireflamesniper
For what it's worth, it's the same issue on a Mali G68/Android 11 device here. retroarch.log
...
[GL]: Found GL context: "egl_android".
[GL]: Detecting screen resolution: 0x0.
[EGL]: Created shared context: 0x78c5ebe3c0.
[EGL]: Current context: 0x78c5ebfda0.
[GL]: Vendor: ARM, Renderer: Mali-G68 MC4.
[GL]: Version: OpenGL ES 3.2 v1.r26p0-01eac0.51fd9afee4759fa64b94f75851712457.
[GL]: Using resolution 1334x750.
...
*Device: Retroid Pocket 4 (Base, non-pro)
Happens to me too since forever on a Realme 7 5G which uses a Mali-G57 MC3 using the Vulkan driver/renderer.
Retroarch version: 3ab3b32. Android version: 12
Here's my log, retroarch.log
And a screenshot:
I'm also having this problem, all default settings, playing on Samsung S24 Ultra, Android 14.
Crash log is here: https://pastebin.com/1dkvdsSm
I've noticed that this is specific to this core. This issue doesn't happen when using ParraLLEI, but that core has a host of other problems which make it a less ideal choice than this one.
I hope you can solve this problem at some point, I really want to play without worrying about that eventuality and losing a game in the process.
I hope you can solve this problem at some point, I really want to play without worrying about that eventuality and losing a game in the process.
If there ever is a solution, this issue will be referenced as is appropriate, so no need for re-pinging active threads that the maintainer has already acknowledged (unless you have something to contribute to the conversation or the problem, ofc).
So, there is a fix for this! If you change Polling Behavior to Early for this core, it fixes the issue perfectly! At least in my case it did. I attempted this on a fresh install of 1.20 and the latest N64 cores.
So, there is a fix for this! If you change Polling Behavior to Early for this core, it fixes the issue perfectly! At least in my case it did. I attempted this on a fresh install of 1.20 and the latest N64 cores.
Does not resolve the issue on Mediatek though.
Seems the audio driver stops which i guess could cause some unexpected behaviour inside of RA Can you check that 1. it doesnt occur with NULL audio driver, 2. it doesnt occur with "pause sounds in menu" (cant fully recall the name of the option) @fireflamesniper
Tried both 1 & 2, same issue. My device is an S24 Ultra, fresh RA 1.21 installation, but also happened in 1.20.
So, there is a fix for this! If you change Polling Behavior to Early for this core, it fixes the issue perfectly! At least in my case it did. I attempted this on a fresh install of 1.20 and the latest N64 cores.
Lucky you. It didn't work for me on an S24 Ultra, 1.21 RA fresh install.
here's another log for you.
obviously context_reset doesn't work.
i think the 0x0 thing is a red herring though...
(it also resets back to the default controller overlay instead of the n64 one. i only noticed because i didn't press any buttons on my physical controller for this test)
on my device i can still hear sounds and pressing buttons works, it's just the video doesn't reinitialize.
retroarch__2025_08_05__10_27_21.log
pretty sure this issue isn't specific to Android. see #158. other (likely) duplicates: #77 #364 #442 #445 #575
... reinit_gfx_plugin literally doesn't do anything after the first startup if you haven't set it to ParaLLEl-RDP...
or did i read first_context_reset backwards? it needs a debug message tbh
This needs to be a higher priority issue. I'm getting this black screen problem on two different Android devices with fresh installs of Retroarch using stock unmodified settings.
The core is completely unusable in this state, I've had to use ParaLLEl instead.
This needs to be a higher priority issue.
Feel free to submit a PR that fixes this issue, then. Or make a bounty so someone else has an incentive to fix this more promptly if you really feel that strongly about this.
This pull request may fix this without needing any changes in the core:
- https://github.com/libretro/RetroArch/pull/18484
Can in fact confirm the above PR resolves this issue (plus preserves the image for GL cores). <3
Can in fact confirm the above PR resolves this issue (plus preserves the image for GL cores). <3
Yessss