Running mGBA on the Wii through the Homebrew Channel, I find that the system hangs a lot and has other odd issues like:

- after exiting a game: hangs for a few seconds to 20 mins to >70 mins before returning to file menu
- write save state: delay of 2 seconds (normal!) to 20 mins

- there seems to be writing above the visible part of the screen.  The first line I can see in the menu is the current location path e.g. "usb:/", then the second line is (up)

- after exiting a game, and the file menu pops up, sometimes it shows me the wrong info.  For example, it shows the path "usb:/GBA_Roms/", but the file/folder list underneath is actually displaying the contents of the root usb directory "usb:/"  Going (up) a level took >10 minutes.  After I re-selected the GBA_Roms folder to select my game, the system hung again for >10 minutes, then showing "usb:/GBA_Roms/" again but still displaying the root directory's contents. Then selecting GBA_Roms again for fun, it system hangs for a few minutes and goes to usb:/GBA_Roms/GBA_Roms, which is a folder that doesn't even exist.

- due to all of this freezing, I rarely exit properly, and it seems like none of my savegames are sticking.

Any tips?  

I have 2 partitions on the usb HDD.  The first one is FAT32 with mGBA and my roms, and the other partition is NTFS because I had a bunch of wii games on it.  Would this be contributing to these errors?  Thanks in advance.


###Edit 1:
Did some more testing and googling.  When using retroarch:  Mother 3 seems to induce this post-close freeze 7 of 7 times.  Riviera did 1 of 2 times.  Mario Tennis I think worked as it should (0 of 4).  Summon night: swordcraft story seemed to work normal (0 of 2).  Is this special to mother 3?  To 32MB games?

Using mGBA by itself, it still seems to hang a lot while exiting for a bunch of games.

Are cheats available for mGBA for ps vita, if so can someone help me please and thank you if not will there be available for the PS Vita

I have this mayflash snes adapter that works well with mGBA, but for some reason mGBA defaults my controller to the second gamepad option, which means every time I load up mGBA I have to manually change it back to controller 1. The big problem is that no matter what controller (XB1, SNES, 360 etc.) it still sets to the SNES #2 gamepad. I tried reinstalling the drivers a couple times, getting 7.1 and it's still happening. Is there anything that I can do like find the config and force the controller to choose 1? Can this be possibly addressed in a later build? I'd appreciate any solutions from yall, thanks.

I recently formatted my pc and when opening the emulator several things do not work, for example, the saved games do not read if I do not put "Load Alternate state", does not apply any shader (I have enabled openGL in the graphics) also does not show the library. Open the file "config.ini" and in the configuration the paths are well configured (savegamePath=C:/Users/marta/Downloads/mgba/file/save_games), besides having set the configuration of the shader I want you to use (shader=C:/Users/marta/Downloads/mgba/shaders/gba-lcd-combo.shader), but the gamepath does not appear to show the library at the beginning. It could be that the emulator saves in some place another configuration file that causes the arrores, or as it could solve what is happening, thank you very much.

Hello everyone,

I'm a Ubuntu user and I wanted to report that I am having a dependency problem with the binary package for Ubuntu 18.04. Versions till 0.6.3 worked fine, however since version 0.7.0 (including 0.7.1) I get the following message:

Are there future plans to run the e-reader cards in mgba?

Hi all, I’m having some issues playing Zelda link to the past using mGBA on the Nintendo switch.

Certain items don’t work properly and sort of “stutter” 

example Pegasus boots: the boots start to activate, but just stutter no matter how long I hold down the A button. If I try to walk, I move at something like 2/3 normal speed. It's almost like the A button is repeating like a keyboard key instead of just staying on the whole time.


Any thoughts of how I can fix this? Thanks all

I've really been enjoying the 3DS port of mGBA, but had a few suggestions for features it would be nice to see in future releases:

- Remapping controls: Being able to map controls by button- so I could use L/R as Start/Select as well as keeping the Start/Select buttons still enabled. Also, the ability to use a touch screen tap as an input would be useful as well as being able to map separate control schemes for GB/C and GBA.

- Autofire: would love to see this implemented, as it's standard in most other emulators.

- 3D slider support: as seen in other emulators such as VirtuaNES and Snes9x for 3DS, enabling the slider, even without the 3D effect, enhances image quality on the 3DS top screen.

- File Browser improvements: An option to hide non .gb/.gbc/.gba files from appearing in the browser would be great, as well as scrolling text for titles that get cut off at the edge of the screen. Having the browser open on the last title you launched would also be a helpful feature.

Thanks so much for your work on this, endrift!

Are there any plans for an Android Port of the emu? 
Also are you planning on adding the multiplayer feature on the DS emu?

I know that medusa is in alpha phase, or pre alpha xD, but I wanted to know if there is any dependence out of the common with mgba, because when trying to compile medusa I get this error.