yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Oh shoot, that's Google Pixel 3 XL, lol, i misread that

Well, the vulkan driver i put in the zip (version 1.0.66) file is from Pixel 2 XL old PPP3 rom.

I'm not quiet sure but, if you can extract it from Mi 8 rom, i'm not sure but maybe from V10.0.2.0.OEAMIFH MIUI rom, you can try it, since Mi 8 has Adreno 630 too.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Alright, I downloaded a Mi 8 ROM to try this, but I don't have any way to extract the files from it. The system and vendor images in the ROM have .br file extensions, and I don't know how to mount them.

If anyone wants to help me out and extract those drivers for me (and all other Pixel 3 owners), I'd really appreciate it.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
a little hint for you : https://wiki.lineageos.org/extracting_blobs_from_zips.html
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Emu:
LG V30, Camera force reboots phone when scrolling through the gallery.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Thanks. I was able to extract a "beta" Android 9 ROM I found on the Xiaomi Mi 8 XDA forum to grab the Vulkan library, and replacing it actually worked, but the driver version was still 1.1. I tried another stock Oreo ROM for the Mi 8, but for some reason, I was unable to extract the vendor image with the same method as before. I'm trying a few other ROMs right now.

If anyone knows of a good ROM to try, that's older than Pie and might have that older Vulkan driver, please let me know.

EDIT:

I just tried all the ROMs I could find, all of them either wouldn't extract, or had Vulkan 1.1 drivers. But for what it's worth, the 1.1 libraries do work fine on my phone, so that's good to know I guess.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
From the information i gathered, vulkan driver 1.0.66 is only on V10.0.2.0.OEAMIFH ROM.

link : http://bigota.d.miui.com/V10.0.2.0....FH_20180912.0000.00_8.1_global_7d6e5e4b45.tgz

If you follow my steps on the link i've given to you, you'll come down to have "vendor.img" file.

After that, it's just mount using this command :

mount -t ext4 -o loop vendor.img /directoryyouwant

And yeah, grab the driver in directoryyouwant.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Thanks! I'll give this one a try. I actually tried that build, but I didn't download it in .tgz format. I also don't have a Linux computer handy, so I used 7zip to open vendor.img. It worked for 2 of the ROMs I tried, and the other 2 just failed to open with 7zip.

I was about to try LG G7 ThinQ ROMs before you commented this. I'll give this a try first before I try another phone. I'll let you know if it works!
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

Actually i'm getting tired of keep repeating this, and maybe eventually i'll just stop updating this driver, maybe i'll just make it private for myself only.

It's stated clearly and bold and have red color font, which please provide logs, so i can help further.

I believe that it wasn't so hard?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there, i never found a method to mount .img file on windows computer.

Because, yes the extension is .img, but the fact is that image is ext4 image file, which ext4 is exclusively linux thing.

If you find a way without using linux, then good for you.

Other thing that you can use VMware, which i use VMware too to develop this driver.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Oh no! Please don't do that!

I extracted the .tgz you linked me, and I actually didn't need to use the method you linked, since vendor.img was already in the archive, no need to convert. Unfortunately, the image won't open in 7zip. It turns out I did have a Linux machine I could use, and it wouldn't mount there either. I got the error:

$ sudo mount -t ext4 -o loop vendor.img ./vendormnt
mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error

I checked, and the MD5sum listed in md5sum.xml even matches, so the vendor.img does not seem to be corrupt. I'll keep trying other things until something works.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
you can type command :

file vendor.img

that command is to identify what is the type of the image.

if it's ext4, you can directly mount using the command i sent earlier.

but if it's sparse image, you have to convert it into ext4 image first, after that you can mount it using the command i sent to you earlier.

to convert from sparse to ext4, you can use simg2img module, read it here : http://rex-shen.net/android-unpackpack-factory-images/

search for simg2img section on that link.

___________________________________________________________________________________

