Jason Carr

Not a bad idea, but how would you suggest that we implement navigation between platforms? This isn't currently possible on Big Box either, so it's an entirely new idea for navigation. It could possibly work out well, or it could just end up being confusing. So it may or may not be something we would want to implement.

You can manually add art for these no problem by editing their media. But yes, we do not have absolutely everything in the included platform media.

Unfortunately no. Yaba Sanshiro will need to be updated to work properly launching games for later versions of Android.

If necessary, you can always download the latest version from the website. Installing the latest version will update and will not remove your games or settings. There are issues with those two specific devices; they have not implemented Android properly and thus the updater is not fully working with them.

We do have plans for this, but we're currently working on adding some missing platforms/emulators and implementing custom themes. Not sure on a time frame for that as of yet. 1.1 is still the latest release. We have not yet put out a new beta past the official release. If you're on a beta version, the version number will have "beta" in it inside the About page. These are probably device-specific issues. That's the biggest problem with Android, it's just so fragmented. It will be difficult for us to figure out exactly what the problem is with network shares on those devices, without having them on hand.

Hi Calvin, this thread contains the most up to date information on LaunchBox for Android:

We are looking to hire another developer with a focus on web and mobile technologies, specifically in the .NET/C# realm. This developer's focus will be on: The LaunchBox Games Database website LaunchBox backend web administration tools LaunchBox and Music Box Alpha's main websites Integrating the various LaunchBox websites together LaunchBox for Android Various other future projects Some sort of knowledge/experience regarding C# web and/or mobile development is required. We are open to both developers with more design experience and developers with more backend experience, but knowing C# is a must, and Microsoft SQL Server is a big plus. However, we are a very flexible team with many different talents already, so often we are able to adjust our focuses as needed to make the best use of available talent. We are also open (for the first time) to a possible part-time position, though it would eventually move to full-time in that case (this is not to say that we are not interested in hiring full-time straight out of the gate). We all work from home and primarily communicate over Discord, so the location is not overly important, and we're not asking anyone to move. A decent home office situation is important, though, because of working from home. Every single member of our current team has come from the LaunchBox community, and we have a wonderful team at this point. If we've learned anything in the hiring process, it's that hiring folks from the community is the best way to go. So we're reaching out! If you're interested, feel free to comment below, but also reach out to us via email at support@unbrokensoftware.com with your resume and examples of your experience. Feel free to reach out with any compensation requirements as well, and we can discuss. We look forward to hearing from you!

It does actually stand apart. This issue should not be related. If you turn on log files in the Options, it should hopefully give us more information on the issue.

This is usually related to using a slow drive. You'll probably need to use a faster drive or SD card.

These Chinese devices seem to constantly crash with a million issues that I think are probably out of our control. That said, I don't have one to tinker with, so it's hard to figure out exactly what the issues actually are. I do know, though, that they are not good implementations of Android and thus cause some significant hurdles/issues for development. My apologies for the issues with these devices; as for now, I'm not sure that we'll be able to resolve the issues with Anbernic or Xiaomi devices. I am able to replicate this with the latest firmware on the Shield with any folder that has too many files. However, apparently it's also an issue with previous versions. My current hunch is that it's just yet another bug with the Android 11 firmware. I will look to see if there's anything we can do to get around the bug here soon.

@Mookdog Where exactly in the interface are you getting the crash? Can you tell me what steps you're taking to cause it?

LaunchBox for Android 1.1-beta-16 is out now with some various fixes related to navigation and video playback.

@littlek4za You may run into issues launching games if you put the LaunchBox folder inside of that folder, because other apps will not necessarily be able to read from that folder. I doubt that's causing the specific issue that you're describing, but it's possible. The metadata files are platform-specific on Android. If you're importing NES, for example, only NES data will be used/downloaded. This is to help with performance on Android. So that may be what you're seeing. The full metadata.xml file is not downloaded on Android. Usually missing images like that are the result of an inconsistent Internet connection.

LaunchBox for Android 1.1-beta-15 is out now with various fixes for videos that should make them more stable and smooth. Betas 13 and 14 were just used for internal testing.

This isn't quite as streamlined as it is on the desktop, but if you dump the custom images into the right folders, with the right file names, and then import *after* putting them into the right spot, the app should pick them up automatically. There are unfortunately known issues with that app. It won't launch games properly on Android 11 or 12.

@thamaster88 I think this should be fixed in LaunchBox for Android 1.1-beta-12, which I just put out.

LaunchBox for Android 1.1-beta-12 is out now with the following: Fix for videos only looping twice and then stopping Added the ability to edit videos in platform edit media Fixed an issue where platform theme videos wouldn't download if they already existed Fix for @Mookdog's reported crash above Hopeful fix for the reported MAME.xml issues on lowend devices

This should be fixed in the LaunchBox for Android 1.1-beta-11 release.

The latest beta (LaunchBox for Android 1.1-beta-11) should fix this duplication issue for the MAME/Arcade imports. Thanks for the reports guys.

This log suggests that there's a compatibility issue with a base-level library that we use for the app. It's a tried and true, well-tested library, so I'm doubtful that there's really an issue with the library. More than likely, it's caused by badly written software on the RG552, unfortunately. Sadly we're seeing tons of issues with that device.

It's possible that something like that could work on one of these devices that I don't have. The devices that I do have suggest that it's not likely, but who knows. It's actually really hard to know without having one on-hand. Still, thanks for the effort and the points, @viking.

I'll take a look at 3DO to see if there's anything we can do. Last I checked, Yaba Sanshiro 2 had serious issues with launching games on Android 11+, so it wasn't possible to get it working correctly.

@Ally68 @thamaster88 I just put out LaunchBox for Android 1.1-beta-11. Can you guys test to see if this is still an issue in that beta release?

LaunchBox for Android 1.1-beta-11 is out now with the following: Many customization options have been added to the platform/filter Wheel with Details and Text List with Details views to hide and show items and configure the background videos You can now change the default version of a game by selecting Change Default Version from the game's context menu Fixed an issue where importing MAME games was not excluding games that already existed properly (even when turning off duplicates)

I see one issue in one of the logs that I can likely fix, so I'll look into that. The other log is basically empty though, unfortunately. We'll see if we can replicate any MAME import issues. I believe this should be already fixed, but if you're stuck on an old beta, you won't be able to automatically upgrade. Instead, try downloading and installing the latest beta here: https://www.dropbox.com/s/c5ab7qhgcjh29x6/LaunchBox-Android-1.1-beta-11.apk?dl=0