Jason Carr

It sounds like EmuMovies was having issues over the weekend because they use Cloudflare and Cloudflare had some issues themselves. From what we can tell, all issues should be fixed now.

Oh, ha. It's possible that it was a glitch with the previous beta that I had already fixed. I remember that now.

LaunchBox for Android 1.1-beta-10 is out now with the following: Platform theme videos are now available for download by selecting Download Theme Videos from the top right menu Platform theme videos can now be played in the background in the Wheel with Details and Text List with Details platforms views

@alexirae Unfortunately this error happens because of a broken device/poorly implemented version of the Android OS, as far as I can tell. I think you should be able to manually run the APK though from the LaunchBox\Updates folder. Unfortunately that log isn't helpful, but hopefully we can still figure it out. Where is your LaunchBox folder on your device?

If you get the beta updates from Nvidia, you should be able to access your NAS. I have this working currently. Nvidia makes it a long and convoluted process though.

Scratch that, my old Samsung tablet runs Android 7, and it seems that Android 7 is fine, so long as it's not cheap Chinese crap. Unfortunately the RG552, as much as I like Anbernic from the past, does not have a good implementation of Android 7. At this point, I think our direction/focus will be Android 7+. It takes way too much time to try and troubleshoot issues with these older/junk devices.

One issue I've been running into is that I just don't have enough older devices to test with. I just tested with an old phone running Android 5, and it was clear that there's not much hope for getting everything working properly on Android 5. There's too many storage issues and the hardware is largely too slow. However, my old LG G5 running Android 8 seems fine. I don't have anything to test with between Android 5 and 8 though. We may end up increasing the requirements to Android 8, especially with the various reports we've been getting of issues that I really don't have any way of fixing on all of these old devices.

Just re-tested changing clear logos with beta 9 and didn't run into any issues. What device are you using and what version of Android is it running? It also might help to provide your log files. You can turn on debug logging in the Options and then log files will show up under LaunchBox\Logs.

Thanks for catching this; it was conflict between the desktop and Android versions. Should be fixed in the next beta.

Screenshots are already there and supported in the 1.0 official release. You may just need to change to a view that supports them (one of the 2-column views). Then you can see both the box and the screenshot at once.

I will put it on the list.

Thanks @joelfabiani. I have a fix for this in for the next beta release.

Per the RG552, I'm kind of stuck on that. I tried installing Android on my Anbernic 351M, but that doesn't seem to be working at all, so I ended up giving up on that. Regardless, it was running Android 11, so it probably wouldn't even be similar anyways. I've also tried using an emulator with Android 7 to see if I could reproduce anything, but there's no real way to test SD card issues with the emulator, so I'm stuck there too. The only other option would be to buy an RG552, but they're around $250 and I might have to wait for it to be shipped from China, so I'm not likely to do that either. For what it's worth, the Android implementations on these devices are kind of junk, which I'm guessing is what's going on here. So until I can get a hold of one of these devices, I can't do much of anything about it, unfortunately.

Good to hear that you were able to get it working on the Odin.

Usually awful performance is caused by a slow SD card.

Sorry for the late reply. Unfortunately Android has made it stupid difficult to do that. It's really ridiculous, to be honest. I don't think a tutorial would be possible, because it's just so complicated and varies so much between different emulators. It's ultimately an issue because of Google's terrible Android designs for that aspect of the OS.

Sorry for the super late reply here. I did look into this a while ago, and it appears to be a glitch with the Android firmware on the device. There doesn't seem to be a straightforward fix for us, so I ended up moving on.

@moudrost Might help if you can post your debug log file from a crash (I didn't see it above). Just have to turn on debug logging in the options and then they show up under LaunchBox\Logs.

Have you gone back to 12.8 to confirm? I'm not sure what would be different in 12.9 that would have anything to do with JoyToKey. That doesn't make much sense to me.

It used to be first, but it was not commonly used, and so it was annoying having it first every time for the root platforms list. We might provide an option for that in the future though.

We have definitely thought of this, but for most users, our experience shows that they want simplicity, and that would largely just be way too complicated. What you can do though, if you want them to be completely separate, is you could duplicate your library (not your ROMs) and just use one for Big Box and one for LaunchBox.

Sorry for the late reply here @CMOSS. Absolutely, we would love your help with the Spanish translation. If you're still interested, please read the first few posts of this topic. That should give you all the information you need in order to get started. Let me know if you have any questions, and thank you very much!

To be honest, I've never tried bezels on Android. Did you manage to get it working?

Since I politely reached out to the developer and was basically told to go stuff myself, I don't have a whole lot of hope here. I'm not sure if Reset Collection somehow got on the developer's good side, or just stumbled on some kind of magic solution, or what. But generally, if an app developer actively does not want us to support their app (which is the case for Aether SX2), we generally don't focus on adding support for it, especially since they could just put out a new version that purposefully breaks that support (which is literally what the developer actually threatened to do when we talked to him). So it's quite an unfortunate situation there.

Not currently, unfortunately. We might find a solution for that in the future, but Android doesn't make it easy, especially without messing with navigation.