I’d argue that Graphene is a better thing since it’s based on an OS that’s been designed for mobile from the ground up. I expect it’s going to be a while before Linux UX on mobile catches up to desktop, but Graphene works great already.
For most use cases though, you don’t really have much of a benefit of running Linux over Android on a phone though. There’s enough Linux compatibility on Android already to make it work seamlessly with your Linux devices. In my opinion, as long as the stack is open source and well supported, it doesn’t really matter whether it’s Android or Linux based.
I’d argue that Graphene is a better thing since it’s based on an OS that’s been designed for mobile from the ground up. I expect it’s going to be a while before Linux UX on mobile catches up to desktop, but Graphene works great already.
By those standards, Halium + ubports might be worth while, it’s using enough of the android binaries to get the job done but is still real linux.
For most use cases though, you don’t really have much of a benefit of running Linux over Android on a phone though. There’s enough Linux compatibility on Android already to make it work seamlessly with your Linux devices. In my opinion, as long as the stack is open source and well supported, it doesn’t really matter whether it’s Android or Linux based.
The binary blobs handling drivers are both the rub AND the part we can’t seem to work without.
reverse engineering this stuff is pretty challenging unfortunately