> what is the remaining work I would need to have done in order to get it working under A good chunk of the Linux community on phones didn't want to have to re

> what is the remaining work I would need to have done in order to get it working under A good chunk of the Linux community on phones didn't want to have to rely on binary drivers for non-technical reasons, and that's one of the reasons why it isn't exactly well taken care of today. For Ubuntu Touch specifically: https://docs.ubports.com/en/latest/porting/introduction/Intro.html https://docs.ubports.com/en/latest/porting/introduction/Intr... for Ubuntu Touch. https://github.com/ubports/porting-notes/wiki/Generic-System-image-(GSI) https://github.com/ubports/porting-notes/wiki/Generic-System... An upgraded Halium (https://github.com/Halium https://github.com/Halium) image on a can work unmodified across the whole ecosystem of Android devices. However, the latest currently developed experimental Halium works on an Android 11 base at most, so that devices launched with Android 12 might be using drivers too new for it at this point in time. (https://gitlab.com/ubports/community-ports/jenkins-ci/generic_arm64/-/pipelines https://gitlab.com/ubports/community-ports/jenkins-ci/generi...) This can be fixed with an engineering effort to do so to make it work on devices launched with Android 12. The Linux on phones community is very small and that causes problems in this case. Together with the unified kernel image (GKIs) on Android 12 which allows to have kernel image binaries built with GNU/Linux-specific features that work across the whole fleet, a full straightforward experience can be made possible. This would fill the last chunk of custom per-device bits. I wonder how big the audience would be for such a project though. :)