Jason Carr

This does appear to be an emulator-specific issue that is caused by Android 13. It would be good to know specifically what all emulators are affected. So far, I know that the following emulators are not working on Android 13: Skyline N64Plus FZ Snes9x EX+ It's worth noting that, at least in my opinion, the RetroArch cores would be better for N64 and SNES anyways, so hopefully that isn't too big of an issue. Regardless, I'm working to hopefully solve the issues with all of these emulators. Let me know if you run into a similar issue with any other emulator that worked on Android 12 but is no longer working on 13. So far, my understanding is that the issue is primarily that Android 13 requires all launched activities to be explicitly marked public by the emulator developer, which wasn't previously required. I'm not certain that that is the only issue, but that does appear to be the main issue. I worked hard today to try and get everything fixed before the 1.8 release that I just put out (to fix a few bugs), but unfortunately that didn't happen because I'm not even sure what is and what is not possible at this point, without updating the emulators themselves. Hopefully we can still get a fix in soon, if it ends up being possible, anyways.

Just put out LaunchBox for Android 1.8 with a few fixes: Fixed an issue where platform categories were not always being populated after games were exported from the desktop app Fixed a rare potential error with grid view column sizing Fixed an issue where the Arcade platform could not be directly edited when it's the only platform in the Arcade platform category (and thus is skipped during navigation)

Hi @Hal9000, I just tested the 1.7 release on my own Fire HD 10 and everything seems to be working fine. Any chance you're running out of space on the device, or something like that?

Wow, good job sleuthing that out. Can you check the 1.7 release to see if it still has that issue? We did disable some system animations for the LaunchBox app.

Hopefully we can do something like this eventually, but it is a ways off.

Yes, this is another wonderful issue that Android has introduced with Android 13. I'm still working on trying to figure out what changed so that I can get it fixed. I'm not sure if it's a bug with Android 13, or if there's something I can do to fix it. In the mean time, most platforms should still work great with RetroArch.

Hi @Kinah, sorry for the late response. Is that RG351P running Android? I think it might be running Linux instead.

Hi guys, this issue was finally fixed in the latest official release. Just make sure you have the "Override Arcade Genres with Improved Arcade Filters" option enabled.

Unfortunately right now we don't have a good way to auto-parse videos from files on Android. We didn't implement it that way originally for performance reasons. So the only options right now in order to get videos into the app is to either use the EmuMovies video downloader inside of the app, or export the games and videos from LaunchBox on the desktop.

Thanks for the details. How did you manually delete that Android games banner? Did you just delete it in the file system?

Ah, I see. Thanks for the detailed post. The issue is that when there is only one platform underneath the Arcade category (the Arcade platform), then we go ahead and skip the platforms list, because it's pointless in that case (other than for editing the platform, apparently). For now, you can temporarily turn off "Start with Platform Categories" in the Options menu, which should allow you to edit the platform. We'll look to add a fix for that here in the future.

That is definitely confusing. Those genres look like MAME genres that come from the MAME metadata, so maybe that is a clue?

@D3K17 Thanks for this report. I have the issue fixed and I'll be putting out a fix release here soon (today).

Unfortunately I don't know of one at this point, but that would be an excellent idea for a plugin.

@eonder87 My apologies for the late response here as well. In the past, we have required translators to be fluent in the translated language, and we have not allowed machine translations, because generally, we want the quality of the translations to be as high as possible. Do you have the ability to remove the machine translations? That would be much better because those could just remain in English while your manual translations are in. Unfortunately we really don't want machine translations in the mix.

Sorry for being so late here myself, guys. I have these translations in for the next beta.

@Gustavo Oliva Thanks for you help testing that stuff. Let me know if you do figure it out in more detail. Otherwise, we'll see if we can't reproduce it. Are you referring to Arcade for those? If so, we basically just fixed that with this release with the new arcade filters features. That is a good idea. Yeah, I like that approach. Hopefully we can add something like that in here soon enough.

That is especially odd because we have that same device for testing. I'll see if there's any way we can replicate it. It might be worth restarting the device to see if it's some kind of fluke with the OS.

Okay, I'll have to look to see if those categories are exported when using the Android export. It's possible (and probably most likely) that they didn't used to be but are now.

I'm guessing that's probably the explanation. Do you have platform categories specified in your desktop platform metadata?

Thanks for the report. What device are you using and what version of Android is it running?

It is in most cases. I'm not exactly sure why it wasn't in yours. Did you import on the handheld, or export to Android from the desktop?

If platforms aren't showing up, it's most likely because your platforms don't have a platform category specified. I'm not sure why that is, but if you edit the platform metadata, you can add a platform category to them. You would just have to temporarily turn off the platform categories. Favorites don't show up unless you actually have favorites to show.

In another thread, we recently discovered that the CriticalZoneV2 theme may be the culprit for some of these issues, so we're doing some additional testing with that theme to see if we can fix those. That said, there are no known issues with the Unified theme (or Unified Redux) in the latest official release. We've been successfully testing both Unified Redux and the Default theme for weeks on end without any stability issues. It is worth noting that the latest official version of LaunchBox/Big Box does have some related fixes in it. In addition, though it may seem that Windows Media Player might fix some issues, there are some serious bugs with Windows Media Player that are likely to *cause* stability issues (it does for us), so we still don't recommend using WMP if you're looking for long-term stability. All this to say that if you haven't tested the latest version, it's worth doing so again with VLC (we put VLC-specific fixes into 13.0). Beyond that, we may still need to resolve some bugs with certain themes that could be causing the issues, or it is possible that further issues could be caused by certain hardware configurations, media libraries, settings, etc. We do know that we've resolved the long-term stability issues for some folks with the 13.0 release, but of course not yet for everyone and probably not for every theme. Thanks for bearing with us guys, and continuing to report the details.

Wow, okay. Thank you for that; that is very helpful information. We'll do some testing with CriticalZone.