Comment on Breaking: Google is easing up on Android's new sideloading restrictions!
GreyEyedGhost@lemmy.ca 1 day agoSo the question becomes when, not if, a Linux phone reaches parity with AOSP-based phones.
Comment on Breaking: Google is easing up on Android's new sideloading restrictions!
GreyEyedGhost@lemmy.ca 1 day agoSo the question becomes when, not if, a Linux phone reaches parity with AOSP-based phones.
Fmstrat@lemmy.world 1 day ago
Android basically is a Linux phone, it’s a distro(ish).
It has a Linux kernel and a Linux-based OS wrapped around it. And just like you can compile FreeCAD for Debian or Arch, you can compile Fossify for Google Android, GrapheneOS, or LineageOS.
“Linux” phones in the sense you mean won’t be a “Debian” or “Arch”, they’ll be something else, just like Android.
GreyEyedGhost@lemmy.ca 19 hours ago
Can I compile FreeCAD for Android? Can I run Linux apps that are compiled for ARM on Android? As far as I know, no. So it’s even less Linux than MacOS is BSD, and how is that helping for software freedom, or placing the control of the phone you bought in your hands?
Fmstrat@lemmy.world 13 hours ago
Huh?
Control of your phone does not equal Linux. Plenty of FOSS OS’s do that (including Android). And Android 16 brought Linux app support with GPU acceleration if you’re into that and want FreeCAD on your phone.
GreyEyedGhost@lemmy.ca 12 hours ago
Android isn’t FOSS, AOSP is. If you keep conflating that, I’m not sure what you’re getting at. And having a sandbox or VM that allows you to run Linux apps is not the same as having native support. That would be like saying Windows had Linux support 20 years ago because VMWare existed.
And no, control of your phone doesn’t equal Linux, but native support for a FOSS OS at the base level means that if the maintainers decide to go in a different direction, you can more easily part ways with them. AOSP used to be a more complete version of Android, but that has been clawed back repeatedly as Google transfers functionality to Google Play services and elsewhere, which has caused difficulties for LineageOS and GrapheneOS to be maintained over the years, including Graphene exploring moving to another device for support from the one line of devices they support now.
Clearly, this isn’t solely the fault of Android and Google, hardware vendors bear a lot of blame, as well as their desire to exert more control over their customers. But Google and Android have the exact same issue and certainly won’t be pressuring hardware vendors to open up their standards.