So lets turn back the clock a bit.
https://forums.mangadex.org/threads/in-your-opinion-what-hacked-modded-consoles-bring-the-most-value.2433901/#post-27884284
Yeah... long story short, old 4.14.193 kernel gave me issues:
- missing namespaces to run a container
- no mesa panfrost kernels
- no tty
- no vt
- no userspace binary's for linux given for my specific arm gpu revision
Only
one other kernel allowed the device to at least boot to telnet stopped working when I tried it again. So no other kernel worked so I'm stuck with that one. Sway, wlroots didn't work because of no vt/tty. X org never took control of the drm and removed the logo to take control of the screen. Weston didn't load anything to the screen (removed logo though!) because apparently the drm wouldn't take the "bytes by pixel". Libhybris didn't work because the device uses gralloc4 while libhybris uses gralloc1/gralloc2. But in
Debian modetest works but panfrost would simply freeze on screen not rotating, killing my hopes.
Mir-android-platform for fossa (20.04) would not load no matter WHAT I did. I would keep getting a boost error when trying to launch miral no matter what.
But wait, back to canonical. Their android platform is stuck to that version and I decided to try a newer version of mir to load to the drm for software rendering. WORKED via gbm with the drm. But software rendering sucks. Running glxgears jumps between 45fps to like 58fps on a 64 Mhz screen device, with heavy delays according to the strace logs and my damn eyes. Need more gpu. I looked back into termux and searched on how people got
hardware acceleration. Mir refuses to take any mesa variables (Canonical uses their "own" version of mesa in a closed source system". Found termux's virglrenderer that doesn't require any termux packages, thus can be ran run
outside of termux in android's environment without android loaded (But you have to mount android paths in recovery to their expected paths, so bind mount it in recovery). Then in whatever distro you choose (I'm alpined focused atm) you have to build mesa with virtro, virpipe and venus. Then launch applications (the whole gl, wayland, vulkan convo is exhausting) by focusing variables like GALLIUM_DRIVER to virpipe after ensuring that everything is bind mounted into the chroot. I ran with a small script using those variables via xterm has it using only gpu rendering on a 3.4 GB RAM device using less than than 700 MB of ram (Android is loaded on ram root=/dev/ram0).
Fucking worked dammit.
Why I did that? Because on normal android it occupies 1.8 GB out of 3.8 GB. I'm assuming I can set it up fine and use less than 1.23 GB of ram, I think.
So I somehow now have a mini guide that I need to clean up and post on youtube to possibly teach people that if your android phone can be flashed to factory when you connect to a PC with firmware you have access to (.img files for example), you can make recovery mode (not the flash to stock button) load linux with gpu hardware acceleration. But first, I need to fix the controller inputs so that they appear properly and start testing some pc games with wine with drastically more ram compared to trying in android with winlator. But yeah,
long time coming.
