Troubleshooting

Practical checks for installation, first boot, storage, networking, and desktop problems.

Reviewed 2026-09-05

The APK will not install

• Verify the download’s SHA-256 on the downloads page.
• Confirm Android 8.0 or later and ARM64 support for the full app.
• Check available storage and the specific source’s permission to install APKs.
• Record Android’s exact error message. An update conflict may involve a different package identifier or signing key.

Do not uninstall an existing environment as your first troubleshooting step; removing app data can remove work you have not backed up.

Setup runs out of space

The compressed download size is not the final installed size. Free space for both downloaded and extracted files, and check Android’s storage screen again. Remove only files you recognize and no longer need. Keep the original environment until important work has been exported.

The environment does not start

Keep the app in the foreground, connect power if necessary, and record the last message. Check whether image setup completed. Restart the app once after any ongoing setup has safely stopped.

If a backend selector is present, record the selected backend. Bundled QEMU/crosvm components do not establish that every acceleration mode works on your firmware. Avoid applying privileged permission commands from older guides without checking their requirements.

Android closes the app

Check low-memory and battery-management messages. Device manufacturers handle background processes differently. Try a foreground session with other resource-heavy apps closed and review the app-specific battery settings provided by your device.

Do not use global ADB process-limit changes as a default fix. First determine whether the failure is a background restriction, memory pressure, or a guest error.

Networking is unavailable

Confirm Android itself has a working connection. Then inspect the guest network state:

ip address
ip route
cat /etc/resolv.conf

Distinguish DNS problems from missing routes or unavailable connectivity. VPNs and network changes can affect connectivity. Record what changed before the failure. Avoid sharing logs with private addresses or credentials without reviewing them.

The desktop is blank

Check whether the guest terminal still responds. If it does, inspect the desktop/display startup output and the options in your installed build. Save terminal work before restarting the whole environment.

A USB accessory is not visible

Check the cable, power requirements, Android USB host support, and any accessory permission prompt. Then confirm the device is supported by the guest workflow. An accessory working in Android is not proof of guest passthrough support.

Collect a useful problem report

Include the device model, Android build, app version, selected backend if available, exact error, and steps that reproduce it. Remove secrets and personal information. See support for guidance on where to go next.