Make sure notifications are enabled for Call Recorder. The app normally asks for notification permission in its Permissions screen, but this request can be hidden or notifications may have been disabled later.

Open the notification shade and look for the Enter pairing code notification. Expand it if the text field is not visible.

After enabling notifications, cancel pairing and start it again.

Make sure the phone is connected to Wi-Fi and Wireless debugging is enabled.

Open Wireless debugging and tap Pair device with pairing code. Keep this dialog open until Call Recorder finds it.

If the dialog is still not found, turn Wireless debugging off and on, then restart pairing.

VPN, firewall, ad-blocking, and network-control apps may prevent discovery of the pairing service. Temporarily disable them or allow Call Recorder to access the local network.

Use the current 6-digit code shown in the open pairing dialog. The code is temporary, and an older code will not work.

Make sure Call Recorder has found the pairing dialog before entering the code.

If the dialog was closed or the code changed, open Pair device with pairing code again and enter the new code.

Pairing also stops on its own after 10 minutes. Start it again from the wizard if it did.

Return to Call Recorder after pairing and continue the setup.

If Android shows the Allow USB debugging? dialog, tick Always allow from this computer and tap Allow. Accept it only if the key shown by Android matches the key shown by Call Recorder on the Authorize step.

If the wizard shows Authorize, tap it — Call Recorder will ask Android for that dialog.

If Call Recorder says that pairing is required, remove the old Call Recorder entry from Wireless debugging > Paired devices and tap Re-pair.

On some phones Developer options is switched on, but its screen still cannot be opened. Android shows "Please enable developer options first" and closes the screen.

To fix this, open System settings > About phone and tap Build number seven times. This makes Android open Developer options again.

Call Recorder's wizard detects this and offers the same walkthrough as its first step.

Connect the phone to Wi-Fi. Call Recorder requires a Wi-Fi connection to restore built-in ADB access after a reboot.

If Wi-Fi is unavailable, Call Recorder may record through the microphone using its accessibility service. The other side of the conversation may not be heard.

Once Wi-Fi is available, Call Recorder will try to restore built-in ADB access automatically, usually within a few seconds.

Android does not allow its debugging dialog to be accepted while the screen is locked. If access needs that dialog, it can only be restored after you unlock the phone.

Call Recorder waits for the unlock and then tries again on its own.

Turning Wireless debugging on restarts Android's debugging service. This stops every app that was started through ADB — Shizuku most often, and with it every app that depends on Shizuku.

This can happen while Call Recorder sets up or restores built-in ADB access. Start Shizuku again afterwards.

Call Recorder avoids this where it can: it reconnects over the existing connection first and only uses Wireless debugging when there is no other way.

This notification comes from Android, not from Call Recorder. It appears while Wireless debugging is on.

Call Recorder turns Wireless debugging back off once it no longer needs it, and the notification goes away with it.

You can temporarily pause built-in ADB access from the Call Recorder notification.

You can also open the navigation drawer and use the three-dot menu at the top of it.

Pausing turns off Developer options, Wireless debugging, USB debugging, and Call Recorder's accessibility service. Resuming restores the settings and services that Call Recorder needs.

Call Recorder will try to restore access when a call starts. Restoring access usually takes a few seconds. If the call begins before access is restored, its first few seconds will be recorded through the microphone, and the other side may not be heard during that time.

Built-in ADB access ends when Developer options or USB debugging is turned off. Call Recorder then shows a Setup required notification.

Tap that notification, then follow the setup wizard steps to restore access.

If the pairing-code field cannot be used, change the notification style to Android in System settings > Notifications > Notification shade.

If pairing succeeds but ADB access is limited, enable USB debugging (Security settings) in Developer options. This is separate from the regular USB debugging option.

Avoid running the scan feature in Xiaomi's Security app during setup because it may disable Developer options.

If ADB access is limited after pairing, disable Permission monitoring in Developer options.

Enable Allow ADB debugging in charge only mode in Developer options if this option is available.

If ADB access is limited, disable Flyme payment protection while testing the connection.

First remove the Call Recorder entry from Wireless debugging > Paired devices, then start pairing again from Call Recorder.

If that does not help, use Revoke USB debugging authorizations in Developer options and pair again.

Warning: revoking authorizations removes trust for every computer and app previously authorized through ADB, not only Call Recorder.