Allows an app to access approximate location. Alternatively, you might want ACCESS_FINE_LOCATION.

Allows an app to access precise location. Alternatively, you might want ACCESS_COARSE_LOCATION.

Allows applications to access information about networks.

Allows applications to access information about Wi-Fi networks.

Allows the app to answer an incoming phone call.

Allows applications to connect to paired bluetooth devices.

Allows applications to discover and pair bluetooth devices.

Allows an application to broadcast sticky intents. These are broadcasts whose data is held by the system after being finished, so that clients can quickly retrieve that data without having to wait for the next broadcast.

Allows an application to initiate a phone call without going through the Dialer user interface for the user to confirm the call.
costsMoney

Required to be able to access the camera device. This will automatically enforce the '> uses-featureall camera features. If you do not require all camera features or can properly operate if a camera is not available, then you must modify your manifest as appropriate in order to install on devices that don't support all camera features.

Allows applications to change network connectivity state.

Allows applications to change Wi-Fi connectivity state.

We need to keep this around for backwards compatibility
removed

Allows a regular application to use android.app.Service#startForeground Service.startForeground

Allows access to the list of accounts in the Accounts Service. Note: Beginning with Android 6.0 (API level 23), if an app shares the signature of the authenticator that manages an account, it does not need 'GET_ACCOUNTS' permission to read information about that account. On Android 5.1 and lower, all apps need 'GET_ACCOUNTS' permission to read information about any account.

Allows applications to open network sockets.

We need to keep this around for backwards compatibility
removed

Allows an application to read the user's calendar data.

Allows an application to read the user's call log. Note: If your app uses the READ_CONTACTS permission and both your ' minSdkVersion and ' targetSdkVersion values are set to 15 or lower, the system implicitly grants your app this permission. If you don't need this permission, be sure your ' targetSdkVersion is 16 or higher.
hardRestricted

Allows an application to read the user's contacts data.

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 access to the device's phone number(s). This is a subset of the capabilities granted by READ_PHONE_STATE but is exposed to instant applications.

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.

We need to keep this around for backwards compatibility
removed

Allows an application to read SMS messages.
hardRestricted

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.

Allows a companion app to run in the background. This permission implies REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND, and allows to start a foreground service from the background. If an app does not have to run in the background, but only needs to start a foreground service from the background, consider using REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND, which is less powerful.

Allows a companion app to use data in the background.

Permission an application must hold in order to use ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS.

Allows an application to send SMS messages.
costsMoney hardRestricted

We need to keep this around for backwards compatibility
removed

Allows access to the vibrator.

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

Allows an application to write the user's calendar data.

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

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

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

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

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