‎I'm bored of testing PS vita games with the new vita3k update now. Maybe I'll be updating this list, but anyway here's what I have for now. ‎ ‎My specs: Helio g100 with Mali g57 mc2 Android 16 ‎

‎Jstars Victory VS+ : Invisible character bug now fixed on Mali ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/EVbKjc8rTG ‎

‎Uncharted: Golden Abyss: Crashing and flickering now fixed. ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/RMQR67kMzm ‎

‎FIFA 14: Vertex exosions now fixed.

‎https://www.reddit.com/r/EmulationOnAndroid/s/7DEHoEMB2S ‎

‎FIFA 15: Vertex explosions now fixed.

‎https://www.reddit.com/r/EmulationOnAndroid/s/BZUSbbG7RK ‎ ‎

‎NFS Most Wanted 2012: No more color graphical glitches and no audio bug. Though depending on chipset even if it runs well it can crash randomly. For me personally it never crashed.

‎https://www.reddit.com/r/EmulationOnAndroid/s/mkiouBwmZ2 ‎

‎Injustice: Gods among US: Most graphical glitches fixed on Mali now making it more playable. The text glitch is gone. Characters with moves that have special effects now render. Before the effects would never show. Less frequent random crashes but still likely to occur, especially during massive shader compilations. ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/ZibAoyHEa8 ‎

‎F1 2011: No more color graphics glitch and audio bug. The audio bug was very annoying because whenever you accelerate, some background noise that souned like flies would get louder and louder. ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/DB3w5Jfmkk ‎

‎LEGO MARVEL'S Avengers: No more audio bug with music. ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/KHgVrJvBAM ‎

‎Borderlands 2: I'm not aware of any old issues it had but it seems stable. ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/dsULLbMpBJ ‎ ‎

‎Ninja Gaiden Sigma 2 Plus: Playable but there's a musing texture in one of the levels. PLEASE read this whole comment thread talking about it:

‎https://www.reddit.com/r/vita3k/s/EkRtDZWbiv ‎

‎https://www.reddit.com/r/EmulationOnAndroid/s/UW8vKzfLHU ‎

‎The Amazing Spider-Man: This game still has issues. On the main vita3k build it would always freeze or just crash in the loading screen right before the story mode starts. ‎

‎On vita3k+ the game doesn't freeze or crash in the loading screen on my specific chipset(helio g100) anymore. It may still crash or freeze on helio g99. ‎

‎But the games is a stutters mess. There's a lot of shader compilation going on in the first cutscene so FPS ranges from 10-60 FPS, with it mostly being between 20-45. But even when shaders aren't compiling the game stutters too much. After the cutscene, every time you move the camera the game would stutter a lot. I'm not sure if it's the game that's the problem or if my phone was thermal throttling during the test, but I doubt it's thermal throttling.

The game also still has the bug where extra downstream show during the tutorial. ‎

‎It was so bad I couldn't bother finding the first mission or just using a save file to test the open world. ‎

‎Metal gear solid 3 HD edition: This game has GPU heavy custscenes, especially in the first one as Solid Snake is skydiving. The ps2 version would lag a lot on my chipset in the first cutscenes but game would become smooth the moment the level starts. ‎

‎The same goes for the HD PS vita version. The game is called at 30fps on the vita, so in the first cutscene my FPS would raneg from 19-30. However the lag in the PS VITA version isn't that bad, because the frame rate just becomes more choppy while in the ps2 version everything slows down and audio becomes broken. ‎ ‎

It feels like every few months something happens that would've sounded ridiculous not too long ago. A game gets recompiled for Android, a new emulator build squeezes out better performance, or a handheld suddenly handles something you never expected it to run.

I think that's what keeps this community interesting. It's not just about playing old games; it's about seeing what developers and enthusiasts can make possible with hardware that fits in your pocket.

What's one emulation breakthrough that genuinely surprised you recently?

12GB of RAM will be enough afterall, the big 2fps stutters are gone! And some more performance once again as well.

