Jason Carr

Thanks much; I've fixed this for the next beta. I've also removed the option to use Favorites as your root or secondary filter, because it just doesn't really make sense. Thanks for the report.

Also, it's worth noting that the issue with DraStic seems to be their latest versions, not just Android 13 (though they may also have an issue with Android 13 lol).

Yes, it definitely wouldn't hurt. We're more than happy to work with them if we can establish contact. Feel free to give them our support@unbrokensoftware.com and we can follow up, or they can always contact us on the forums.

I've removed all duplicate games in the database, and added a restriction to the game table on the database that no two games can have the same title and platform. There were roughly 300 duplicates in the database that have been deleted. Going forward, in the very rare case that there are two different games with the same title for the same platform, we should add them as Game Title (Developer Name). This should stop any back and forth with games getting deleted and re-added because they're assumed to be duplicates, and should help us maintain a much cleaner database. Thanks everyone for your feedback and help on the database.

Alright, apparently I re-introduced the duplicate games issue in the last update, sigh. It should be resolved now. I'm also working on removing the duplicates that were introduced in the mean time.

Sorry for the super late reply. Just catching up on Android issues on the forums.

This is fairly odd, because we do a ton of testing with Xbox controllers and we've never seen this. Admittedly though, I've only used Xbox One and Xbox One X controllers in my testing, but 360 controllers are so similar that I doubt that's the issue. I'm wondering if maybe there's an issue with the device itself, or the operating system or something. What device are you using?

They are stored in the LaunchBox folder, but only if they are changed. The default images are stored in the app itself.

FYI, make sure you're using a paid EmuMovies account. That's the only way downloading videos in LaunchBox for Android will work.

We did our best to fix this for LaunchBox for Android 1.9-beta-1, but unfortunately it's clear that something is broken in DraStic itself, because nothing seems to work to launch games. None of the other frontends out there seem to have this working either, so sadly I think it's safe to say that launching games with DraStic is broken as of the current version.

We did our best to fix this for LaunchBox for Android 1.9-beta-1, but unfortunately it's clear that something is broken in DraStic itself, because nothing seems to work to launch games. None of the other frontends out there seem to have this working either, so sadly I think it's safe to say that launching games with DraStic is broken as of the current version.

Hey all, I just put out LaunchBox for Android 1.9-beta-1. See here: It has fixes for Skyline, M64Plus FZ, and M64Plus FZ Pro. Unfortunately though Snes9x EX+, DraStic, GBC.emu, and PizzaBoy all need updates from the emulator developers before we can make them work. Please let me know if you run into any other emulators that aren't working on Android 13.

The very best thing to do for MAME on Android is to download the RetroArch sideloaded APK from the RetroArch website and use the official MAME core with a recent ROM set. You'll want to use the core that doesn't have anything special on it or a date on it. Just "MAME".

If you have an EmuMovies account, you should be able to just import and download the videos directly on Android with no need to use the exporter. Otherwise, yeah, I see the issue.

@dmaker If you're still having trouble getting games to work with RetroArch, make sure you're using the sideloaded version (download the APK directly from the RetroArch website and not from the Google Play Store). Unfortunately Google has forced RetroArch to cripple the version in the Play Store and it has many issues.

LaunchBox for Android 1.9-beta-1 is out today with the following: Fixed issues with launching the following emulators on Android 13: Skyline, M64Plus FZ, M64Plus FZ Pro For other emulators that still need to be updated in order to work correctly launching games on Android 13, LaunchBox will now warn the user and just launch the emulator without a game instead (instead of erroring out) We have two big new features that are in the works, but unfortunately they're not ready yet (and one of them is waiting on outside involvement). Stay tuned. Also, we've tested and tried to fix Snes9x EX+, DraStic, GBC.emu, and PizzaBoy, but all of them are unfortunately broken on Android 13 and there's nothing we can do to fix it that we're aware of until the emulator developers release their own updates/fixes.

Thanks for the heads-up; will look into it.

I don't really understand the issue here. You should be able to use the same hard drive between your Windows PC and Android (assuming you're just plugging and unplugging it, and assuming that Android can actually see the drive). You won't be able to share the data XML files between Windows and Android, but it doesn't sound like that's what you're trying to do. You should be able to just import the games on Android and things should ultimately work. Or are you trying to use the Export to Android process? Is that the issue?

I will admit that I've never had videos for my Android games, so I've never really tested that either, but I also don't know of a reason why it shouldn't work. I can test it out though and see if I can replicate any issues.

Yeah, again, you probably have the wrong core selected in the LaunchBox emulator settings.

Okay, it should be automatically launching the games. I'm guessing maybe you have a different MAME emulator core selected in LaunchBox than what you have downloaded in RetroArch. So you probably just need to go in and download the correct MAME core.

Sounds like you were just using an outdated version then.

Are you using LaunchBox for Android to launch your games?

You should be able to use your SD card for the LaunchBox folder, yes. There are probably some broken devices that don't allow this properly, but they should be few and far between. You can change the folder by going to Options > Data Folder, and follow the instructions.

Yes, the last time we tried to get Lemuroid working, it did not allow frontends to work properly, so we had to give up on it. It's probably been a while though, so that may or may not still be the case. It's on my list to review, but unfortunately it's a very long list for the moment.