Jason Carr

@Neosoul Did you get it to work with the sideloaded version? You probably just need the sideloaded version, which is pretty easy to download and install. You can download the APK from the RetroArch website. Or, if you'd rather just give up, just email us at support@unbrokensoftware.com.

I'm guessing you're referring to Tools > Clean Up Media?

Google has been imposing *new* restrictions on apps in the Play Store. So it's possible (and maybe likely) that older versions from the Play Store worked just fine, while newer versions do not. Unfortunately we don't have any debug logging in place specifically for the launching of RetroArch. We could certainly add it in some form, but Android doesn't really make it easy to log how an application is launched (nor does it make it easy to launch). It's not straightforward like the command line is on the desktop.

Alright, LaunchBox for Android 1.2-beta-5 is out now with the following: Loading up emulators should be slightly less jarring now (Android's launching animations have been disabled when launching emulators) RetroArch will no longer require you to complete exit the game before launching a new game Added support for the following new platforms: Amstrad GX4000, Capcom Play System, Capcom Play System II, Capcom Play System III, Commodore Amiga CD32, Nintendo Famicom Disk System, Nintendo Satellaview, Philips CD-i, Sega Naomi, Sega Naomi 2 Fixed an issue where backing out of the metadata search page with a controller was backing completely out to the filters view Several improvements to the three built-in themes Thank you all for the testing and support. We're hoping that this will be the release candidate for the 1.2 official release, which should hopefully go out early next week. Please let me know if anyone runs into any issues with this beta. Also, please note, some improvements have been made to the built-in themes since the previous betas, and so they are updated in this release. However, in order for folks to be able to upgrade them in the future, we do not automatically replace your existing theme files. So you may want to delete your Themes folder (or at least the three built-in themes folders) from your LaunchBox folder in order to receive these theme updates.

Just FYI, finally looked into adding Lemuroid support. Ran into this thread here: So it looks like the developer isn't supporting launching from other frontends. Let me know if anyone discovers otherwise. As for now, we won't be diving into it any further.

Sadly, I still can't seem to reproduce it with those steps. I'm guessing it's something specific to the Odin, or lower-end devices, or something like that. It's possible though that it was actually fixed in beta 4. Can you test to see if you can still reproduce it?

Thanks, we fixed that image size (Raiden) issue in the latest beta.

LaunchBox for Android 1.2-beta-4 is out now with the following: Three themes are now included with the app: Alisia, BannerBox Lite, and The Grid Image downloads have now been limited to 2000 pixels wide and 2000 pixels tall, which will reduce media storage space requirements and increase performance and stability Fixed an issue where excessively large images (bigger than 4K) could crash the app on some devices Fixed an issue where the Sort Title field was not being used properly to sort the games in the games views

Okay, so you're trying to manually tweak the XML files? Most likely that is the issue; I'm guessing LaunchBox for Android doesn't know how to deal with both platforms, and it's probably thinking they're one and the same, or something like that. As of right now, LaunchBox expects platforms to be only platforms that it knows about. It doesn't yet know how to properly deal with custom platform names and such. So we'll need to implement that stuff before we can get something like this working.

Trying to brainstorm what this could be. We have heard of this issue before, but everything works just fine in our testing, so it's been difficult to pinpoint exactly what the issue is for users that are running into it. One hunch that I have is that it could be related to where you're downloading RetroArch from. Are you using a version from the Play Store? RetroArch is now saying that versions from the Play Stored are nerfed, and are no longer recommended because of Google's stupid restrictions (which is also one reason why LaunchBox is not on the Play Store). It would be great if we could figure out exactly what the issue is though, because I'd like to have an answer for folks in this situation going forward. This is my best guess as to what might be going on though.

@RenniG Sorry for the late reply here. Usually when this happens, it's because the game is ending up as an additional version of another game (probably Mega Man Star Force 2 or 3). That is still a mistake on our part that we need to fix, but that is likely what's going on.

I'm confused as to what exactly is happening here. In my testing, it is working correctly to replace one of the default banners with a custom image. What are you trying to replace and how is it not working?

FYI, this issue should be solved with version 1.2-beta-4, which should be out before the end of the day.

Still trying to resolve this issue, but we have not been able to reproduce it as of yet. If anyone is willing to help, we could use a log file and/or any confirmation if it's still happening with the latest beta release (1.2-beta-3).

Generally, the memory usage is because of all of the large images we use for the various themes/views. We could probably get the memory usage down some by providing options for the cached images to be smaller. We're not actively targeting devices with as little as 2GB of RAM, though, admittedly. Those devices are definitely more lowend than we're shooting for. That said, we may offer more options for that kind of thing in the future, but it will probably be a bit.

Can you clarify this? I haven't been able to reproduce it, but I have heard about it from a couple different people. I assume you're referring to Edit Metadata (on a game) > Search, correct? What does it do when it fails?

Unfortunately not at the moment. I'll note the request though.

That is certainly strange. My guess is that maybe this would be caused by a different version of that RetroArch core, maybe it's broken for some reason? Can you try an older version of the core? I'm really not sure what else it would be. Were you running the same version of LaunchBox for Android on the old SD card?

I can confirm that all you need to do is just re-run the installer over top. The installer does not make any registry changes, outside of installing DirectX, .NET, and C++ if needed.

Did you respond in the wrong thread here? This doesn't seem relevant to this thread. Or maybe I'm confused, idk. Regardless, there are no known issues launching games in RetroArch. We've tested that on many different devices without any issues.

LaunchBox for Android 1.2-beta-3 is out now with the following: Fixed: Navigating to a game without metadata was causing the background threads to get clogged up, so that images were not loading properly Fixed: Single-pressing games in the box grids was not working in some views Better performance when navigating with a controller @faeran is also working on updating the custom themes that are available here on the forums to fix some issues and improve some things.

Interesting, no we don't have anything like that for LaunchBox for Android (or even in LaunchBox for Windows). I believe you're the first to request it. I would suggest making a BitBucket ticket for it via Help & Support > Request a Feature at the top of this page.

MAME is definitely a supported platform. It's listed as Arcade, since "MAME" is an emulator, not a platform. If I recall correctly, I do believe people have been able to get FBA working as well, though I have not tested it specifically myself. I'll put FBA4droid on my list to review.

Interesting. We don't do any IP banning at all for those downloads, so I think something else must be going on. Unfortunately it looks like it's specific to that device. If anyone can provide a log file, that might help.

We have documentation coming before the offiical release, but unfortunately it's not finished yet.