Jason Carr

Make sure you select the correct BigBoxSettings.xml file at the bottom of the LaunchBox tab in the LEDBlinky configuration. I believe that's how it knows the controls.

Yeah, we are using smaller, cached images where necessary. But we are still downloading the full-size images from the games database.

@Kuro Houou Good to know. I'll look into the possibility of supporting the Shield's network storage. The fact that it doesn't show up automatically means that it's not using default Android mechanisms, honestly, because otherwise it would just work. But I'll do my best to figure out how to make it show up. The Shield has been the biggest pain in the butt device to support thus far lol (it's obvious that they've done a relatively poor job implementing the various Android APIs). Regardless, hopefully we can make it happen. Per using the same LaunchBox folder on the desktop and on Android, that isn't likely going to work. There's too many differences in the data files between the desktop and Android. But in theory, you might be able to get away with putting the LaunchBox Android folder on network storage. It is likely to affect performance though, especially when loading up all the images. ROMs should be no problem, but the media is another story.

Thanks for the notes. I put those emulators on my list here to add. Per the wheel and box art, that's just kind of how it has to work to handle touch screens well. If you use a controller, it will work more in the traditional desktop way, but the way we have it is the most accessible way to do touch screen support. We plan to add the missing banners soon here as well. Per 3DS, sadly, it isn't supported with any frontends, unless I'm unaware of an emulator. Both Citra and Citra MMJ are broken and won't launch any games (frontends can launch the emulators, but the emulators do not allow you to launch a game). We'll look into adding Naomi and different arcade systems though.

Great to hear. You can uncheck the box to update to beta releases any time. Most likely, we'll be putting out a new official release tomorrow.

For anyone who has had issues starting the app on Nvidia Shield devices, we finally have the issue fixed. Version 0.36 is out now and should resolve the remaining issues. If you need a download link, here you go: https://www.dropbox.com/s/7lhx9yq4dexto20/LaunchBox-Android-0.36.apk?dl=0 Please let me know if anyone is seeing any additional issues on the Nvidia Shield (or other devices), with version 0.36. @Kuro Houou @SupaGrova @TheMadMan007 @dmaker @dia @smitchell6879

Praise the Lord! That one was a doosy lol. Many thanks @Madcore for spending all that time helping me get this fixed. I'll get a new official release out for everybody else.

Okay, getting closer. Once again, thank you very much @Madcore; really appreciate your help. This new version may end up fixing it, but we'll see. There's also some additional logging which may help. https://www.dropbox.com/s/mvs7zqhvk4glb9y/LaunchBox-Android-0.36-beta-4.apk?dl=0

I'll probably have to revisit this in the code. I did play around a bit with it early on, but Android was fighting me tooth and nail at every step. I'll put that on the list.

Thanks again @Madcore. That did help. It's possible that this new version will fix the issue, but I'm not certain. I also added some additional error messages to help if it doesn't end up solving the problem. Let me know. https://www.dropbox.com/s/6bv2rg65vwf1atg/LaunchBox-Android-0.36-beta-3.apk?dl=0

@Madcore Thank you very much. That gets me closer, but I have a new version now that should help us get even closer to the solution. My apologies for the back and forth. Unfortunately this issue may take a bit more back and forth to get resolved, but if you can test this new version, I would very much appreciate it: https://www.dropbox.com/s/dooks8rg45snixm/LaunchBox-Android-0.36-beta-2.apk?dl=0 Basically, again, I just need to know what the error messages that come up are. Thanks again.

It does not look like you're using the latest version of Dig, though I'm not sure that should matter. The latest version on Google Play is 1.39.6. Also, the latest version of M64 Plus FZ Pro is 3.0.291, so that is out of date as well. I'm afraid that M64 Plus FZ Pro may have broken that functionality with the latest version. Can you upgrade everything and confirm? Beware though, because I'm not sure if you'll be able to downgrade...

@Madcore @Kuro Houou @SupaGrova @TheMadMan007 @dmaker @dia I have a new version ready for folks that haven't been able to get it running on their Shield devices. This won't likely solve the issues, but it will get us more information to help us pinpoint what's going on. If you can manually download this new APK on your device and install it, and then let me know what the full error messages are, then hopefully we can better figure out what's going on. Here's the APK: https://www.dropbox.com/s/71xneb6obbn5bjk/LaunchBox-Android-0.36-beta-1.apk?dl=0 Thanks much; I'm hoping we can resolve this issue today.

@scenariol113 We have beta 2 out with a fix for this. Can you update to beta 2 and check to see if it fixes the issue for you? You can enable beta updates in the LaunchBox options and then just restart and you should be prompted to update.

Thanks, yeah, I tried with DIG already and it did not work with the latest version. But if you have it working, do let me know, because that means I'm just missing something.

Sadly, we've already tried to get M64Plus FZ running, and it's not possible, because the developer chose to switch to the new, broken Android data model (thanks Google), which doesn't work for launching games at all. So unfortunately, as it currently stands, it's impossible for a frontend to launch any games with M64Plus FZ. Just in case I'm wrong (which does happen from time to time), let me know if anyone finds any frontends that work properly with the the latest version of FZ. From what I can tell, it isn't possible. Sorry @steliokantos.

@Madcore Okay, that is good news. I should be able to fix it then, just have to figure out exactly what's happening. I'll be diving in later today. Can you look in your device settings for the exact model number of the device and the Android version?

Good to know. @Madcore I assume yours is not a tube version? Either way, I don't think that all users with this issue are running the tube version of the devices.

Thanks for the info. If you use a file manager app, can you write to the root folder (create a folder in the root of the internal storage)? Most likely that is the issue, but I don't really know how to solve it if the Shield just isn't allowing write access to the internal storage. I don't understand why some Shield devices are allowing it, while others aren't. Any chance you can screenshot me a list of files and folders in the root of your internal storage (from a file manager app)? I use FX as my file manager on my Shield.

@scenariol113 We have seen this error once since release as well. We're currently working on a fix, which should be out very soon. Thanks for the report.

Unfortunately not yet, but we'll have a new version out very soon with that ability.

@Kuro Houou Thanks for the report. What specific model of the Shield do you have? It's working great for me on my Nvidia Shield TV Gaming Edition from 2019, but we do have reports from people saying that for whatever reason their Shields don't allow writing to the root folder in the file system, which basically screws us from being able to do anything with it. I currently don't understand why that's the case. Do you have any external USB drives attached?

Yup, both of these things will be coming soon.

Android doesn't really provide us with a good way to determine what is and isn't a game, unfortunately. You can delete any non-games though and they won't show back up. You can also just turn off parsing Android games completely if you want in the options.

FYI, @faeran has been able to replicate this on his machine, so at least we now have a system that we can test with to resolve the issue. We're hoping to figure out a fix for it tomorrow. Thanks for the reports.