> ## Documentation Index
> Fetch the complete documentation index at: https://dragonwingdocs.qualcomm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Answers to the most common problems encountered with the Qualcomm® VSCode Extension.

<AccordionGroup>
  <Accordion title="I cannot connect USB devices to WSL" icon="usb">
    **Cause:** Some organizations block `usbipd` via group policy — this typically surfaces as an error during `usbipd bind` or `usbipd attach`.

    **Fix:** Contact your IT department and ask them to allow the `usbipd` group policy on your machine.

    As an alternative, try the [mirrored networking workaround](../setup/wsl-usb#corporate-firewall-workaround).
  </Accordion>

  <Accordion title="I cannot flash images to the device" icon="bolt">
    **Check 1:** Verify the device is in EDL mode.

    ```bash theme={null}
    lsusb
    ```

    You should see:

    ```text theme={null}
    Bus 002 Device 002: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
    ```

    If the device does not appear, power-cycle it and retry.
  </Accordion>

  <Accordion title="Device shows in lsusb but QDL reports permission errors" icon="lock">
    **Cause:** Your user account is not a member of the `plugdev` group.

    **Fix:**

    ```bash theme={null}
    sudo usermod -aG plugdev $USER
    ```

    Log out and back in. See [the Android developer guide](https://developer.android.com/studio/run/device) for detailed instructions.

    Also verify that your [udev rules](../setup/udev-rules) are correctly configured.
  </Accordion>

  <Accordion title="Host environment setup fails during the Getting Started stepper" icon="wrench">
    **Most likely causes:**

    1. **Missing sudo password** — The VS Code Terminal is waiting for your password. If the Terminal panel is hidden, open it via **View → Terminal**.

    2. **APT conflicting GPG signatures** — A small number of users encounter an error like:

    ```text theme={null}
    Conflicting values set for option Signed-By regarding source
    ```

    This is the same issue described in [this AskUbuntu post](https://askubuntu.com/questions/1156409/conflicting-values-set-for-option-signed-by-regarding-source). Fix it by removing one of the files that contains the conflicting GPG asset.
  </Accordion>

  <Accordion title="VS Code extension icon is missing after install" icon="puzzle-piece">
    1. Confirm the extension installed successfully: open the Extensions panel and look for **Qualcomm IDE** in the Installed list.
    2. Reload the VS Code window: `Ctrl+Shift+P` → **Developer: Reload Window**.
    3. If you are on Windows, confirm VS Code is running connected to WSL (status bar should show **WSL: Ubuntu-22.04**) and reinstall from within WSL.
  </Accordion>

  <Accordion title="IntelliSense is not working in my project" icon="code">
    The auto-generated `.vscode/c_cpp_properties.json` may be pointing at a stale SDK path.

    1. Open the Command Palette (`Ctrl+Shift+P`).
    2. Run **C/C++: Edit Configurations (UI)**.
    3. Verify the include paths point to your installed SDK.

    Alternatively, delete the `.vscode/` folder and re-import the project from the **Projects** section to regenerate it.
  </Accordion>
</AccordionGroup>

***

Still stuck? Visit the [Qualcomm Developer Forum](https://developer.qualcomm.com/forum) or check the [VS Code FAQ](https://code.visualstudio.com/docs/supporting/faq).