Published by linuxct

Report an issue with PhoneAccount Abuse Detector.
Send the customer service your feedback so they can fix your issue asap.

Email Support directly

Chat with our AppContacter AI Support

Why should I report an Issue with PhoneAccount Abuse Detector?

  1. AppContacter will directly Email your issue/feedback to an apps's customer service once you report an issue and with lots of issues reported, companies will definitely listen to you.
  2. Pulling issues faced by users like you is a good way to draw attention of linuxct to your problem using the strength of crowds.
  3. Importantly, customers can learn from other customers in case the issue is a common problem that has been solved before.
contact PhoneAccount Abuse Detector image 1 contact PhoneAccount Abuse Detector image 2

About PhoneAccount Abuse Detector

1. No permission is (ab)used to log, collect or process any personally identifiable user information. - 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.

2. PhoneAccount Abuse Detector is a simple application to enumerate and detect any application that (ab)uses adding an indefinite amount of PhoneAccount(s) to Android's TelecomManager.

3. This application exists because malicious or just improperly programmed applications can, intentionally or not, block your device from the ability to call emergency numbers.

4. This application requires two call management permissions, Manifest. permission.

5. This is because on Android, in order to read which applications are adding PhoneAccounts to Android's TelecomManager, these permissions are necessary.

6. Alongside each app, the number of accounts is displayed to facilitate the identification of the malfunctioning/hijacking application.

7. READ_PHONE_STATE is used in all supported Android versions, whereas READ_PHONE_NUMBERS is requested on Android 12 and onwards exclusively.

8. READ_PHONE_STATE and Manifest. permission. READ_PHONE_NUMBERS.

9. If you are in such a situation, this app helps you to find the culprit – which you then can uninstall (or disable).

10. If you have doubts, check the YouTube video at the top!

11. This application and all its components are Open-Source software, licensed under the AGPL-3. 0 license.

PhoneAccount Abuse Detector Customer Insights

1. Thank you!Super simple app that checks for duplicate Phone Account entries that can trigger the recently discovered Android 911 calling bug.According to the app, you don't need to download this app, if you have Android security patch January 2022 or newer.very great app.

2. Just nice that this app is helping detect a bug and kudos to the dev not taking advantage by putting ads, but making this AGPL.With thanks to the maker, and to Ars Technica for publicising the Google/ Microsoft bug.

3. Fine work!Quick, easy, no nonsense app that'll help put your mind at ease regarding the Android 911 bug.

4. Thanks!Fast and easy way to see if my phone is affected by the critical PhoneAccount bug.

5. I guess it works differently? Oh, I think I found the Easter egg :-) Reminiscent of developer mode..A very easy app to use.

6. 911 calling on ars technica today, so finding this tool linked at the bottom of the article was very helpful and reassuring.

7. Thank you so much for the effort for creating this app! As a fellow developer, I understand.No frills and just straight to the point.

8. Thanks for putting me at ease in case of an emergency.

9. This app provided an easy check for peace of mind.

10. do perfectly what it says and tbh this app can save ur life so definitely recommendedUseful app for knowing whether or not you have the "911 bug" phone accounts.

11. Now to wait for the Google Pixel 6 patch later this month.

Steps to Troubleshoot & Fix PhoneAccount Abuse Detector Issues

1. Fix PhoneAccount Abuse Detector Not Working/Crashes/Errors/Unresponsive & Black/White screen:

  1. Restart PhoneAccount Abuse Detector: Restarting the app will resolve most errors.
  2. Update the PhoneAccount Abuse Detector App. Here is how:
    1. On Android goto PlayStore » Search for "PhoneAccount Abuse Detector" » Open PhoneAccount Abuse Detector » click "Update".
    2. On iPhone, goto AppStore » Your profile » Available Updates » Check for PhoneAccount Abuse Detector » click "UPDATE".
  3. Clear PhoneAccount Abuse Detector app cache: Clearing cached data will force your app to retrieve the latest data directly from PhoneAccount Abuse Detector servers.
    1. On Android, goto Settings » Apps » Select "PhoneAccount Abuse Detector" » click Storage » click "Clear Cache".
  4. Check PhoneAccount Abuse Detector app permissions. If any of these permissions required to use your device's features are disenabled, PhoneAccount Abuse Detector might not work.
  5. Uninstall and reinstall PhoneAccount Abuse Detector. If nothing else has worked, completely uninstall PhoneAccount Abuse Detector then reinstall.
  6. Restart your device. Last, restarting your device can often clear most problems causing PhoneAccount Abuse Detector not working

2. Fix PhoneAccount Abuse Detector Server issues & Internet Connection

  1. Check network connection: An unstable Internet will make PhoneAccount Abuse Detector be unable to connect to it's servers. Ensure your wi-fi is working then restart app.
  2. Disable VPN: VPN can cause connection errors and lead to PhoneAccount Abuse Detector not working. Make sure all VPNs are off
  3. Enable background data: When Background data is turned off, PhoneAccount Abuse Detector may not be able to connect to the Internet when running in the background.

Reported Issues