Some basics on Android storage system

[Anke]

From an Android point of view there are an → Internal Storage and an → External Storage .

1. Internal Storage
The Internal Storage can only be accessed with a rooted device.

1.1 The app package is saved in

/data/data/<packageName>/

In order to be able to debug your app, AI2 saves the assets for → Companion on devices with

• Android ≥ 10 (API ≥ 29):

/storage/emulated/0/Android/data/edu.mit.appinventor.aicompanion3/files/assets/

• Android < 10 :

/storage/emulated/0/Android/data/edu.mit.appinventor.aicompanion3/files/AppInventor/assets/

1.2. The Private directory is

/data/user/0/<packageName>/files/

This private directory can be used with the File component to save / read text (setting the path without a slash). It can only be accessed by your app and is automatically removed when the app is uninstalled.

2. External Storage
The root directory of the External Storage is:

/storage/emulated/0/  or
/sdcard/ or
file:///storage/emulated/0/  or
file:///sdcard/
file:///mnt/sdcard/

To access the external storage, READ_/WRITE_EXTERNAL_STORAGE permission is required.

2.1. App-specific directory
In addition, there may be an app-specific directory (ASD) which can be created with

• Taifun’s File extension App Inventor Extensions: File | Pura Vida Apps or the
• FileTools extension FileTools : Some tools to work with files or
• Get the path of → ASD (app-specific dir) & → private data dir (internal storage).

Note: The ASD is now usually created automatically or, in the case of old devices (with API < 19, Android 4.4), only when it is needed (i.e. appropriate blocks are used).

The path of the ASD is:

 /storage/emulated/0/Android/data/<packageName>/files/

which is in the External (private) Storage, but does not require READ_ / WRITE_EXTERNAL_STORAGE permissions. The ASD can only be accessed by your app and is automatically removed when the app is uninstalled.

See: https://developer.android.com/reference/android/Manifest.permission.html#READ_EXTERNAL_STORAGE

2.2. External (removable / micro) SD card
There may also be another External Storage: a removable (micro) SD card, eg:

/storage/82C3-E96C/

that can only be read (on devices with Android ≥ 4.4 / KitKat, API 19).

Note:
The root directory of the External Storage

/storage/emulated/0/

is displayed on the device as Internal Storage (unfortunately this is a bit ambiguous).

When targeting Android ≥ 10
https://developer.android.com/training/data-storage
→ Scoped storage

To give users more control over their files and to limit file clutter, apps that target Android 10 (API level 29) and higher are given scoped access into external storage, or scoped storage, by default. Such apps have access only to the app-specific directory on external storage , as well as specific types of media that the app has created .

Android storage use cases and best practices  |  Android Developers

I would like to introduce these three basic terms:

Absolute path │ relative path │ full path

1. This path is an → absolute path:
/storage/emulated/0/Android/data/packageName/files/

2. This path is a → relative path:
/Android/data/packageName/files

Some components need a relative and others an absolute path.

3. And on top of that, some components or Android versions require a → full path:
file:///storage/emulated/0/Android/data/packageName/files/

I recommend these terms to distinguish the paths, for example:

• relative path: /Download
• absolute path: /storage/emulated/0/Download
• full path: file:///storage/emulated/0/Download

EDIT (May 11, 2022):

Storage Permissions on Android 10 & 11
Since AI2 & Kodular decided to declare requestLegacyExternalStorage=true in the Manifest (which is only ignored on Android 11+), storage permissions must also be requested on Android 10.

If you remove this from the Manifest, which I would recommend, no permission for the Shared folders would be required on Android 10 either. The storage permissions would then have to be declared as follows:

<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="28" />

I generally prefer to request as few permissions as possible.
I don't like permissions and my users even less.

How to access to non-media & media files on Android 11+
How to access non-media & media files on Android 11+

---

EDIT (Sept 8, 2023): → targetSdkVersion = 33

On August 31, 2023 new apps and updates must target SDK 33 (Android 13):

Starting with Android 13, READ_EXTERNAL_STORAGE is replaced by 3 other permissions, separately for images, audio and video:

• READ_MEDIA_IMAGES
• READ_MEDIA_AUDIO
• READ_MEDIA_VIDEO

So the "old" storage permissions could be then declared like this:
<uses-permission android:maxSdkVersion="32" android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:maxSdkVersion="29" android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

