I agree. As it stands, there is no immediate problem with buying a vendor unlockable phone for LineageOS or GrapheneOS. It does seem like Google is slowly closing the doors to FOSS, so the future could require an AOSP fork. But it also might not. We don't really know for sure. As long as LineageOS and GrapheneOS exist and have developers, we have nothing to sorry about.
If, in the future, all hardware manufacturers fail us, I have used Waydroid on an old Thinkpad, and it is fantastic. And, more in the Linux ecosystem is Android Translation Layer which translates Android syscalls into Linux syscalls. It is buggy, but I could see it getting better in the future.
Anyway, I'm not really worried. There are still a lot of paths forward, and FOSS advocates are persistent.
I would love to use it, but I've had some issues with getting it working with Termux. The author provides some builds that have the same signatures as Termux, along with instructions on setting up early-init.el here: https://sourceforge.net/projects/android-ports-for-gnu-emacs/ which I thought should resolve any issues. However, I've encounter issues with permissions and with interpreting certain paths (/usr/bin, /etc/ /usr/lib) which makes some features which execute commands fail on Emacs. I also get annoying warnings spamming the console like WARNING: linker: normalize_path - invalid input: "nil", the input path should be absolute. I'm kind of waiting until someone has a better solution for Termux integration.
I agree. As it stands, there is no immediate problem with buying a vendor unlockable phone for LineageOS or GrapheneOS. It does seem like Google is slowly closing the doors to FOSS, so the future could require an AOSP fork. But it also might not. We don't really know for sure. As long as LineageOS and GrapheneOS exist and have developers, we have nothing to sorry about.
If, in the future, all hardware manufacturers fail us, I have used Waydroid on an old Thinkpad, and it is fantastic. And, more in the Linux ecosystem is Android Translation Layer which translates Android syscalls into Linux syscalls. It is buggy, but I could see it getting better in the future.
Anyway, I'm not really worried. There are still a lot of paths forward, and FOSS advocates are persistent.