Open metal450 opened 6 years ago
+1 for Android/data/ to prevent clutter.
i dont mind it being in the root directory since its easier to access it with resilio and sync the folder with other phones. i think ive had permission problems with things being in the android/data directory but either way, letting us choose the location of the folder seems like the best option to keep everybody happy!
It looks like Google themselves are introducing changes in Android Q to prevent this kind of "clutter" behavior: https://developer.android.com/preview/privacy/scoped-storage. Hoping this will finally force Maps.Me to be updated to behave like other apps.
(Context.getExternalFilesDir() is the function it should be using to determine where to store its files.)
Twenty-six months later, any hope of making some progress towards behaving properly with regards to file/data storage...? :/
(Scoped storage was delayed until Android 11 - which now makes it required for all apps.)
I also wonder why it must be in the root of storage. Is this a very difficult change? No response in 3 years?
Maps.me stores its data to the root of the internal storage (in a /MapsWithMe directory). As standard practice is for apps to store their external data in /Android/data/.../files, please consider either moving the data there, or much better, allowing the option to choose our own path.
Hard-coding the data to this top-level location causes several issues. In addition to increasing clutter unnecessarily (could you imagine if every Windows application stuck its data in the root C:?), it causes it to be missed by common backup applications (which look for app data in the standard Android/data location), as well as causes Android itself not to be aware of the true storage usage of the app (when viewed in the app settings). A user-definable data path would solve all of these, as well as issues with specific devices that may use unexpected paths not yet known to the app (i.e. Blackberry bb10, see issue #1259).