Allows applications to access information about networks.

Allows applications to access information about Wi-Fi networks.

Allows applications to connect to paired bluetooth devices.

Allows applications to discover and pair bluetooth devices.

Allows applications to change network connectivity state.

Allows applications to change Wi-Fi connectivity state.

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

No longer enforced.

Allows applications to open network sockets.

Allows an application to call killBackgroundProcesses.

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 access to the vibrator.

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

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 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