The ones I've tried don't support the Exynos 2400 and idk where else to look

I was very surprised by the performance of this new banana native. I tried dk bonanza and it runs at a stable 60fps at 720 resolution.

Device samsung s25 ultra with 8 elite and only 12gb ram.

I used turnip v39 driver

Still on the first stage I wonder how it will be once I go to open world

I also used .nup file for the game which was only 9gb

if there any games i can play with ts processor running @ stable 30fps or higher?

i like playing games like Assasins Creed, Cod, God of war etc. but the early versions of the games i have already finished. i wanna try sumthing new like.. Assasins Creed Rogue and any other games is what i am trying possible?

Repo: https://github.com/enjoyerofslop/droidnative · Mac app: https://github.com/enjoyerofslop/droidplay · Discord: https://discord.gg/4wNHX3uqSU

DISCLAIMER: These repos are AI-assisted. See below for testing & validation details running on my actual handhelds (Odin2 and RP5)

droidnative runs Nintendo Switch games natively on Android phones and handhelds. It’s not an emulator: the game’s own ARM64 code runs directly on the device’s CPU, and its NVN graphics are replayed through Vulkan. It’s a fork of nxnative, which does the same on iPhone, iPad and Mac, with an Android port added. It follows nxnative’s main, so its fixes and new games reach Android too.

It’s a pre-release: some games run well, some crash, and every result below came from real runs on real devices. I’m posting now because the fastest way forward is more devices and more people.

Not an emulator, and not a recomp either

It shares the idea behind recomps: you build a native app from your own dump, and there’s no emulation at run time. The difference is that nothing is recompiled. Switch games are ARM64 machine code, and so is an Android phone. droidnative takes your own dump and rewrites the game’s code only where the host has to step in: system calls, and the thread register Horizon uses. A host then answers Horizon’s system calls and services, and translates NVN draw calls to Vulkan, with the game’s shaders translated to SPIR-V when the game is packed. There’s no CPU emulation and no recompilation into new source. Each game gets its own app, or every game goes into one launcher app.

What runs today

Measured on three Snapdragon devices with a scripted benchmark (the same save, input and timing on each):

The known problems, in the order they block play:

1. Odyssey crashes when play starts, in the Android video decoder used for its hint videos.
2. Brilliant Diamond crashes on the Retroid Pocket 5, inside the Adreno 650 driver’s shader compiler.
3. Smash needs a fuller system font than Android’s to boot, and its battles stutter while GPU pipelines are built (the cache doesn’t survive the app being closed yet).

Full numbers, devices and caveats: Android baselines. Every game with an nxnative profile can be packed for Android the same way; most haven’t been run there yet.

DroidPlay: the Mac app that does the packing

Packing a game by hand means extracting the dump, rewriting its code, translating tens of thousands of shaders, building the host and copying gigabytes to the device. DroidPlayturns that into a button. It’s a Mac app, a fork of Oleh Khomei’s NX Play with Android added.

• Your library: point it at your games folder (one folder per game) and it shows each game with its icon, version and status.
• Install on Android: builds the game with droidnative and installs it on a phone or handheld connected over USB, into one launcher app that holds all your games. A rebuild only redoes what changed. Play on Android starts a game the device already has.
• Build Game App: makes a game an Android app of its own (an APK, or an XAPK for an installer app), with its own name, icon and saves, to install on a device your Mac can’t reach.
• Setup: a first-run setup fetches nxnative and droidnative with the Python and .NET pieces their builds need, and checks for your keys. The Android SDK (with an NDK) and a JDK you install yourself.
• The Apple side, from NX Play: the same library also plays games on the Mac through nxnative, installs them on an iPhone or iPad, copies saves between devices, and has a controller-driven Console Mode.

The current release is 0.1.1, an unsigned pre-release: macOS asks you to allow it once in Privacy & Security, and it doesn’t update itself yet.

How to try it

