Everyday use

Explore the guest terminal, care for your files, and end sessions cleanly.

Reviewed 2026-09-05

Start a session

Open Kalidroid and use your installed build’s control to start the Linux environment. Wait for startup to complete before opening multiple sessions. If startup stalls, note the last visible message rather than repeatedly restarting setup.

Explore the terminal

Run these commands inside the Linux guest terminal, not an Android shell:

pwd
ls
cat /etc/os-release
df -h

They show your working directory, files, distribution information, and filesystem space. A terminal provides direct control over the guest, so read commands before running them and keep your first experiments small.

Keep track of your files

Guest paths and Android shared-storage paths are different. Do not assume a file in the guest home directory is already backed up to Android’s Downloads folder.

Use the file-transfer or sharing method supported by your installed build. Verify the exported copy can be opened outside the app. Back up important work before updating, clearing app storage, changing the guest image, or uninstalling.

Desktop sessions

If your build provides a desktop option, start it after the environment is ready. A blank desktop view does not necessarily mean the guest has stopped; check whether the guest terminal still responds.

Use the display options exposed by your installed build. Device-specific rendering or memory problems belong in your troubleshooting notes rather than being treated as universal configuration defaults.

Services and networking

Review which services are running and which interfaces or ports they use before enabling network access. An Android address, a guest address, and a forwarded port are not interchangeable.

Start one service at a time, check its output, and consult that service’s documentation. Do not assume a guest port is automatically reachable from another device.

End a session cleanly

Save work in terminal and desktop applications, stop ongoing jobs, and use the app’s normal shutdown/stop control. Give it time to complete before closing the app or powering off.

After your first session, restart and verify that a test file is still present. Keep a separate backup of anything you cannot replace.