Project

General

Profile

Actions

Emulator Issues #13486

open

Android: Random freezing in multiple games

Added by bsod123456 2 months ago. Updated about 16 hours ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
Android
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

GC: Zelda Twilight Princess / WII: Fragile

Game ID? (right click the game in the game list, Properties, Info tab)

GZ2J01 / R2GJAF

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

I can't find it in Android version.

What's the problem? Describe what went wrong.

In games, it frequently freezes randomly. Especially when the buttons are pressed frequently.

When frozen, the graphic will move back and forth in about half a second of content, and the sound is alright.
Sometimes you can even hear the game content running correctly, but the screen keeps getting stuck in place.
And then, few seconds later, the entire app will freeze completely, then crashed.

What steps will reproduce the problem?

In Fragile(R2GJAF), start a new game, skip the opening.
Then quickly and continuously pressed the touch screen before the 1st tutorial message.
The problems will occur in a high probability.(But not always)

In Zelda TP(GZ2J01), just running around in the first village, it occurred randomly.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes. I tried 5.0-2109x(I'm not so sure about the last number), and 5.0-21148.

Is the issue present in the latest stable version?

I don't know. Android cannot roll back version.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

[First broken version number here (if applicable)]

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

I don't know how to use that. But I uploaded a log.

What are your PC specifications? (CPU, GPU, Operating System, more)

Phone device: iQoo Neo7, Andriod 13
CPU: Dimensity 9000+
GPU: Mali G710
resolution: 2400 * 1080

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

[Anything else here]


Files

dolphin.log (29.6 KB) dolphin.log a log when freezing bsod123456, 02/22/2024 10:10 PM
Screenshot_20240409_045008_org.dolphinemu.dolphin.jpg (278 KB) Screenshot_20240409_045008_org.dolphinemu.dolphin.jpg the error message bsod123456, 04/09/2024 08:38 AM
Actions #1

Updated by bsod123456 2 months ago

Additionally,
I'm not quite sure which is the first broken version.
I haven't updated the version for half a year.

The last version I used before this should have been from half a year ago, and there was no such issue at that time.
The first version I used this time was 5.0-2109x, and this issue occurred.

Actions #2

Updated by Billiard26 about 1 month ago

  • Operating system Android added
  • Operating system deleted (N/A)
Actions #3

Updated by bsod123456 19 days ago

In version 5.0-21264, the issue still exists, but there is an additional error message.
As shown in the attached image.
After displaying this error, the game will be frozen. The menu can be opened, but no response.

Actions #4

Updated by bsod123456 about 16 hours ago

In version 5.0-21453, the issue still exists, and the warning "VK_ERROR_DEVICE_LOST (-4)" is still reported.
So I changed the video backend from Vulkan to OpenGL, then it never crashed again.

Actions

Also available in: Atom PDF