• shrugs@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    28 days ago

    Pixel 4a (5G), Pixel 5 and Pixel 5a are end-of-life and shouldn’t be used anymore due to lack of security patches for firmware and drivers. We provide extended support for harm reduction.

    So do I get this update because they are providing extended support or won’t I get android 15 based graphene os on my Pixel 5?

    • GrapheneOS@grapheneos.socialOP
      link
      fedilink
      arrow-up
      3
      ·
      27 days ago

      @shrugs@lemmy.world It won’t be ported to Android 15 because it would require a lot of our resources while creating a lot of regressions for Pixel 5 users. It would take a long time for it to become stable with Android 15 since it has no official support for it and would need a bunch of hacks to make it work. We’d need to switch to using a prebuilt vendor.img built from Android 14 QPR3 and combine that with Android 15. It’d theoretically work but in practice lots of bugs and lots of work.

      • GrapheneOS@grapheneos.socialOP
        link
        fedilink
        arrow-up
        2
        ·
        27 days ago

        @shrugs@lemmy.world Pixel 5 has been end-of-life since December 2023 after the last update in November 2023. It hasn’t received driver and firmware updates since then. We provided what we could with very limited resources available for insecure devices via the Pixel 5a still being supported, but the Pixel 4a (5G) and Pixel 5 had significant regressions with each quarterly release we had to work around. A15 would cause enormous problems and we don’t need to port it to 15 to keep it working for another year.

        • shrugs@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          26 days ago

          Damn, this phone looks and works as good as new. Sucks that it can’t be updated any longer. I hate it so fucking much that they (google) managed to make the hardware closed source enough, so that we can’t keep it running after the manufacturer dropped support. Anyway, i know that’s not your fault.

          Thanks for the reply and thanks for all the work to make android a little bit safer for all of us.

          • GrapheneOS@grapheneos.socialOP
            link
            fedilink
            arrow-up
            1
            ·
            26 days ago

            @shrugs@lemmy.world It has nothing to do with Pixels specifically and applies to all other hardware whether or not it runs Android. There are no devices where we wouldn’t need ongoing support for firmware updates and development of the drivers and other device support code.

            • shrugs@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              26 days ago

              So then open source drivers and firmware should be mandatory. It’s insane that this fully working phone isn’t usable any longer just because the manufacturer wants to sell new stuff. They should at least open source the drivers or firmware if they stop supporting it. What a humongous waste of resources.

              I know this is the same for all devices. Microsoft is killing old PCs without TPM to push Windows 11. You can still use linux on those devices though, android seems to be way more short lived.

              • GrapheneOS@grapheneos.socialOP
                link
                fedilink
                arrow-up
                1
                ·
                26 days ago

                @shrugs@lemmy.world It would still be end-of-life from lack of development or releases for the firmware and drivers even if it was fully open source. It wouldn’t be possible for us to take over development of everything and we don’t receive the security issue reports for it. Additionally, building firmware updates requires the signing keys for that and we don’t have those so having the sources doesn’t allow us to build firmware updates in general. The signing is important for security for a lot of firmware.