I like it when a guy like you were around in xda, wants to learn something, i'll help you with the little knowledge i have :

1. on your linux (i'm using ubuntu), install the required package using this command :

sudo apt install brotli

sudo apt install python2.7 python-pip

sudo apt install simg2img

2. download python module : https://github.com/xpirt/sdat2img/blob/master/sdat2img.py

2. download the rom you want. and extract it.

3. different rom files have different structure, some have .dat.br files, some have .dat files, some have .img files. the difference :

*- if it's .dat.br, you have to run this command :

brotli -d vendor.new.dat.br -o vendor.new.dat

*- if it's .dat, you have to run this command :

python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img

you have to put sdat2img.py on the same directory as vendor files you want to extract.

*- if it's .img, run this command :

file vendor.img

**- see the command outcome, if it's sparse image, you have to run this command :

simg2img vendor.img vendor.ext4.img

after that you can mount using command :

mount -t ext4 -o loop vendor.ext4.img /directoryyouwant

**- if it's ext4 image, you can directly run this command :

mount -t ext4 -o loop vendor.img /directoryyouwant

4. copy the files you want from the directory you mount the vendor files.

5. done!

You can ask me back if you have difficulties, i write this in such hurry, maybe i missed something.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
You're awesome! That was it, it was a sparse image. I was able to mount it and grab the vulkan library files from it.

Unfortunately, unlike the Vulkan 1.1 driver from before, it doesn't seem to work on my phone. Having them installed just breaks Vulkan support, with Hardware Capability Viewer being unable to find a GPU with Vulkan.

Oh well! It was worth a shot. I can generate some logs for you if you are interested.

Edit: I was just thinking, maybe it didn't work because all of the other files I previously deleted were required for the driver to run? Which might be why a Vulkan 1.1 driver file worked, but since the other files were not built for Vulkan 1.1, this replaced 1.0 driver didn't work? I could be totally wrong, I'm just guessing.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

Maybe you should check in (system)/vendor/etc/permissions, did you have proper xml files.

You can check android.hardware.vulkan.version.xml and (or) android.hardware.vulkan.version-1_0_3.xml.

If you have 1.0 vulkan driver, inside the xml the version should wrote 4194307.

If you have 1.1 vulkan driver, inside the xml the version should wrote 4198400.

For safety measure i ussually do this :

For vulkan 1.0, i make sure have 2 files android.hardware.vulkan.version.xml and android.hardware.vulkan.version-1_0_3.xml.

For vulkan 1.1, i make sure have 2 files android.hardware.vulkan.version.xml and android.hardware.vulkan.version-1_1.xml.

If things i mentioned is already good, the only thing you can do is to catch logcat and i'll see what's the cause, i'm not 100% sure can help to fix but it's okay to analyze it.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
I only found an "android.hardware.vulkan.version-1_0_3.xml" file in the vendor.img from the Xiaomi Mi 8, I couldn't find "android.hardware.vulkan.version.xml."

I also added "android.hardware.vulkan.version-1_0_3.xml," but the driver is still not working. By the way, I know what you said in the OP, but I'm using Magisk modules to do all of this. The Pixel 3/XL doesn't have TWRP yet, so I don't have a clean way of touching files on the system while not booted. Since Magisk was able to successfully replace the 1.1 driver I tried before, this shouldn't be a major issue, at least in terms of making the driver show up in Hardware Capabilities.

I'll PM you the logcat in a few minutes.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

I saw your logs, but i couldn't see anything leads to the vulkan driver not found.

It would be hard to identify the issue with no things to check.

For now, i don't know if magisk causing it, or the vulkan driver is not compatible, so many things to test.

Your logs isn't detail enough, i don't see any magisk mount in that logs, are you sure you capture it right? the command :

- from adb :

adb logcat -v time -d > logcat.log

- from android terminal :

su

logcat -v time -d > /sdcard/logcat.log
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Yes, that's the command I ran right after boot. Magisk is definitely loaded. I captured the log from a Terminal Emulator, but I can try capturing it from ADB when I get home.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
okay, please try to capture from adb, and this time capture the logcat after you open vulkancapsviewer app and try to run games on dolphin, maybe there's some hint from it.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Ok. I just sent you two logs. I captured them like this:

First capture:

Rebooted the phone

Opened vulkancapsviewer (Vulkan listed as 1.1.66)

Opened Dolphin, loaded a game with Vulkan set as the backend

Captured log using adb logcat -v time -d > logcat.log

Second capture:

(From last session): Enabled Magisk module I made to replace the driver

Rebooted the phone (this took noticably longer than normal)

Opened vulkancapsviewer, it fails to find a Vulkan GPU

Opened Dolphin, tried to load the same game as before

Dolphin tells me it can't find any Vulkan physical GPUs

I hope this helps!
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

Okay there's a little hint from that logs, you'll find a row stated : "Could not load /vendor/lib/hw/vulkan.sdm845.so from sphal namespace: dlopen failed: library "libllvm-qgl.so" not found."

2 possibilities :

1. no libllvm-qgl.so found on your device. located at (system)/vendor/lib and (system)/vendor/lib64

2. the libllvm-qgl.so is there but not compatible with vulkan 1.0

Things to try, is to include libllvm-qgl.so too on the magisk module.

Keep in mind that there is big possibilities that bootloop can happen.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ubergeek77:
Ok. Thanks for looking into it!

Since there is the possibility of a bootloop, as much as I want this to work, I should wait until I have some downtime and won't need my phone to take calls. That way, if a bootloop does happen, I'm next to my computer and prepared to flash a clean boot image to get back into the system. Alternatively, I could just wait until TWRP comes out for this phone.

In the meantime, is there any way to examine these library files to see what their dependencies are? I've done a little of that in the past for Windows DLL's, and I think there's a way to do it with Linux shared libraries, but I'm not sure what to use for that, especially since these are compiled for ARM64.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] qqzwc:
This is useful with the PUBGM game,thank you!
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

