Skip to content
DuolixDuolix
HomeAll RobotsKits & partsEvents

My

Saved itemsOrders

Explore

Developer docsCommunity
AboutSupportPrivacy

© 2026 Duolix

Duolix
Developer documentationAidLux system
All documentation
Start hereDevelopment overviewQuick startConnect to the device
QCS6490 hardwareQCS6490 hardware overviewQCS6490 interfacesQCS6490 bring-up
AidLux systemAidLux workspaceNetwork and remote accessDevelopment environmentStart an application at boot
AI developmentInference workflowAidLite SDKROS 2 integration
SDK referenceAidLite Python APIAidLite C++ APIAidCV Python APIAidConnect C++ APIAidConnect Android APIAidStream C++ APIAidVoice C++ API
TroubleshootingTroubleshooting
AidLux system

AidLux workspace

Navigate the desktop, files, terminal, and application environment.

AidLux brings an Android-facing application surface together with a Linux development environment. The exact launcher labels and installed tools depend on the image release, but the workflow is consistent: open the application, enter the Linux desktop or terminal, and work from your user-owned project directory.

Work in a project directory

Create a separate directory for each application. Keep source files, model files, and generated output distinct:

mkdir -p ~/projects/my-app/{src,models,output}
cd ~/projects/my-app

Run pwd before using relative paths in commands or SDK examples. Check available storage with df -h . before copying a large model.

Use the desktop tools

The AidLux desktop may include an application center, file manager, terminal, and code editor. Package availability depends on the image. Install only the tools required by your project, and record their versions so the environment can be reproduced.

Android applications and Linux programs have different file and permission boundaries. When a Linux process needs a camera, microphone, or other shared resource, check both the AidLux application permission and the Linux-side device access.

Transfer files

For an SSH-enabled device:

scp ./model.bin <username>@<device-ip>:~/projects/my-app/models/

Use the file manager for interactive transfers when SSH is unavailable. Verify the copy before running a model:

ls -lh ~/projects/my-app/models/

Avoid editing installed SDK files directly. Keep application code in your project directory and reinstall packages through the image's package manager when needed.

PreviousQCS6490 bring-upNextNetwork and remote access