Topics

Wow, that was a fantastic explanation...I know explanations like the above take time, thanks! no offence taken...I know I don't know much, but I enjoy learning technical things.

No, I think you got me wrong. No offence but, like many, you do not seem to understand what "Linux" really is. Do not worry, you are not alone in this. Especially people with many years of experience in running Linux on x32/64 servers or workstations often make wrong assumptions when it comes to embedded systems, like phones. Android does use a real Linux kernel, and thus is a true Linux system. You can grab its kernel source from kernel.org, configure it to you liking and create your own custom ROMs based on it. The only limitation is that you practically can only run the single major kernel version (e.g. 4.19.xxx) your phone was shipped with. The profane reason for this is that all those drivers the phone's functions rely on are typically available only in binary form (as *.ko "kernel objects") from the vendor, and will only run together with the one kernel version they were compiled with. There is the purpose of "mainlining": reverse-engineer the driver code so it can be included in the living Linux source tree. Unfortunately that is a tedious process. But if we had the source code of all drivers, Android would be a completely open Linux system. When you say you want to run "plain old linux", what you really mean is you want to run a "GNU system with a Linux kernel". Before the advent of embedded systems, the "Linux" vs. "GNU/Linux" thing was often seen as a purely philosophical debate. If you are willing to learn, Android can teach you a lot in this respect: While running on the Linux kernel, Android is not a GNU/Linux operating system. This is possible because the difference between a "Linux" and "GNU/Linux" system does not lie in the kernel, but in the C-library! The latter is as important a component of any UNIX system than the kernel itself, and the designers of Android decided not to rely on the GNU C library (glibc) -- as used in all those PC/server Linux distros you are used  to -- but to develop their own C-library: bionic. Almost all of those "Android is not real Linux" arguments collapse to nothingness once you understand that technical background. Now, you and many others (myself included) have been looking for ways how to run a GNU/Linux-like environment  on their Bionic/Linux phones. That is where all those "Linux-like" alternative OSes (UB Touch, Sailfish, Droidian) come from. All those systems implement a middleware layer (libhybris) in-between their GNU userspace and the vendor-supplied Bionic/Linux base system. That middleware translates system calls from glibc to bionic so you can run all that open-source software we know and love. In my personal view, those systems do qualify as true GNU/Linux systems, even if relying on a vendor-supplied Bionic/Linux system (Android) underneath. My above comments about sustainability of course still hold. 

Honestly with how this device turns out. I am no where near the idea of using this as a phone. My original goal was to have primarily a pocket computer that just happens to be able to make calls and text. Now, my only use for it is a pocket computer. I only care about the keyboard, screen, and speakers really. I won't be using the camera much as my real phone has a way better one anyway. Fingerprint would be nice, but definitely can do without. I would love to be able to run plain old linux on it (I am seeing that my understanding was correct, that "mainline" linux is just that).

These issues seem to be *mostly* solved with latest updates - I've been trying for 2 days now to replicate the random C2D issues and so far have been unable to replicate it anymore. I was able to pull a crash log from android shortly after it happened again about 10 days ago. I don't know in what way it would be useful, but it's there at least. Now I just need to figure out how to properly get SafetyNet stuff configured so I can try migrating again. I tried ih8sn but that seems to be unsuccessful.

Droidian, like all functional alternative OS's for the Pro1X (Ubuntu, Sailfish, Droidian), works by specifically not using the "mainline" (i.e. upstream) Linux kernel. Under the hood, they all run a minimal version of Android 11, including its original (downstream) kernel version and closed-source driver binaries. That hidden Android OS is then interfaced from the GNU userspace via middleware layers like Halium and libhybris. While this technically works well, it also means that critical bugs in the driver blobs are present in these OS's just as if you were running the original Android 11 OS that came with the phone. Using outdated binary driver blobs in more recent kernel versions is not and will never be possible. That's due to first principles of Linux's architecture. Mainlining is thus the only sustainable way for a hardware to be supported in the long run. Kudos to @Danct12 for their effort.