I feel like what you are saying is on the same level as installing Termux on a rooted Android phone. There might be some quirks of GrapheneOS I am unaware of though.
IMO orphan kernels are not Linux. If it can’t update with mainline, it is a sterile mule. So no, even as an avid user of Graphene, it is not Linux because google has stollen ownership with an orphaned kernel using proprietary and publicly undocumented hardware.
In this vain, no mobile chipset or radio modem has been FOSS or Linux in a very very long time if ever. Like the last radio that was fully documented was the Atheros stuff, and the last processor to come close to fully documented is the stuff Leah Rowe supports in Libreboot and that is only because of her hacking skills.
I don’t think it’s really relevant then. The argument is more about wanting a traditional Linux experience on mobile phones and Android operating systems (including GrapheneOS) being too far removed from that. Breaking away from Google is more of a possible positive byproduct
Other people have mentioned the limitations of the hardware so I won’t bother rehashing it but I do think there is a lot of potential in a Linux distro for phones.
Right now Linux phones are incredibly niche but we have seen some improvements in software around the release of the PinePhone and the Pro model so I have hope that it will, eventually, work. SailfishOS is a paid OS and is a fairly limited but it does feel quite smooth to daily drive on supported devices. Simple frequent tasks (ex. Finding public transit routes to a coffee shop) do seem to take longer to complete on Linux phones but I am hoping that will be sorted in the next couple years.
It’s just hardened Android, but it still uses the Android kernel, Bionic C Library, etc. They have a custom memory allocator which was based on a port from OpenBSD though.
*Laughs in Graphene *
Is GrapheneOS that much more like Linux?
I feel like what you are saying is on the same level as installing Termux on a rooted Android phone. There might be some quirks of GrapheneOS I am unaware of though.
IMO orphan kernels are not Linux. If it can’t update with mainline, it is a sterile mule. So no, even as an avid user of Graphene, it is not Linux because google has stollen ownership with an orphaned kernel using proprietary and publicly undocumented hardware.
In this vain, no mobile chipset or radio modem has been FOSS or Linux in a very very long time if ever. Like the last radio that was fully documented was the Atheros stuff, and the last processor to come close to fully documented is the stuff Leah Rowe supports in Libreboot and that is only because of her hacking skills.
It’s more that it’s de-googled.
I wouldn’t describe it as Linux, per se, but it is de-googled
I don’t think it’s really relevant then. The argument is more about wanting a traditional Linux experience on mobile phones and Android operating systems (including GrapheneOS) being too far removed from that. Breaking away from Google is more of a possible positive byproduct
Yeah, I don’t think that’s ever really going to work.
As similar as the hardware is, the reality is they’re different interface. One of the things that made windows 8 awful was trying to do both.
Other people have mentioned the limitations of the hardware so I won’t bother rehashing it but I do think there is a lot of potential in a Linux distro for phones.
Right now Linux phones are incredibly niche but we have seen some improvements in software around the release of the PinePhone and the Pro model so I have hope that it will, eventually, work. SailfishOS is a paid OS and is a fairly limited but it does feel quite smooth to daily drive on supported devices. Simple frequent tasks (ex. Finding public transit routes to a coffee shop) do seem to take longer to complete on Linux phones but I am hoping that will be sorted in the next couple years.
It’s just hardened Android, but it still uses the Android kernel, Bionic C Library, etc. They have a custom memory allocator which was based on a port from OpenBSD though.