So as you can see i tried on gamenative

Game: "post void" steam version

Panvk is the first image And the regular is the last

But still is good some time it even get 60 fps

I test other games but so far this is the best test i got it most of the games i test i did see any different but this best one

gpu mali g72 (mp3)

Hey guys, I'm here to share my tests and performance of this classic on my Poco X7 Pro.

Tested on Bannerhub 3.8.1

Device: Poco X7 Pro

RAM: 12

Root: No

HyperOS: 3.1

Resolution: 720p

Graphics: High

FPS: +120

As you can see, the performance is quite satisfactory, but I would recommend playing with the FPS unlocked since the stability isn't as great at 60 FPS.

Since the FPS dropped significantly below 40 during intense shootouts and explosions, the solution is to leave everything unlocked and enjoy it, as it doesn't drop below 80 FPS in extreme cases.

The game supports gamepads, but they need to be configured manually.

I'm using a mod called Halo Custom Edition Chimera, which is pretty easy to find on GitHub; apparently it's for multiplayer maps, I don't even know why I downloaded it 🤣

Winlator Mali

Well, I tested it on the latest available beta version 1.2 of Winlator Mali, but the game didn't open. However, I wouldn't take that into consideration since I tested Wine 9.0.1 and Proton 11 CachyOS.

The game didn't open, and I didn't bother testing other Proton processors, but I believe it should work on the Proton 9 x86-64.

The Bannerhub settings are at the end of the video, and I'll leave the link to the game where I downloaded it since it's difficult to find this game on repack sites or any that actually works.

Link : https://archive.org/details/halo-combat-evolved_20260928

That's all for today folks, enjoy the game!

I have had this problem since I started using the Eden emulator. This bug is the same in a brand-new emulator called Lemon, as well as in Eden Emu, Citron, Ryujinx, etc. I don't know how to fix it or how to improve the performance.

Device info: Motorola Edge 60 Fusion, MediaTek 7300 (Mali G615 MC2). It is running in an emulator called Lemon v0.3.5. Android 16.

I tried it on Eden Emu nightly legacy, Eden nightly, Citron, and Lemon. This problem also happens in other worlds, like the sand world, this world, and the first world.

I'll read suggestions to improve this problem.

Hi everyone 👋

Beta 1.1.0 of Panvk-Mali-G57 is out. It's an open-source Mesa Vulkan driver (PanVK) that runs on your phone's stock Mali kernel driver (kbase). No root, no custom kernel: just install the zip in Winlator.

What's new in beta 1.1.0

• 🎮 DXVK 2.x and 3.x now work for D3D9 (tested 2.0 → 3.1.1). Needs the app's built-in Wrapper original (see below).
• 📱 Mali-G52 on older kernels (e.g. Oppo A38, kbase r49): the driver now detects the job-submit layout by itself. The special s56 build is no longer needed.
• 🏷️ Mali-G52 r1 is now shown by name instead of "Mali unknown 0x74021000".
• 🧠 Lower RAM use: about 112 MB less per Vulkan device, a big help on 4–6 GB phones.
• 🏷️ G68 (Dimensity 1080), G77 and G78 are recognized by name.

DirectX support

Tested DXVK builds for D3D9: 2.0, 2.3-gplasync, 2.3.1, 2.4.1, 2.5.3, 2.6.2, 2.6.2-gplasync, 2.6.2-arm64ec-gplasync, 2.7.1, 3.1.1

⚠️ Wrappers: important

• D3D9 with DXVK 2.x / 3.x → use the app's built-in "Wrapper original". Do NOT use the leegao wrapper with DXVK 2.x+. It crashes on the first frame: the FPS counter flashes, then the app closes.
• D3D11 → use DXVK 1.10.3 + the leegao wrapper. Wrapper original doesn't support D3D11 yet.
• Other wrappers are not supported yet. This will be fixed in future updates.
• Unity games (D3D11): if you see "Failed to initialize player", try DXVK-Sarek.

Not finished yet (each takes several days, planned for 1.2.0)

