Project

General

Profile

Actions

Emulator Issues #12980

closed

PR 10783 broke Dolphin on Android using Real WiiMotes and a DolphinBar.

Added by golivax about 2 years ago. Updated about 2 years ago.

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

0%

Operating system:
Android
Issue type:
Bug
Milestone:
Current
Regression:
Yes
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
5.0-16940
Fixed in:
5.0-16944

Description

Game Name?

N/A

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

N/A

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

N/A

What's the problem? Describe what went wrong.

Dolphin for Android won't load anymore after it is configured to use Real WiiMotes (crashes on Dolphin startup).

What steps will reproduce the problem?

Install Dolphin 5.0.16940
Go to Settings - Wii Input - Wii Remote 1
Change from Emulated to Real Wii Remote
Go to Config - Wii
Enable Wii Remote Continuous Scanning
Enable Wii Remote Speaker
Go to game selection screen and confirm that INI file has been updated
Close DolphinTry to open Dolphin

Dolphin will try to launch, but will crash immediately.

**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. Problem happens on Dolphin 5.0.16940 onwards.

Is the issue present in the latest stable version?

No (5.0-16793)

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.)

This regression was introduced in PR 10783 (Dolphin 5.0.16940), which changes how Dolphin initializes controllers.

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

N/A

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

This is all I have for logs:
https://www.dropbox.com/s/1fmeowdnhm4nn6b/dolphin.log?dl=0

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

Phone is a Galaxy S10 with Snapdragon CPU running Android 12.

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

N/A

Actions #1

Updated by JosJuice about 2 years ago

Is it possible for you to run logcat? Getting logs from there would let me know exactly where in the code it's crashing.

Actions #2

Updated by JosJuice about 2 years ago

  • Milestone set to Current
  • Regression changed from No to Yes
  • Regression start set to 5.0-16940
  • Operating system Android added
  • Operating system deleted (N/A)
Actions #3

Updated by golivax about 2 years ago

JosJuice wrote:

Is it possible for you to run logcat? Getting logs from there would let me know exactly where in the code it's crashing.

Hey,thanks for quickly following up. So I tried to install and use a LogCat reader app, but it seems that either the phone needs to be rooted or some adb setup needs to be done using a PC. I'll try to do the latter tonight or so.

Some additional info: I never got Dolphin to recognize the DolphinBar via the front-end. Only when starting up a game, Dolphin would request permission to access the DolphinBar and then controllers would vibrate and everything would work.

Actions #4

Updated by golivax about 2 years ago

Here you go: https://www.dropbox.com/s/g52gwrj6sf6r3ml/logcat_07-19-2022_16-46-58.txt?dl=0

I did the following:

  • Ran LogCatReader app
  • Started recording logs
  • Followed all steps to reproduce the issue (open fresh dolphin install, configure it to use real wiimotes, exit, try to open Dolphin again, Dolphin crashes)
  • Stopped recording the logs

Hope this helps :-)

Actions #5

Updated by JosJuice about 2 years ago

Thanks! With the two logs combined, I think I was able to track down the issue. Could you test if it's fixed in this pull request build? https://dl.dolphin-emu.org/prs/c7/fa/pr-10877-dolphin-latest.apk

Actions #6

Updated by golivax about 2 years ago

JosJuice wrote:

Thanks! With the two logs combined, I think I was able to track down the issue. Could you test if it's fixed in this pull request build? https://dl.dolphin-emu.org/prs/c7/fa/pr-10877-dolphin-latest.apk

Wow, that was fast! And yep, it does fix the regression :-)

Actions #7

Updated by golivax about 2 years ago

JosJuice wrote:

Thanks! With the two logs combined, I think I was able to track down the issue. Could you test if it's fixed in this pull request build? https://dl.dolphin-emu.org/prs/c7/fa/pr-10877-dolphin-latest.apk

Thanks a lot!

Actions #8

Updated by JosJuice about 2 years ago

  • Status changed from New to Fix pending
Actions #9

Updated by JosJuice about 2 years ago

  • Status changed from Fix pending to Fixed
  • Fixed in set to 5.0-16944
Actions

Also available in: Atom PDF