Android permissions explained: mouse control, pairing and audio

One feature, one reason for access

A connection is not a blanket permission. Install the companion, read its explanation and choose access for the feature you intend to use. You can use the setup guide to distinguish a missing app permission from a PC that has not been approved.

Mouse and keyboard control

PhoneBridger’s mouse-control setup opens Android’s accessibility service settings. Accessibility access can let an app read screen content and interact with other apps on your behalf. Grant it only after you understand that capability and trust the app source.

Open the permission flow in PhoneBridger, review the explanation and choose the PhoneBridger service in Android settings if you wish to enable it. Return to the companion and check its status. A saved switch and a service that is still starting are not always the same state; give the app’s status a chance to update before repeatedly toggling settings.

When Android shows a restricted setting

Some Android 13-and-later settings can be restricted for installed apps. Google’s guidance describes a route through Settings → Apps → the app → More → Allow restricted settings, with on-screen confirmation. Availability and wording vary by device.

That is a sensitive choice, not a routine error to bypass. Google advises allowing it only when you trust the developer. If the option is absent, managed by your organization or unclear, stop and ask for help. Do not install another tool simply to defeat Android’s protection.

Camera access for pairing

The in-app pairing scanner uses the camera to read the code on your own PC. Review the camera request in that context. The sample QR illustration on the website cannot pair a device. Approving the PC is a separate confirmation after scanning.

If scanning is unsuccessful, check the current PC code, lighting and scanner framing before changing unrelated permissions. Do not share a pairing code in a public post or send it to an unsolicited helper.

Listening through your PC

Phone audio requires Android 10 or later and Android’s capture consent. The source app must also permit playback capture; some apps or content do not. Silent audio does not by itself mean mouse control or pairing failed.

Start audio sharing from the app and review the system prompt. Declining audio consent leaves that audio feature unavailable. Check the source app and PC volume before retrying; repeatedly granting unrelated permissions will not make protected audio capturable.

USB authorization

USB debugging is needed only for the current physical USB transport. It approves development access for a computer, while PhoneBridger’s own approval establishes application trust. Use USB or Wi-Fi? for the cable preparation steps. Ordinary PhoneBridger Wi-Fi does not require wireless debugging.

How to stop or revoke access

• Use the PC app’s pause control or return to Windows with Ctrl + Alt + S when you want to stop controlling the phone.
• Disable the PhoneBridger accessibility service in Android settings if you no longer want that service access.
• Use the app’s forget action to revoke the saved phone/computer pairing rather than treating an unplugged cable as revocation.
• Review or revoke Android debugging authorizations separately when you no longer trust that PC for debugging.

What to send support

Describe the feature you are enabling, the exact visible prompt, your Android version and the app version. A cropped screenshot of the setting can help if it contains no personal content. Do not include a password, pairing token, private app messages or a full settings export.

Product steps checked against the current release documentation on 6 October 2026. This private preview records a prepared editorial edition; it is not a past public publication. Review method & corrections.