Heasterian

> > > Might be a stretch, but consider looking at the Halium project? https://halium.org/ > > > > > > This looks like another good approach. I think you...

This proot don't have GPU acceleration. GL4ES can have acceleration in proper environment but don't provide any on it's own.

I'm using old box86 build now so it can be caused by this. I need to upgrade it.

Looks like new builds are crashing much earlier. ``` 10946|SIGSEGV @0x5a66934 (???(/data/user/0/org.winehq.wine/files/armeabi-v7a/bin/box86/0x5a66934)) (x86pc=0xe72c0bfb//data/user/0/org.winehq.wine/files/armeabi-v7a/bin/../lib/wine/ntdll.so:"/data/user/0/org.winehq.wine/files/armeabi-v7a/bin/../lib/wine/ntdll.so/create_view + 1147", esp=0xe6c3ea90), for accessing 0x241a2ab1 (code=2) ``` @io12 If you would have time, could you help...

Ok, I tried to compile it with drm.h and now I have issue with drm_mode.h. I have day off tommorow, so I'll compile headers and try to resolve all issues...

Could you post logs form compilation as txt? I'm not a coder, but was able to fix code couple of times with assistance of Google (i.e. SwiftShader compilation on armhf).

Small thing I found out meanwhile. Safetensors yaml file is saved without EMA `use_ema: false` Can lack of ema be cause of this issue?

What about loading glibc GL libs directly with termux-gfx-wrapper glibc build directly in chroot/proot?

Some phones have Mesa drivers working fine with Android kernel, in this case it could work without dealing with bionic and glibc incompatibility.

To use termux-gfx-wrapper WSI as devices don't have access to any Linux ones and software debug version is slow. Keep in mind that I'm just droping this idea here, not...