My partner has a Pixel 3 which I've just seen is no longer supported for Graphene. She did an OTA update the other day and is now having problems with charging a booting. Is that likely to be from the update or is it likely to be a hardware issue? If the latter we can get it repaired and bang another OS on there but I couldn't find a thread detailing what happens to P3's as a result of obseletion. Thanks!

    BozLotyer I'm sorry to hear your partner is having trouble with a GrapheneOS device. If people here can provide advice I suspect more details will be necessary. What is going wrong with charging? What is displayed when booting doesn't work? There wasn't a GrapheneOS update designed to break old devices.

      BozLotyer the outcome of a device being unsupported is that it no longer receive OS and security updates from the OEM. Thus, they are increasingly at risk for compromise and instability.

      Some other Android projects continue to partially support outdated devices. This support is only partial because they have no way to provide proper, complete updates. They can and do provide some of the newer OS features and security patches from AOSP. However, they cannot provide the proprietary (e.g., firmware) security patches that vendors and OEMs no longer offer. In other words, they can typically port the AOSP stuff but they cannot port the no longer provided, non-existent OEM-specific code.

      A recent, notable example is the modem RCE affecting Exynos chipsets and some Pixel models. Unsupported devices will not be receiving a patch for this from OEMs. Other projects may provide the AOSP updates from March 2023 but they won't be able to provide the OEM-specific firmware patch. So, you may receive a false sense of security, "I have the March 2023 updates" when the reality is that you only have a partial March 2023 update. Then compound this every month that the device is unsupported and other high risk vulnerabilities are not patched.

      I also recommend that you read the project FAQ on legacy devices.

          guser39 thanks a lot for the answer. I had imagined that to be the case but Ihad misunderstood her and thought the phone had done an OTA update just before it stopped working (which of course it didn't). It must be a battery/charge circuitry issue since the thing is dead as a brick now.