This object is in archive! 

Cannot get write access on some folders

Tapio shared this problem 2 years ago
Not a Problem

Hi guys,

I want to point Locus to my external SD card for some big directories - that is the mapsOnline/mapsVector and SRTM.

The problem is, it is not possible for some folders. See video. You can see, Locus is calling different Android dialogs - the bad one with "mapsOnline", the good one with "Backup". The darker one is one that can ask for writing permission. The bright on does not get writing permission and does not try to. But writing permission is important, also for SRTM, because the Locus Store is capable to download hgt files.

Why is Locus triggering different Android folder dialog windows?

https://youtu.be/9yquVnAa00E

My idea is, it depends where it is starting from. The non-working one is /sdcard/Locus/ and the good one is starting at /storage/emulated/0/Locus/ - but there is no way for me to change those.

Replies (2)

photo
1

Hi,

I would recommend keeping all folders except mapsVector, Backup and SRTM within the main app working directory. See more at https://docs.locusmap.app/doku.php?id=manual:faq:locus_on_external_sdcard#locus_in_internal_and_some_data_in_external_storage_-_recommended

photo
1

OK, I can live with how it is now (SRTM and MapsVector are now on ext. SD) - but do you see the problem? It's a weird thing. E.g. as for the SRTM folder, at first there was this window not being able to get file writing permissions. Locus is then complained about a read-only path. After a restart of Locus I again went to the SRTM path setting. Then the other dialog window appeared where I was able to get write access.

But this method did not work for any of the paths. Under no circumstances I was able to change MapsOnline to ext. SD PLUS write access.

It's alright for me now, but well, this sh** (thanks Google) is likely to be a source of trouble for the next 12000 years.

photo
1

I don't know what version of Android you have but be prepared that beginning with Android 11, autumn edition, apps will be banned to use other than private storage space. We're already preparing for the nightmare. Anyway, we'll have a closer look at the problem you're pointing at. Thanks.

photo
1

Yup, good luck, expecting a bigger nightmare than the introduction of access restrictions, iirc @ Android Lollipop.

I'm on Android 10. Ugh, and Storage Access Framework I guess is a thing as well. Totalcommander deletes like 2 files per second from external MicroSD. Painful.

photo
1

Hi Tapio,

just a quick note from my (dev) perspective : current behavior visible on the video is correct (expected). Only the "backup", "srtm" and "mapsVector" directories are prepared to use SAF, so they ask system for a write permission. Other directories are not yet ready (who knows if they will be ever) so they use only app internal file browser to pick a directory. This worked correctly in the old Androids, but not anymore. So soon, I'll probably remove these settings and keep only three mentioned above, that works reliably. Thanks for understanding

photo
1

Understood, sounds reasonable.

Replies have been locked on this page!