Troubleshooting Runtime Setup

Symptom: setup reports "unsupported device"

Likely cause: your device's primary CPU architecture isn't arm64-v8a — this includes most Android emulators, which typically run x86_64.
What to try: Deputy Shell currently requires a 64-bit ARM Android device; see Requirements. This isn't something a retry will fix.
Data preserved: nothing was written yet — no impact on any other app data.

Symptom: setup is stuck or very slow

Likely cause: a slow or unstable network connection, or insufficient free storage for the runtime (roughly 500 MB download, more once extracted).
What to try: check your connection, confirm you have enough free storage, and retry setup using the in-app retry option.
Data preserved: any projects or sessions from before are unaffected; setup itself hasn't finished so there's nothing to lose there.

Symptom: setup fails with an error

What to try: use the in-app "Retry" option first. If it keeps failing, restart the app and try again.
When to export diagnostics: if retries consistently fail, create a diagnostics export before contacting support — it captures setup-relevant metadata without your personal content.
When to contact support: if the same failure persists after a retry and a fresh app restart, reach support@deputyshell.com with your device model, Android version, and (if you made one) your diagnostics export.