Yes, it's good you're aware of that.

Another way to get around bootloop of magisk module is through TWRP using "uninmod" magisk module, but TWRP isn't available yet for your phone.

To examine depedencies, we need source code, and unfortunately we don't have that. So still bumped.

_________________________________________________________________________________________

For your additional information, files needed for vukan working properly :

system\lib\libvulkan.so

system\lib64\libvulkan.so

system\vendor\lib\libllvm-qgl.so

system\vendor\lib64\libllvm-qgl.so

system\vendor\lib\hw\vulkan.xxx.so

system\vendor\lib64\hw\vulkan.xxx.so
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] xd8877:
i haved changed vulkan.msm8996.so and flashed in TWRP

but the driver still not updated, still in v269 . i have tried both treble and no treble version

my device:

lg v20 h918 with stock 8.0 , magisk 17.3, TWRP 3.2.3-4 , mk2000 kernel

anyone faces the same problem?:(
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] rippledrums:
Have you tried clearing data for your system information app?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] xd8877:
tried already:(
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] mehra1:
Tried the v313 rev23 getting bootloop on lg v30+

Snapdragon 835
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] rippledrums:
Damn...

Maybe try getting TWRP logs for [MENTION=8436723]heindrix[/MENTION] to look at then.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Try to follow this post and the next post continuation : https://xdaforums.com/mi-mix/development/driver-adreno-530-540-gpu-driver-t3815853/post77969462

Keep reading what's the other members doing.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] karlosworx:
did you mount system and vendor before flashing the file?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
Im rly confusing in INSTRUCTIONS 2, i got vulkan.msm8998.so for default

EDITED