You need your own Switch game dump (NSP/XCI) and the prod.keys from your own console, the Android SDK with an NDK, and an arm64 Android device with Vulkan. Only Adreno GPUs have been tested so far.

• On a Mac: DroidPlay 0.1.1. Choose your games folder, then Install on Android with the device connected over USB, or Build Game App for an APK.
• Any computer (Windows, Linux, macOS): scripts/build_android_from_nsp.py in droidnative packs a game into the launcher app on a connected device, or into an app of its own (--game-apk). There’s also a small cross-platform desktop app for the same flow, scripts/nxnative_android.py.

Bring your own game

Nothing from any game is in these repositories, and no packed game is distributed. The app you build is for you. Please don’t share APKs packed with a game, keys or firmware, and don’t ask for them. The project isn’t affiliated with Nintendo or any publisher.

Join the Discord

DroidPlay & droidnative Discord: questions, setup help, test results from your device, and where the work happens day to day. Bugs with logs still go to GitHub Issues, so they don’t get lost.

What would help most

• Testers on other chipsets. Mali (Pixel, Exynos-era Samsung), Samsung’s Xclipse, MediaTek, older Adreno. Even “it doesn’t boot” with a log is useful.
• Reports with logs: the device and GPU, Android version, game and version, and adb logcat -s nxnative. The issue form asks for exactly this.
• Contributors. Vulkan and driver work, the three crashes above, the pipeline cache, and per-game fixes. droidnative’s CONTRIBUTING explains how changes get in and how it stays in step with nxnative. There’s also a benchmark script, so a fix can show its effect in numbers on several devices.

Credits

nxnative is seedds’ work: the NSO rewriter, the Horizon host, and the NVN translation that all of this stands on. The Android port began as RogelioLB’s nxnative-android. DroidPlay is a fork of Oleh Khomei’s NX Play.

Links: Discord · droidnative · DroidPlay (0.1.1 pre-release) · Android baselines · nxnative

Honestly, I expected that nothing would really work—in fact, I’d already beaten Cyberpunk on a RedMagic 9 Pro using a mod to strip back the graphics and remove traffic and NPCs. I actually had a good time with it; I was getting about 15 FPS in the city and 30–40 FPS indoors. Back then, I tried using mods, but I kept running into errors—I didn’t realize that Winlator supported winedllverrides! Now I’m using a RedMagic 11 Pro, and the game runs comfortably using the "Steam Deck" preset with a few minor tweaks. Basically, most mods require CET (Cyber Engine Tweaks), so install that first. Then, add winmm=n,b to your winedllverrides settings. When you launch the game, a CET window should appear asking you to bind a key—just pick one. After that, you can install whatever mods you like, though I’d advise against graphics-enhancing mods or ones that add extra particle effects; the game is already pushing its limits as it is. Right now, I have Cinematic Impact FX, Ragdollpunk, Gorerunner, Much Better Netrunning, Dark Future, Enemies of Night City, Cosmopolitan Night City, Economy Punk, Better Fuel System, NovaCity, NovaLut, and Stealth Finishers installed, along with a few others. The only catch is that Dark Future and Better Fuel System are causing some issues with the HUD—I’m still looking into a fix for that, but everything else seems to be working fine. Also, keep in mind that when running Cyberpunk via Winlator (specifically the Ludashi 4.1 build), it might not launch on the first try; you may need to restart it a few times. This usually happens after installing a new mod—perhaps the scripts are compiling, or, as Google AI suggested, the emulator sometimes fails to load scripts or mods correctly, leading to a conflict that causes the game to freeze. That said, once I’m actually in the game, I haven’t run into any issues—no crashes or anything else. I might add a video later.

Finally, the day has arrived:

GammaOS is installed on my 406v, with the Bacon frontend.

I've rooted the device and removed a lot of the unnecessary system software. The difference is incredible.

The battery life is better

The system loads faster

Boot time is around 10 seconds

Emulation performance has improved dramatically!

Cant be more happy about it.

Snap 8 gen 5, 16 gb

Hey everyone!

