Before doing anything, it is to be noted that this emulator needs specific FinalBurn Alpha roms, like from a FB Alpha (0.2.97.40) romset, and by this I mean that you CANNOT use the same roms that you use for MAME. The easiest way to know if you are using the right ROMs or not, is knowing if the source is for FBA roms and NOT MAME roms, and opening the .zip file to check the extension for the ROMs. For example, in the KOF2002 ROM for FBA, the file extensions are related to the filename (265-c1.c1), while extensions on the MAME ROM often end in .bin (265-c1.bin). Note that you also need the NEOGEO bios to run the games, and they have to be in the same folder as where the roms are going to be added.
An necessary step to run larger games with the VM FBA core is to create an cache for each ROM. By using the romcnv_R2 app, you can create the cache for an single .zip ROM file, or for an folder filled with ROMs, creating one for each rom inside.
Pro users will have additional in-app donation options. Some very supportive users like repeatedly supporting my developments (thanks, I really appreciate that), and the number of people emailing me about not wanting to use PayPal is on the rise. So here's another option to do it. Like getting SuperSU Pro itself, this is completely optional and does not unlock any features (remember there's a checkbox in settings to get all Pro features if you don't want to or are not able to pay for Pro).
+chainfire slight issue: Updated my mtk clone running 4.2 through the play store. It installed, supersu and said the binary needed updating, so I said ok, and chose "normal method", as I always did in the past. It reported 'failed' and supers dumped out. I tried a couple more times, got the same results. So I tried the cwm/twrp method. It rebooted to recovery, flashed the update.zip, then my recovery warned me I had no root access any more. I.e. no su binary, and prompted me to fix it (I use carliv touch recovery). I said no, rebooted, and supersu also reported no su binary. So I said screw it all, downloaded the flashable zip, uninstalled supersu, booted to recovery and installed it. Which lead me to a bootloop. I have never had this before. I wish I saved a log or two, but my last nandroid is about a month old, and I was quite passed at myself for not making one before this, so I just restored without thinking and I have 68 package updates to go on my phone. Just wanted to report an issue. Maybe later I'll try updating the supersu package again and send you a log if I have the problem again.
UPDATE-SuperSU-v2.36.zip, in the script "- Creating space" and "- Restoring files" parts,there is a problem: if there is no "GMS_Maps.apk" "YouTube.apk" or "Maps.apk" ,after install finished,then 3 files named before will be created in "/system/app" folder,but 0 byte,and can not be deleted,hope to fix this.Thanks!
+Chainfire please help stuck in bootloop here. I did a clean install of 5.0.1 (due to custom recovery, franco kernel etc... being unable to OTA), after which i flashed latest TWRP from their site and attempted to install this ZIP from TWRP: -SuperSU-v2.40.zip now I'm stuck with tho colored gooogle dots moving around. am I doing something wrong? which logs do you need? 2b1af7f3a8