This is the core library used by the UD fork of melonDS Android.
It builds into the app's APK. Users install the app once; they do not download
or install this library separately. Both fork repositories use main, and the
app fixes its core dependency to a specific Git commit.
The comparison is against official Android core 431ab4bd, still the upstream
master checked on 6 November 2026. Native corrections are at ac5e6ba0;
2bb701ff added the public overview. The app pins an exact core revision.
- Optional hostname answers for a frontend. UD adds a disabled-by-default hostname-to-IPv4 override table to the built-in DNS responder. It supplies endpoint addresses, not a replacement system DNS resolver. The Android firmware Wi-Fi editor does not use this API. Implementation · Packet tests and limits
- Shared fixes used by UD Nightly. NAND recovery, JIT ownership, instruction/data bounds and work budgets below compile into the Android app. Existing DS/DSi emulation, renderers and high-resolution 3D are upstream work. No separate core APK is needed.
The B7 save-page correction adapts Arisotura's merged cartridge refactor #2595. The JIT teardown research retains credit to maximxlss and RSDuck from #2537. Other existing authorship, licenses and credits remain intact. The app feature record retains the adapted Android UI contributors separately from shared-core work. Integration/provenance register
Each linked dossier states the caller, original failure, correction, exact source/tests and limits. High/Medium reproduce the linked security record's rating. Other impact labels describe a functional failure without assigning a security score. Component tests do not establish full-game or driver acceptance.
| Correction | Impact | Evidence and remaining limits |
|---|---|---|
| Stage NAND replacements, retain the previous generation and recover after failed renames before retry. | Save loss risk | One-shot fault sweep: host sanitizers and Android ARM64 4/16 KiB RED/GREEN. Persistent hardware faults, power loss, ART/SAF and DSi HOME remain outside that result. |
| Reset fast-memory mappings before ARM9 teardown; keep DTCM aliases within configured windows. | Expired memory, wrong mapping | Teardown/mapping controls. Host and Android component results are distinct from physical gameplay. |
| Fold Thumb literals only when writes can invalidate the generated block, on AArch64 and x86-64. | Stale generated code | AArch64 reproduction · Linux x86-64 RED/GREEN. Linux checks do not establish Android x86-64 runtime acceptance. |
| Check ROM headers, cartridge transfers, NAND save pages and GBA flash accesses before reading/writing native buffers. | High: native memory bounds | Cartridge image · NAND page RED/GREEN · GBA flash. Per-case proof levels differ. |
| Validate savestate sections, scheduler parameters, FIFO positions, graphics/audio dimensions and peripheral state before use. | High/Medium: native memory bounds or nontermination | Section parsing · Callbacks/indices · Scheduler follow-up. Paired-app load rollback is separate; arbitrary old savestates are not certified. |
| Bound DS/DSi Wi-Fi frame conversion and restored multiplayer lengths to the destination capacity. | Native buffer bounds | DS host/Android RED/GREEN · DSi host/Android RED/GREEN. Real multiplayer/server interoperability remains separate. |
| Reject truncated Action Replay instructions; share a frame work budget and resume deferred cheats. | Out-of-bounds read; Medium: emulation hang | Instruction-length RED/GREEN · Work-budget case. This does not prove every cheat correct or every workload fast. |
| Validate firmware ranges, DSP descriptors/commands and G.711 transfers before dispatch. | High: native buffer access; Medium: stalled or invalid DSP execution | Firmware · DSP descriptors · G.711 follow-up. Source review and focused suites are not individual runtime reproductions of every card. |
| Bound DNS parsing, release resolver allocations and restrict guest access to private/loopback endpoints. | Medium: native read, leak or access to host services | DNS parsing · Network policy. Private-network services and the changed LAN representation need compatibility review. |
| Apply DS/DSi SCFG access rules and Wi-Fi automatic power-down only in the requested mode. | Incorrect emulated hardware behavior | Source changes, provenance and test scope. No general C-Gear, DSi HOME or all-game closure follows. |
| Skip unchanged Compute renderer configuration, unused edge-data work and a false cache-rejection log. | Redundant work, misleading diagnostic | Source-level comparison. No measured FPS, CPU, GPU or battery improvement is claimed. |
The complete per-occurrence register covers both repositories: 97 code-corrected occurrences, two repository corrections with external controls unverified, one Android-not-applicable case and one informational reconciliation. The 101 occurrences are not 101 independent bugs, and the app's release controls are not core runtime fixes.
These retained changes were already consolidated in core
fd7582400bb7e35fe0d36dbb0c89b6766c1a8f2e; later native corrections remain
identified by their own dossiers above. This is a source-level comparison with
official Android core 431ab4bd, not new runtime or performance acceptance.
| Boundary | Retained correction | Evidence and limits |
|---|---|---|
| DS/DSi registers | Apply initialization and SCFG access rules consistently with cartridge/console mode | Source correction and historical builds/suites; no all-game DSi or HOME/C-Gear claim |
| Wi-Fi power saving | Disable automatic transceiver shutdown when automatic power saving is disabled | Core control flow; no measured battery gain or complete multiplayer qualification |
| DTCM mappings | Keep RAM/DTCM aliases within the configured windows; preserve offsets, remapping symmetry and invalidation | Historical synthetic sentinel/window/mirror/base-change controls include 4/8/16/32 KiB windows and Android ARM64 4/16 KiB pages; current ownership dossier distinguishes host from Android evidence |
| Compute renderer | Skip rebuilding unchanged renderer configuration | Source-level removal of redundant work; no measured FPS/CPU/GPU/energy improvement |
| OpenGL renderer and diagnostics | Avoid generating/uploading unused edge indices or compiling the inactive edge-pass shader; report compilation accurately instead of a false cache rejection | Source-level correction; no new renderer, upscaler, OpenCL backend or accelerated-quality claim |
| Optional DNS overrides | Keep the frontend hostname-to-IPv4 table empty by default; normalize case/trailing dot and answer supported A queries | Production packet regression source and parsing/security limits; the Android firmware editor does not invoke this API |
No core 1.1, DS/DSi emulation, OpenGL/Compute renderer or resolution-scaling implementation is newly attributed to this fork. Preserved upstream authorship and the named human credits above apply independently of these descriptions.
The validation report separates host sanitizer tests, Android native execution on ARM64 4 KiB/16 KiB page sizes, app tests and real-app checks. Each finding states its proof level; a passing suite does not certify every game. DSi HOME/quota, physical-device driver behavior and the compatibility of changed network rules remain limited or pending. No measured CPU, GPU, battery or all-game improvement is claimed.
The app downloads carry their own package, signing and build identities. A fork-signed APK cannot replace the official author's signed APK in place. Source changes can be reviewed and built by the author with the official signing identity. ROMs, BIOS, firmware, NAND and saves are not distributed with the application.
Use the app repository's build instructions for the Android APK and initialize submodules recursively. A plain source ZIP does not include submodule contents. For the core itself, see BUILD.md and CONTRIBUTING.md. Original authorship, credits and licenses are preserved below.
DS emulator, sortaThe goal is to do things right and fast, akin to blargSNES (but hopefully better). But also to, you know, have a fun challenge :)
Firmware boot (not direct boot) requires a BIOS/firmware dump from an original DS or DS Lite. DS firmwares dumped from a DSi or 3DS aren't bootable and only contain configuration data, thus they are only suitable when booting games directly.
- 128KB: DSi/3DS DS-mode firmware (reduced size due to lacking bootcode)
- 256KB: regular DS firmware
- 512KB: iQue DS firmware
DS BIOS dumps from a DSi or 3DS can be used with no compatibility issues. DSi BIOS dumps (in DSi mode) are not compatible. Or maybe they are. I don't know.
As for the rest, the interface should be pretty straightforward. If you have a question, don't hesitate to ask, though!
See BUILD.md for build instructions.
- better DSi emulation
- better OpenGL rendering
- netplay
- the impossible quest of pixel-perfect 3D graphics
- support for rendering screens to separate windows
- emulating some fancy addons
- other non-core shit (debugger, graphics viewers, etc)
- big-endian compatibility (Wii, etc)
- LCD refresh time (used by some games for blending effects)
- any feature you can eventually ask for that isn't outright stupid
- Martin for GBAtek, a good piece of documentation
- Cydrak for the extra 3D GPU research
- limittox for the icon
- All of you comrades who have been testing melonDS, reporting issues, suggesting shit, etc
melonDS is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
- Images used in the Input Config Dialog - see
src/frontend/qt_sdl/InputConfig/resources/LICENSE.md
