Google has taken the issue of security very seriously with Android 11, a new update of its well-known mobile operating system that will come with a very interesting feature called “Scoped Storage”, that will make downloads from external apps, i.e. outside the Google Play Store, a little more complicated.
With “Scoped Storage” on Android 11 it is produced a major reinforcement of the necessary permits to be able to download apps outside of Google’s official app store. I explain how it works, when we start the download process to install an APK we will receive a warning that we must authorize such installation.
By giving permission the process should continue as normal, but it’s not, since there is a sudden closure and unexpected that takes us directly to the operating system’s home screen. If we want to complete the installation of the APK, we will have to go back manually to the place where it is.
For example, if you pass us an APK through an instant messaging application and we want to install it on Android 11 twe will allow its installation, assume the spontaneous closure of the application, re-entering it and starting, a second time, the process installation.
In that second round the installation is completed no problems, at least as indicated by those who have had the opportunity to try Android 11.
What explanation has Google given about this issue affecting Android 11?
The Mountain View giant has commented that the way the file system is configured and in which storage is mounted on Android R (Android 11) have changed greatly compared to previous versions.
Now, when an application starts the installation process and it doesn’t have, by default, the necessary permissions, receives a file system view that does not allow you to start the write process on certain directories. When you get permission that view doesn’t work for you, it has to be renewed and updated, a process that can’t be done on the fly.
So the only way that the app we want to install get the new view you need to after you have obtained the required permissions is by performing that closure and starting a new opening of the installation process.
Google said that are evaluating possible changes internally, which means that this issue may not be present in the final version of Android 11, at least in principle.