Halfway through he describes this as malicious compliance with the “right to repair” law. Apple and others are making a mockery of the law.

    • partofthevoice@lemmy.zip
      link
      fedilink
      English
      arrow-up
      12
      ·
      16 hours ago

      Yes, that one exactly. Good call out, but let’s be honest. There’s a big difference between Android and the Linux we know and love. It’s not about using the Linux kernel. There is no widespread, polished, supported mobile Linux distribution comparable to iOS or Android in reach (at least nothing functional for use as a phone). GNU/Linux distros on phones would be a warm welcome.

      • u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        7
        ·
        14 hours ago

        Biggest issue is whatever is going on with mobile devices compared to desktop. I don’t know what you call it here, drivers? But each device is just so closed down, you can’t “just run” another software on it. I imagine if desktops also each required custom images based on model, people would only be using unmodified pre-installed Windows.

        • ApertureUA@lemmy.today
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          3 hours ago

          Oh, see, unlike on x86 where you have the ACPI to detect hardware with minimal device quirks (still a lot of them), everything else doesn’t have that. Well, except some Qualcomm chips, but their implementation sucks and basically only works reasonably with Windows and Windows Phone. So you need a device tree blob (DTB) to tell the kernel where everything is. But enabling all of the drivers in a single kernel build makes it not fit (the partition for that is traditionally quite tight), so you make different kernels per device.

          AND, on Android in particular, lots of features need device specific configuration for all of the small stuff like the proximity sensor and the cameras (a LOT more complex than webcams). This + the need for OEMs to insert their own spyware and the already existing tradition at the time to make device specific images made the decision stick around. There’s GSI, which basically forces the OEM to write drivers and all of that with a stable-ish API to make universal images possible, but it results in a system with lots of tiny inexplicable problems that slowly make you loose your sanity in my experience.

          How postmarketOS handles it is that there are basically meta packages per device that depend on the kernel package appropriate to the device (sometimes for a whole platform or SoC, having multiple DTBs inside for each device) that flashes itself to the appropriate partition via a post installation hook, as well as all of the config files for apps that need device specific stuff and don’t already have it upstream (like camera apps).