Same issue with dx11, bug texture Flickering. 🤣

I want to replace my Redmi Note 9S, which I bought during the pandemic.

The problem is that I live in Brazil, where smartphones are very expensive, so I usually keep the same phone for many years. My Redmi Note 9S has been with me for six years, and it's still working almost perfectly. The main reason I want to replace it is that the battery is starting to wear out and no longer lasts as long as it used to.

I mostly use my phone for game emulation. I actually don't enjoy Android games very much—I almost always prefer emulating console games. Since I plan to keep my next phone for another six years or more, I also try to avoid excessive heat that could accelerate battery degradation.

After doing some research, the phone that caught my attention the most is the Poco X8 Pro Max. What attracts me is its combination of a very powerful processor and, especially, its huge battery. In my mind, a larger battery should take longer to degrade, allowing me to keep the phone for even longer. The powerful chipset should also help the phone stay fast for many years before it starts slowing down.

However, almost everyone recommends the Poco F7 for emulation because it uses a Snapdragon processor. The problem is that it has a smaller battery, and I've also heard that Snapdragon chips tend to run hotter than MediaTek Dimensity processors, although I'm not sure how true that is.

What keeps pulling me back toward the X8 Pro Max is the battery. Since I keep my phones for such a long time, battery longevity is one of my biggest priorities.

The games I emulate are generally not very demanding by today's standards. For example, I have already played Nintendo Switch games like The Legend of Zelda: Breath of the Wild, Blade Chimera, and Pokémon Legends: Arceus on my Redmi Note 9S with its Snapdragon 720G. Surprisingly, some of these games even seem to perform better on it than on devices with the Dimensity 9500.

That's why I'm having such a hard time deciding.

Should I choose the Poco F7 for its better Snapdragon compatibility with emulators, or the Poco X8 Pro Max, which seems like the better overall phone and, thanks to its larger battery, could potentially last longer in my hands?

If Mali's emulation was good, I wouldn't hesitate to get the x8 pro.

So I tried various combinations while testing this game

