1. 21
  1.  

  2. 16

    weirdly, this could be a boon for F-Droid and apps that don’t rely on the GOOG subsystems.

    1. 3

      My LineageOS 14.1 powered phone from some Chinese brand known for well-made durable laptops is running Magisk and says it’s “Certified” and it will probably be certified for next 100 years. And I didn’t even needed hex-patching the binary, casting magical spells or summoning demos for that.

      I can’t see your problem :)

      1. 2

        If you don’t mind me asking, what phone are you using? I’m using a Motorola G5s+ with an unofficial rom, but it’s a PITA to build and maintain.

        1. 2

          Lenovo P2.

      2. 1

        I was curious what impact this might have on the microg open source Google framework reimplementation. But they don’t seem too bothered: https://github.com/microg/android_packages_apps_GmsCore/issues/510

        1. 1

          Can anyone explain in layman terms how Google can take the GPL license Linux kernel , build some stuff on top of it and have those to be proprietary ? How does this work ? How can the stuff built on top be proprietary ?

          1. 14

            It’s the same thing as building proprietary software that runs on linux. GPL means that google has to release any changes it makes to the linux kernel under GPL as well. Software that just runs on top of Linux/Android can be proprietary.

            1. 2

              It’s basically due to using the “Android” name, which is copyrighted, and having the Google apps (Maps, Play Store, etc) pre-installed. Forking Android and calling it something else is just fine.