One of the new options offered by the latest version of Google's operating system is the possibility of Manage permissions on Android 6.0 regarding the applications installed on phones or tablets. This is very useful, since, for example, You can deny access to contacts If you consider it so. Ultimately, it gives the user greater control, which is especially positive.
The fact is that this can be indicated in the installation process itself, but on some occasions it may be desired manage app permissions To reduce the options available to a development or provide more options to make it more complete. Below we indicate the steps to take to do this once an application is already installed. These, by the way, are not complex and do not jeopardize the integrity of the operating system.
What has to be done
To manage permissions in Android 6.0 already granted (or limited) to a development, the first thing is to access the Applications section What is there in Settings, which you can access with the gear icon in the notification bar. Once there, you'll see a list of installed apps.
If you want to change the settings for a specific app, tap on it and, in the new screen, tap on Permissions. You will see the list of what you need and a slider to enable or disable each access. Change what you see fit.
There is an additional way, more efficient in many cases: change permissions by type. In the same Applications menu, press the gear icon at the top and enter App permissions. Choose the type (for example, Contacts) and you'll see which apps use it for allow or deny In block.
Depending on your system version and manufacturer, you may find this view in Security & Privacy > Privacy > Permissions Manager. In permits such as location (query how to manage it), camera or microphone Options such as: Allow only with the app in use, always ask o Do not allow (and, for location, sometimes All the time).
Old apps
Before finishing this section, it is worth knowing one detail: some developments are still they have not adapted to the permissions management in Android 6.0, so when making a change a warning appears. It is possible to manipulate the options at will, but certain tasks They stop working If you don't have all the options enabled (because your code doesn't account for the absence of the permission), keep this in mind and check the app after changing something.
Advanced privacy and security options
In addition to changing permissions per app or per type, Android allows global measures. In Security & Privacy > Privacy > Privacy Controls can disable access to camera or microphone for the entire system. This is useful if you want to temporarily block sensitive sensors without going app by app.
Another very practical function is the automatic revocation permissions on apps you don't use. In each app's tab, you'll see “Pause activity if not in use" or similar. When activated, the system will remove sensitive permissions after a few months of disuse, reducing risks.
Types of permits and what they mean
To make better decisions, it is important to know what each category protectsAmong the most common: Calendar (events), Contacts (agenda), Call logs (record), Phone Number (calls), SMS (messages), Location (positioning), Camera (photos/video), Microphone (audio), Files/Photos and Videos (storage), Music & Audio (media), Nearby devices (Bluetooth/nearby), Notifications (notices), Physical activity (movement) and Health/wellness (body sensor data).
In recent versions, when an app asks for access to your location, camera, or microphone, the option may appear “Just this once”. A temporary permit which is revoked as soon as you stop using the app or after a short period.
Tips to avoid errors when revoking permissions
If you disable basic permissions for the principal function of an app, it could fail. For example, a messaging service without access to notifications, storage or network will lose functionality. If you notice problems after a change, selectively reactive the essentials and try again.
When an app asks for a special permit, look at him context: Grant only if you are going to use that feature. If you are unsure, choose always ask o Do not allow and adjust later from Settings.
For developers: good permission practices
If you develop apps, request permissions at runtime and in context, only when the user activates the feature. It checks the status with a permission verification API and, if appropriate, returns a justification before issuing the request. After the response, it handles the denial with graceful degradation of the affected function, avoiding blocking the interface.
The location requires special considerations: foreground (ACCESS_COARSE/FINE_LOCATION) and, if applicable, background (ACCESS_BACKGROUND_LOCATION), in addition to the type of service in the foreground for location where applicable. In recent versions, you can revoke by programming permissions you no longer use to reinforce user confidence.
For testing, there are installation options that grant permissions automatically and, while debugging, you can inspect the permissions state to detect permanent denials. If your app handles calls or SMS, remember that certain sensitive permissions require the default driver of that function.
Other tutorials for the Google operating system you can meet them in this section of Android Help, surely you will find more than one that helps you.
With these options you can decide what each app shares And when, strengthening privacy without giving up the features you really need. Adjust gradually, verify behavior, and take advantage of views by permission type to keep everything under control.
