Support
Troubleshooting
Symptom → cause → fix
| Symptom | Likely cause | Fix |
|---|---|---|
| The project list is empty and Add device does nothing | The bundled native library does not match the app build (a missing C symbol makes the project store fail to load) | Install a build whose native library matches — fixed in 1.100.1. On a developer machine rebuild the Android C library before rebuilding the APK. |
| Dialogs and bottom sheets are in Chinese while the rest of the UI is English | The language scope sat below the navigator, so modal routes fell back to the default language | Fixed in 1.100.1 — modal routes now follow the selected language. |
| Network-check results appear in the wrong language | The data layer reads a process-wide language value that was never written at start-up | Fixed in 1.100.1 — the value is set when settings are restored and on every language switch. |
| “Joined a network (Wi-Fi name unreadable)” | Android hides the SSID from apps without the Location permission | Grant location permission to the app, or ignore it — the connection itself is fine. |
| “No device found on the LAN” | mDNS and the fixed hotspot address both failed; you may be on a different network | Continue with step 3 of the check — it tells you which network to join. |
| “No device hotspot found — the device may be off” | No Etchmara_A1_XXXXXX network is in range |
Check the power light and the screen, then press Continue check. |
| Process says “No job selected” even after Send to process | The project was empty when sent | Draw or import something first; the job card only appears with real geometry. |
| “Cannot connect to 192.168.0.1:23 … errno = 110” | Nothing is listening there — wrong network, or the controller is off | Join the machine's hotspot, then use the network check's Connect button. |
What the network check can and cannot tell you
It distinguishes nothing answered at this address from something answered but it is not a controller. Only the second case is a software problem; the card will not call the app broken when the machine is simply elsewhere on the network.
Still stuck?
- Pull the Run log at the bottom of the Process screen — it is the controller's own words.
- Send feedback from the avatar → Send feedback; the app attaches the recent log lines.
- Check the version at the bottom of the avatar panel (
Etchmara · v1.100.1+234) before reporting a bug.