The FullRoid Evolution: Cores, Save States, And Android Modernization

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.

FullRoid emulator history is one of the longer-running stories in the Fulldive ecosystem. The FullRoid repository (fulldiveVR/FulldiveExtension.FullRoid, published as One Emulator for Game Consoles and its Pro counterpart) has 1,778 commits across all refs, spanning 2017-09-04 to 2026-04-10. This post walks through that Android emulator app evolution with direct commit references, so you can see what has actually changed versus what gets claimed in marketing copy.

2017-2021: the emulator base

FullRoid is not a greenfield Fulldive emulator. The repository history starts in 2017, before any Fulldive-specific release work, on an existing emulator codebase. That matters because a lot of early emulator behavior — library scanning, core loading, input handling — was inherited and then adapted. The first several years are iterative work on the base, not headline features.

2022: Fulldive extension releases

The Fulldive-specific release path shows up in 2022.

Commit 2f6608e1: updated core app, target SDK, and version 1.0.4. That’s the first “branded” Fulldive extension release we can point to for the emulator.
Commit 74852fd8: Discord community promo added and version bumped to 1.0.6. Discord would keep appearing across Fulldive apps for years as the standard support channel.
Multiple late-2022 commits bumped cores — the baseline maintenance rhythm that would continue through the whole history.

This pattern — take a mature emulator codebase, integrate it into the Fulldive extension family, ship through a standard release pipeline — is the same one we applied to other apps like Wize AdBlock VPN and Full Cleaner. The “extensions” story is covered in What are Fulldive extensions?.

2023: game library UX and target SDK work

2023 is when the app’s UI started pulling onto Jetpack Compose.

Commit 38ddf7fa: moved the search, systems, and games screens to Compose. This is a real migration, not a cosmetic restyle — it changed how the library screen handles state, scrolling, and configuration changes.
Commit 4d836cb4: animated game list changes, tightening the feel on bigger screens and Android TV.
Target SDK updates in August 2023, keeping the app in line with Google Play requirements.

2024: saves, cores, and delivery fixes

2024 was less glamorous work on the parts of the app users notice when they break.

Commit 2372e240: Compose game menu, which made per-title settings easier to find during play.
Commit 28a1f115: imported previous melonDS saves, so users moving forward on that core didn’t lose progress.
Commit 52e9487d: save sync crash fix. Save code is the single riskiest surface in an emulator because a crash there can erase progress.
Commit 3c3a0626: core download minification fix. Android app shrinking can quietly break download paths; this was a pragmatic fix for a production issue.

We go deeper on save-state behavior in Save states vs in-game saves on Android emulators.

2025: Game Activity modernization and controls

2025 was a focused modernization window.

Commit def0215f: began the Game Activity migration to Jetpack Compose, which affects how the running game screen handles input, lifecycle, and overlays.
Commit 47c9c8c3: migrated the gamepad layout to Compose. This is the foundation of the touchscreen overlay story told in Controllers for an Android emulator.
Commit 86d4d1b1: added quick save/load and fast-forward shortcuts, which made save states actually usable in the flow of play.
Commit acf79d78: target SDK bump, keeping the app publishable on Google Play. Target SDK bumps also trigger runtime permission and storage behavior changes that ripple through the codebase.

Late 2025: core migrations and Fulldroid branding

Late 2025 had a cluster of core and branding changes:

Commit be65800d: bumped emulator cores. Routine in appearance, not routine in effort — core bumps often need save format checks and control-mapping verification per system.
Commit f71aade4: deprecated desmume and lazily migrated saves to melonDS. Lazy migration is the respectful version of a core change — no up-front data migration prompt, but any existing save gets moved to the new core the next time it’s loaded.
Commit 8a356db8: Fulldroid branding and multilingual string updates. The Fulldroid naming appeared in some contexts alongside the store-listing “One Emulator for Game Consoles” / “Pro Emulator for Game Consoles” branding.
Commit 3f31c74f: version 1.8.3 ship.
Commit c8952402: Discord community link updated, continuing the shared Fulldive support path described in the Fulldive company story.

2026: 3DS, shader cache, games catalog

Into 2026, the work shifted toward newer systems and a games catalog integration.

Commit 640cdc59: Citra hardware shader cache. Shader caching massively improves first-run performance on 3DS titles.
Commit 1030d028: experimental Citra save-state support. Intentionally labeled experimental — save states on a newer core for a more complex system need rounds of tuning.
Commit e9ca6f9b: new 3DS core support. Details in Citra, melonDS, desmume: how Android emulator core updates work.
Commit 5e265141: version 1.9.5.
Commit 809ab678: free game catalog integration, pulling from the separate fulldiveVR/FullRoid.Games repository. That catalog is explained in FullRoid games catalog.

What the history says about emulator apps on Android

Three things stand out across 1,778 commits:

Maintenance is the product. Target SDK bumps, core updates, save migrations, Compose migrations, and delivery fixes are the bulk of the history. A long-lived Android emulator is a maintenance story.
Save state work is careful. The repository treats saves as precious — lazy migration, import paths, crash fixes. That’s not an accident; save-code bugs destroy user trust fastest.
Compatibility is earned per system. New 3DS core support, Citra shader cache, melonDS migration — each is a specific investment in one system, not a universal compatibility claim.

Legal and compatibility notes

FullRoid’s history is about the emulator app, not about the games people play on it. The app does not include copyrighted games, BIOS files, or ROM downloads; users are expected to provide legally obtained game files. Compatibility varies by game, file, device, Android version, controller, and emulator core version. We do not claim universal console or game compatibility.

Sources

Internal repository evidence brief: website/docs/app-evolution/one-emulator-fullroid.md.
Jetpack Compose and Game Activity documentation from Android Developers.
Android target API requirements.
Lemuroid for Android multi-console emulation reference.

Last updated: 2026-04-16. Commit hashes and version numbers are drawn from Fulldive repositories inspected on 2026-04-13.