No permissions to SD Card

[zuku]

Hello,
I would make backup to my sdcard, but when I choose my sdcard /storage/0000-0000/aquamail_backup I have message "No privileges to create new files in this folder, choose other" my sdcard working OK pictures are saved into it. Android 6.0.1 How to fix it?

[StR]

From what I know, starting with Android 4.4 when Google made serious changes in working with the SD cards (essentially blocking apps access to those), Aquamail cannot store any files that would be accessible from outside of the app on the external SD card. The changes made in the later versions of Android require serious rewriting of the code to enable the use of the SD card in Aquamail. Until that is done, saving the Aquamail configuration backup or attachments to the micro-SD card is not possible.

You can read more details about this in the FAQ entry "Cannot save attachments on the external sdcard" http://www.aqua-mail.com/?page_id=227

[zuku]

thanks for explanation,
You write in FAQ "The change affects all third party applications, and there is no way around it – it’s a system policy..." it's strange because other application like SMS Backup& Restore can write backups to my external Sdard without problem.

[StR]

First of all, for clarity: I did not write that FAQ. I am just a user of Aquamail.
As for that FAQ entry, it was written when 4.4 came out and affected all apps.
Then, there were changes in 5.x and 6.x that allowed writing but in a different, more restricted way, and some apps were rewritten for that, but not Aquamail (yet).

That FAQ entry has a URL that explains the details of the changes.

[arbit12]

Well, Auqamail will have to come into sync with the new MM permissions model sooner or later. Can request the Dev.

Sent from my SM-N915G using Tapatalk

[Kostya Vasilyev]

It's not about Android permissions.

To access the microSd with write access, apps have to use completely new functions, not the old standard File based functions.

And the process of granting access to the microSd card is complicated to the user, I don't expect many will be able to.

In short, this is another one of Google's screw-ups and I really not too keen on cleaning up this mess for them.

Now in terms of "request permission on first use, not at install time" -- this is as I wrote above, completely unrelated.

This one is not a priority since the app will have to ask for them on first launch anyway (because they have to do with the app's core features, like being able to see sender images in message lists), not really different from the current "pre-6.0" permissions where you grant them at install time.

I mean this is very very different from "A flashlight app with Send SMS permission".