Android device connected via ADB

Android devices can be intercepted by connecting them to the Android Debug

Bridge on your machine, enabling debug mode, and then selecting this option.

The option will only be enabled when an accessible device is connected. You can
run adb devices on the command line to use ADB to check for devices for yourself
and debug any issues with this.
This will attempt to automatically install a temporary system certificate on rooted
devices and some emulators, then download & install the HTTP Toolkit Android app
if it's not already present, and then send configuration to that app to start interception.
The first time you do this, the device may show some permission prompts to activate
a VPN and setup certificates.

Interception requires connectivity between your Android device and your computer.
They need to be on the same network, the network needs to allow connectivity
between them, and if your computer has a firewall it must allow incoming traffic to
HTTP Toolkit's proxy port.

For more details, see the in-depth Android interception guide.

Android device connected via QR

Alternatively, Android devices can be intercepted by scanning a QR code, without
enabling debugging on the device. You can scan this with any QR code reader, or
with the "Scan QR Code" button in the HTTP Toolkit app.

The first time you scan the code, if you don't have the HTTP Toolkit app installed, it
will open the Google Play store page for the HTTP Toolkit Android app so you can
get set up.
The first time you do this, the device may show some permission prompts to activate
a VPN and setup certificates. The QR code contains the configuration required for
the device to connect to your computer, but it can't automatically set up certificates
like ADB setup can, so ADB setup is recommended, especially on rooted devices &
emulators.