4 ms·

> Google trying new tactics to move Android from open-source to "source available, lol"? It seems to be the opposite - more of AOSP internal development moving

> Google trying new tactics to move Android from open-source to "source available, lol"? It seems to be the opposite - more of AOSP internal development moving out into the open. QPR's are getting more frequent releases than the old AOSP code-drops. (Tbh I do think that AOSP has always had way too much churn for a sensible system. A Linux phone should just work, and share as much of its codebase as possible with Linux systems running on other device classes; distributions like pmOS and Mobian - and quite possibly Debian Mobile in the future - are working towards this goal.)

throw5959 2y ago
Android is not "a Linux phone", it just happens to use Linux kernel under the hood. What you're saying was always an explicit anti-goal.
- surajrmal 2y ago
  This is gatekeeping. Linux is a kernel. You're talking about userspace which is not part of the Linux kernel project.
  - throw5959 2y ago
    What gatekeeping? I'm talking about Android project goals. They never intended to provide any direct userspace access to the Linux kernel. The Linux kernel is supposed to be an implementation detail that can be replaced without breaking app compatibility.
    - surajrmal 2y ago
      That is more of a theory than reality. In practice you need to emulate the Linux kernel in order to run Android. Keep in mind that Android is more than just the apps you run.
      - throw5959 2y ago
        Yes, I agree. But it is the stated goal.
gf000 2y ago
Or maybe the Linux Desktop (used by a couple of people) should use more code from the android project (which is the biggest OS on the Earth) The latter has sane sandboxing, proper IPC, an app lifecycle that makes sense for embedded devices (an app in the background should only ever take CPU time if it has an explicit service with permission for that) etc.
- zozbot234 2y ago
  Plain old Linux has these features. For example: > an app in the background should only ever take CPU time if it has an explicit service with permission for that You can run your services in a cgroup and use "freeze" and "thaw" support for that purpose.
  - gf000 2y ago
    It doesn't have it, because this is like security. You either have it everywhere, or it doesn't matter. Sure, the Linux kernel is very capable, but the "gnu" userspace doesn't make good use of its features. Android makes much better use and has a bunch of software that could be re-used on the former as well.
    - ykonstant 2y ago
      Is the reason GNU doesn't use these kernel features aggressively that they want to be portable? Or something else?
      - zozbot234 2y ago
        Freezing background apps just isn't needed all that much if you run a fully FLOSS system. It's much more of a concern for proprietary software where you don't have the source code available. There's a similar story for sandboxing actually, it's not a coincidence that it's been getting more popular as proprietary apps have been made widely available via Flathub and the like.
        2y ago

throw5959 2y ago

Android is not "a Linux phone", it just happens to use Linux kernel under the hood. What you're saying was always an explicit anti-goal.

surajrmal 2y ago
This is gatekeeping. Linux is a kernel. You're talking about userspace which is not part of the Linux kernel project.
- throw5959 2y ago
  What gatekeeping? I'm talking about Android project goals. They never intended to provide any direct userspace access to the Linux kernel. The Linux kernel is supposed to be an implementation detail that can be replaced without breaking app compatibility.
  - surajrmal 2y ago
    That is more of a theory than reality. In practice you need to emulate the Linux kernel in order to run Android. Keep in mind that Android is more than just the apps you run.
    - throw5959 2y ago
      Yes, I agree. But it is the stated goal.

gf000 2y ago

Or maybe the Linux Desktop (used by a couple of people) should use more code from the android project (which is the biggest OS on the Earth) The latter has sane sandboxing, proper IPC, an app lifecycle that makes sense for embedded devices (an app in the background should only ever take CPU time if it has an explicit service with permission for that) etc.

zozbot234 2y ago
Plain old Linux has these features. For example: > an app in the background should only ever take CPU time if it has an explicit service with permission for that You can run your services in a cgroup and use "freeze" and "thaw" support for that purpose.
- gf000 2y ago
  It doesn't have it, because this is like security. You either have it everywhere, or it doesn't matter. Sure, the Linux kernel is very capable, but the "gnu" userspace doesn't make good use of its features. Android makes much better use and has a bunch of software that could be re-used on the former as well.
  - ykonstant 2y ago
    Is the reason GNU doesn't use these kernel features aggressively that they want to be portable? Or something else?
    - zozbot234 2y ago
      Freezing background apps just isn't needed all that much if you run a fully FLOSS system. It's much more of a concern for proprietary software where you don't have the source code available. There's a similar story for sandboxing actually, it's not a coincidence that it's been getting more popular as proprietary apps have been made widely available via Flathub and the like.
      - 2y ago