Manifest Destiny

Mobile Manager

TOOLS

Trackers

Permissions

Total permissions: 56
Unknown permissions: 29
Signature permissions: 9
Permissions considered normal: 15
Permissions considered dangerous: 3
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.
This permission used to allow too broad access to sensitive methods and all its uses have been replaced by a more appropriate permission. Most uses have been replaced with a NETWORK_STACK or NETWORK_SETTINGS check. Please look up the documentation of the individual functions to figure out what permission now protects the individual function. Allows an internal user to use privileged ConnectivityManager APIs.
Allows a regular application to use android.app.Service#startForeground Service.startForeground
No description yet, this could be a misspelling or a permission created by the app itself
Allows an application to find out the space used by any package.
No longer enforced.
(signature privileged development)
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 call killBackgroundProcesses.
(signature privileged)
Allows an application to call APIs that allow it to query and manage users on the device. This permission is not available to third party applications.
(signature privileged development appop retailDemo)
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 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 read access to privileged phone state. Used internally.
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.
(signature setup appop installer pre23 development)
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 applications to change tether state and run tether carrier provisioning. Not for use by third-party applications.
Allows access to the vibrator.
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
(signature preinstalled appop pre23)
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()
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
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
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
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
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
We need to keep this around for backwards compatibility
removed
No description yet, this could be a misspelling or a permission created by the app itself
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
TOOLS 0

Map of past connections