Behavior changes: Apps targeting Android 13 or higher  |  Android...

On August 31, 2024 new apps and updates must target SDK 34 (Android 14).

Behavior changes: Apps targeting Android 14 or higher  |  Android...

[Salman_Dev]

Thank you @Anke your tutorial really helped me

[Patryk_F]

Despite the limitations of android 11, is it still possible to write to any directory after obtaining write and read permissions?

[Anke]

@Patryk_F

android 11, is it still possible to write to any directory after obtaining write and read permissions?

No, when AI2 targets API 30 (targetSdkVersion = 30) it is no longer possible.

[Patryk_F]

I understand that ASD does not require permissions. However, the permissions for writing and reading in Android will remain. If android completely blocks reading and writing to any folder, what then will these permissions be for?

[Patryk_F]

Another question. Will the ASD directory be accessed only from the application? What about file managers, they won't be able to read files created by my application?

[Anke]

@Patryk_F

If android completely blocks reading and writing to any folder, what then will these permissions be for?

See here:

Preparing for Scoped Storage

Summary

[Anke]

@Patryk_F

Will the ASD directory be accessed only from the application?

Yes.

@Patryk_F

What about file managers, they won't be able to read files created by my application?

Maybe, but try to open the ASD on your (Android 11) device:
→ No files available.
I can see them connecting the device via USB to my PC.

[Patryk_F]

So how will cameras, scanner handlers, create pdf, word, excel and much more work? File manager programs will also cease to exist? In my opinion, it is too much of a blockage. I like systems with freedom like on a PC and not limited to the maximum.

[Taifun]

@Patryk_F

is it still possible to write to any directory after obtaining write and read permissions?

not any, but some...

@Patryk_F

So how will cameras, scanner handlers, create pdf, word, excel and much more work?

everything is explained in the link, @Anke already provided

Android storage use cases and best practices  |  Android Developers

in short: it will be more complicated...

@Patryk_F

I like systems with freedom like on a PC and not limited to the maximum.

I agree...

Taifun

[Patryk_F]

So I don't think we can say "you can't" You can, but it's more complicated. But I think our Java programmers who make extensions will be able to handle it . It was a shame when google bought an android. Now they tell people how to use the phone, they will soon be telling how to live ... although they already know too much about our lives ...

[Taifun]

@Patryk_F

But I think our Java programmers who make extensions will be able to handle it

exactly... we will try to help to provide a solution as easy as possible...
Taifun

[Anke]

@Patryk_F

I like systems with freedom like on a PC and not limited to the maximum.

Yes, read some comments here, then you know what users think of it.

Preparing for scoped storage (Android Dev Summit '19)

[TIMAI2]

@Patryk_F

I like systems with freedom like on a PC

That won't be a Windows or Apple Computer then

[Anke]

@Patryk_F

I like systems with freedom

Me2.

@TIMAI2

That won't be a Windows or Apple Computer

Yes, but the wind is changing right now (also for Windows, Apple & Co) and wonderful times of freedom are coming (without lies, electoral fraud, oppression, C-restrictions, opinion terrorism, ...) - I've been very confident for a long time ... (many will be very surprised).

It all depends on the US election and this has already been decided.
Does anyone want to bet for whom?

[Zol]

Very Helpful! Thank you!
But shame on Google for scoped storage...

[Patryk_F]

I think Windows is less restrictive when it comes to file systems and accessing them, installing applications, etc.
Google is moving towards controlling its users and wants to be present even where it is not needed. Well, but you know - money and masking for the "good of users".

[Zol]

By the way, does anybody know when will AI2 target API 30? Is there any announcement about this?

[Anke]

@Zol

does anybody know when will AI2 target API 30? Is there any announcement about this?

Yes, AI2 has to target API 30 before August 2021, because targetSdkVersion=30 is required for

• new apps from → August 2021 and
• updates from → November 2021

You must also publish apps with the (new) Android App Bundle ( AAB ) format.

New Android App Bundle and target API level requirements in 2021

[Zol]

Thank you, but i'm curious about the AI2 team plan to implement it, not the deadline, but never mind, i'm starting to prepare my apps for this change.
One more question.

The ASD can only be accessed by your app and is automatically removed when the app is uninstalled.

What about reinstall without uninstall? Logically it is stays in case of app update, but i ask to be sure.