Jason Carr

Part of the problem is that I don't have one of those devices to test with. I suspect that the hardware is just a little weak, and is thus causing issues. If you can turn on debug logging in the options, and share your log files, that might help.

Did you mean constantly updated? Confused there. The sideloaded version of RetroArch is better than RetroArch Plus from the Play Store. We only recommend RetroArch Plus over the sideloaded version because it's easier for users to download.

Actually, come to think of it, I've tested deleting an entire platform, and confirmed that the media files are deleted. I will test to confirm if a single game's deletions are working properly.

Hi @joelfabiani, thanks for the purchase. LaunchBox for Android won't delete the media if it's in use, which I guess is probably what's happening. But if none are deleted, I doubt that it's LaunchBox that's holding onto the files. Maybe there's another app that's causing the problem? I've tested on my devices and I haven't been able to replicate an issue with the deletes. Worst case scenario, you can always just manually delete the relevant media folders when necessary.

Any theme can do this. You would just need to either navigate by genre in Big Box, or create a custom dynamic playlist and put it in the platform categories.

It does not fix your issue, no. So yes, I still need the details and log file.

Beta 9 is out now with fixes for all known missing pieces and remaining issues with the game metadata and media editing. The only thing we haven't added yet is a way to choose a particular image from the games database to download, if there are more than one. I'm thinking we'll probably put that off for a future release. Thanks guys for all your help testing these betas.

I am seeing some weird issues with Dolphin here as well. Will review. Thanks for the heads up. What device are you using? Where exactly is it kicking you out? Can you share your log file?

LaunchBox for Android 1.1-beta-8 is out now with the following: Full game editing is now available by long-pressing a game and selecting Edit Metadata or Edit Media Fixing incorrect matches to the LaunchBox Games Database is now possible by selecting the Search LaunchBox Games Database option in the Edit Metadata screen However, there are currently some minor caveats/known issues with the game editing: Additional versions can't be edited yet After being edited, the games lists and platforms lists don't yet update with the new data until you back out and reload them Controller navigation for editing the Notes and Release Date fields needs some improvement We still need an interface for selecting a particular image to download from the LaunchBox Games Database when there are multiple options available

I will review, but if I remember correclty, last I checked it did not properly handle launching games (it was only half developed for scoped storage). Great to hear about Dolphin.

Are you exporting from your desktop collection? What's strange is that you're getting the same slow experience on multiple devices, but we're not seeing it on any of them. So there has to be some kind of unique thing for you, that is also the same across all your devices. All I can figure is that it's data-related at that point. Having the ROMs over the network should not be cause for slowness like this. My ROMs are also over the network on my Shield device.

Yes, it would be better to post this over there. That said, the file names of the MP3s don't matter all that much; what matters is the file tags (the ID3v2 tags on the MP3s).

Hmm, yeah, that is definitely a much worse experience than what we're seeing in our testing. Odd. Some ideas that could be causing it: Where have you installed the LaunchBox folder? Is it on a really slow SD card, USB, or network device? Do you have an Internet connection on the device? Have you tried turning off the auto-download missing media option?

Thanks all; I have the translations in for the next beta, which should be out today. We're hoping to put out the official release tomorrow.

The Shield TV is not one of the most powerful Android devices out there...not even close. Just to clarify that. Regardless, I'm wondering if your experience is not normal, because I honestly don't know what you're referring to here. I have a relatively smooth experience with the wheels on all the devices I own, including a Shield TV, my Samsung Galaxy S10+, and the latest Amazon Fire HD 10. What specifically are you referring to with lag?

Ah, so that means it was actually fixed in the previous version, lol, of course. That makes sense. Good to hear.

Hey all, we're hoping to release the next official version this coming Monday. Thanks as always for all your work on the translations. Now is the time to update them if you can. @Kondorito @Cauptain @Nyny77 @Opak @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock @Soomin papa

Thanks, sorry for the delay here. I have the updates in for the next beta (unfortunately they didn't make the beta that just went out today).

LaunchBox for Android 1.1-beta-7 is out now with the following: More robust data saving and loading (including backup files) Hopeful fix for the above updater issues for some devices on Android 9 and below Keep in mind that even if the updater is fixed for those devices, we'll unfortunately only know when we update the *next* time, not this time. For this update, folks were having issues with the automatic updater will unfortunately have to still manually update.

@spacemonkey @Eyebrows Cat Sorry, one more question: do you know when the updater stopped working for you? Did it work with previous versions?

Thanks, yup, all of those we do have in mind. Yeah, I have seen that before. I think this happens when the app is killed during the XML generation, which we already work hard to prevent, but apparently it's not quite 100%. I'll be revisiting this for the next beta. Good to know. In general, we need a better way to filter game file types on imports, so we'll probably tackle this when we tackle that.

Thanks guys, so it looks like we've fixed the APK so that it actually installs, but we must still have an issue with the code that installs the APK, from what it sounds like. I'll see what I can do to get that fixed for the next version. Unfortunately though, even if I do get it fixed, you'll need to manually update to the next version (at least), since the updater will be using the current code to update.

@spacemonkey @Eyebrows Cat I'm a bit weirded out, because that com.unbrokensoftware.launchbox.provider reference from the error message isn't anywhere that should matter in the code, but I did remove it from the one spot that it existed, though it shouldn't have been relevant. Beta 6 is out now, and hopefully it might fix the issue? I've been testing on Android 9 with an Amazon Fire tablet, but it doesn't seem to have these issues. @Eyebrows Cat What device are you using and what version of Android is it running?