The motor address may differ from the default (0xFFFF). On Android, go to Settings > Motor > Discover Motor Address. On Alice Studio, go to CFG > Settings > Motor and click Scan with the hex address field.
- Verify the dongle is plugged in:
ls /dev/ttyACM* - Run the udev rule installer:
cd src/desktop && ./alice-setup install, then re-plug the dongle - Check
./alice-setup statusto confirm the rule is active - If not using the udev rule:
sudo usermod -aG dialout $USER, then reboot
This usually indicates a calibration issue. Recalibrate with more points across your focus range. Verify you're measuring actual distances rather than estimating.
- Increase the confidence threshold in autofocus settings
- Reduce response speed for smoother transitions
- Add more calibration points in the distance range where hunting occurs
- Ensure adequate lighting (RealSense performs best in well-lit scenes)
- Avoid reflective or transparent surfaces
- Clean the depth camera lens
- Move closer if at the edge of the sensor's range (> 6m for D435, > 4m for D415)
The depth colormap only renders in CFG mode or when sync streaming is active. Switch to CFG > Calibration to see the depth preview.
- Verify the device appears in
ls /dev/video*(Linux) or Device Manager (Windows) - Some capture cards need a specific V4L2 driver. Check
dmesg | tailafter plugging in. - Try a different USB port. Some hubs don't enumerate UVC devices correctly.
- Verify the RealSense is connected (the face detector runs on the RealSense color feed, not the capture card)
- Check the log for
Face detector loaded: yolov11s-face.onnx (EP=...). If it says "face tracking disabled", no YOLO model was found inmodels/ - Ensure faces are at least ~4% of the frame height (roughly 20 px on a 480p feed)
Two similarly-sized faces at the same distance can compete for the primary slot. Alice applies a 15% score hysteresis, but extreme ties may still flicker. Tap one face to pin it as the primary target.
The sync server failed to start. Check the Alice Studio log panel for errors. Common causes:
- Port 8765 is already in use by another application
- Firewall blocking WebSocket connections
- Both devices must be on the same LAN (same WiFi network, or wired to the same router)
- Check that the desktop's firewall allows inbound TCP on port 8765
- Try disabling VPN if one is active
- On 2.4 GHz WiFi, lower the camera quality slider or reduce Max FPS to 15
- Switch to 5 GHz WiFi or a wired connection for best results
- The camera stream defaults to quality 92 at native 1080p. Drop to 80 to halve bandwidth.
Alice Studio converts all capture-card frames to sRGB before encoding, and the Android decoder is locked to sRGB. If you still see a tint difference, it may be your phone's display color profile (e.g., "Vivid" mode on Samsung). Switch to the sRGB or Natural display preset in your phone's settings.
- On Linux, install the
-develpackages listed in BUILD.md - On Windows, set
-DCMAKE_PREFIX_PATHto your Qt 6 installation directory
- On Fedora:
sudo dnf install librealsense-devel - On Ubuntu: follow the Intel librealsense installation guide
- Verify JDK 11+ is configured in Android Studio
- Ensure Android SDK API 35 is installed
- Open
src/android/as the project root (not the repository root)
- Press the Reset button to enter bootloader mode (LED should pulse)
- Try a different USB port
- On Windows, install J-Link software with "Legacy USB Driver" selected
- Disconnect all USB devices
- Force-stop and restart Alice
- Connect devices one at a time, granting permissions for each
- Try a powered USB hub if using an unpowered one
Check the terminal for the stack trace. The most common cause is a use-after-unmap in the frame processing pipeline — if you see this after upgrading, rebuild from a clean build/ directory.