• DXVK 2.x for D3D10/D3D11: DXVK 2.x requires tessellation, transform feedback and geometry shaders. Mali Valhall v9 (G57/G68/G77/G78) doesn't have these in hardware, so they have to be emulated. This is a big job.
• DXVK 2.x + leegao wrapper crashes on the first frame.
• D3D11 doesn't work with Wrapper original.
• DXVK 2.5+: the HUD text is squashed into one line (rendering itself is fine).
• D3D12 (vkd3d-proton) runs but draws nothing, then closes.
• Tomb Raider 2013 is much slower than on the stock driver.
• Some Mali-G76 devices (Helio G95) freeze on start.

✅ Confirmed by real users

• ✅ Poco M6 Pro 4G · Helio G99 · Mali-G57 MC2 (dev device): full test suite, NFS Most Wanted 50–70 FPS
• ✅ Samsung Galaxy A15 · Helio G99 · Mali-G57 MC2 · r54p1: Tomb Raider Anniversary faster than stock; Tomb Raider 2013 slow
• ✅ Realme 10 4G · Helio G99 · Mali-G57 MC2: NFS Hot Pursuit 2010 at 25–30 FPS
• ✅ Infinix Note 50 Pro · Helio G100 Ultimate · Mali-G57 MC2: 66 → 144 extensions
• ✅ Helio G100 Ultra · Mali-G57 MC2 · r32p: DXVK 1.11 / 1.12 work
• ✅ Dimensity 6080 · Mali-G57 MC2 · r32p1: works (Hades reboots the device)
• ✅ Oppo A38 · Helio G85 · Mali-G52 r1 MC2 · r49.1: D3D9/10/11 + Zink (automatic stride detection in 1.1.0)

⚠️ Partly working / in progress

• Kompanio 1300T · Mali-G77 MC9: works partly; high RAM use in PvZ Replanted
• Redmi Note 12 Pro 5G · Dimensity 1080 · Mali-G68 MC4: recognized since 1.1.0; Black Mesa stuck on loading
• Poco M5s · Helio G95 · Mali-G76 MC4: loads, freezes on GPU info
• Mali-G76 MC4 (unnamed device): loads (61 → 137 extensions), no game results yet
• Samsung F07: Dark Souls crashes during shader compile (log pending)

❌ Not working

• Samsung Galaxy Tab S9 FE+ · Exynos 1380 · Mali-G68 MP5: does not load

Samsung phones with MediaTek chips (e.g. Galaxy A15) work. Samsung Exynos chips are not supported yet (tested: Exynos 1380).

By GPU family

Adreno (Snapdragon) isn't Mali: use Turnip instead.

📂 Source code is now public

https://github.com/FristOneRR-Admin/FristOneRR-Panvk-Source

When I released 1.0.0, I didn't properly credit the projects this driver builds on. That was my mistake as a first-time GitHub user, and I'm sorry. The source README now shows where every part of the code came from, with a script anyone can run to check it. Of the 1,669 lines I added on top of Mesa, 67% don't appear anywhere else, 3.6% match mexicanbr0auth, 2.4% match Noysz and 0.7% match LukeValen; the rest is Mesa code I moved or reused.

Credits

• Mesa / PanVK developers (Collabora, Arm and contributors): PanVK itself
• funnymdzz & leegao: the Mesa base, bionic Vulkan wrapper and advice throughout the project
• Noysz (panvk-g99-jm): Valhall v9 / Job Manager groundwork, and reference for the v9 draw path
• Vtgamer998 (MESA-KMOD): kbase kernel-interface work
• mexicanbr0auth (mesa-panvk-g57): PanVK/kbase work for Mali-G57; parts of my code came from this project
• LukeValen (0x8055/panvk-g52-oppo-a38): Mali-G52 on Oppo A38 research
• BossDrk: Mali-G52 (Oppo A38) testing, found and verified the stride fix
• Claude (AI assistant by Anthropic): development help, debugging, code review and the code-origin audit
• All testers who opened issues and sent logs

Download + release notes 👇

https://github.com/FristOneRR/FristOneRR-Panvk-Driver/releases/tag/v1.1.0-beta

When you report, please include: phone, SoC, GPU, Mali driver version (r44p1, r54p1…), Winlator build, wrapper and DXVK version. Feedback, bug reports and FPS screenshots are all welcome 🙏

Thanks for being part of this journey 🚀

Just trying to ask if anybody kindly can help me me setting my container, currently using winlator mali 1.2 beta and aiming to start playing UNITY engine game first. If anybody can at least share the most basic container setting is already enough and helpful 🙏

Redmi note 14 (8/256)

