Mobile Session
Mobile devices in QDC are accessed through ADB (Android Debug Bridge) over an SSH tunnel. This secure connection allows you to run ADB commands on remote devices as if they were connected locally. This guide walks you through the full connection process.
Prerequisites
Before you begin, make sure you have:
- An SSH key imported or generated in QDC. See SSH Keys for setup instructions.
- A running Interactive Session with a Mobile device.
Step 1: Set up SSH tunneling
The SSH tunnel creates a secure connection between your local machine and the remote device. This tunnel must stay running for the entire session.
Open a PowerShell or Terminal window and run the SSH command shown in the Connect dialog.
The command follows this format:
ssh -i {path_to_private_key} -L {adb_port}:sa{session_id}.sa.svc.cluster.local:5037 -N sshtunnel@ssh.qdc.qualcomm.com| Value | Description | Where to find it |
|---|---|---|
{path_to_private_key} | Path to your SSH private key file | The file you created/uploaded when setting up SSH keys |
{adb_port} | Local port for ADB access to the device | Shown in the Connect dialog |
{session_id} | Your session execution ID | Shown in the Connect dialog |
Keep this window open
The SSH tunnel must remain active for the duration of your session. Do not close the terminal window running this command.
Step 2: Run ADB commands
Once the tunnel is running, open a new terminal window and run ADB commands to interact with the device:
adb devices — Verify the device is connected
adb shell — Open a remote shell on the device
adb push / adb pull — Copy files to and from the device
adb install — Install an APK on the device
adb logcat — View device logs in real-time
For a full list of commands with examples, see the ADB Commands reference.
Troubleshooting
The SSH tunnel fails with "Permission denied"
If the ADB port is already in use (usually by a local ADB server), run adb kill-server to free the port, then try the SSH tunnel command again.
For more common issues, see SSH Troubleshooting.