ah i got it thx and ignore me :D
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Bogdans29:
After a lot of testing the reason why this driver is not compatible with sd 410 or lower it's have conflict with OpenGL 3.0 ....
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] hypeartist:
Xiaomi Mi6X (sdm660, Adreno512) - 313@23 works just fine on my MIUI 10 (Oreo 8.1). The only issue is that AI mode in camera doesn't work with new drivers. Tried to clean Camera app's data - no help.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Try to follow this post and the next post continuation : https://xdaforums.com/mi-...3/post77969462

Keep reading what's the other members doing.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
Dude for tweak, i have 2 buildprop in system and vendor. Should i used this tweak for both buildprop?

I treble [MENTION=8436723]heindrix[/MENTION]
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] hypeartist:
Seems like deleting may not be needed.

Just clear camera app's data and reboot.

I tried both methods - they both fix camera start-up issue.

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

None of mentioned did help.

Still FC on selecting AI mode.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
Dude i have 2 buildprop (in system and vendor) so what should i do? Just put in system? Or vendor? Or both? I used treble rom btw
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] rippledrums:
I put those lines in /system/build.prop but my device is non-treble. No idea if it makes a difference for treble devices but I believe the build.prop in /vendor just adds to the one in /system.

I might be wrong though... :confused:
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
I think for non treble just applied in system and for treble just applied in vendor but i applied thats tweak for both :D thats why i ask [MENTION=8436723]heindrix[/MENTION]
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Mar-cel:
Its not showing rev23 after installing it :confused:
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Ice Bear:
It doesn't show the rev number. If you flashed rev23, you're good to go.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] tkhquang:
Hi, thank you so much for this driver, I successfully flashed it for my Zenfone 3 ZE520KL AEX Android 9.0, dolphin (Vulkan) is running okay on my device but only when I disable HW overlays. Without it disabled, dolphin is choppy and flickering badly despite high fps and steady speed in any game (it feels like it skips 1 millisecond and runs again). Well, no big deal at all but having to disable HW overlays everytime my phone reboots is kinda annoying to me. Do you have any idea I can fix it without having to turn off HW overlays, or at least is there a way to make my device remember that HW overlays settings after reboots?

I know this is kinda off-topic since the driver is working flawlessly on my phone, but I actually have no other place to ask :(
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Jole7:
I applied the lines in System - build.prop only i think that's the correct place
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

I think the build.prop i post on the first page doesn't activate Disable HW Overlays, you should check the other lines in your build.prop to see if anything causing that, you can just find it by removing it one by one.

Or you can search google about this matter, i see there are many page refer to this matter.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

Mostly it should put on vendor's build.prop.

But some ROM (like MIUI), doesn't vendorize their system, so you just could find build.prop in system, how you know if your rom doesn't vendorize? you can't find build.prop in vendor directory.

In your case, you should just put it in vendor directory.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Bharath A:
The ROM I use has vendor directory, it's build prop just has 11 lines, but build prop present in system has some 250-280 lines.

I noticed all build prop optimisations written to my system build prop..
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
Ah thx dude
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] tkhquang:
Thanks, I've checked through some threads (mostly changing values in build.prop) and stuff that was outdated it seems, sadly all didn't work. Maybe I'll just leave it as is then, not a big deal at all :fingers-crossed: Again thank you for answering and this driver :good:
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

How about delete "debug.composition.type=gpu" line and reboot?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] tkhquang:
Just tried and it didn't work sadly ?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Rohit Shelke:
My device is mi max

SD 652

I'm confused about which version to download.

I'm on Android 9.0

So V330, 313, 319 or 328??

And the download also has Rev2, Rev 3

What is it?

Sorry I'm kinda noob, please help me out with finding the correct version
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Rohit Shelke:
This is version
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
U just need clearly read OP dude
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Ice Bear:
You're able to use up to V330 since you're on Android 9.0 (Pie)
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
Tbh dude, which better between 330 or 313?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
This is v330 gpu 81 with same config