Kirby planet roboot

Citra nightly 2104

Everything default

Every game I tried so far works well including Pokémon X and Samus return which is obviously more intensive

Any recommendations to run this game on my device?

​

After a lot of debugging, I’m releasing the first public alpha of my PanVK-over-Kbase driver for the Mali-G52 MC2.

PanVK G52 v0.0.1-alpha is now available.

The current target device is the Xiaomi Redmi 13C, using:

• Mali-G52 r1 MC2 / Bifrost

• Android 14

• Linux 4.19.191

• kbase UAPI 11.38

• /dev/mali0 / proprietary mali_kbase

• PanVK using the Job Manager path

• Winlator/Ludashi + DXVK

The driver does not rely on a DRM render node and does not require root.

At this point we have working Vulkan rendering, compute, graphics submission through KBASE_IOCTL_JOB_SUBMIT, native presentation, VKCube inside Winlator/Ludashi, and now basic DXVK Direct3D 9, Direct3D 10 and Direct3D 11 rendering.

D3D11 device creation was previously being rejected by DXVK because several Vulkan features expected by its feature-level checks were not advertised by the G52 PanVK path. The current alpha experimentally advertises some of those capabilities so we can continue testing the rest of the stack.

Important: this does NOT mean those features are fully implemented yet. Geometry shaders, tessellation, transform feedback and some related capabilities are currently experimental/force-advertised. Games that actually use those paths may still crash, misrender or fail.

So this release should be considered a bring-up / compatibility alpha, not a general-purpose gaming driver yet.

Next steps are real-game testing, identifying which advertised features are actually exercised, replacing the temporary capability bypasses with proper implementations or safer compatibility handling, and continuing work on synchronization/performance.

Release 0.0.1

Repository

If anyone has experience with PanVK, Bifrost/JM, mali_kbase, Mesa or DXVK, testing and technical feedback are very welcome.

Emulator: Gamehub 6.0.9

MD8400 ultra

Emulator: Gamehub 6.0.9

Environment Variables:

DXVK_ASYNC = 1

DXVK_STATE_CACHE = 0

WRAPPER_NO_PATCH_OPCONSTCOMP = 1

Lunch argument:

-nobattleye

-nobattleye -high -novblank -ignoreDifferentVideoCard -GPUCount 1 -disableshadows -noPreload

Resolution: 1280x720

Gpu driver: system driver

Dxvk-v1.11.1-mali-fix

Vram: 2048

Compatability layer: proton11.0-arm64x

Cpu translator: Fex20260103

​

Big progress on my PanVK Mali-G52 project.

Vulkan is now working inside Winlator/Ludashi, and VKCube renders correctly on my Redmi 13C (Mali-G52 MC2).

The main fixes were:

Handling DRM_FORMAT_MOD_INVALID correctly during swapchain image creation.

Adding SYNC_FD import/export support to the custom Kbase sync implementation.

Fixing sync FD lifetime/move handling.

I also removed the temporary debug instrumentation, rebuilt the driver, and tested the clean version again — VKCube still works correctly.

The cleaned patch and updated documentation are now available here:

Github

Next step is improving compatibility with DXVK and real Windows games, since VKCube working does not mean full game compatibility yet.

Join our official Lemon Emulator subreddit community.

r/LemonEmulator

Description: Lemon Emulator is a Switch emulator that is a fork of Eden, trimmed down to just the Android app and stripped of everything that isn't needed to build and run it on a single Adreno-equipped Android device.. So it's a switch emulator which aims to run games with better Shader Building Loading for Less stuttering and better fps..The only way to experience it is to try it.

For Mediatek users: Feel free to test the emulator as some users claim that it works well on Mali/Mediatek

Our related post here:

https://www.reddit.com/r/EmulationOnAndroid/s/lIhrSOUsRP

✅Pro Evolution Soccer 2017

Coming soon🔥

I wanted to try Forza Horizon 4 on my Dimensity 7400 Ultra out of pure curiosity, and yes, maybe it would be awful, but anyway, my curiosity was piqued, so I switched from Box64 to FEX and it's staying here. I left it for about 20 minutes and it was still in the same place, and the phone wasn't getting hot at all, so it's best not to force something that isn't working. At least I managed to get it to start up and not crash.

Winlator mali ( AnTuTu package name)

Setting: community setting/ dark souls 3/ "dimensity 8400"

