Allows an application to access extra location provider commands.

Allows applications to access information about networks.

The system process that is allowed to bind to services in carrier apps will have this permission. Carrier apps should use this permission to protect their services that only the system is allowed to bind to.

Must be required by a android.telecom.ConnectionServic, to ensure that only the system can bind to it.

No description yet, this could be a misspelling or a permission created by the app itself

Allows an application to modify the current configuration, such as locale.

Allows applications to change network connectivity state.

Allows an application to expand or collapse the status bar.

No longer enforced.

Allows applications to open network sockets.

Allows modification of the telephony state - power on, mmi, etc. Does not include placing calls. Not for use by third-party applications.

Allows mounting and unmounting file systems for removable storage. Not for use by third-party applications.

Allows an application to read from external storage. Any app that declares the WRITE_EXTERNAL_STORAGE permission is implicitly granted this permission. This permission is enforced starting in API level 19. Before API level 19, this permission is not enforced and all apps still have access to read from external storage. You can test your app with the permission enforced by enabling
softRestricted immutablyRestricted

Allows read only access to phone state, including the current cellular network information, the status of any ongoing calls, and a list of any android.telecom.PhoneAccount registered on the device. Note: If both your ' minSdkVersion and ' targetSdkVersion values are set to 3 or lower, the system implicitly grants your app this permission. If you don't need this permission, be sure your ' targetSdkVersion is 4 or higher.

Allows applications to read the sync settings.

Allows applications to read the sync stats.

Required to be able to reboot the device. Not for use by third-party applications.

Allows an application to receive the ACTION_BOOT_COMPLETED that is broadcast after the system finishes booting. If you don't request this permission, you will not receive the broadcast at that time. Though holding this permission does not have any security implications, it can have a negative impact on the user experience by increasing the amount of time it takes the system to start and allowing applications to have themselves running without the user being aware of them. As such, you must explicitly declare your use of this facility to make that visible to the user.

The restartPackage API is no longer supported.

No description yet, this could be a misspelling or a permission created by the app itself

Allows an app to create windows using the type TYPE_APPLICATION_OVERLAY, shown on top of all other apps. Very few apps should use this permission; these windows are intended for system-level interaction with the user. Note: If the app targets API level 23 or higher, the app user must explicitly grant this permission to the app through a permission management screen. The app requests the user's approval by sending an intent with action ACTION_MANAGE_OVERLAY_PERMISSION. The app can check whether it has this authorization by calling android.provider.Settings#canDrawOverlays Settings.canDrawOverlays()

Allows access to the vibrator.

Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming.

Allows an application to write to external storage. Note: If both your ' minSdkVersion and ' targetSdkVersion values are set to 3 or lower, the system implicitly grants your app this permission. If you don't need this permission, be sure your '>getExternalFilesDir and getExternalCacheDir. If this permission is not allowlisted for an app that targets an API level before Q this permission cannot be granted to apps.
softRestricted immutablyRestricted

Allows an application to read or write the secure system settings. Not for use by third-party applications.

Allows an application to read or write the system settings. Note: If the app targets API level 23 or higher, the app user must explicitly grant this permission to the app through a permission management screen. The app requests the user's approval by sending an intent with action ACTION_MANAGE_WRITE_SETTINGS. The app can check whether it has this authorization by calling android.provider.Settings.System#canWrite Settings.System.canWrite()

Allows applications to write the sync settings.

No description yet, this could be a misspelling or a permission created by the app itself