MyPhoneExplorer Client is an Android app developed by FJ Softwaredevelopment.

MyPhoneExplorer Client first became available on 08 Aug 2010. It is estimated that MyPhoneExplorer Client has been downloaded between 5000000 and 10000000 times from the Play Store.

MyPhoneExplorer Client 2.6 requires the following permissions:

Allows applications to access information about networks.

Marker permission for applications that wish to access notification policy.

Allows applications to access information about Wi-Fi networks.

Must be required by an AccessibilityService, to ensure that only the system can bind to it.

Must be required by an NotificationListenerService, to ensure that only the system can bind to it.

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.

Allows applications to enter Wi-Fi Multicast mode.

Allows applications to change Wi-Fi connectivity state.

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

Allows access to the list of accounts in the Accounts Service.

Allows applications to open network sockets.

Allows an application to modify global audio settings.

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

Allows an application to read the user's call log.

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

Allows an application to read from external storage.

Allows read only access to phone state, including the phone number of the device, current cellular network information, the status of any ongoing calls, and a list of any PhoneAccounts registered on the device.

Allows an application to read SMS messages.

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 application to receive SMS messages.

Permission an application must hold in order to use ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS. This is a normal permission: an app requesting it will always be granted the permission, without the user needing to approve or see it.

Allows an application to request installing packages. Apps targeting APIs greater than 22 must hold this permission in order to use ACTION_INSTALL_PACKAGE.

Allows an application to send SMS messages.

Allows an app to create windows using the type TYPE_SYSTEM_ALERT, 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.

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.

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

Allows an application to write to external storage.