- cross-posted to:
- android@fedia.io
- cross-posted to:
- android@fedia.io
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
@doerk @GrapheneOS No I don’t tbh all I can say is I love it and the support from the calyxos devs is 1st class. I only have microg so I can run my UK banking apps otherwise I’d drop that too. As for my FP4 I have loved it from day one.
@justine@bsd.cafe @doerk@nrw.social 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.
@justine@bsd.cafe @doerk@nrw.social 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.