Skip to main content

FAQ

1. Can I use a GitHub sample if its device type doesn't match the one I have?​

Yes, you can partially use it, but keep the following in mind:

A device application consists of two main parts:

  1. Application Code (usually in the src directory)
    This part is composed of JavaScript logic and resource files, which are device-agnostic and can run on any device.

  2. Module Code (downloaded via install into the dxmodules directory)
    This includes two types of content:

    • JavaScript module code (generally universal)
    • .so dynamic libraries compiled from C/C++ (highly dependent on the device architecture)

Therefore:

  • JS code is universal and can run on different devices without modification.
  • .so files must be re-installed and generated on the target device, and module versions may be incompatible between different devices.
  • Some modules are device-specific (e.g., dxNetwork is only for devices with network capabilities).
  • Screen-related code needs to be adapted or trimmed based on the device's screen size or whether it has a screen.

2. Why does my device automatically restart when running some GitHub samples?​

This is because some samples have the watchdog mechanism enabled.

These sample applications originate from production environments and often integrate "watchdog" logic to ensure stability: If the system does not detect the application's "petting the dog" behavior within a certain time (usually 20 seconds), it will automatically restart the device to prevent the application from becoming unresponsive for a long time.

During debugging (e.g., using VSCode), frequently restarting/interrupting the application might be misinterpreted by the system as a "crashed app," triggering a restart.

Solution:​

  • Temporarily comment out the watchdog logic in the sample code.
  • Most GitHub samples do not have the watchdog mechanism enabled by default and are generally not affected.

3. Why do I get a ".so file not found" error at runtime, even though it's in the dxmodules directory and synced to the device?​

This is because the .so file is strongly tied to the device model, and a project configuration mismatch will cause it to fail to load.

Here are the specific reasons:

  • Your device model is A.
  • But the device model selected in the project configuration file app.dxproj is B.
  • When you run install, the downloaded .so file is compiled for device B.
  • You sync this .so file to device A.
  • Due to the mismatch, device A cannot load this so file, resulting in a ".so file not found" error at runtime.

Solution: Please ensure that the device model in the project configuration matches your actual device. Then, re-select the module versions, run install to download the modules and .so files compatible with the correct device model, and finally, sync them to the device.

4. Why does my development device hang on the boot screen after reboot, with no app running?​

This is normal. Here's why:

  • A development device defaults to Development Mode, where the system does not automatically start any application.
  • At this point, the device interface may remain on the boot screen or appear blank.

How to Run an App?​

  1. Sync the application code to the device using VSCode.
  2. Click "Run" in VSCode to start your application and see it in action.

What if I want the app to start automatically on boot?​

Switch the device to Production Mode.

  • In Production Mode, the system will automatically load and run the installed application on startup.