PowerVR ge8320 (mediatek Helio p22) corrupted graphics

[fzurita]

There seem to be some issues with the GPU drivers for PowerVR ge8320 on a Realme C2. See the attached screenshot.

This will be hard to debug without having the device, the best hope is that the phone gets an update with a non-bugged GPU driver.

[fzurita]

@Panderner In Mupen64plus FZ, go to settings, then display. Scroll down to the "Flicker Reduction" option. Please try all the options it gives you and see if any of them make the issue go away.

[Panderner]

Yeah, I tried all flicker reduction profiles but it didn't work

[fzurita]

This will be hard to solve without having the device unfortunately.

[Panderner]

And it's happened for other devices like Samsung Galaxy a10s, redmi 6, Xperia l3, lg k50s and vivo y91i

[Panderner]

Enabling Fragment based depth and N64 depth compare to fix corruptions

[fzurita]

Do you have those other devices? How do you know that they have the exact same problem?

[Panderner]

I don't have any devices but it's corrupted for PowerVR ge8320 devices including mediatek Helio P22, a22 and p35 on most games

[Panderner]

Enabling N64 depth compare to fix corruptions but it has problems for some games like tiles in FIFA 99 and Conker's bad fur day shadows

[Panderner]

This will be hard to solve without having the device unfortunately.

Have you tried other PowerVR GE8320 Devices?

[fzurita]

I don't have any to try it on.

[Panderner]

In glideN64-medium there are almost no polygons are drawn.

Tested 5 Games: Super Mario 64 The Legend of Zelda Ocarina of Time Mario Kart 64 Banjo Kazooie Conker's Bad Fur Day And it happened for most games

[Panderner]

In retroarch's mupen64plus-next (gles2 and gles3) same as glideN64 medium in M64Plus FZ on default settings

[fzurita]

This is most likely an issue with your device drivers. Best we can do is hope that your drivers get updated.

[Panderner]

This is most likely an issue with your device drivers. Best we can do is hope that your drivers get updated.

It Doesn't Allow to Update GPU Drivers on Android, I hope that Adreno 620 & 650 drivers are updatable via Google Play Store

[fzurita]

They can get updated if your when your OS is updated.

[Panderner]

They can get updated if your when your OS is updated.

My phone Realme C2 is preparing for android 10 update in Q3 2020

[fzurita]

Unless someone with the affected devices that knows how to debug this kind of issues comes along, this is unlikely to get solved.

[Panderner]

Unless someone with the affected devices that knows how to debug this kind of issues comes along, this is unlikely to get solved.

Some phones are stuck at Android 8 like LG K40, Alcatel 5V, Vivo y83, Lenovo K9, Panasonic Eluga Z1, Etc. Some phones running Android 9 are unannounced or refused to update to Android 10.

[Panderner]

Why? This driver is not bugged and working fine for some android games and emulators

[Panderner]

@gonetz But please fix it in glideN64-medium and don't close it

[Panderner]

And still corrupted on glideN64 medium. My phone supports OpenGL ES 3.2

[gonetz]

I can't fix it. "Unless someone with the affected devices that knows how to debug this kind of issues comes along, this is unlikely to get solved."

[Panderner]

I can't fix it. "Unless someone with the affected devices that knows how to debug this kind of issues comes along, this is unlikely to get solved."

@gonetz Why you can't fix it?

[Panderner]

Please reopen.

[gonetz]

Because I can't reproduce it on my hardware. @fzurita is our expert for mobile devices. If he can't solve it, the only hope is that someone else will take it. I reopen it, but chances are slim.

[fzurita]

I would have to get a hold of the affected hardware. I don't have the PowerVR devices mentioned here.

[Panderner]

Here's a list of PowerVR GE8320 devices: https://mobile.phonebunch.com/phone-filter/gpu/powervr-ge8320/page/1/ And if you buy any phone powered by this GPU at online shopping websites and cell phone stores.

[fzurita]

Is this still an issue? If it is, what is the cheapest device that has this problem?

[Panderner]

It's still a issue for my old Realme C2.

[fzurita]

With the latest version of M64Plus FZ?

[Panderner]

With the latest version of M64Plus FZ?

Yes.

[fzurita]

Unfortunately, the Realme C2 is hard to get in the USA. So I need to find a different phone that has the issue and that it's not too expensive.

[Panderner]

@fzurita choose one: Samsung Galaxy A10s LG K40s Alcatel 3L (2020) Xiaomi Redmi 6

[fzurita]

Are those phones for the Indian market? I can't find any here on Amazon.

[Panderner]

Are those phones for the Indian market? I can't find any here on Amazon.

https://www.amazon.com/s?k=mediatek+helio+p22&rh=n%3A2335752011%2Cn%3A7072561011&dc&qid=1611580028&rnid=2941120011&ref=is_r_n_4 you can find here.

[fzurita]

I guess I wasn't using the right terms. $150 is a little too much to swallow at this point.

[fzurita]

I was able to get a hold of a phone with a PowerVR Rogue GE8100.

The phone is extremely slow. Any ways, unfortunately I'm not seeing the same issues. I do see flickering textures with Super Mario 64, they are fixed though when I disable fragment based depth and framebuffer emulation is enabled with the resolution factor set to 1x.

The main thing that seems to hurt texture rendering is fragment based depth. Fragment based depth is disabled if you use the GLideN64-Fast emulation profile.

Can you confirm that choosing the GLideN64-Fast emulation profile fixes the issues for you? If not, I would not be fixing the same issue that you have.

[Panderner]

When I disable fragment based depth all almost polygons are broken.

[fzurita]

Ok, what about the GLideN64-Fast profile? Are you using the latest version of the app?

[Panderner]

Ok, what about the GLideN64-Fast profile? Are you using the latest version of the app?

Same happens in GLideN64-Fast and yes I'm still using latest version.

[fzurita]

Ok, so it sounds like the device I got a hold of is not good for debugging the issue. It does have different issues though.