And this is 313 gpu 86k with same config
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
V330
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Fahrilubis:
V313
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] Ramdhan Kim:
Can you update vulkan api version to 1.1?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ValKyre:
You are right bro. I get error (crash youtube) because i try make magisk module and use :(
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] BajinganTengik:
[MENTION=8436723]heindrix[/MENTION] V313 works well on sdm630 treble. Thanks.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] smariob:
About sdm845 & adreno 630

Hey there! First I would like to congrat your efforts to get proper driver working [MENTION=8436723]heindrix[/MENTION] and also [MENTION=7042628]ubergeek77[/MENTION] to research how to get vulkan working on pie/adreno 630, it's very kind from both of you.

Could be possible you share the blobs extracted from the oreo miui rom?

I've observed that Mi 8 on pie runs vulkan 1.1 and also has the blackscreen bug on dolphin.

The system libs are the same as heindrix mentioned, just changes on system\vendor\lib64\libllvm-qgl.so and system\vendor\lib\libllvm-qgl.so the name instead is libllvm-glnext.so,

Could be this refered to the error ubergeek77 mentioned in the quoted post?
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

You should try it yourself, delete all files inside (system)/vendor/lib and (system)/vendor/lib64 directory recursively, except :

* libadreno_utils.so

* libllvm-qgl.so

* vulkan.xxx.so

And flash the zip file, see if it's booting or not.

But becareful of the high possibility of bootloop.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] ciberworm:
Tester on los 16.0 working perfecto
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] smariob:
Done it. Not bootloop but broken vulkan support not gpu with vulkan support detected.

I could find in the log when openning vulkancapsview

Loading libvulkan.so...

11-07 13:37:49.056 E/vndksupport( 6811): Could not load /vendor/lib/hw/vulkan.sdm845.so from sphal namespace: dlopen failed: library "libllvm-qgl.so" not found.

11-07 13:37:49.056 E/HAL ( 6811): load: module=/vendor/lib/hw/vulkan.sdm845.so

But verified that files that flashed are present in vendor/lib/ and vendor/lib64/...

Attached the log, thanks in advance!
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
This is quiet difficult to solve, and i don't know if it's gonna be solved or not.

For now, i've created a zip file contains vulkan libs and dependecies that i've hex-edited to match snapdragon 845 structure.

You can download it in the google drive, but i will remind you again that the possibility of bootloop is high.

You can report back with logs if you can/want.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] KazeoX:
No gpu vulkan support after flash test file ?

Sd845 too
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
Hi there,

Yeah, it would difficult to solve it through hex edit alone.

The problem is very clear in the logs, vulkan libraries can't find dependencies file in the respected directory (libllvm-qgl.so). altough in the test zip file i've edited it to get the dependencies to libllvm-glnext.so, it still error, but it would be difficult to see the exact error without the device and without logs.

I curious how it can't find the dependencies altough it's already there, maybe should modified the permissions.

I'm so busy these days so i can't solve this quickly, but i won't promise that i could fix this too.

But the latest driver is still v330, i will update it if there's new one.
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] fahri170693:
Dude im not sure what happen when i update my rom i got black screen on both 313 and 330 even it was okay before update....

Sagit

Aex treble
[Xiaomi Mi MIX  ROMs, Kernels, Recoveries, & Other ] heindrix:
[MENTION=1936224]blackver[/MENTION] [MENTION=7042628]ubergeek77[/MENTION] [MENTION=3910634]smariob[/MENTION] @Abibboy [MENTION=7448790]more_than_hater[/MENTION] [MENTION=5314891]Mar-cel[/MENTION]

For everyone who have device SDM845 / Adreno 630, which have blackscreen problem on Dolphin Emulator when using Vulkan API, i've created several zip files to test, file name is : adreno 630 - v330 revTESTx

There are 5 files, you can test one-by-one and report to me if anything is working or not.

Please provide logcat or i can't do anything without it.

I will remind you guys that bootloop can happen.