In between been called out this weekend I’ve been playing with my #Fairphone4 which has #Calyxos and #MicroG . I’ve know about #Obtainium for a while but never thought I’d install it until now. Guess who loves it and I get new releases of apps before #Fdroid . I also ditched calyxos default launcher for #NiagraLauncher and I’m really loving the work flow. Even bought the full version and installed the apk with Obtanium. It maybe doesn’t look much but I like it. 😍
#Android

https://github.com/8bitPit/Niagara-Issues?tab=readme-ov-file

  • GrapheneOS@grapheneos.social
    1·
    1 month ago

    @[email protected] @[email protected] Fairphone devices have very poor security and don’t meet our security requirements. They lack very basic security patches and features. Fairphones lag at least 1-2 months behind in applying the partial Android security backports and around a year for shipping the full patches. Even in the recent Fairphone 5, the SoC has CPU cores from 2021 and lacks security features like PAC and MTE. Fairphone doesn’t set up the standard SoC security features. FP4 lacked working verified boot.

    • GrapheneOS@grapheneos.social
      1·
      1 month ago

      @[email protected] @[email protected] Our hardware security requirements are listed at https://grapheneos.org/faq#future-devices. GrapheneOS uses more hardware-based security features than the stock Pixel OS such as heavily using hardware memory tagging (MTE), much more heavily using pointer authentication (PAC), using hardware-based disabling of the USB-C port by default when locked (not software-based like AOSP, LineageOS and CalyxOS where most attack surface remains) and hardware-based attestation using pinning for Auditor.

      • GrapheneOS@grapheneos.social
        0·
        1 month ago

        @sleepybisexual @doerk @justine It still uses older ARMv8.2 cores similar to the Pixel 5 and earlier without support for pointer authentication or branch target identification. It’s also missing hardware memory tagging but that’s also the case for current era Snapdragon CPU. The older cores are also missing current era hardware-level side channel mitigations. Additionally, since it’s already quite old, it’s nearing the end of regular Qualcomm support and will only getting very reduced support.

        • GrapheneOS@grapheneos.social
          1·
          1 month ago

          @[email protected] @[email protected] @[email protected] Fairphone chose to use an industrial-oriented SoC rather than a regular smartphone SoC because it receives cheaper long term support, but it’s not the same as the long term support provided for a current era smartphone SoC. Samsung is paying Qualcomm for 7 years of full support for their devices now. It wasn’t necessary to use an industrial SoC with older CPU cores for long term support, it was cheaper. FP5 is priced as if it’s got a current high end SoC though.

          • GrapheneOS@grapheneos.social
            1·
            1 month ago

            @[email protected] @[email protected] @[email protected]

            Fairphone skips the monthly/quarterly releases entirely and has a 1 year delay for the yearly updates for their new devices which gets longer. SoC choice will make this worse. Worth noting the monthly, quarterly and yearly releases need to be shipped for full privacy/security patches and Fairphone ships the partial backports 1-2 months late instead.

            • GrapheneOS@grapheneos.social
              1·
              1 month ago

              @[email protected] @[email protected] @[email protected]

              There’s also no performance core included in the SoC they’re using since it’s not meant to be for a user-facing device requiring great performance. It has the 2021 era big and little cores. Cortex X1 was the standard pre-ARMv9 performance core.

              Sustainability should include long term support providing all standard updates instead of what they’re doing and also good performance at launch so that it’s tolerable in 5-7 years. An iPhone or Pixel has far better LTS.