Earlier quoted context omitted.
>If you are a tinkerer or prefer to install your custom OS, then you'd choose a "foss" device like the pinephone, librem or other. Except the hardware and ecosystem of those suck in comparison to The Big 2 (iPhone and Android). If I could install a custom OS on iPhone, I'd buy one in a heartbeat. Otherwise I'm stuck with AOSP on my Pixel.
Not having to run Android makes up for the mediocre hardware on the Pinephone IMO. Also Linux has a far more healthy ecosystem than Android.
Oneplus GPL violation for Android 12 Kernel
61–66 of 66 posts
Re: Oneplus GPL violation for Android 12 Kernel
#62Earlier quoted context omitted.
Not having to run Android makes up for the mediocre hardware on the Pinephone IMO. Also Linux has a far more healthy ecosystem than Android.
Android/Linux is Linux. You must be confusing "Linux" with Systemd/Linux.
The Android userspace is actual garbage. It's very heavy and the UI paradigm means you're sitting staring at blank screens while you wait for things to load or switch or whatever and things are constantly getting evicted from memory and forced to restart (or crash sometimes.) It made some dubious amount of sense when phones had 512mb of ram but once you hit 1Gb it just became this over complicated mess that adds nothing but pain.
Android's app ecosystem isn't much better, it's mostly converging with iOS as a tool for corporations to deploy their telemetry into your life rather than a platform for running useful community maintained software. Because of this most of the useful software projects for it are slowly dying if they're not already dead.
Re: Oneplus GPL violation for Android 12 Kernel
#63Earlier quoted context omitted.
Not having to run Android makes up for the mediocre hardware on the Pinephone IMO. Also Linux has a far more healthy ecosystem than Android.
Android/Linux is Linux. You must be confusing "Linux" with Systemd/Linux.
Re: Oneplus GPL violation for Android 12 Kernel
#64Earlier quoted context omitted.
Android/Linux is Linux. You must be confusing "Linux" with Systemd/Linux.
Yeah I mean GNU/X11/Linux obviously. I don't always want to write it out because most people know what I mean. The Android userspace is actual garbage. It's very heavy and the UI paradigm means you're sitting staring at blank screens while you wait for things to load or switch or whatever and things are constantly getting evicted from memory and forced to restart (or crash sometimes.) It made some dubious amount of s…
Compared to your average desktop computer, Android at least tries to use SELinux, and by-app unix user partitions. Systemd/Linux "Flatpak app" and "snap app" security by comparison is awful.
I think that Termux, (once you get past Zygote forking) to be reasonably fast and responsive, and it runs on almost barebones Android/Linux fine. So I don't think it's fundamentally related to the Android userspace platform as well.
> Android's app ecosystem isn't much better, it's mostly converging with iOS as a tool for corporations to deploy their telemetry into your life rather than a platform for running useful community maintained software.
I think we all need more libre software in our lives. Or at the bare minimum, more things like F-Droid; not ideal since the base OS is still somewhat locked, but a start.
Re: Oneplus GPL violation for Android 12 Kernel
#65Earlier quoted context omitted.
The binary blobs question has never really been resolved. You'll find kernel devs and other open source community members on both sides of the issue. My sense is that most have no interest in forcing the issue. The closest (something similar) came to being forced was the VMware ESX-related GPL case but that ended up dismissed for unrelated reasons.
This is not the “binary blobs” issue (which is still debated, as you say). This is the “binary kernel modules” issue, which is pretty much settled: Even though they are commonly used and distributed, the kernel can never explicitly allow it! This is what would happen if they did: https://lwn.net/Articles/162686/
Re: Oneplus GPL violation for Android 12 Kernel
#66Earlier quoted context omitted.
This is not the “binary blobs” issue (which is still debated, as you say). This is the “binary kernel modules” issue, which is pretty much settled: Even though they are commonly used and distributed, the kernel can never explicitly allow it! This is what would happen if they did: https://lwn.net/Articles/162686/
What's the situation now? Did kernel developers revert their decision?