Notice: tempnam(): file created in the system's temporary directory in /home/gearwfgj/public_html/wp-content/plugins/xcoobee/xcoobee.php on line 575

Warning: file_put_contents(): Filename cannot be empty in /home/gearwfgj/public_html/wp-content/plugins/xcoobee/xcoobee.php on line 646

Warning: include(): Filename cannot be empty in /home/gearwfgj/public_html/wp-content/plugins/xcoobee/xcoobee.php on line 672

Warning: include(): Failed opening '' for inclusion (include_path='.:/opt/alt/php72/usr/share/pear') in /home/gearwfgj/public_html/wp-content/plugins/xcoobee/xcoobee.php on line 672
Android 11: installing apps from unknown sources becomes more complicated - GEARCOUPON

Android 11: installing apps from unknown sources becomes more complicated

Android 11 makes it more difficult to install apps from unknown sources, i.e. sources other than the Google Play Store. At least there is 4 criticism from developers in the Developer Preview. If you want to give apps permission to push additional APKs onto their smartphone, which is important for third-party app stores, for example, the app must be restarted after the respective rights have been granted.

Until Android 10 it was different, because you were simply redirected to the control panel, the function was activated and then led back to the app that initiated the procedure so that you could now complete the procedure. In Android 11, the original app is closed using a force quit, which of course means that entries can also be lost. According to Google, this procedure is intentional.

After the authorization has been granted, the app must have write access to new directories – for Android 11 it is necessary that it be restarted. Developers do not like that this can lead to problems in some applications, since such a force quit is actually not a normal event. Google has taken note of the criticism and would like to examine the situation again.

Conclusion: If an app under Android 11 is authorized to install new APKs itself, it has to be completely closed and restarted once again, because the write rights cannot otherwise be adjusted. Previously, this was done without a restart. At least as a user, you only have to go through this procedure once per app, so that this new stumbling block can be overcome for most users.

Android Police

Source link

We will be happy to hear your thoughts

Leave a reply