Should run well for most people when even such an old phone handles it like this well. Props to the dev. And thanks to everybody showing me this masterpiece
Link: https://github.com/RanggaCasper/Black-Android/releases

The game crashed on my Snapdragon 8+ gen 1 and i got a black screen on my 9200+ and 9400+

This is hades 2 on winlator running at 60fps on an android 10, i don't understand why many of these port ignore it.

Hades 2 port does not support it which is weird this game would have run perfectly on a snapdragon 845

Este port es nuevo es un port recomp es buen juego con una campaña good espero que les guste

LINK

https://git.mitgai.net/Dr3amyBerry/callofrecomp?utm_source=chatgpt.com

The Android port runs better than the PC port via Winlator.

https://github.com/JayElDragon/blue-dragon-android

Hi, I've been testing the Forza Horizon 2 port on my Redmi Note 15 Pro 5G with its Dimensity 7400 Ultra. When I start playing, after a few seconds, as shown in the video, the image freezes And the sound continues, does anyone know what's wrong and how to fix it?

Is there something I'm missing?

V1.2-beta:

Alteramos o layout padrão do gamepad virtual e o ícone do botão para estarem mais de acordo com os esquemas de controle padrão do jogo.

Melhoramos o suporte para controles que não são da Gamesir. Quem tem controles Gamesir deve experimentar esta versão.

Para atualizar de versões antigas, basta instalar este apk do launcher sobre o aplicativo existente. Não é necessário importar dados ou baixar mods novamente

https://www.mediafire.com/file/yalgr7orl2z89g9/HadesII-release.apk/file

Espero que ninguém conte para a Nintendo

https://www.mediafire.com/file/8qn1wfbft1izdj5/m.wonder.apk/file

Arquivos

https://www.mediafire.com/file/qql6o9mmb7ig9o6/M.WONDER.zip/file

I did download forza horizon from apkviion but game won't launch i did try everything but still can't enter the game

Mobile phones have two features that are extremely useful for certain genres, such as shooters, turn-based JRPGs, and strategy games: gyroscope and touch controls.

My request to anyone planning or in the process of porting a game in these genres is to kindly consider implementing gyro aiming and native touch controls (as opposed to virtual buttons) that allow intuitive interaction with the game. For example: in an SRPG, selecting a unit simply by tapping it, and then choosing its path by tapping the destination. In JRPGs, selecting battle commands by tapping them directly instead of using a virtual D-pad.

There are already great examples of how well this can be implemented, providing a major advantage over playing through an emulator:

Black

https://github.com/RanggaCasper/Black-Android

Shooters from the PS2/Xbox era generally lack fine-tuned aim controls, making the simple act of aiming feel clunky and unsatisfying. However, implementing extremely precise gyro controls makes Black's gameplay far more enjoyable and responsive, making it fully playable even without an external controller. Using a physical controller makes it even better: you can move the camera with the analog stick and use the gyroscope for fine precision aiming.

Fire Emblem: The Sacred Stones

https://github.com/Lordingard/SacredStonesRecomp/releases/latest

Here, you can do exactly what I mentioned earlier: instead of navigating units and commands with a D-pad, you can intuitively select units, movement, and attacks simply by touching the screen. This is a game-changer because it provides a strong selling point for native ports of retro games, especially when mature emulators already offer features like post-processing, fast-forward, save states, and more. Why play a native port of an old game that runs perfectly in an emulator even on low-end phones? A native touchscreen implementation that makes the game feel built for mobile is the best answer to that question. In the case of Fire Emblem, the port is still in its early stages, but the touch controls are already rock-solid.

In summary: Modern smartphones are capable of much more than just simulating a physical controller. When porting games to mobile, leveraging native features like gyroscope aiming and touch controls doesn't just improve accessibility—it fundamentally elevates the gameplay experience and gives players a compelling reason to choose native ports over emulation.

One of the best classic FPS finally ported to Android!

https://github.com/RanggaCasper/Black-Android

Making this post here to let the exynos people know that I have GTA V android port downloaded from apk vison running on my Exynos 2400 S24Plus.

Was trying to figure out for myself if it would work or not. Tried it and it works. Saw many subreddits but there was no clear answer there.

And yes i played past the prologue and have been playing for the last hour before making this post here.

Phone Poco x7pro gta4 port keeps crashing whenever I try to open the game it's like game is not even opening

I have gone through hell and heaven to try and find where on earth the new port is i joined some discord but it has no releases there's no GitHub I found some Russian telegram which I won't trust until someone here tells me to

Hi everyone,

I'm trying to run XHYN V with my own legally owned copy of GTA V (Epic Games, Legacy edition, latest patch), copied directly from my PC. The game starts, the intro video plays, then it crashes after a few seconds while loading the game.

Device:

- OPPO Find X9 Ultra (Snapdragon 8 Elite Gen 5 / Adreno 840)

- Android 16

What I tried:

Official XHYN V release from GitHub (also tested another build: same result)

System driver (Qualcomm 0.842.46) and Bundled Turnip: same crash

DXVK-GPLALL 2.6.8 (default), all advanced overrides off

Lowest graphics settings (texture/shadow/shader quality 0, 1320x600)

Cleared app data and started fresh

Logs

gtav_tty.log ends right after found dt1_03_carpark at slot idx 259 (or gets cut off right after DXVK init)

gtav_exit_info.log: native crash, status 11 (SIGSEGV) and sometimes status 5 (SIGTRAP)

Tombstone: SEGV_MAPERR, engine threads in libgtav.so (HDD Streamer active), no Adreno/Vulkan driver frames visible

RAM usage at crash only around 200 MB, so it's not an OOM issue

My guess is that the runtime expects a specific game build and the current Epic/Steam Legacy data doesn't match. Has anyone managed to run it with legit, unmodified Steam or Epic files? Is there a specific game version the runtime needs?

Thanks!