Skip to main content
This guide covers connecting and configuring Android devices for testing with Qaptly.

Prerequisites

On Your Mac

  • Android SDK installed (via Android Studio or standalone)
  • ADB (Android Debug Bridge) accessible
  • USB cable for device connection

On Your Android Device

  • Android 7.0 (API 24) or higher
  • USB debugging enabled
  • USB connection in “File Transfer” mode

Enabling USB Debugging

Step 1: Enable Developer Options

  1. Open Settings on your Android device
  2. Go to About phone (or About tablet)
  3. Find Build number
  4. Tap Build number 7 times
  5. You’ll see a message: “You are now a developer!”

Step 2: Enable USB Debugging

  1. Go back to Settings
  2. Find Developer options (usually under System)
  3. Enable USB debugging
  4. Confirm the prompt

Step 3: Connect to Computer

  1. Connect device via USB cable
  2. On the device, you’ll see a prompt:
  3. Check “Always allow from this computer”
  4. Tap Allow

Verifying Connection

In Qaptly

  1. Open Pilot Control
  2. Check the Android Devices section
  3. Your device should appear in the list

Via Terminal (Optional)

Should show:

Installing Qaptly Auto Service

The Qaptly Auto Service APK enables automation on Android devices.

Step 1: Install the APK

  1. In Pilot Control, select your Android device
  2. Click Install Service
  3. Wait for installation to complete

Step 2: Grant Permissions

Accessibility Service

  1. On device, go to Settings > Accessibility
  2. Find Qaptly Auto Service
  3. Enable the service
  4. Confirm any prompts

Display Over Other Apps

  1. Go to Settings > Apps > Qaptly Auto
  2. Tap Appear on top or Display over other apps
  3. Enable the permission

Storage Permission

  1. Go to Settings > Apps > Qaptly Auto
  2. Tap Permissions
  3. Enable Storage or Files and media

Step 3: Verify Installation

  1. In Pilot Control, refresh the device list
  2. The device should show “Service Installed”

Starting Screen Streaming

Start Stream

  1. In Pilot Control, find your Android device
  2. Click Start Stream
  3. The device screen will appear in the streaming panel

Stop Stream

  1. Click Stop Stream on the device
  2. Or close the streaming panel

Device-Specific Settings

Screen Resolution

Qaptly displays the device’s native resolution. The resolution is shown next to the device name.

USB Mode

Ensure your device is in one of these USB modes:
  • File Transfer (MTP): Recommended
  • PTP: Also works
Avoid:
  • Charging only mode
  • MIDI mode

Multiple Devices

Connecting Multiple Devices

You can connect multiple Android devices simultaneously:
  1. Connect each device via USB
  2. Enable USB debugging on each
  3. All devices appear in Pilot Control

Selecting a Device

When multiple devices are connected:
  1. Choose the target device from the list
  2. Selected device is highlighted
  3. Actions apply to the selected device

Troubleshooting

Device Not Detected

  1. Check USB cable: Try a different cable
  2. Check USB port: Try a different port
  3. Restart ADB: Run adb kill-server then adb start-server
  4. Revoke authorizations: On device, go to Developer options > Revoke USB debugging authorizations, then reconnect

”Unauthorized” Status

  1. Check for a prompt on the device
  2. Accept the USB debugging authorization
  3. If no prompt, revoke authorizations and reconnect

Service Installation Failed

  1. Enable “Install from unknown sources” on device
  2. Check available storage space
  3. Try manual APK installation via adb install

Streaming Issues

  1. Ensure Qaptly Auto Service is running
  2. Check accessibility service is enabled
  3. Verify display over other apps permission
  4. Restart the streaming

Performance Issues

  1. Close unnecessary apps on device
  2. Lower screen brightness
  3. Check USB connection (USB 3.0 recommended)
  4. Reduce streaming resolution if available

Best Practices

  1. Use quality cables: Poor cables cause connection issues
  2. Keep devices charged: Low battery can affect streaming
  3. Update regularly: Keep Qaptly Auto Service updated
  4. Clean up: Disconnect devices when not testing
Related: