Runtime Logs
DroidVM provides a Runtime Logs screen for viewing the live output of the daemon, making it easier to troubleshoot issues such as VM startup failures and network anomalies.
📷 Screenshot placeholder: Runtime Logs screen
Description
- Displays the daemon's logcat output in real time (filtered by its PID)
- Keeps up to 10000 lines
- Automatically follows the latest logs when scrolled to the bottom; scrolling up pauses following so you can review earlier logs
- Pauses capture when sent to the background (onPause) and resumes when brought to the foreground (onResume)
Top Bar Menu
| Action | Description |
|---|---|
| Save to File | Export as droidvm_logs_<time>.txt |
| Share | Send the logs via the system share sheet |
| Scroll to Bottom | Jump to the latest logs |
| Clear and Restart Capture | Clear the current content and start capturing again |
Difference from Console Logs
- Runtime Logs (this page): logs from the DroidVM daemon itself, reflecting the state of the app backend, VM management, networking, etc.
- Terminal Console logs: logs output by the operating system inside the VM over the serial port (kernel / init / applications)
When troubleshooting:
- VM won't start / crashes on launch → check the Runtime Logs first
- VM starts but the system misbehaves → check the Terminal Console
Reporting Issues
When filing an issue, attaching the relevant runtime logs greatly improves troubleshooting efficiency. You can use "Save to File" to export them and attach them to GitHub Issues.