| Reported pattern | What users say |
|---|---|
| When it crashes | At startup, after the import finishes — several reports mention audio already playing, then a crash |
| Chips mentioned | Snapdragon 8 Gen 2 and 8 Gen 3 broadly; Adreno 740 and Adreno 750 named specifically; Galaxy S24 Ultra (#123), Xiaomi 13 Ultra-style devices (#146), Meizu 20/21 and others |
| Graphics-level detail | One report (#141) cites VK_ERROR_DEVICE_LOST with a kernel page fault — the port is looking at Vulkan driver behavior on these GPUs |
| What works today | Older Adreno generations do run: the project's own numbers come from a Snapdragon 8+ Gen 1 phone (median 60 fps) |
What we recommend if you own one of these phones: wait for a project update before investing a setup evening — check the project's Releases page for a fix, and if you do install, go in knowing a launch crash is likely. If you can test and report, the project explicitly asks for your device details in the issue tracker; every report shortens the fix.
A user-raised limitation (#140): Android saves sit in the app's internal storage, so backing them up, migrating phones or copying saves out is not straightforward today. The iOS ecosystem has iCloud sync (paid signing); Android has no equivalent documented. Until the port adds one, treat your save as device-bound — plan long farming projects accordingly.
iOS builds also produce the occasional abnormal exit — these are reports, not patterns:
What to do: note your app version and the moment it happens, export the Share Diagnostics file from the pause menu, and file it in the project's tracker — that diagnostic export is literally what the maintainers ask for.
If the app is not crashing but refusing to start, the cause is almost always version or file related. The full decode lives on the install guide; the short version:
| Symptom | First thing to check |
|---|---|
| "One More Step for This Device" | You are on A16-or-earlier hardware without the Legacy Device Pack — rebuild the package with it (devices guide) |
| "This Package Is Not Ready" | You installed the shell itself, not your packaged build — redo step 1 |
| Shell/source version mismatch error | Repackage with the new shell and matching source (update guide) |
| App can't find game resources | The resource folder is incomplete — the import screen lists what is missing (game files guide) |
Not publicly as of 2026-10-26 — the reports are open and the port is investigating Vulkan driver behavior on those GPUs. Watch the Releases page; we update this page when the project ships a fix.
Yes — controllers work on both platforms; on Apple devices the UI switches to the controller layout, and Xbox / PlayStation pads get their own button icons. See the controls guide.
Nowhere public on purpose: the project is built around your own purchased Switch copy. The game files guide explains exactly which files you need and how to extract them from your own console. Neither we nor the project provide downloads.
Issue references (#90, #123, #134, #140, #141, #142, #150, #146) and status as of 2026-10-26 from the d2r-mobile public issue tracker; feature facts from the v2.0.0 release notes. Where the project has no confirmed cause, we say so — no invented fixes.