Expert Mode fails adb pairing when a system-wide VPN is used

[Holbormon]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

When using Android's always-on VPN, wireless debugging listens on the VPN-local IP (10.2.x.x) instead of the physical interface's IP (192.168.x.x), which means KeyMapper fails adb pairing when a VPN is on (I'm assuming it expects the phone to be reachable on the physical interface's IP).

What did you expect to happen?

If the VPN-local IP is visible to KeyMapper, it should try using it to connect. If not, Keymapper could prompt the user for the debugging IP/Port as needed (in addition to the pairing code).

What would the developer need to do to reproduce the bug?

1. Toggle Always-on VPN
2. Try to start Expert mode following the wizard steps

App version

4.0.5-foss

Android version

Android 16

Device model and manufacturer

Pixel 8 w/ GrapheneOS

Extra info

• My device is rooted

[sds100]

For reference: I use a Pixel 7 with Wireguard VPN all the time and never had issues. I've noticed the thing where the settings UI only shows the VPN address but it still works for me on localhost and my LAN. Key Mapper always uses localhost. Is this some GrapheneOS privacy/security setting?

Have you tried connecting to your phone over ADB wireless on your LAN?