I have to use the LINE messaging app (although I hate it for being a proprietary bloated software). I granted it the Network, Notifications and Sensor permissions only.

However, since then, an empty folder called “mei” has been created in DCIM (a similar issue is discussed in this XDA Developers thread). I deleted it a first time, but it keeps appearing.

How can this happens if the app has no Storage permission?

    boarim

    This is okay. Modern apps that target recent enough api levels can do this.

    I'd suggest you read through this part of the GrapheneOS website: https://grapheneos.org/usage#storage-access

    A relevant part:

    For modern apps, access to the shared storage is controlled in the following way:
         - Without any storage permission, an app is allowed to:
              - create media files in standard directories (audio in Music/, Ringtones/, etc, images in Pictures/ and DCIM/, videos in DCIM/ and Movies/)
              - create files of any type (both media and non-media) in Documents/ and Download/
              - create new directories inside standard directories
              - rename/delete files that were created by the app itself
              - rename/delete directories if it can rename/delete all files within those directories

    There's a lot more info there, so I'd still suggest looking at that section of the website.

      • [deleted]

      • Edited

      unwat so does that mean if you assign app storage scopes with a particular folder, will it still be able to do all what you mentioned above? Just for clarification...

        [deleted] It's covered in our storage access section. Enabling Storage Scopes doesn't reduce access compared to not having storage permissions. It's an alternative to granting storage permissions. The purpose of Storage Scopes is to make the app work as if it had all storage permissions granted while not being able to see or use anything created by the user or other apps rather than itself. Adding scopes is for granting access to directories/files created by the user or other apps.

        unwat Thank you. That clarifies everything.

        Well, problem is solved as this is the expected behavior.