![]() I built my library on Windows and followed the instructions of copying the "Launchbox" folder from the Android Export folder to the root of my SD card and it cannot be accessed for the same permission reasons mentioned here. My SD card is in portable storage mode and everything can access it fine except Launchbox for Android. ![]() I'm having this same exact issue on an Odin Pro which has Android 10. I don't have access to either an RG552 or an Odin Pro, but for what it's worth, I do have confirmation that this is not an issue on the Odin Pro. In our experience, the devices that have these issues are lower-end devices that run older versions of Android, and unfortunately there are a lot of those types of devices that just don't implement Android properly. Unfortunately there are some devices out there that just will not work to do what LaunchBox needs to be able to do in order to function properly as a frontend. However, I'm not sure what version of Android that the RG552 is running. Hi Greg, make sure you've updated to the latest official release, as that will fix all known issues with storage access on Android 11 and 12. When I try to select External (SD) storage in Options, I get the "launchbox android is not granting read and write permissions." error.Īlso have an Odin Pro on the way, so really want to use Launchbox on Android. I have a new RG552, latest (paid) version of Launchbox, and a lot of ROM files. That might work to keep it on the SD card, but I believe it will break the zip file extraction features, because games won't be able to launch from the temporary folder. ![]() You could try putting the LaunchBox folder inside of /Android/data//files. So, anyways, unless you can find a setting to change on your tablet, unfortunately the best thing you can do right now is to just leave the LaunchBox folder on internal storage (hopefully it's not too big with just some media) and keep your ROMs on your SD card. It's really a mess, and unfortunately there's nothing we can do about it. But if we do anything with that folder, then none of the emulators will be able to access any files in that folder, which of course causes other issues. Just to explain this dilemma further, we *can* write to the /Android/data/ folder on the SD card. If we switched to the new security model, it would not likely be an issue, but it would also break launching games completely, so we can't do that either. I don't have that device available to play with, so I'm not sure if there's a setting to change for that or not. Unfortunately, though, for whatever reason that device is still restricting write access to the SD card. ![]() The good news though is that in most cases, the old storage security model still works. Unfortunately, the new storage security model completely breaks all emulation frontends on Android and pretty much makes them impossible. Storage permissions on Android are a complete mess, because Google is switching everything over to a new storage security model, but it's a complete wreck because it's a very poorly designed solution on Google's part. Hi I wish I had a good, concrete solution for this, but for whatever reason that device is just not allowing us to write to the SD card.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |