Allows applications to access information about networks.

Allows applications to disable the keyguard if it is not secure.

Allows an application to retrieve state dump information from system services. Not for use by third-party applications.

Allows an application to expand or collapse the status bar.

Allows an application to call forceStopPackage.

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 an application to collect application operation statistics. Not for use by third party apps.

No longer enforced.

Allows an application to call APIs that allow it to do interactions across the users on the device, using singleton services and user-targeted broadcasts. This permission is not available to third party applications.

Allows applications to open network sockets.

Allows an application to collect component usage statistics Declaring the permission implies intention to use the API and the user of the device can grant permission through the Settings application.

Allows an application to read the low-level system log files. Not for use by third-party applications, because Log entries can contain the user's private information.

Allows applications to read the sync settings.

Allows applications to read the sync stats.

New version of GET_TASKS that apps can request, since GET_TASKS doesn't really give access to task information. We need this new one because there are many existing apps that use add libraries and such that have validation code to ensure the app has requested the GET_TASKS permission by seeing if it has been granted the permission... if it hasn't, it kills the app with a message about being upset. So we need to have it continue to look like the app is getting that permission, even though it will never be checked, and new privileged apps can now request this one for real access.

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 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 an application to initiate configuration updates An application requesting this permission is responsible for verifying the source and integrity of any update before passing it off to the various individual installer components

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

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.

Allows an application to install a shortcut in Launcher. In Android O (API level 26) and higher, the INSTALL_SHORTCUT broadcast no longer has any effect on your app because it's a private, implicit broadcast. Instead, you should create an app shortcut by using the android.content.pm.ShortcutManager#requestPinShortcut requestPinShortcut()method from the android.content.pm.ShortcutManagerclass.

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