Requesting permissions in Android: from manifest to dynamic request

• 🔒 android.permission.SYSTEM_ALERT_WINDOW — display on top of other applications
• 📱 android.permission.WRITE_SECURE_SETTINGS — changing system settings
• 🔄 android.permission.BIND_NOTIFICATION_LISTENER_SERVICE — access to notifications

⚠️ Attention: Starting from Android 10 (API 29), permission WRITE_EXTERNAL_STORAGE limited scoped storage. To work with files, use MediaStore or Storage Access Framework.

2. Declaration of permissions in AndroidManifest.xml

The first step is to declare the necessary permissions in file AndroidManifest.xml. Without this, the system will not even allow the application to request permission from the user.

Add the necessary permissions inside the tag <manifest>:

<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

For permissions related to hardware capabilities (for example, camera or Bluetooth), you also need to specify the tag <uses-feature>, so Google Play can filter devices that do not support these features:

<uses-feature android:name="android.hardware.camera" android:required="false" />

Starting with Android 12 (API 31), the ACCESS_BACKGROUND_LOCATION permission requires an explicit setting in the manifest, even if it is requested as part of the LOCATION group.

⚠️ Attention: If your application is targeted Android 13 (API 33) or higher, permissions for accessing media files (READ_EXTERNAL_STORAGE) are replaced with more granular ones: READ_MEDIA_IMAGES, READ_MEDIA_VIDEO i READ_MEDIA_AUDIO.

3. Requesting permissions at runtime (Runtime Permissions)

For dangerous permissions, only declaration in manifest - they need to be requested while the application is running. The process includes three key steps:

1. Checking the current status —whether permission needs to be requested.
2. Requesting permission —calling the system dialog.
3. Response processing —actions depending on the user's choice.

Example of requesting permission for a camera on Kotlin:

// 1. Checking status
if (ContextCompat.checkSelfPermission(this, Manifest.permission.CAMERA)
!= PackageManager.PERMISSION_GRANTED) {

// 2. Requesting permission
ActivityCompat.requestPermissions(
this,
arrayOf(Manifest.permission.CAMERA),
REQUEST_CAMERA_PERMISSION
)
} else {
// Permission has already been granted
openCamera()
}

To process the response, override the method onRequestPermissionsResult:

override fun onRequestPermissionsResult(
requestCode: Int,
permissions: Array<String>,
grantResults: IntArray
) {
when (requestCode) {
REQUEST_CAMERA_PERMISSION -> {
if (grantResults.isNotEmpty() && grantResults[0] == PackageManager.PERMISSION_GRANTED) {
openCamera()
} else {
showPermissionDeniedMessage()
}
}
}
}

In Android 11 (API 30) and above it is recommended to use ActivityResultContracts.RequestPermission() instead of the outdated one onRequestPermissionsResult:

private val requestPermissionLauncher = registerForActivityResult(
ActivityResultContracts.RequestPermission()
) { isGranted ->
if (isGranted) {
openCamera()
} else {
showPermissionDeniedMessage()
}
}

// Call
requestPermissionLauncher.launch(Manifest.permission.CAMERA)

4. Explanation of the need for permissions (Permission Rationale)

Starting from Android 6.0, if the user has previously rejected the permission request, the system will show a dialog with checkbox "Do not ask again". In this case, a repeated request via requestPermissions() will not show the dialog, but will immediately return a refusal. To avoid this, before the request you need to explain to the user why the application needs permission.

Use the shouldShowRequestPermissionRationale():

if (ActivityCompat.shouldShowRequestPermissionRationale(this, Manifest.permission.CAMERA)) {
// Show an explanation (for example, AlertDialog)
showPermissionExplanationDialog()
} else {
// Request permission or redirect to settings
requestPermissionLauncher.launch(Manifest.permission.CAMERA)
}

Examples of explanations for the user:

• 📸 "Access to the camera needed to scan QR codes and create a profile photo."
• 📍 "Geolocation helps show nearby stores and optimize routes."
• 💾 "Access to files required to download and save your documents."

⚠️ Attention: Do not overuse explanations - they should be short and specific. Long texts irritate users and increase the likelihood of refusal.

5. Handling permanent denial and redirecting to settings

If the user selected "More. do not ask" and denied the permission, calling again requestPermissions() will not show the dialog. In this case, you need to redirect the user to the application settings, where he can manually enable the permission.

Check for permanent refusal:

if (!ActivityCompat.shouldShowRequestPermissionRationale(this, Manifest.permission.CAMERA) &&
ContextCompat.checkSelfPermission(this, Manifest.permission.CAMERA) != PackageManager.PERMISSION_GRANTED) {
// Redirect to settings
val intent = Intent(Settings.ACTION_APPLICATION_DETAILS_SETTINGS)
intent.data = Uri.fromParts("package", packageName, null)
startActivity(intent)
}

It is important to warn the user that he will be redirected to settings. Example message:

"Permission deniedTo use the camera, enable access in the application settings Click 'OK' to proceed. go there now."

Some manufacturers (Xiaomi, Huawei, Oppo) modify Android and add additional levels of permissions. In such cases, you may need to:

• 🔧 Manually enable permission in "Settings → Permissions → Autorun" (for background tasks).
• 📱 Resolution "Show on top of other applications" for overlay windows.
• 🔄 Separate permission for "Changes to system settings" (for example, screen brightness).

override fun onResume() {
super.onResume()
if (ContextCompat.checkSelfPermission(this, Manifest.permission.CAMERA) == PackageManager.PERMISSION_GRANTED) {
openCamera()
}
}

6. Features of working with permissions in Android 13 and 14

Android 13 (API 33) i Android 14 (API 34) have made significant changes to the permissions system, especially for working with media files and notifications.

Main changes in API 33:

• 🖼️ Resolution READ_EXTERNAL_STORAGE outdated. Instead, use:
  • READ_MEDIA_IMAGES — access to photos
  • READ_MEDIA_VIDEO — access to video
  • READ_MEDIA_AUDIO — access to audio files
• 🔔 New resolution POST_NOTIFICATIONS —required for displaying notifications (previously did not require an explicit request).
• 📱 Permission NEARBY_WIFI_DEVICES replaces ACCESS_FINE_LOCATION for scanning Wi-Fi devices.

An example of requesting permission for notifications:

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
requestPermissionLauncher.launch(Manifest.permission.POST_NOTIFICATIONS)
}

Changes in API 34 (Android 14):

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
// Logic for Android 13+
} else {
// Logic for older versions
}

if (grantResults.isNotEmpty()) {
val cameraGranted = grantResults[0] == PackageManager.PERMISSION_GRANTED
val microphoneGranted = grantResults[1] == PackageManager.PERMISSION_GRANTED
// Process each result separately
}

adb shell dumpsys package <package_name> | grep "grant"

adb shell pm revoke <package_name> android.permission.CAMERA
adb shell pm grant <package_name> android.permission.CAMERA

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
requestPermissionLauncher.launch(Manifest.permission.POST_NOTIFICATIONS)
}

ActivityCompat.requestPermissions(
this,
arrayOf(
Manifest.permission.CAMERA,
Manifest.permission.RECORD_AUDIO
),
REQUEST_CODE_MULTIPLE_PERMISSIONS
)