Jason Carr

The 0.18 update just now finally went live on the Play Store.

Wow, it's not 100% clear, but that definitely helps. I'll give it another shot here. I thought I remembered something like that. If I recall correctly, that is the recommended solution, so I'll probably just add that automatically to the exports. Thanks @dragon57.

Good to know, thanks. Unfortunately that doesn't help me to figure out what parameters are needed to launch Dolphin properly, but at least I know it's possible now. I've scoured the web but I haven't found any good details on how to launch Dolphin into a game, so if anyone has any good info on that, let me know. Otherwise, I'll experiment with it again here soon. I might have to dive into the Dolphin code to figure it out if nothing else pops up.

It's about that time again guys; I'm hoping to put out the 10.0 official release early next week on Monday or Tuesday. I've managed to get the new Android app working with our existing translation system as well, so all the Android translations are also included in the Strings.resx file. There's not a whole lot of things to translate at current for the Android app, so it shouldn't add much extra work. Thanks as always. @Opak @dukeemu @cyanjiang @Bardock @MajKSA @gamehacker @Cauptain @Kondorito @Nyny77 @alexposad @k_kutsugi

Thank you @alexposad. I have all the translation updates into beta 4 which I just put out.

Also, FYI, I attempted to add support for Dolphin, but as far as my research could find, it looks like Dolphin is not currently working to launch directly into games. Either that, or I'm just missing the secret and I can't find it. If anyone is aware of another frontend for Android that is successfully launching Dolphin directly into games, please let me know.

I just submitted version 0.18 to the Play Store with the following: New boxes view overhaul with support for background fanart images New launching view overhaul, also with support for background fanart images Added Yaba Sanshiro and Yaba Sanshiro Pro emulators for Sega Saturn In order to make the best use of the new background fanart images, you'll need to download the new beta 4 release of the desktop app, and re-export everything, as backgrounds were not included in the previous versions of the Android export process. I'm looking to put out the official releases early next week, so I'm hoping this beta will fare well.

Yeah, I can see that being helpful. I'll be putting the release notes in the app here at some point. As it stands, for the beta releases, I always have to limit the amount of busy-work I put in as it distracts from development.

Beta 4 (of the desktop app) is out now with the following: The Android exporter now allows you to choose what types of media you want to export The Android exporter now does a better job of prioritizing the correct images to use, such as using proper Box Front images if they are available instead of another category (like advertisement flyers) The Android exporter now allows exporting background images for use in the newest beta of the Android app (out later today) The Android exporter now has minimal support for bin/cue files, but only if they are named the same (such as Mario.bin and Mario.cue) The Android exporter is now much more stable, and truncates file names if file paths are too long Fixed a glitch with attract mode in Big Box where in some cases the speed was unlimited and not obeying the attract mode settings The associated Android release will be out in a bit with background images for the boxes view. I am hoping to put out the 10.0 official release early next week, along with the 1.0 official release of the Android app.

No, emulator associations do not automatically migrate over. That would be too messy. Not all Retroarch cores that run on Windows work on Android. Nor do all emulators.

Oic; that list includes not only the default platform names, but also any custom platform names that you already have in your collection. So it isn't there the first time; you would have to manually add it. Then subsequent times it's there whether it's a default platform name or not.

No, the desktop themes will not be fully compatible with upcoming Android themes. Unfortunately that's impossible. I will be looking to build themes that are very similar, but each theme will require at least some manual conversion.

I suppose that could have been the case a long time ago, but I just checked the platforms list in the importer and Super Famicom is not listed there as best I can tell. Where were you seeing it?

Oic, I think I understand now. The LaunchBox Games Database sees Super Famicom and Super Nintendo as the same platform (as it should). Basically, Android currently requires the platform names to match the games database exactly. But the exporter should name the platforms to match the games database if Scrape As is set correctly for the platform in LaunchBox for Windows.

Can you explain? Why isn't Retroarch an option for SNES? Is the issue specific to Super Famicom?

I'll see if I can get that added in today. There should be no problem with exporting one platform at a time like that. The only thing to note is that you have to export entire platforms. If you try and export only part of a platform, it will overwrite any games that you already had for that platform on Android.

I'll see if I can get that added in today. There should be no problem with exporting one platform at a time like that. The only thing to note is that you have to export entire platforms. If you try and export only part of a platform, it will overwrite any games that you already had for that platform on Android.

Currently the only way to remove a platform is to delete the platform's XML file under /Android/data/com.unbrokensoftware.launchbox/files/LaunchBox/Data/Platforms. You'll probably also want to delete the image and game folders as well for that platform.

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.