-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legacy storage on Android for savegames #119
Comments
Hmm. I like the consideration to make saves accessible/non-deleted between installations, but this seems to rely on functionality that will likely be phased out in the near future (knowing Google's approach) and I'm not entirely sure we can even repoint GameMaker at that directory if we were to get the flag into the app manifest. Worth looking into at some point, but I'll be up front and say it's not a huge priority what with the current internal process going on unless @Miepee decides to take on some Android pain. |
An alternative, we may have a manual save import/export feature into the app own scoped storage. |
You actually can. I found a way to do that, but forgot to document it publically / put it on faq
I am not that familiar with Androids storage systems that developed over the years. In order for your approach to work, would one need to do both, or would simply setting the MAME4droid is able to get away with that, because they have the possibility to write their own apk and code for it. With GameMaker (which is what the project is written) we do not have such luxury, as we're bound to whatever YoYoGames decides would be best. |
Is your feature request related to a problem? Please describe.
I'd like to backup and restore my saves without rooting the device.
Describe the solution you'd like
set the
LegacyExternalStorage
flag in the app manifest and change the savegames location to/sdcard/AM2R
.Mame4Droid is currently providing this as an option.
Describe alternatives you've considered
Rooting the device.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: