FAQ

Hardware and Power

Q1: No response after power-on

• Check whether the power adapter meets 12V/3A (recommended).
• Confirm power interface is connected correctly and plug is not loose.
• If using Type-C power, confirm required resistor soldering is completed.

Q2: No serial output

• Confirm you are using debug serial interface (J7) and the correct serial port.
• Recommended serial parameters: 115200, 8N1.
• Replace cable to exclude charge-only cable issues.

ADB and SSH

Q3: Device not recognized by adb devices

adb kill-server
adb start-server
adb devices

• Confirm device is powered on normally.
• Replug USB data cable and replace cable if necessary.

Q4: SSH connection timeout

• Run ping <A8625_IP> first to verify network reachability.
• Verify login command: ssh aidlux@<A8625_IP>.
• Confirm device and host are in the same subnet.

Drivers and Network

Q5: Driver installation failed (dpkg reports file not found)

• Enter the directory containing the driver package before installation.
• Use ls to verify package filename matches a8625-driver-ubuntu_*.deb.

Q6: Network configuration lost after reboot

• ifconfig/ip route commands are usually temporary and may be lost after reboot.
• Use system network management for persistent configuration.

Build and Flashing

Q7: Build script execution failed

• Confirm you are in source root directory.
• Confirm Aidlux_build.sh has execute permission.
• Avoid building directly as root.

Q8: Device cannot boot after flashing

• Confirm flashing package version matches device model.
• Check QFIL logs for interruptions or errors.
• If forced flash via DIP switch was used, restore the switch to normal boot position after flashing.