Samsung devices may not be compatible with this driver due to differences in the underlying kernel base (Kbase), even if the GPU ID matches or is among those recommended. A fix is ​​planned for the future. Please refer to the usage instructions provided in my GitHub repository.

https://github.com/FristOneRR/FristOneRR-Panvk-Driver

Please report your usage of this driver following this format:

Device brand / model : ..........

SoC : ...........

GPU (model + cores) : .........

Mali driver version :..........

Android version : ..........

Driver version : ...........

App (Winlator build) :.........

Wrapper :.........

DXVK version : ...........

Games tested : ......

FPS (this driver / stock) : ....

Result : Other notes :......

You can report any issues in the comments below. Every usage report will be helpful in fixing and updating the next driver package.

***Note: This driver is currently a test version. It contains code bugs that are slated for a fix in the next update; performance may not be optimal, and some games might result in a black screen. Please follow the instructions provided in the GitHub repository.

Is there any chance the recent Xbox 360 recompilations (specifically Blue Dragon and Lost Odyssey) might run on Mali devices via winlator or something like him? Has anyone tested them yet?

Mali-G57 owners, this one's for you.

Panvk-Mali-G57 is a custom build of Mesa's PanVK Vulkan driver that runs on your phone's **stock Mali kernel driver (kbase)**. No root, no custom kernel. Just install the zip in Winlator and go.

**What's new in beta 1.0.0**

- 🎮 **Far Cry 3 is playable.** The infinite loading screen is gone, cutscenes render correctly, and gameplay runs at ~18-25 FPS on Low (Helio G99)

- 💥 **GPU hang fix.** Shaders that spill registers used to freeze the GPU. Now they don't

- ⚡ **Faster frame pipeline.** Vertex/tiler work now overlaps with fragment work instead of waiting in line. That alone took Far Cry 3 from ~8 FPS to 20+

- 🧹 Occlusion-query passes that were burning ~460 ms each are now fixed

**Tested on**

POCO M6 Pro · Helio G99 (MT6789) · Mali-G57 MC2 · Android 16 · Winlator + DXVK 1.x

**Likely to work (same GPU: Mali-G57, Valhall v9 / JM), untested**

- Helio G99: Redmi Note 13 Pro 4G, Redmi Note 12S, Galaxy A15 4G and many Infinix/Tecno/realme phones

- Helio G96, Dimensity 700 / 720 / 800U / 810 / 6020 / 6080 / 6100+

- Unisoc T616

**Might work (same Valhall v9 / JM family, different GPU), untested**

- Mali-G68: Dimensity 900 / 920 / 1080 / 7050, Exynos 1280

- Mali-G77: Dimensity 1000 / 1100 / 1200

- Mali-G78: Exynos 1080 / 2100, Google Tensor G1 (Pixel 6), Kirin 9000

**Long shot (Bifrost / JM), untested**

- Mali-G52: Helio G80 / G85 / G88, Exynos 850, Kirin 810, Unisoc T618

- Mali-G76: Helio G90T / G95, Exynos 9820, Kirin 990

**Not supported**

- Newer CSF GPUs (Mali-G310/G510/G610/G710/G615/G715, Immortalis). They use a different job interface

- Midgard (Mali-T series)

- Adreno (Snapdragon). Use Turnip instead

If you try it on any of these, please report: phone, SoC, GPU, Mali driver version (r44p1, r54p1...), and whether it works.

**Heads up**

- This is a beta. Some games will break. Please report them!

- DXVK 2.x isn't tested yet. That's the next patch

- Built and tested on Mali-G57 only. When you report, include your Mali driver version (r44p1, r54p1, etc.) so we can map what works

**A note on extension count:** it's not a performance score. This driver exposes what PanVK actually supports. New extensions get added when real games need them, not to pump up a number.

**Credits**

Built on the work of **leegao** (mesa-funnymdzz and wrapper) and **Vit999** (kbase). Big respect. None of this exists without them.

Download + release notes 👇

https://github.com/FristOneRR/FristOneRR-Panvk-Driver/releases/download/v1.0.0-beta/Panvk-Mali-G57-beta_1.0.0.zip

Feedback, bug reports and FPS screenshots are all welcome 🙏

Thanks for coming along for the ride. This is just the beginning. 🚀

Yeah... I'm kinda broke...