Jason Carr

Yup, no problem.

@dunnster Sorry to hear. At this point though, it has pretty much been proven that SD cards do work fine, so there must be some kind of odd permissions or configuration issue. I currently do my main testing on a Galaxy S10+, with the app installed on the internal memory and the data on the SD card. I've also tested this on the S8+, so I'm guessing it certainly should work fine on the S9+. Have you tried deleting the /Android/data/com.unbrokensoftware.launchbox folder from your internal storage? If it picks up the internal storage folder, then it won't pick up the one on the SD card.

0.17 is live now.

I was able to reproduce this and fixed it for the 0.17 release. See a couple of posts above.

Just uploaded version 0.17 to the Play Store with the following: Added Sony PSP Minis platform to valid emulators Fixed an issue where controllers were sometimes not working after returning to LaunchBox from a game Temporarily removed the MESS core option for Retroarch as it is not launching properly Fixed the message box that comes up if no data is found to only show up on initial launch, instead of every time LaunchBox is resumed Hopefully Google makes it live soon. There's not a whole lot of new/fixed stuff for this release, but I figured that the controller bug was important enough to warrant a release today.

Per my previous release post for 0.16, unfortunately Android does not provide an accurate method to determine what is and is not a game. There is a game classification, but unfortunately not all games are properly classified as games. So determining what is and is not a game is basically an impossible thing to do accurately, sadly. In previous versions, I was only showing games that were properly classified as a game, but I noticed that lots of games that I had installed were not showing up, so I had to include unclassified apps as well (though I've heavily filtered down the list to not include a bunch of system apps and such). Eventually, I will add an option to hide things manually, but it will probably be a bit yet. Per auto-deleting games that don't exist, it'll probably be a long time before we add something like that. I think first off, we need to add the ability to add, edit, and delete games directly on Android before we look to auto-delete games. Ah, I'll look into that. What device and controller are you using? Awesome, if you can provide a list of those separate emulators, that'd be great. Then I can add them in and recommend them for users. Currently the exporter only allows adding an entire platform at a time. If you attempt to add games to an existing platform, it will overwrite the current platform XML file, and thus you'll only have the new games. Basically, if you need to modify a platform, you'll need to re-export the entire platform. Ah, good to know. I don't even know how we'd do that on Android. I should go through the list of platforms that use MESS in Retroarch and probably disable them for now (or figure it out). Yes, this is a known issue (see above). Android doesn't really provide a good solution. It will probably be a while yet, as it's a major job. It will be a priority, but considering the amount of work required, it'll probably be a couple months at least.

Thanks for this; sorry, I hadn't yet seen it before my previous reply. The next question is whether these systems are working without LaunchBox, but looking above it looks like the answer is no. In some cases, it could be because of missing BIOS files, or incompatible ROMs, or something of that nature (even could be a glitch with Retroarch on Android for that core). If anyone knows of good, working emulators for these platforms on Android, please let me know, and I can add them in.

Thank you very much for all the testing. For these particular issues, please let me know what emulator/core was used and not working. I would say that most of these issues are most likely emulator issues, but if there is something for us to fix in LaunchBox for Android, it would be good to know that. Gotcha; I just added the Sony PSP Minis platform in for the next Android beta. The exporter should tell you what systems are compatible if you select the option to export your whole collection.

I've personally used an i-Pac controller in a cabinet myself with zero issues. No promises, but if you still have the problem after getting an i-Pac, then it's either a configuration issue or an issue with a different piece of hardware.

You can try disabling keyboard automation, but I'm not sure if that's even in that older version of Big Box. That's probably your best bet. Other than that, honestly no amount of key presses or input should ever lock up a keyboard controller like that, so I would be hesitant to trust the keyboard controller in general. But try disabling the keyboard automation stuff.

I just submitted version 0.16 to the Play Store with the following: New per-platform option to extract ROM archives or not Fixed missing games issue from Android platform; due to the poor classification of games vs. apps on Android, some apps may show up now, but at least all games will be included. Eventually you'll be able to hide apps that you don't want displayed. Added support for two new emulators: My Boy! for GBA and Mupen64Plus FZ for N64 Fixed the PPSSPP Gold emulator Extracted ROM archives are now cleaned up with a max of ten archives kept, and existing archives will be used instead of re-extracting

There's a lot involved with that, so I'm not exactly sure if you'll be able to pull that off or not at this point. In theory, it might work if your Scrape As is arcade on the desktop, but I'm not entirely sure. I have a lot to look into yet with MAME on Android. Thanks @Mu144. DraStic should already be there for DS. Yes, I did, but I was receiving conflicting information from people. Regardless, I've fixed PPSSPP Gold for the 0.16 beta release.

@viking Not sure why that keeps happening, but it should be fixed now.

Thanks for all the testing and updates guys. I'm planning to keep hammering things out, and hopefully we can put out the official release early next week.

At this point, network share drives are not supported. I'm sure we'll add that in eventually, but it probably won't be a focus for a while yet. Aaah, good to know. I wondered if it might have been some kind of issue like that. Glad we finally have that figured out.

We'll get MAME working; the problem is that no one is going to be using such an old ROM set on their desktop PC, so our export process isn't really going to work. Everything is located under /Android/data/com.unbrokensoftware.launchbox/files/LaunchBox. Check to make sure the images exist under Images/[Platform Name]/Box - Front - Thumb subfolder. I still have yet to try this, but I'll give it a shot here soon. I have the latest version of the Shield TV though, so my efforts might not be the same. I expect that ETA will put out a tutorial for that specifically eventually. ETA just put out a tutorial on Friday. Per #1, unfortunately that is just a fluke of Retroarch. I researched for hours trying to find a fix, but unfortunately it doesn't exist. You just have to make sure that Retroarch exits before launching a different ROM. Other emulators exist that work much more properly for Android, and will load up a ROM even if another ROM is running, but unfortunately Retroarch doesn't do that properly. We might eventually have some luck if we report the issue to the Retroarch development team though. Per 7-zip, I'm going to add an option here soon to allow you to choose whether to extract archives before running the game, on a per-platform basis. Per #2, check to see if the images are included in the export package before it is transferred over to your device. In the vast majority of cases, the operation to copy the files to the device is just not completing properly. Unfortunately Windows doesn't do a great job making sure that the copy operations complete properly when copying to Android devices. Also make sure that your collection has box front images for those platforms. Strange with that controller. I'll see if I can pick one up for testing. Sure; I'll add that emulator to my list of emulators to add. All previous versions always extracted archive files, but I'm going to add a platform-specific option to enable or disable it, so a fix for that is coming. I'll also look into Mupen64+ FZ. I'm guessing that this issue is related to not having an option to *not* extract the archives. Hopefully it will work once I add that in.

@bojo5150 You could try disabling game controller support in Big Box to see if perhaps that could be the issue. Other than that, I'm clueless; I've never heard of anything like that before. And sadly, @DOS76 right; I would need that specific hardware to test and try and fix it, and since that issue has never come up before, I'm more inclined to believe it's some sort of configuration issue than an incompatibility with Big Box.

So odd. We've tested 1.8.0 and it's been working fine from our end. What device are you using? Can you try uninstalling and reinstalling PPSSSPP Gold from the Play Store?

What version of PPSSPP Gold are you using?

I just uploaded version 0.15 to the Play Store with the following: New startup screen with file extraction progress bar Now checks to make sure that the ROM file exists before launching in order to reduce confusion Added SNK Neo Geo AES and SNK Neo Geo MVS to the supported platforms for Retroarch It's not live quite yet, but should be soon.

Thanks; I'll look into this. No problem; that is good to know though. Kind of strange, but I believe I've heard something similar from someone else as well. MAME I haven't tackled yet; not sure why that wouldn't be working from LaunchBox, especially since the other platforms are working fine. I'll be taking a look at that later on. We've tested the latest versions of PPSSPP and PPSSPP Gold without issues. Try loading closing it if it's open and then loading it up outside of LaunchBox. You may be prompted to accept permissions. Then maybe you'll be able to launch. If that still doesn't work, check to make sure that your ROM files actually exist on your device in the right folder. Sames goes for Neo.emu. This really sounds like you're missing files; it sounds like maybe they're not all getting copied over properly when you copy them over to your device. I'm putting out a new version now that will check to make sure that the ROM file actually exists before attempting to launch it.

@ETAPRIME just tested PPSSPP, PPSSPP Gold, and the PPSSPP core in Retroarch and all three were working correctly for him with 0.14. What version of PPSSPP Gold are you using?

Alright, well, the next version I put out will at least be able to verify if LaunchBox can see and has permission to the files. It looks like somehow the file extraction process is failing when the games are on the SD card.

Odd. Why are the files .7z.zip files? That could potentially be the issue. Doesn't make sense that it would be if those exact files work from internal storage though.

Those are NES, not SNES, so that 66 megs is about right.