Connecting a Device
The extension supports two connection protocols:ADB
Standard Android Debug Bridge connection over USB. Device must be connected
and udev rules must be configured.
SSH
Network-based connection. Supported on both Qualcomm Linux and Ubuntu. Add
any device by IP address — useful for headless setups or devices on the same
network.
Available Devices
When a device is plugged into the host, it appears in the Available Devices section along with metadata such as dev kit type, serial number, connection status, and mode (USB, WiFi, etc.).
Activating a Device
- Open the Dashboard → Devices section.
- Locate your device in the Available Devices list.
- Click Activate.
Only one device can be active at a time. Switching the active device
automatically retargets all build and deploy operations.
Device Connectivity — WiFi
To connect a device to WiFi, open the connectivity options menu from the active device pane.
Adding a Device by IP Address (SSH)
- In the Devices section, click Add Device.
- Enter the device IP address.
- Select SSH as the connection method.
- Click Connect.
SSH Setup
SSH connections are supported for both Ubuntu and Qualcomm Linux devices. You will need:- Target device powered on and accessible on the network
- SSH client installed on the host
- Both machines on the same network
Device Setup
Get the device’s IP address and username:Extension Configuration
Navigate to the Devices page and click the Connect device via SSH button to open the dialog.
- SSH Key Name — name for the generated key file
- SSH Key Folder — directory to save the key (defaults to
~/.ssh) - Private SSH Key Passphrase — optional passphrase
- Device Identifier — enter either an IP Address (e.g.
10.92.162.215) or Device Name (e.g.mydevice.local) - Device Username — username on the device (e.g.
ubuntu) - Device Password — device password (used to copy the public key)
- Port —
22(default)
- Private SSH Key File Path — path to your existing private key (e.g.
~/.ssh/my-ssh) - Private SSH Key Passphrase — optional passphrase
- Device Identifier — IP Address or Device Name
- Device Username — username on the device
- Device Password — device password
- Port —
22(default)
Flashing Device Software
Ubuntu Device Setup
For Rubik Pi and IQ-9075 EVK devices with Ubuntu OS, follow these steps after flashing:- From the Dashboard, navigate to the Operating Systems tab and click Flash to begin flashing the OS image. A dialog will direct you to EDL mode instructions.
- Once the device enters EDL mode, it appears in the Available Devices section. Activate it, then go back to Dashboard and click Flash.
- After flashing completes and the device shows as Active, click the SDKs tab in the Downloads section to configure the device with all required packages (approximately 15–20 minutes).
UFS Provisioning
If you encounter UFS-related issues, consult the provisioning guide for your specific hardware:
CDT Configuration
Custom Device Tree (CDT) configuration may be required for some hardware setups:
Change Overlay Configuration
The Change Overlay Configuration feature lets you switch the software overlay stack on your active device between Qualcomm Open Source and Qualcomm Proprietary implementations for individual hardware subsystems. This is useful when evaluating open-source drivers, testing proprietary optimized stacks, or reproducing issues specific to one software path.Supported only on devices running Qualcomm Linux 2.0. Operates on the
currently active device only. Ensure the correct device is set as active
before applying changes.
Accessing the Feature
The Change Overlay Configuration option is in the three-dot overflow menu (⋮) on the active device card in the Dashboard.- Open the Dashboard and locate the Active Device section.
- Click the ⋮ (More options) button on the right side of the active device card.
- Select Change Overlay Configuration from the dropdown.
The Configuration Dialog
The dialog shows the currently running OS and a table with three columns:
| Column | Description | Example values |
|---|---|---|
| Overlay | The hardware subsystem being configured | Graphics, Video, Camera, Audio, Sensors |
| Qualcomm Open Source | Open-source driver/stack. Click to select. A dash (–) means none available. | Freedreno Graphics, Video, Libcamera Camera, ASoC Audio |
| Qualcomm Proprietary | Qualcomm-optimized proprietary stack. Click to select. | Adreno Graphics, Video, CamX Camera, AudioReach Audio, Sensors |
- Graphics — Freedreno (open-source Mesa/DRM) vs. Adreno (Qualcomm proprietary GPU driver)
- Video — Open-source vs. Qualcomm proprietary video stack
- Camera — Libcamera (open-source) vs. CamX (Qualcomm proprietary pipeline)
- Audio — ASoC (Linux ALSA/ASoC) vs. AudioReach (Qualcomm proprietary audio)
- Sensors — No open-source option (shown as –); Qualcomm proprietary stack only
- All Qualcomm Open Source — Sets every configurable overlay to its open-source variant
- All Qualcomm Proprietary — Sets every configurable overlay to its Qualcomm proprietary variant
Applying the Configuration
After making your selections, click Apply Configuration in the bottom-right corner. The dialog closes and the extension begins applying the overlays to the device. The active device card immediately shows a progress bar:
Post-Apply Status
Success: The device card shows Overlay configuration applied successful in green and returns to Active – SSH (or Active – ADB) status. A notification confirms: Overlay configuration applied successfully.
