Whoscall is an Android app developed by Gogolook (23F-1, No. 102, Sec. 2, Roosevelt Rd., ZhongZheng Dist., Taipei 100, Taiwan).

Whoscall first became available on 24 Jul 2010. It is estimated that Whoscall has been downloaded between 50000000 and 100000000 times from the Play Store.

Whoscall 7.23 requires the following permissions:

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.

Marker permission for applications that wish to access notification policy.

Allows applications to access information about Wi-Fi networks.

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

Required to be able to access the camera device.

Allows applications to change network 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 an application to install a shortcut in Launcher.

Allows applications to open network sockets.

Allows an application to modify global audio settings.

Allows an application to see the number being dialed during an outgoing call with the option to redirect the call to a different number or abort the call altogether.

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 applications to read the sync settings.

Allows applications to read the sync stats.

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 monitor incoming MMS messages.

Allows an application to receive SMS messages.

Allows an application to record audio.

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 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 contacts data.

Allows an application to write to external storage.

Allows applications to write the sync settings.