rafaelvcaetano / melonDS-android

Android port of melonDS
GNU General Public License v3.0
787 stars 48 forks source link

melon nds #138

Closed maylotex closed 3 years ago

maylotex commented 3 years ago

Problem:
Insert a small description of the problem.

Stack trace:

me.magnum.melonds.ui.emulator.EmulatorActivity$f: Failed to load ROM: NDS_FAILED
    at me.magnum.melonds.ui.emulator.j$e$a$a.a(Unknown Source:204)
    at f.a.b0.e.e.a.o(Unknown Source:10)
    at f.a.s.a(Unknown Source:14)
    at f.a.b0.e.b.e$a.d(Unknown Source:26)
    at f.a.b0.e.b.l$a.d(Unknown Source:2)
    at f.a.b0.e.b.j$a.run(Unknown Source:21)
    at f.a.r$a.run(Unknown Source:9)
    at f.a.b0.g.j.run(Unknown Source:13)
    at f.a.b0.g.j.call(Unknown Source:0)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:764)

Configuration:

RomCrashContext(emulatorConfiguration=EmulatorConfiguration(useCustomBios=false, dsConfigDirectory=null/, dsiConfigDirectory=null/, internalDirectory=/data/user/0/me.magnum.melonds/files, fastForwardSpeedMultiplier=-1.0, useJit=true, consoleType=DS, soundEnabled=true, micSource=BLOW, firmwareConfiguration=FirmwareConfiguration(nickname=Player, message=Hello!, language=1, favouriteColour=0, birthdayMonth=1, birthdayDay=1), rendererConfiguration=RendererConfiguration(videoFiltering=LINEAR, threadedRendering=true)), romPath=/storage/raw//storage/emulated/0/Download/PKM_Platino_ByRichardGames.nds, sramPath=/storage/raw/storage/emulated/0/Download/PKM_Platino_ByRichardGames.sav)
rafaelvcaetano commented 3 years ago

Could you try putting your ROMs in a different directory outside of the Downloads folder? Don't forget to update the ROM search directory in the emulator settings.

shabbirmahmud commented 3 years ago

Can you use the latest beta v1.3.0 and open a new issue? The latest version does not fix the problem but includes additional info that will help to find the cause.

rafaelvcaetano commented 3 years ago

If your problem is not yet fixed, try the latest Beta 1.4.0 release. If the problem is not fixed, please open a new issue.