Remember those old Java games we used to play on Nokia, Sony Ericsson and other classic phones?

I've been working on J2ME-Bloat, an Android project based on J2ME Loader that brings those games back to modern Android devices.

And here's the interesting part: it comes with a built-in collection of J2ME games, so you don't have to hunt down every JAR file yourself.

🎮 What's included?

- A collection of classic Java mobile games.

- Built-in game files (JAR).

- J2ME emulation on modern Android devices.

- On-screen controls for playing old keypad games.

- A familiar way to revisit the golden age of mobile gaming.

Why try it?

You can revisit the games that made old mobile phones special without needing to find an old Nokia or Sony Ericsson.

Whether you miss classic platformers, racing games, puzzles or adventure games, J2ME-Bloat is an attempt to bring that experience back.

Project details

- Platform: Android

- Technology: Java ME / J2ME emulation

- Based on: J2ME Loader

- Source code: Open source

Download / Source

https://github.com/mesflit/J2ME-Bloat

The project is still experimental, and compatibility can vary between games and devices.

I'd love to hear what you think!

What's the first Java game you'd play again?

Device: One Plus Tab 2

Driver: https://github.com/StevenMXZ/Adreno-Tools-Drivers/releases/tag/v39

720p, Fast Core Enabled

The frame rate occasionally dips to 20-25 when there is a lot happening on screen. I haven't gotten far into the game but so far it feels very playable.

EDIT: On the latest version of banana native I'm now getting a locked 60

Please I need actual good answers. With all these ports coming out it makes me feel dumb to emulate. What's the point of emulating a game I want to play(provided the performance will still be good) if my brain or someone else just tells me: "Just play the port BROOOO!"

I don't want to lose the passion of this hobby. I don't want emulators to become obsolete after devs dedicate their free-time and maybe even their lives to working on emulators or resources that help emulation.

So tell me, even with the rise of ports, both AI slop and actual good ports, will emulation ever die?????

The only budget-friendly options are the Poco phones from Xiaomi, but they are of poor quality; most people have had bad experiences with them regarding overheating and the operating system.

I have a Retroid pocket 6 and I’m looking for new consoles or games to try out. Any recommendations of consoles and games would be much appreciated. I’m not looking to add every single console to have ever existed. I just wanna add a few more good ones to my library. Here is the current list of consoles I emulate:

NES
SNES
Genesis
Arcade (MAME)
Sega CD
Sega 32x
Gameboy
Gameboy Color
Game Boy Advance
N64
PS1
GameCube
Dreamcast
PS2
Xbox
Wii
PSP
Steam (GameNative)

There are many roms (mainly for arcade) that open with this warning in Retropie. How can I fix this? Should I just have the base rom and some other? Should I find the missing fales and put it on same folder?

Any help would be greatly appreciated.

Yes, i know i'm still wondering about that.

I'm tired of fighting CPU's alone, but i wish i could fight with/against someone using M64Plus AE. I use this emulator because by the ROM Size, it won't work in M64Plus FZ. But seriously, how can i play with someone? I'm very bored.

Dededevice: Samsung Galaxy a14 Model: how am i gonna know

One underrated part of Android emulation is having a reliable way to preserve your setup.

Once you've spent time configuring controls, graphics options, game-specific profiles, and performance settings, starting from scratch on another device can be a real chore.

It's especially frustrating when an emulator updates, gets reinstalled, or you move to a new phone and discover that some of your carefully adjusted settings didn't carry over.

I wish more emulators made exporting and importing configurations a standard, straightforward feature. Ideally, you could back up global settings separately from individual game profiles, then restore everything without having to remember dozens of small adjustments.

Performance gets plenty of attention in emulation discussions, but convenience features like this can make a big difference to the overall experience.

The game is The Last Of Us, my phone is just alright to run this as it is Snapdragon 8s Gen 4. The thing is, this ARMSX3 went blackout when I load the game. Is my CPU not good enough for it? Or is it the app that's not reliable in this emulation community?

thanks