This application exists because malicious or just improperly programmed applications can, intentionally or not, block your device from the ability to call emergency numbers. If you are in such a situation, this app helps you to find the culprit – which you then can uninstall (or disable).
For the exact details on the vulnerability (why this happens, how it was discovered, fixes timeline, ...), please check the article by Mishaal Rahman hereopen in new window.
This application requires two call management permissions:
- Manifest.permission.READ_PHONE_STATEopen in new window
- Manifest.permission.READ_PHONE_NUMBERSopen in new window.
This is because on Android, in order to read which applications are adding PhoneAccounts to Android's TelecomManager, these permissions are necessary.
READ_PHONE_STATE is used in all supported Android versions, whereas
READ_PHONE_NUMBERS is requested on Android 12 and onwards exclusively.
No permission is (ab)used to log, collect or process any personally identifiable user information.
The application is very simple, and contains 2 components:
- A message at the top of the device, explaining if the application detected a possible abuse of this functionality which may cause issues while attempting to call Emergency Services.
- A list of the applications that have registered a Phone Account in your device, usually including your own SIM Cards, Google Duo, Teams, among others. Alongside each app, the number of accounts is displayed to facilitate the identification of the malfunctioning/hijacking application.
Check this video if you have doubts on how to interpret this data:
(Thanks to Explaining Androidopen in new window for the video)
Permissions necessary for the app to work:
Case where Teams added 4 PhoneAccounts to TelecomManager:
The app flags this as abnormal behaviour
Case without any abnormal app behaviour"
Building the app
You can use Android Studio to build the application, or you can build it by using the CLI.
Navigate to the folder where the source code is located:
Then, check that Gradle runs properly by executing:
You can now build the application in release or debug flavor:
After it's done building, you will now need to sign the resulting APK by using apksigner, or jarsigner. Here's an example:
apksigner sign --ks /path/to/example.keystore --ks-pass pass:"EXAMPLEPASSWORD" --v1-signing-enabled true --v2-signing-enabled true --verity-enabled true *.apk