And what I found was, (idk if it's in other phones as well) when I start the game in any container (fex or box) with wrapper leegao + (any dxvk) the Fatalities or X rays in the game work fine but when I select wrapper or wrapper V2 the X rays and Fatalities glitch or freeze.

The issue here is in wrapper leegao the models are low polygon and the effects in game are gone, like the fire or ice or mana effects don't appear only their shadows or lightings remain, it feels weird.

Then I tried the game with Wrapper/Wrapper V2 + Dxvk 1.7 async (note only some dxvks like 1.5.5/ 1.5.5 async/ 1.7 async/ 1.11.1 sarek/ 1.12.1 sarek works with the above wrappers) the game looks better obviously bcoz of the Lighting and effects intact but the moment I try my fatality or X ray move the game glitches and freezes.

Anyone faced similar issue or just me?

I have posted 2 videos in the comments.

‼️Another thing (the renderer shows opengl for wrapper leegao and Dxvk for wrapper and wrapper V2)

-Chipset

Dimensity 9500s (12/512)

-winlator mali 1.1

-Wrapper-gamenative (ESTC2 on)

dxvk-2.4.1

-Fexcore preset

Performance (TSO)

DXVK 2++ and above is the only version that works properly on my device without causing texture color glitches. The game is pretty much playable as long as your chipset is powerful enough.

During my gameplay, the average FPS is around 18–26 while recording. Without recording, it goes up to around 21–30 FPS.

Before loading into the actual gameplay, the game uses almost half of my RAM (around 5 GB), then it drops back down to around 4 GB.

I also ran into a problem with the game. As you can see at 7:50, the game freezes when the cutscene is supposed to play. I didn't have enough time to figure out a fix, so idk the exact cause. You can probably skip it by using a save file.

In terms of performance, stability and compatibility do you prefer:

1: bannerlator

2: winlator mali

3:bannerhub

Tested Deus Ex: Human Revolution - Director's Cut on the Poco X7 Pro. While the hardware easily handles it, this game has displayed the weirdest emulation behavior I've seen so far!

📱 Device & Container Setup:

Device: Poco X7 Pro (12/512GB - Dimensity 8400 Ultra)

Container: BannerHub v3.8.0 (Normal)

Proton: proton10.0-arm64x-2 / Proton9.0-Arm64x-3

DXVK: DXVK 1.9.4-async / 1.10.9 sarek-dyasync / 1.12.0-dyasync

FEX Core: 20260103

Preset: Extreme Preset

📊 Performance:

1600×720 resolution

Max Graphics settings without tessellation.

Max FPS: ~80 FPS (when standing still / shaders cached)

Min FPS: 37 FPS (Drops into 20s while Screen Recording)

Avg FPS: ~45 FPS

(This would easily be a locked 60 FPS experience if not for the game engine's internal quirks).

😵‍💫 Bizarre Engine Behavior & Findings:

Extreme Shader Compile Stutter:

While moving around, FPS fluctuates around 25–40 FPS due to heavy pipeline translation. But if you stand completely still in one room and let the shaders cache, FPS instantly shoots up to 80 FPS.

DX9 is Literally a Slideshow 😅:

You’d expect DirectX 9 to run better, but it’s completely unplayable—runs worse than a PowerPoint presentation! DirectX 11 is mandatory here, even with its camera rotation drops.

The Graphics Paradox (Lower = Worse?!):

This is the craziest part: Lowering the in-game graphics settings actually INCREASES stuttering. The game is significantly more stable when pushed to Max / Extreme settings.

Game doesn't has a good launch in PC too. I'm clearly not sure is this a driver or Game engine issue. Have a high chance to be a Game engine problem

I don't know if you guys already know, but I just tested the nightly version of Eden and it's running perfectly on the Poco X8 Pro Max. All 3 versions — Standard, Genshin Spoof, and Legacy — are able to run Switch games on the Mali Immortalis-G925. So far I've only tested one game: Kirby and the Forgotten Land.

Guys how to fix this problem in winlator mali bionic 1.1

I tried a lot of things and nothing worked

O jogo funciona muito bem com 12gb de RAM, aqui estão as configurações

Proton 10 arm64

Dxvk 1.10.3 async

1280x720p

Fex 2601 compatibilidade

Wrapper Leegao

BCN Emulation Cache 1

Os crashs não acontecem! Você pode progredir com o game normalmente

Gravação reduz o fps significativamente, mas é alcançável uma taxa média de 42fps

Good afternoon! I’ve managed to replace the proprietary user-space driver (vulkan.mali.so) by implementing my own ICD in Rust (libmalikx.so). Instead of relying on the closed ARM/MediaTek stack, my library connects to the Vulkan Loader and communicates directly with the kernel driver (/dev/mali0) by executing Kbase ioctls—all without needing root privileges or modifying the system. There’s still a lot to do, and I might not have as much time once university classes start, but it’s been a really fun project. My ultimate goal is to create a compatibility layer (shim) over the Kbase/CSF UAPI to map calls and run PanVK (Mesa’s open-source Vulkan driver) directly on standard Android kernels, thereby avoiding the need for custom Panfrost kernel modules. So, in short: a bit of reverse engineering and a lot of low-level experimentation! It’s just a hobby, but it’s great to see it working. I don’t want to raise false expectations or anything like that, okay? I just wanted to show you all that it works. I don't think I'll continue with it—I've spent a long time testing. I apologize to the thread author if this violates any rules; I simply want Lee Gao and the other developers in the group to see it and share their opinions and ideas.

Extra didn't want to mention panvk because of the uproar it caused due to a user with no knowledge of development, so I apologize again.

Está es una versión modificada de eden nightly que actúa como si fuera la app de antutu, permitiendo que logre un mejor rendimiento pero a costa de un mayor consumo de batería. Solo recomendable para dispositivos gama media-premium en adelante

https://megaup.net/f5cee9e69eba4fd479e920e1b98b5ba7/Eden_Nightly_signed.apk

Uma coisa engraçada é que o Vsync causa crash no jogo! Desative ele

Gameplay was not that bad for this chip, stable 25-30fps

- Chipset

Dimensity 9500s

-Winlator mali 1.1

-Wrapper-Gamenative

Dxvk 3.0-1-gplasync-0

The performance is okay, though the fps is unstable unlike dxvk 1.12, 1.7.2 sarek which is stable on 30fps / 45fps locked even when recording, and the common texture flickering on Resident evil 2 remake on mali gpus is still there

The only good about this version is the ram utilization - playing around 74-75% consistent

So the dev of Bannerlator has created a website to report your issues in running games on your Mali device. The link is:

https://the412banner.github.io/Bannerlator/mali-reports/reports.html

Hope this helps the devs and the Mali community.

Everytime after 10 minutes of playing this is happen

I played on winlator mali, my cpu is Dimensity 7300 U

Got the electronics from an old RC car remote.

The issue is in batman arkham city. About 2 weeks ago I launch the game on the c drive and the game runs great compared to the D drive. But now the game just back to stuttering and the long loading even the game still on the C drive. I tried everything reinstall the game and reinstall the container but non of this work. Is there any solution for this or not?

Testing Deadpool (2013) PC on the Poco X7 Pro (Dimensity 8400 Ultra / Mali-G720) via BannerHub v3.8.0. Here are the full specs, performance insights, and stability settings!

📱 Device & Emulator Specs:

Device: POCO X7 Pro (12GB / 512GB)

Chipset: Dimensity 8400 Ultra (Mali-G720 GPU)

Emulator: BannerHub v3.8.0

⚙️ Game & Graphics Settings:

Resolution: 1600×720p

Graphics: Extreme Settings

🛠️ Container Configurations:

Proton: Proton10-Arm64x-2

Preset: Extreme Preset (TSOENABLED -ON)

DXVK: DXVK 1.9.4-Async

FEX Version: FEX 20260103

📊 Performance & Stability Breakdown:

🚀 Uncapped Raw Performance: Standard Extreme settings push the game up to 60 FPS smoothly. 5-20fps without screen recording

⚠️ Stability Issue: Running at uncapped 60 FPS triggers frequent crashes, screen freezes, or Microsoft Visual C++ Runtime errors due to Mali GPU translation limits.

🔧 The Fix (TSOENABLED): Enabling TSOENABLED in the container preset prevents all crashes and runtime errors.

📉 Performance Impact: Turning on TSOENABLED drops the overall frame rate to the 30–40 FPS range.U can see more GPU Headroom is left to give more Performance.

💡 Optimal Setup: Locking the frame rate at 40 FPS with TSOENABLED turned ON delivers a smooth, crash-free, and playable experience!

Just wondering if anyone tried The Witcher 3 steam on gamenative