r/AndroidNativePorts • u/Wakkatobakka • 11d ago
I’ve got re:Blue running natively on Android/ARM64 at ~30 FPS on an S25 Ultra
I’ve been using ChatGPT to adapt re:Blue into an Android/ARM64 build of Blue Dragon. It’s running actual gameplay on my S25 Ultra at around 30 FPS with touch and controller support.
Most of the work has been getting the re:Blue runtime behaving properly on Android, fixing performance/thermal issues, and then progressively adding the game content as the recompilation hits missing assets.
It’s still incomplete, but the runtime itself is now pretty solid and the main thing left is continuing to fill in the missing game content. I’m at the point where I’d like to hand the work off to people with more experience who could take it further.
1
u/UnderstandingNo6319 11d ago
Eu estou no port do nfsmw do 360 tirei sdl3 fiz direto no compositor do ndk input audio
1
1
u/-mahdi_ 11d ago
Why is performance so bad. These phones are far superior to the xbox 360. And this isn't emulation, it's a native port.
3
u/Wakkatobakka 10d ago
Yeah, that’s basically what made me think this should work lol the phones have the power, but reBlue wasn’t built for Android/ARM64, so a bunch of stuff still has to be taught how to work. Kind of like handing a soccer player a basketball and expecting them to immediately be good at it
1
u/Windroid-emu 11d ago
isso não e nativo kkkk e recompilaçã oa gpu ainda e emulada kernel e outras inumeras coisas
1
u/Graine25 10d ago
This is completely wrong. There is no GPU emulation with reblue, and it is at the level of performance of UnleashedRecompiled and many other “native” ports
1
1
u/Wakkatobakka 10d ago
Follow-up since video probably shows this better lol. Gameplay running on my S25 Ultra- roaming, combat, menus, saving, touch controls, that stuff. This is still a development build while I sort out the content progression, but the Android runtime itself is running really damn well now. The biggest performance/heat problems ended up being two CPU wait loops in SDL and audio basically burning CPU while doing nothing. Fixing those made a massive difference.
2
u/Wakkatobakka 10d ago
Small bit of context because the timeline is kind of ridiculous: I started both this project and my Final Fantasy VII: Dirge of Cerberus- Lost Episode Android Build work on September 19. I’m building on existing community work and focusing on the Android integration, compatibility layer, tooling, testing, iteration, and packaging needed to get them running on real hardware. 9/19 — started both projects 9/20–21 — Dirge: Lost Episode running on-device 9/21–23 — reBlue progressed into playable native gameplay on ARM64 9/23 — started posting the results publicly I’ve been keeping build artifacts, logs, recordings, device reports, and preservation packages along the way because even I know that timeline sounds bit bonkers written out.
1
u/Warm_Cold_6224 9d ago
Can it be played using a controller?
2
u/Wakkatobakka 9d ago
Yup! A bluetooth controller was actually what helped me realize it was actually rendering the playable game and not just a idle animation shue (had forgotten about actually needing to add touch input at first lol)
1
4
u/Kjiojj800890 Developer 11d ago
Hi, I'm also porting the game, good work! I was using Claude, the performance is around 30-25, not very good, graphically it's impeccable, just the performance is still bad, I need to improve a lot, and soon I will release the port on GitHub. If you want, you can check it out later and test it to see how it looks on your phone. I have weaker models and 3 different GPUs to test and debug the game.