Jason Carr

Not sure what you mean here; the APK does not require root permissions. Retroarch shouldn't need the ROM location specified, but this could be caused by a missing core or a missing BIOS file, or an invalid ROM file. Also, try completely closing Retroarch via the task switcher to see if that makes any difference. I see; this thread is for Android, so we should troubleshoot that elsewhere in a different thread.

Please see the previous posts I've made. I'll need more details though in order to help further for this specific case. Thanks!

That would be an issue with the Play Store or your connection. I haven't seen any issues there, but unfortunately that's out of my control. I'm guessing that might just be an issue with the Play Store due to the fact that it's a beta? I'm not sure, but I can't really do anything about that. One thing that does always work to get it installed is this: Log into your Google account that you use on your Android device and then click the link at the beginning of this topic Press the button to opt in Go to your Android device and search for com.unbrokensoftware.launchbox LaunchBox should show up in the list so you can install it Of course it's easier just to click the link in this forums topic on your actual device, and then follow the links on through. I've been able to use the SD card successfully on all the devices I've tested myself, but it does appear that some people are having issues with it. That's interesting...good to know. Thanks; I had a hunch that would be the case.

Okay, make sure that the file structure looks like this: /Android/data/com.unbrokensoftware.launchbox/files/LaunchBox/Data/(xml files) Also, you can check to see if there is another /Android/data/com.unbrokensoftware.launchbox folder on your internal storage as well as your SD card storage. If there is, delete the one that does not contain the platforms that you exported. That might work. I am going to simplify all of this as best I can here soon though, so I'll get it easier to work with soon enough. Not sure exactly what you mean; the link appears to be working fine. Let me know what you're seeing. See my above response here to bri0528.

If it's requiring root permission to delete that folder, then yes, that's probably the issue. On all the devices I've tested, I've never seen root permissions required to do anything with the /Android/data/com.unbrokensoftware.launchbox folder (or child folders). So maybe that is the cause for crashes, as if the folder can't be read, then it's definitely going to have issues. I'll have to research that further. The app currently requires that you export your collection from the Windows LaunchBox application, and you have to use the beta version. The Android app does not currently automatically pick up whatever ROMs you have on your device already. It goes platform-by-platform. So if you export SNES, and then export more SNES, the previous SNES will be overwritten, so you have to export entire platforms. However, after exporting SNES, you can then go and add in NES (for example) at any time. It just has to be a complete platform at a time. I'm still looking into this. I'm hoping get it figured out and put a fix out tomorrow. Gotcha. All I can figure is it's some kind of weird permissions error. I'll get it fixed here soon. This is likely because the device is running a version of Android that is too old. Someone told me that GPD XDs were running Kit Kat, which is ancient. I'm going to look to see if we can support it though.

Can you try deleting the /Android/data/com.unbrokensoftware.launchbox folder from your internal storage and/or SD card? This seems to be happening only to a handful of users and all I can figure at this point is that maybe it's a file permissions error. I'll be putting out a new version soon that has better error reporting to track it down.

Actually, no; it's the fact that the *data* is on both storage devices. The app itself's files aren't really accessible.

There is still a crash coming through with 0.10 that I haven't figured out, but we're down to only one left at least. I'll be diving into that one later today. I do need to clarify some things with the above though: no, the app and the data do not have to be on the same data storage. You can, in my testing, install the app onto your internal storage and export the data to your SD card; that should work. However, the folder path always has to be /Android/data/com.unbrokensoftware.launchbox/files/LaunchBox, regardless of whether it's on the SD card or internal storage. Also, @krater9 is correct in saying that it can only be in one location at a time. The default location is in your device's internal storage, so if you have already used the app and you want to export to your SD card, you'll need to delete the LaunchBox folder in your internal storage. After seeing the difficulty with that, I'll probably make that easier here going forward.

Eventually, I'll consider adding that, at least. As for now though, ROMs and media are required to be on internal or SD card storage.

You'll need the latest beta for the Windows version. You can update to the beta release by checking the option to update to beta releases under Tools > Options > General > Updates in LaunchBox.

I've submitted the 0.10 release; hopefully it will go live quickly like the last one did. This should hopefully fix the crash on startup issues after accepting permissions.

I am still seeing something really weird where only my Shield TV is crashing on the first launch, after accepting permissions. So I think we do still have a crash there, but I think it's only in that situation. If you close the app and restart it, it should work. I'm currently working on fixing that issue though, so I'll have another release up soon.

I didn't realize that GPD XD devices were on such an old version of Android. Someone else told me that it was running Kit Kat, which is ancient at this point. I'm gonna do some research to see if I can easily support Kit Kat as well, but we'll see where that leads me. Syncing may come in a later release, but it's not a simple thing to tackle. Currently, you can export entire platforms one at a time, but if you export a platform that you already have it will overwrite anything that was previously there for that platform.

Thanks for bearing with me guys, those of you who are experiencing crashes. I just submitted another new version to the Play Store, but if history repeats itself it'll be another 8 hours before it actually goes live (version 0.9). I was able to reproduce one of the two crashes that I'm seeing coming through, and I believe I've got that one fixed. The other one unfortunately may still be there, but I'm hoping that it was related to the first. Time will tell. Again, thanks for your patience guys and let me know whether it's fixed for you once 0.9 finally goes live.

I will take a look, but as I don't have any devices with an Android version that old to test on, I'm honestly doubtful. Google is discouraging support for versions that old at this point. Thanks; please let me know if the new version is working on your Shield.

It looks like the 0.8 update just now went live on the Play Store. For everyone who's seeing just a white screen or a crash on startup, please try this updated version and let me know if it fixes it.

Yes, I do plan to address this very soon. I'll look into this. This may or may not be possible, as I'm not sure if game saves would be compatible between, for example, Retroarch on Android and Retroarch on Windows. I can see it being a cool feature though.

There is an update I've already submitted to hopefully fix this issue. I'm just still waiting on Google to make that new beta live. What device are you using?

Ah, thank you for pointing that out. That text was a relic of a previous version. I'll change it up for the next Windows beta.

I just submitted version 0.8 to the Play Store with a hopeful fix for the startup crashes. I've disabled the auto-parsing of Android games on startup, as I believe those to be the cause of the issues. The ironic thing is that I had rush-added that feature in order to get Google's approval to finally launch the app. I'll add that back in after some additional testing and development. Eventually, I should be able to see details on the crashes via the Play Store's error reporting, but apparently it's delayed because I don't have any details on any crashes yet, so I can't yet dive in to fix things in more detail. This new version may take a few hours to go live; I can never tell how long it's going to take. For those of you who are having issues with crashes on startup, please let me know if this new version fixes it.

I'm not sure an external hard drive will work at all at this point. What folder is it installed to on internal storage? What's the exact full path?

Thanks. I will get these issues fixed here very soon guys.

I'm currently just trusting Google to do its best converting everything to $5 USD. I'm sure it won't be perfect, but there's unfortunately too much to worry about for me to handle all the exchange rates.

Also try closing the app using the task switcher, and then restarting it. We may have an issue with the first run after approving permissions.

Okay, that's strange. I have a Shield TV that I've been using for testing, and haven't run into that. I should get crash reports here soon from the play store though; hopefully that will help to identify whatever the issue is.