Emulator Issues #11264
closed
Android and DolphinBar
0%
Description
Game Name?
ALL WII GAMES
Game ID? (right click the game in the game list, properties, info tab)
ALL WII GAMES
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
N/A
What's the problem? Describe what went wrong.
Whenever the wii remotes sync up and vibrate the application stops working. If I remove the Dolphin Bar it works fine but I want to use real wiimotes
What steps will reproduce the problem?
Have any wii rom
Open in with the Dolphin app on Android
Connect Dolphin Bar as an otg USB device.
Connect a wii controller
Launch any wii game
Dolphin will crash
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, 5.0-8316
Is the issue present in the latest stable version?
N/A, no android version available
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.)
I do not have time to test every version
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
What are your PC specifications? (CPU, GPU, Operating System, more)
Android 7.0
LG v20 H990DS
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Use a dolphin bar and original wii remotes to try and play any wii game (especially Mario kart wii)
Files
Updated by Helios almost 6 years ago
- Operating system Android added
- Operating system deleted (
N/A)
Newer versions of Android (I think starting in Marshmallow?) broke most USB devices in Dolphin.
Updated by SirBlobman almost 6 years ago
Helios wrote:
Newer versions of Android (I think starting in Marshmallow?) broke most USB devices in Dolphin.
Any plans to fix them? Most of my apps support OTG devices, Especially since my V20 has USB-C
Updated by ScottE almost 6 years ago
- File Dolphin Crash 148.txt Dolphin Crash 148.txt added
- File Dolphin Crash 8449.txt Dolphin Crash 8449.txt added
Issue replicated in 5.0-8449 (logs attached), 5.0-148 (logs attached), and a few interim builds - from NVIDIA Shield TV with Android 8.0.
Two areas that look suspicious in the 8449 logcat:
07-14 11:55:38.161 6406 6505 I DolphinEmuNative: Wii Remote 1 connected
07-14 11:55:38.161 6406 6505 I DolphinEmuNative: Wii Remote 2 connected
07-14 11:55:38.764 6406 6525 I zygote64: Starting a blocking GC Alloc
07-14 11:55:38.764 6406 6525 I zygote64: Starting a blocking GC Alloc
07-14 11:55:38.770 6406 6525 I zygote64: ThreadFlipBegin blocked for 6.380ms
07-14 11:55:38.779 6406 6525 I zygote64: Alloc concurrent copying GC freed 12612(852KB) AllocSpace objects, 0(0B) LOS objects, 50% free, 1488KB/2MB, paused 160us total 15.312ms
07-14 11:55:38.789 6406 6525 I zygote64: Starting a blocking GC Alloc
07-14 11:55:38.798 6406 6525 I zygote64: Alloc concurrent copying GC freed 1762(95KB) AllocSpace objects, 0(0B) LOS objects, 51% free, 1424KB/2MB, paused 127us total 8.667ms
07-14 11:55:38.798 6406 6525 I zygote64: Forcing collection of SoftReferences for 665MB allocation
07-14 11:55:38.798 6406 6525 I zygote64: Starting a blocking GC Alloc
07-14 11:55:38.807 6406 6525 I zygote64: Alloc concurrent copying GC freed 1170(57KB) AllocSpace objects, 0(0B) LOS objects, 52% free, 1382KB/2MB, paused 107us total 9.707ms
07-14 11:55:38.807 6406 6525 W zygote64: Throwing OutOfMemoryError "Failed to allocate a 697303052 byte allocation with 1556480 free bytes and 190MB until OOM, max allowed footprint 2988608, growth limit 201326592"
(That OOM seems weird...that allocation size seems wrong, but is only in the recent (8449) build logs)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] JNI DETECTED ERROR IN APPLICATION: java_array == null
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] in call to GetPrimitiveArray
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] "Thread-31" prio=5 tid=53 Runnable
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] | group="main" sCount=0 dsCount=0 flags=0 obj=0x12d83890 self=0x29203f0a00
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] | sysTid=6525 nice=0 cgrp=default sched=0/0 handle=0x29349f94f0
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] | state=R schedstat=( 49962812 234791 25 ) utm=4 stm=0 core=1 HZ=100
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] | stack=0x29348ff000-0x2934901000 stackSize=1005KB
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] | held mutexes= "mutator lock"(shared held)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #00 pc 0000000000397384 /system/lib64/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPN
S_9ArtMethodEPv+212)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #01 pc 000000000045d588 /system/lib64/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMapb+34
8)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #02 pc 00000000002d5760 /system/lib64/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+1040)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #03 pc 00000000002d5cd0 /system/lib64/libart.so (_ZN3art9JavaVMExt9JniAbortFEPKcS2_z+176)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #04 pc 00000000003585b4 /system/lib64/libart.so (_ZN3art3JNI17GetPrimitiveArrayIP11_jbyteArrayaNS_6mirror14PrimitiveArrayIaEEEEPT0_P7_JNIEnvT_P
h+1452)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #05 pc 00000000001b9d40 /data/app/org.dolphinemu.dolphinemu-W4_b3vTaRJAgM1RQkwN-BQ==/lib/arm64/libmain.so (???)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #06 pc 000000000014126c /data/app/org.dolphinemu.dolphinemu-W4_b3vTaRJAgM1RQkwN-BQ==/lib/arm64/libmain.so (???)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #07 pc 00000000001427b4 /data/app/org.dolphinemu.dolphinemu-W4_b3vTaRJAgM1RQkwN-BQ==/lib/arm64/libmain.so (???)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #08 pc 0000000000143f2c /data/app/org.dolphinemu.dolphinemu-W4_b3vTaRJAgM1RQkwN-BQ==/lib/arm64/libmain.so (???)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #09 pc 0000000000065f88 /system/lib64/libc.so (_ZL15__pthread_startPv+36)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] native: #10 pc 000000000001ed24 /system/lib64/libc.so (__start_thread+68)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504] (no managed stack frames)
07-14 11:55:39.047 6406 6525 F zygote64: java_vm_ext.cc:504]
07-14 11:55:39.269 6406 6525 F zygote64: runtime.cc:492] Runtime aborting...
I don't get what's happening here, but looks like a null-pointer-exception.
Happy to do more debugging, but I'm not familiar with debugging Java and Android stuff.
Updated by billygoat over 5 years ago
- Status changed from New to Duplicate
Updated by JosJuice over 5 years ago
- Is duplicate of Emulator Issues #11372: AndroidTV / NVidia Shield: Using DolphinBar with 2 Wii Remotes crashes on startup added