GrapheneOS has has many more feature that AOSP/LineageOS lack (https://grapheneos.org/features) and also 0 google connections unlike LineageOS (https://grapheneos.org/faq#default-connections)
>some of graphene's touted features are geared towards being able to use google's services
and they are 100% optional and opt-in by default
For example years ago I opened an issue around runtime-patching applications (https://github.com/GrapheneOS/os-issue-tracker/issues/284) and was told it didn't make sense in the OS.
Putting aside the validity of arguments on either side of that issue, runtime patching allows me to very quickly excise large swaths of anti-privacy code across every app on my phone.
If I was to switch to GrapheneOS I'd have to accept that I'd be giving up a fair amount of privacy for the added security.
How about GrapheneOS connections?
Zero or non-zero?
"By default, GrapheneOS only makes remote connections to GrapheneOS services and the network provided DNS resolvers. There aren't any analytics/telemetry in GrapheneOS. The only information revealed to the GrapheneOS servers are the generic device model (such as Pixel 7 Pro) and OS version which are necessary for obtaining updates. The default connections provide the OS and apps with updates, set the system clock, check each network connection for internet connectivity, download a global database (does not vary based on location) with predicted satellite locations when using Location and obtain attestation chain signing keys for the hardware keystore needed for the hardware-based attestation feature."