Jason Carr

That is planned, but I still have to add that functionality both to the exporter in the desktop app, and into the Android app. Unfortunately I can't give you a date as to when that will happen, but I will be looking into it soon. It's on my shortlist.

Currently, storing the games locally is the only option, unfortunately, unless you use something like the nVidia's Shield's functionality to mount a network share as a storage device (which I have yet to test). I will be adding some sort of option later on to be able to pull files off of a NAS or similar (I think, not sure how yet), but that will be coming at a later date.

We could, but I think Google will probably do a good enough job getting people here. One of us will be around to answer it again if not. Thanks @misteridjit.

Thank you @misteridjit. I've seen that the Windows file transfer utilities to Android devices can be really finicky. I would guess that there was probably already an images folder in there that just wasn't showing up. Can you try disconnecting and reconnecting to see if maybe there's a duplicate folder in there? Otherwise, maybe try looking for an images folder with a file browser on your Android device.

What specific model of GDP XD do you have @Akis? Are they still available for sale?

That is great to hear. Thanks @Skelnik.

LaunchBox and Big Box on Android will be the same application. Basically, I'll be adding views to the Android app to behave like Big Box. So no additional purchases.

That said, I do want to note that if you're spending a decent amount of money already on building an arcade machine, I would still highly recommend Windows over Android. Emulation on Android is improving quickly, but it's still nowhere near as good as emulation is on Windows, and it's worth the extra money if you have it.

Welp, developing an app for Android and developing an app for any particular flavor of Linux are very different beasts, so I can say that a version for Raspbian is not in the picture for the near future. I haven't experimented myself with Android on the Pi, so I'm still fairly green on the subject, but yes, I would hope that eventually we can get it working well for Pi 4-based arcade machines.

I see. It may be an issue with that old version of Android, sadly. There might not be much I can do. The issue is that Android's security system will only let me access certain storage and certain folders, and it's probably refusing the app access to the SD card. I'll see if there's anything further I can do.

Gotcha. Can you try completely deleting the /Android/data/com.unbrokensoftware.launchbox folder from your internal storage? Make sure LaunchBox is closed first and then try to re-open it.

Hi Akis, I have not tested on the GPD XD and I don't have one, so unfortunately I can't troubleshoot this myself. What exactly is happening when you try and run the app? Do you have any data at all?

Hi electro, I've done the same thing on my Shield with a "removable storage" drive and LaunchBox is finding everything correctly, so I know it does work to do that. It could be because you already have data on your internal storage though, so LaunchBox is just using that folder instead. Try deleting your LaunchBox folder from your internal storage.

Thanks @WhiteNoseThunderPants. Honestly, I hadn't thought of that until just yesterday. I am looking into getting it up on the Amazon store.

Can you confirm if you really have Refaktor available for you in the themes manager? Could you maybe have downloaded it from the forums instead? I just confirmed that it isn't there in my testing for the 10.1 release.

...if Refaktor is available to you, then it sounds like I have a bug. I'll look into that...

Thank you @danpow. In theory, all the themes available in the themes manager have been tested and should not cause memory leaks. If you discover one, though, please do let me know. Refaktor has been in the process of getting approved for the themes manager, but it has not been approved yet because testing has resulted in issues like this, and eatkinola is working on it.

Switching to WMP probably isn't a good idea; it's likely to only introduce more issues at this point. That said, Refaktor especially is known for the possibility of memory leaks, so I do think that it is likely theme related. It's also possible that you may need to upgrade those themes. I know eatkinola is at least working on updates to his themes, and the 10.0 update did also break some things in some of his themes, so that is probably at least part of the issue. It probably would be worth testing with the default theme to confirm if that fixes the issue, though.

Hmm, then apparently WMP is not the issue. There's only one place to switch it out, in the Big Box settings. What Big Box theme are you running?

LaunchBox for Android has been out of beta since early Monday morning. Unfortunately a purchase from us for one product is not going to enable access to every product we ever put out. I really appreciate your purchases though. Thank you guys; I really do appreciate it. I will do my best to keep the updates consistently coming, but of course I do have to focus on the Windows apps for a bit now first. It won't be long though. Per donations, I really appreciate the offers, but since we are a business (and not a non-profit organization), I chose to stop taking donations a while ago.

@danpow I did a ton of testing recently and discovered that unfortunately Windows Media Player is causing some very unfortunate issues, including memory leaks and crashes as you describe. Unfortunately though, this was happening with all previous releases as well. Microsoft apparently updated something in Windows 10 recently that started causing this nonsense. I've tried getting the Big Box WMP code down to the bare minimum, and the issue still happens, so I don't think there's a way for me to fix it. My recommendation at this point is to use VLC and stay far away from WMP.

The challenge here for pause and startup screens is that they don't work well with batch files, because then I don't have direct access to the DOSBox exe for finer control. I do have it on my list to look into though, but honestly it may or may not be possible to pull off, unfortunately.

@Thunderbird1400 You should try downloading and installing the .NET Framework 4.8 I linked above to see if it resolves the issue. However, I'm not sure if you're running into the same issue. The IOException suggests that it could be an issue with file permissions, file system corruption, or perhaps you could be running out of space on your hard disk. Since I was able to replicate and fix this issue, I'll be putting out the 10.1 release shortly which will install .NET 4.8 in the installer.

You're probably thinking of the Text Games View, which will go directly into the game details without switching screens. The wheel screens have never done that though.

I've just confirmed that this issue shows up if you're still running the old 4.7 version of the .NET Framework Runtime on Windows 7. Apparently 4.7 has a glitch that causes LaunchBox 10.0 to crash on startup. That issue is resolved with .NET 4.7.1, but if you're going to update the .NET Framework, you might as well install 4.8, which is the latest version.